Dear StorjLabs and Community,
I write this message from my heart, trying to express the opinion of many. For everyone, who agrees with my message: please mark this message with heart, or write your own opinion if you do not agree.
Looks like that StorjLabs hurry too much to get in production state in January and observe the schedule, forgetting their own words about there is only one chance to do it right way. There is no second chance to build the network.
The closer to the product release, then greater the feeling that the project is raw, and not ready to launch yet. Too serious changes have been made last months, many of them are not sufficiently tested.
Perhaps the most important thing is that most SNO unable to test the network by upload and download their files. as for whom has received invites: their reviews often not very happy.
There is no chance to look at SNO’s personal escrow and other statistics, founded by satellites; compare it with own calculations (at SNO side via scripts etc…) One of the options for the node’s health (uptime) has just been removed without providing an alternative method.
We read about qualification gates, but these numbers are not available to us, they are not verified since you turned off all third-party monitoring, such as the site storjnet.info not providing anything instead.
Things like this make us worry about the success of the first launch and the project in general at this stage. It seems to us that it is worth spending a little more time on working out issues that are important from the point of view of the overall network’s operability and from the point of view of development backlog and from the point of view of testing and from our SNOs, for the implementation of must have functionality. Let us to test the project by uploading/downloading our files to the network. Collect our feedbacks. We are afraid that v3 will turn into v2.2 when the network consisted exclusively of test traffic and data, because clients data will be unavailable to download it, because of insufficient testing and feedback lack. Or dozen of new unknown yet reasons.
Personally, as a lover of computer history, saw too many failed projects, both because of rush and because of delay and over-engineering. It is important to maintain balance. Perhaps a few additional months to polish fix and testing the current solution and create missing important tools will benefit the project.