# Bye bye for now

**URL:** <https://forum.storj.io/t/bye-bye-for-now/15346>\
**Category:** Node Operators\
**Created:** [September 17, 2021, 3:32pm UTC](https://forum.storj.io/t/bye-bye-for-now/15346 "2021-09-17T15:32:28Z")\
**Posts on this page:** 18\
**Page:** 3

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [September 24, 2021, 11:21am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/41 "2021-09-24T11:21:54Z")

</div>

> [@penfold](#):
>
> average node life is 9 months

I’d have to go back to the video, but I believe they said the network was built around that assumption. I’m not entirely sure that was actually a real statistic. But even if it is, that doesn’t tell us a lot yet. There are probably lots of nodes that check in, but never resolve port forwarding issues. Others who never get out of vetting phase and many more. Those do barely any damage to the network, if any at all, but would drag down that average a lot.

We would need a bit more info, which is why it’s one of the questions I asked. But the response was basically: “Don’t worry about it, we don’t think it’s a problem”. And I’m sure it isn’t a problem for the network. But it may point to SNOs not being happy.

---

<div class="post-metadata">

**Author:** ![penfold](https://storj.bcdn.literatehosting.com/letter_avatar/penfold/32/5_5575768a8748004e209b776fc1b2916d.png) [@penfold](https://forum.storj.io/u/penfold)\
**Post date:** [September 24, 2021, 11:28am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/42 "2021-09-24T11:28:39Z")

</div>

> [@BrightSilence](#):
>
> “Don’t worry about it, we don’t think it’s a problem”. And I’m sure it isn’t a problem for the network. But it may point to SNOs not being happy.

That is my assessment as well.

---

<div class="post-metadata">

**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\
**Post date:** [September 24, 2021, 3:37pm UTC](https://forum.storj.io/t/bye-bye-for-now/15346/43 "2021-09-24T15:37:55Z")

</div>

> [@BrightSilence](#):
>
> Egress percentages this month so far compared to amount of data stored.  
> Largest node that has always had free space: about 5.8%  
> Smaller node that has been full for about a year: 3.8%  
> Another small node full for about a year: 3.1%

My oldest node is 17 months now. 3.25 TB stored. I have reduced allocation to 0 before the recent increas in customer uploads. So without the latest develpment my download traffic is 5 % customer downloads and 5% repair downloads so 10% in total. I see that behavior on most of my nodes.

> [@BrightSilence](#):
>
> This does suggest that recently uploaded data is downloaded more frequently. That also kind of makes sense for most use cases I can think of. Backup probably doesn’t trigger much download at all, but if it does, you’re more likely to want last weeks version of data than a snapshot from years ago. Videos get more views right after being uploaded. Security footage is most likely to be watched shortly after being created. Software distributions see a peak shortly after a new version has been released.

It is not possible to predict the customer behavior. I wanted to track the number of downloads per pieceID. My idea was to identify customers that upload mostly backup data and never download it. It would be allowed to reject the upload. However I ended up not doing it because it would reduce my payout. Let’s say from 100 backup customers 1 needs to download the full backup. That would still be 1% download traffic. My bottleneck is my internet connection. I want to max out my connection with customer downloads. Hard drives are cheap. So what I need to do is fill my hard drive with as many backups as possible and take the money if one of them needs to restore the backup. A customer might upload a video file and share it. First few month barly no hits and suddenly it get postet several times in a short time generating a hugh amount of download traffic. I don’t think the assumption is correct that old data has to fall behind in download traffic. At least not on my nodes.

---

<div class="post-metadata">

**Author:** ![rit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/rit/32/63_2.png) [@rit](https://forum.storj.io/u/rit)\
**Post date:** [September 24, 2021, 3:44pm UTC](https://forum.storj.io/t/bye-bye-for-now/15346/44 "2021-09-24T15:44:09Z")

</div>

If you want a full understanding of the how frequently files have been accessed on a linux system you can always run agedu.

As my node is a Pi with a single spinning disk agedu took 36 hours to run against my 6TB of storage as it creates a data file and then uses this to create a reporting database. All the resulting IO on the same drives as STORJ is running against is painful.

Sadly the resulting heat map shown in the web output is not that useful to share, but for my system, about 50% of the files had not been touched for over 6 months.

---

<div class="post-metadata">

**Author:** ![penfold](https://storj.bcdn.literatehosting.com/letter_avatar/penfold/32/5_5575768a8748004e209b776fc1b2916d.png) [@penfold](https://forum.storj.io/u/penfold)\
**Post date:** [September 26, 2021, 3:25am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/45 "2021-09-26T03:25:54Z")

</div>

> [@Vadim](#):
>
> STORJ is long time investment project, so it can be not profitable in the beginning and mid terms, but in lont term it is profitable. When BTC dropped in 2019 i stopped mining, i not accounted that mining will be very profitable in long term, if i wold not stopped, today I wold have several thousand’s EUR more on my account. So I learned from that. So i build my Storj farm slowly from junk, and today I have 140TB of data, and 500-600$ income every month.

Vadim, I had hoped to emulate your setup over the longer term but I no longer think that is possible with current data levels. Maybe that will change as adoption grows.

1. Every isp connection is a cost that needs to be paid for.  
It means a SNO would be in the hole for a significant period of time before even breaking even.
2. If a SNO has only a single ISP then it means 9-10 months before even one payment - as the L2 system is still useless for now in terms of using it to offset costs.
3. Surge payments that existed during the early part of the network life have gone the way of the dodo.

I just don’t think at current usage levels anyone can replicate your setup without incurring significant additional costs. Maybe if one has a large extended family where you can locate nodes on different isp’s. 🙂

---

<div class="post-metadata">

**Author:** ![GERGX](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/gergx/32/65_2.png) [@GERGX](https://forum.storj.io/u/GERGX)\
**Post date:** [September 30, 2021, 10:57am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/46 "2021-09-30T10:57:03Z")

</div>

with the current state of ETH Storj is doomed  
also Storj has bad tokenomics for the SNO  
and the worst is Storj as a construct does not offer “public” data, so Stroj is just glorified backup  
it is over for Storj

---

<div class="post-metadata">

**Author:** ![twl](https://storj.bcdn.literatehosting.com/letter_avatar/twl/32/5_5575768a8748004e209b776fc1b2916d.png) [@twl](https://forum.storj.io/u/twl)\
**Post date:** [September 30, 2021, 11:48am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/47 "2021-09-30T11:48:11Z")

</div>

> [@GERGX](#):
>
> it is over for Storj

2014: Bitcoin is dead  
2015: Bitcoin is dead  
2016: Bitcoin is dead  
2017: Bitcoin is dead  
2018: Bitcoin is dead  
2019: Bitcoin is dead  
2020: Bitcoin is dead  
2021: Bitcoin is dead

---

<div class="post-metadata">

**Author:** ![rit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/rit/32/63_2.png) [@rit](https://forum.storj.io/u/rit)\
**Post date:** [September 30, 2021, 11:55pm UTC](https://forum.storj.io/t/bye-bye-for-now/15346/48 "2021-09-30T23:55:17Z")

</div>

> [@GERGX](#):
>
> Stroj is just glorified backup

That does happen to be their primary business, Storj tokens are a means of funding and payment processing - it is not their primary business.

If you are here because you think that the business aims are based on the idea that Storj tokens are a way to gain untold wealth you may be somewhat mistaken.

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [October 1, 2021, 5:25am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/49 "2021-10-01T05:25:00Z")

</div>

> [@GERGX](#):
>
> does not offer “public” data

Are you mean this: [https://docs.storj.io/dcs/how-tos/host-a-static-website](https://docs.storj.io/dcs/how-tos/host-a-static-website)  
Or this: [Publicly Exposed Network Data (official statistics from Storj DCS satellites)](https://forum.storj.io/t/publicly-exposed-network-data-official-statistics-from-storj-dcs-satellites/14103) and as result - [Storj Network Statistics - Grafana](https://storjstats.info/d/storj/storj-network-statistics?orgId=1)

---

<div class="post-metadata">

**Author:** ![GERGX](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/gergx/32/65_2.png) [@GERGX](https://forum.storj.io/u/GERGX)\
**Post date:** [October 1, 2021, 5:39am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/50 "2021-10-01T05:39:21Z")

</div>

yes similar, can you host a website on storj (the files) or serve videos  
the problem is you need keys to ask for fragments  
so you have to have a back end point where the fragments are requested and then assembled (cashed) and then served  
this is not useful, using stroj does not benefit you as content provider

---

<div class="post-metadata">

**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\
**Post date:** [October 1, 2021, 8:42am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/51 "2021-10-01T08:42:24Z")

</div>

> [@GERGX](#):
>
> this is not useful, using stroj does not benefit you as content provider

I have problems to follow you. Storj supports all that right now. You can host and share content. We have customers that start using this feature. Are you saying these customers will get a problem later on and some external force will stop them? I don’t understand why these customers are saying it is useful to them while you are claiming it is not useful. So one side must be wrong then?

---

<div class="post-metadata">

**Author:** ![GERGX](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/gergx/32/65_2.png) [@GERGX](https://forum.storj.io/u/GERGX)\
**Post date:** [October 1, 2021, 8:58am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/52 "2021-10-01T08:58:27Z")

</div>

lets say I have hosted a file, hello\_world.jpg , on storj  
how do I send a link(or something) to that file, without using amazon or 3rd party

---

<div class="post-metadata">

**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\
**Post date:** [October 1, 2021, 9:03am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/53 "2021-10-01T09:03:09Z")

</div>

Do you have an account on any satellite? Just login, open the object browser, type in your encryption key, navigate to your file and press the share button. You get a link that you can send to your friends.

If you don’t like to enter your encryption key (server side encryption) you can also use uplink cli to share a file. It is more secure but requires some command line magic.

---

<div class="post-metadata">

**Author:** ![GERGX](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/gergx/32/65_2.png) [@GERGX](https://forum.storj.io/u/GERGX)\
**Post date:** [October 1, 2021, 9:10am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/54 "2021-10-01T09:10:06Z")

</div>

can you post one such link ?

---

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [October 1, 2021, 10:56am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/55 "2021-10-01T10:56:04Z")

</div>

You can have a look at this one: [Fireplace 10 hours full HD.mp4 | Storj DCS](https://link.us1.storjshare.io/jvkwgy4sunprf7wg33y7z7lf5kda/fireplace%2FFireplace%2010%20hours%20full%20HD.mp4)

---

<div class="post-metadata">

**Author:** ![GERGX](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/gergx/32/65_2.png) [@GERGX](https://forum.storj.io/u/GERGX)\
**Post date:** [October 1, 2021, 11:09am UTC](https://forum.storj.io/t/bye-bye-for-now/15346/56 "2021-10-01T11:09:25Z")

</div>

I stand corrected. It is a storj link.

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [October 1, 2021, 3:28pm UTC](https://forum.storj.io/t/bye-bye-for-now/15346/57 "2021-10-01T15:28:57Z")

</div>

Here’s a blog post of pixel experience using exactly this for ROM distribution.

> **[PixelExperience Scales Up Software Distribution With Storj DCS](https://www.storj.io/blog/pixelexperience-scales-up-software-distribution-with-storj-dcs)**

---

<div class="post-metadata">

**Author:** ![Fetch](https://storj.bcdn.literatehosting.com/letter_avatar/fetch/32/5_5575768a8748004e209b776fc1b2916d.png) [@Fetch](https://forum.storj.io/u/Fetch)\
**Post date:** [October 5, 2021, 3:51pm UTC](https://forum.storj.io/t/bye-bye-for-now/15346/58 "2021-10-05T15:51:11Z")

</div>

Well , this is long “Bye bye” thread  
Best of luck @direktorn

[Previous page](https://forum.storj.io/t/bye-bye-for-now/15346.md?page=2)
