I am curious to know the thought process that goes behind changing links. What drives developers to change links ? A list of reasons would suffice. I want to learn how the logic works.
We changed where our documentarion was hosted once or twice. There was a migration process but some links.didnt carry. There can also be times that documents are updated to new versions and previous versions are removed if out of date.
I understand that and I have noticed the new change from docs.storj.io to storj.dev. In my experience when I migrated static websites to CMS it kept the links intact. Would migration always change links ? Could there be any other reasons?
Ooh what if the RS settings were selectable, so the user can pick between âdurableâ or âcheapâ.
⌠actually thatâs a terrible idea no one would pay for cloud storage with the idea of âwell you are more likely to lose your data with this one but itâs cheaperâ. Maybe options of fast vs cheap would work better.
Itâs better to not give this option to be handled by the customer. Many donât understand how things work, even though they think they do; they can use wrong settings and realise it too late. As long as these are hanlded by the Storj team, it also provides support and advises, and help the client make the best choise tailored to his needs.
I canât spare you this: For years the community has emphasized the importance of compliance and certification for customers and that it can even bring new customers. There have been numerous threads on this. For example:
There are even more threads in which you have been asked again and again on the status on this issue and you have been made aware of new opportunities in the data storage business that can come along with proper compliance and certification.
And I think one of your last answers or the last answer on this was:
Now we have to read:
While it sounds great that such a decision has been made, it appears that not much has been achieved until now in regards to the public network.
I strongly suggest not to focus on SOC2 only but also on the other certifications and compliance requirements that do exist. Wasabi has a nice overview of what they cover and that should give an idea what Storj also should seek for: What third-party compliances have been attained by Wasabi?. This seems to be sort of a minimum requirements for a successful cloud storage business.
Without the proper compliance and certification the big business will move their data to compliant competitors like this one that I have made Storj aware of over and over again.
As it seems it was just pure luck that this 10PB-customer fits into the Select network, Storj management needs to take this as a wake-up call for the public network and make 2025 the year of compliance and certification. To attract large enterprise customers and government customers, certifications of compliance are ultimately required, probably even code reviews, code audits, audits of coding practices, review and auditing of company and management processes, and more. This can take long, should have been started years ago and it is crucial to start this process now.
Finding an auditor with experience in decentralized infrastructure could be beneficial and time saving. Seal Storage Technologyâs successful SOC2 audit by Audit Peak is a good example:
I found this:
Seal Storage Technology, a leading provider of blockchain-powered cloud storage, is proud to announce the successful completion of a System and Organization Controls (SOC) 2 audit conducted by the highly respected audit firm, Audit Peak. This milestone underscores Sealâs commitment to maintaining the highest standards of data security and integrity, giving clients the confidence that their valuable data is stored with the utmost vigilance, fostering trust through transparent and reliable business practices.
As the first compliant blockchain-powered cloud storage provider, Seal recognizes the critical importance of maintaining robust data security measures. Globally, enterprises are increasingly recognizing the importance of process controls and compliance, which is why Seal made SOC2 certification a core priority. This commitment sets Seal apart as the only decentralized cloud storage provider currently certified to the stringent SOC2 standards. Sealâs dedication to upholding these rigorous data security and integrity measures underscores its pioneering role in the decentralized cloud storage field, especially in a digital landscape where data protection is paramount.
So maybe talking to Audit Peak is a starting point:
Certifications cost a lot of time, effort and most importantly: money. If you donât have a customer at your doorstep that requires it, it may not make much sense to go down that road. Better focus on the product first.
Storjâs significant investment in their product for this 10PB customer ultimately proved futile due to the lack of certification, which turned out to be a non-negotiable requirement. This experience highlights the importance of prioritizing certification alongside product development.
In reality, you canât afford to wait until a customer expresses interest in your storage solution to start the certification process. Certification is a lengthy and ongoing process that requires proactive effort. Moreover, potential customers with strict regulatory requirements will not even consider your offering, let alone contact you, if your storage solution doesnât meet their necessary standards.
Other cloud providers are doing this all day. The cheapest tier usually is just a single datacenter and you have to pay more if you want higher durability.
No need to get defensive. Nobody says youâre underworked and nobody is having a go at developers.
But clearly someone dropped a ball during the negotiating process for this customer by not considering certification requirements (the customer seems to have forgotten about it too!).
Itâs fine, no harm done. Itâs income for Storj and ultimately that is A Good Thing, but there is clearly something to be learned by this.
We are getting back into âyou should have done this years agoâ which is pointless. Everytime that comes up I have to explain again and again that we have limited resources and canât do everything at the same time. We have to prioritize. It doesnât look like performance improvements was a bad priority. Sure we could be soc2 compliant by now but at what cost? Think about all the other things we wouldnât have time for in the meantime instead of pretending there would be a magic unicorn that can get us a soc2 certificate with no additional work.
Fair comment and I understand your frustration. Iâm sure you understand ours too, though.
I do not know the makeup of the Storj team, but certification compliance doesnât seem like something that should be taking up developer time. Itâs more âlegaleseâ, therefore it is plausible that it could have been happening at the same time as the code improvements.
But surely you must concede that there is no point in fine tuning the product if customers cannot take it because of the certification requirements?
Again, these are strategic decisions that are to be made by the people âin the knowâ, but in this particular case at least it seems to have partially backfired.
So far storj select was enough to make these customers happy. This 10 PB deal was a close call but even that one is fine with storj select and we just agreed on a timeline to work on pentests and other stuff. From that point of view it has worked out.
And what you call fine tuning are big features like object lock and to make this possible we had to implement object versioning first. We are working on these 2 features for months now. The implementation is almost finished and hopefully soon this will get us more customers. Customers that we wouldnât get if we would postpone features like these just to get a soc2 certificate. Again there is no shortcut that would allow us to do both.
A potential use case for low R/S numbers is a caching CDN: it is not actually expected to durably store content on its own, because the content can be re-fetched at any time from the primary source. I can imagine this being offered by Storj, and the only net-new thing to implement to the basic operation of the storage network would be repair workers getting an ability to download data from the primary source, as opposed to just other storage nodes.
With no GET_REPAIR costs and low R/S numbers a CDN might be quite cost-efficient for Storj.