Let me repeat the question. Customer knocks at your front door and would like to upload some data the moment the paperwork is signed. Is that a no no for you? No no means don’t sign the deal!
2 Likes
I got the point. But there is no Point about laughing at the ones who are sceptical and ask questions 
Just my 2 Cents.
The client can’t upload data the moment the paperwork is signed. There will always be some delay. Whether it’s because of operations or of bandwidth limitations. So allow me to repeat my question as well: what is this prospective client’s upload speed?
1 Like
Hi, I read on the forum that there was going to be movement in the trash…
But I still didn’t expect this big reset !!!
Do you want to scuttle the ship or what ??? 
It’s going to make a hole in our socks this month, you’ll buy us a beer eh 
You confirm that everything is normal ?
1 Like
Yeah one of my 5TB node got 1TB to trash in one day. Haha.
1 Like
There are deletes, but US1 sat dosen’t display data for today on the dashboard. I believe there is already a thread about that.
today? hasn’t diplayed data for the past couple of weeks. And before that it was a 50:50 if any data got returned. 
this is interesting. Could you please provide your graphs from the node?
Thats a very important question.
@littleskunk in Relation to this in my understanding you will start to work if the contract is signed.
My Boss would Kick me in the Ass if i would Invest Hours of working before the contract is signed.
Sure there is Investment in Sales etc. But i think thats a different Point 
Edit: And sure there is investing in developing like the Performance Tests etc. - thats totally understandable.
We are talking about this: https://stats.storjshare.io/data.json
(us1 isn’t even there, so it’s not returning any kind of data whatsoever).
Ah, I see. Yes, it’s stopped to provide data for a while, because it cannot do it in time. We are working on a solution. The first suggestion is to stop providing this info, until it would be resolved, but I disagree. Let it’s provide an info from the not affected satellites until the problem with BI databases would be resolved.
It depends on the kind of service you are selling. In software development the product has to meet the customer requirement before the paperwork gets signed and not after. It is a balance game for sure. Requiring a signature before doing any work sounds more like physical products or services.
7 Likes
But honestly given the work they are investing into this upfront, this seems to be a huge deal and it seems that chances are prospective. Let’s say it this way, it is probably more likely that the deal gets signed than the other way around. We really don’t know, maybe there is some kind of verbal commitment already and there is really only a signature that’s missing.
1 Like
The data from US1 only is missing on 104 node version.
Same machine, other node on 102 ver. has that data.
I feel this is getting worse every day. When I started my first node years ago it was like install and forget. Nothing to care about, just checking payment once a month.
Today it is a full time job to keep some nodes running. 
Who should I blame if not the storj devs? 
1 Like
How I personally view it: it’s a sort of growing pains for both sides. On one side the SNOs see their side of pains (I won’t repeat them, we all know them). On the other side storj sees their side of pains (ie satellite limitations). It’s a chance for both sides to end the standoff and work together to solve any issues that come up.
That of course means that both sides work to the best of their abilities to work out issues.
1 Like
Let me guess. You running multiple nodes on the same hardware? And, perhaps, on the same disk?
2 Likes
I think we’ll all be visiting this thread to cry once-per-week when a load of trash comes through. 
And the rest of the week we’ll be reading the posts about how the new firehose of SLC data is causing issues with potato nodes… and celebrating all the ingress. 
And we’ll repeat that cycle all summer… 
3 Likes
I have to admit that a disk can handle multiple nodes. Until I learned it’s against ToS it ran fine. But after the migration they ran even better than before.
But if you ran two or more nodes on one disk, they will impact each other and make you profit worse