We would prefer pay each GB a higher price (erasure, encryption, distribution and metadata justifies it), but at least, one can easily estimate his bill by the end of the month. Or, even worst, tell the users to not upload small files as the cost of each small object grows the bill and to ZIP them before upload… We just can’t prevent users post a link to a 3GB public file on Twitter and get it downloaded hundreds of times. The problem here is mainly the cost is unpredictable in this case. Just do the math (cots of: storage + egress + objects). there are approximately 8TB of egress each month, mainly by desktop syncing.these files are mainly photos, documents and some mid-sized files (300Mb each).a Single Nextcloud instance hosting 2TB of files.Using Tardigrade with something like Nextcloud or Owncloud has a lot of pros, but also a lot of cons in terms of costs. That said, I think most of us (including me who gets relatively large payouts) are disappointed with the payouts mainly because our nodes are being significantly under-utilised. The smaller SNOs may disagree and find running a small node even less profitable. Ofcourse it’s easy for me to say that because I’m offering shed loads of storage and bandwidth. ![]() I’d personally be happy to accept a smaller payout for egress (assuming Storj does the same!) on the assumption it would increase egress usage. If things are looking good and it’s just a case of waiting for the traffic organically then that’s fine, but if new customers aren’t where you expected them to be by now, I agree with some of the other comments that perhaps a smaller piece of the pie is better than no pie at all. ![]() I suppose we should start with “where are Storj now?” It’s still early days, how are promotions and new customers going? Have we on boarded any big fish? Firstly I think it’s great you even asked the community for our thoughts!
0 Comments
Leave a Reply. |