-
Paypal. Don’t wanna start the discussion again, don’t worry, but if you have reasons to share, why you decided not to accept Paypal while very similar competitor like yours (ImpossibleCloud) are happy to accept Paypal, it would be interesting to learn.
-
Website localization. Again ImpossibleCloud does that for the German market: https://de.impossiblecloud.com/. And they are a direct Storj competitor with the same product offering. It might be generally worth it to have a localized website for most important markets but with that direct competitor in place in Germany even more.
-
Node performance optimization. Is there a systematic process in place for codewise node optimization? The nodes are getting larger these days and it appears that the code is not well suited for that. Suddenly we see issues popping up with filewalkers, bloom filters and IOPS getting wasted for database transactions instead for customer data. It seems that problems are getting solved only when node operators complain that there is something not working. On the other hand we see for the customer side very clear goals (Like: Performance Tuning & Optimizations (PTO) - Improve single-threaded download performance of 1GB object to 25 seconds or better on EU1). I did not see something similar for the storagenode side ever. So this is why I am wondering if a systematic process exists that is constantly monitoring node performance and suggesting code improvements pro-actively and not waiting until something does not work as expected and a SNO complains. Or worse: Waiting until SNOs make suggestions and even code proposals because they experience bad performance of their nodes.
6 Likes