Why does Storj not accept Paypal as payment option for Storj DCS storage and are there any plans for it?
What are Storjs thoughts or plans on localization of the websites and resources to attract more customers outside of native English speaking countries?
Are there any quantifiable growth expectations or any larger customer expected to make use of Storj or at least estimates, hints or rumors?
Now even President Biden was talking about decentralization and zero trust architecture. But on Storj social media this marketing support from the White House finds no mention, or I did not see it. Twitter, Reddit and Medium appear rather sleepy or even dormant than actively used for marketing. Is that going to be changed?
Why did Paul Ford leave Storj? Why was there no announcement contrary to Storjs transparency claim? And what does it mean for the Storj product, the developer relations, marketing, community relations and the potential danger of competition with Chia (in case they might starting to use their capacity as storage, maybe even through Storjs own Open Source software)?
When will be the next Town Hall?
And a suggestion: If not everything can be answered during the Zoom, it would be great to receive the answers in this thread here.
Jocelyn was heavily involved in the forum community but since her departure that involvement doesn’t seem to have been replicated. Any plans to change that?
How much does Storj currently owe to SNO’s who have not signed up for L2 payments and haven’t met the threshold for L1?
How can Storj consider small SNO’s in any way profitable considering you need to wait up to a year for a L1 payment and L2 Exchanges are yet to exist?
Is there a plan to make Storj nodes resilient to SMR disk technology?
More generally I guess the questions is: Could the node software ensure that it automatically refuses ingress requests whenever the underlying storage system (HDD, SSD, …) cannot keep up? Is that feature considered?
Currently, if the storage system cannot keep up, the node eats up all the RAM of the system by caching data waiting to be written down, and gets killed by the system eventually. The only workaround currently is to limit the number of concurrent requests the node is authorize to process, which is a shame because that drastically limits its ability to handle bursts of requests (even SMR drives can keep up with high loads for some time before starting to stall - limiting the number of concurrent requests prevents the node from using this ability).
I love your post, great questions! But this is a stretch for sure. Chia and Storj have only one thing in common… they use HDD space. They use it for wildly different purposes though. There may be some mild competition on the supply side, but Storj is in a good position there as used space on Storj is much more valuable. Anyone doing both would be wise to remove Chia plots to make room for Storj when needed. That’s what I do at least.
I would be curious to know Pauls motivations for that career move though.
Both of these suggestions have gotten positive response from Storj Labs and a mention that “something like it will probably be implemented” but no further follow up.
This is great. Thank you for the questions. We’ll get through all that we can and if we run out of time, we’ll get a blog post out with the rest or respond here.
If this fireside chat format works well, we’ll try to work this into our regular cadence.
Thanks to everyone who attended and for the great questions. We’ll get the recording into the queue to get posted. We’ll go through the questions above and figure out what didn’t get covered and post answers as well.
The next Town Hall is scheduled for October 20 and we’ll have some Q&A around the TH, too.
@john I understand you have very limited time and huge demands but I must admit I was disappointed more questions were not addressed.
If a similar format was to be followed in future I doubt I would tune in live if most of the questions would be answered post event anyway. There would be little point to do so live.
A purpose can change. And maybe they’d become interested in using all the space they have for something other than only mining. In any case I think it is worth a second thought if a member of the leadership team of a decentralized storage provider switches to another decentralized platform that handles large amounts of disk space.
I would expect the video to be be both on Storj and other channels. To be transparent, we posted the call for questions a week in advance and ended up getting all the questions the day before the fireside chat. We prepped and organized as quickly as we could, but it was a lot of ground to cover.
I will get around to answering the remaining questions, but it will take me probably a week or two to get through it all.
We’re considering a few options for the next one of these, including an AMA style, here or in Reddit, but we’ll post a poll when we have dates and give some options. We want to continue with the Fireside Chats, but we want to make sure the format is what the community will find most valuable.
@penfold we would have liked to have made it through more questions, also, but we will get all the answers posted.
Here’s a plug for the the next one of these - please post your questions earlier! JT and I are at a disadvantage from a time zone perspective. The bulk of the questions were posted in the middle of the night for us and the Fireside chat was first thing in the AM.
We’ll try to give even more notice next time. The AMA style here or in Reddit might also be more effective.
Overall though, we just appreciate the engagement!
I propose a deadline. Collect questions in the thread and close comments something like 3 days before the event. Questions that arrive too late have to be posted in the AMA/live chat then.
I think the fact that the first post redirected us to an email address may have been part of why the questions didn’t come in right away. I know for me that was the reason why I only asked some questions after you mentioned to post them here a day before the event.
I do like the video format. I like seeing the excitement about what you’re working on when answering these questions rather than just the facts in text format. It also allows for a bit more back and forth (though I think I was the only SNO using the chat).
In my experience a blog post that had around 22 Q&A was reduced to ~11 questions when the blog post was migrated/updated. This post had important answers regarding HIPAA/GDPR. There was no explanation whatsoever on why those questions were removed. I hope this won’t happen in a video format.
We already saw Brighsilence’s response get massaged down to "“Don’t worry about it, we don’t think it’s a problem”. Which is perfectly correct when looked at from the network as a whole but might need a different response when looked at from the SNO perspective.
For myself if the average node life (mean, median and mode numbers would all be interesting for different reasons) really is 9 months I’d have some concerns. Particularly if it was a lot of people starting to drop off after 6 months or so. Hard drives should be lasting longer than 9 months!
A node life of 9 months would mean the average SNO would only ever get on average 1 payment on L1 and even that wouldn’t be certain.
The problem I see in the current format is the limited ability for the SNO to jump in and say 'Hey, that’s not what I am asking here!" That is even worse when the response is post event. But that is if the question gets addressed at all.
Could the node software ensure that it automatically refuses ingress requests whenever the underlying storage system (HDD, SSD, …) cannot keep up? Is that feature considered?
