# A new logo for storagenode **URL:** \ **Category:** Uncategorized\ **Created:** [May 4, 2024, 8:45am UTC](https://forum.storj.io/t/a-new-logo-for-storagenode/26088 "2024-05-04T08:45:19Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\ **Post date:** [May 4, 2024, 12:35pm UTC](https://forum.storj.io/t/a-new-logo-for-storagenode/26088/2 "2024-05-04T12:35:30Z")
Perhaps this can help put things into perspective: > [@](#): > > # Mar 14 v1.100.1-rc > > ## Changelog > > ### Storagenode > > - 21de0c3 storagenode/blobstore: store trash under per-day directories > [@Trash does not go away in 7 days](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/100): > > We don’t have a fix yet. **This situation is not considered ultra-high priority** because the only data at risk of being lost is already in the trash. We definitely do see how it’s a problem for our SNOs, though, and we would like very much to fix it. The plan is to recognize the recursive directory problem and the unmigrated directories problem and correct them automatically on node start. > [@](#): > > # 4 days ago v1.103.2 > > ## Changelog > > ### Storagenode > > - 67edcd9 web/storagenode: update STORJ logo It is quite evident that it’s not sarcasm on my end. The only real testing that has been done in the past 18 days has been updating the storj logo and making sure it’s pretty. There has been absolutely NO testing performed on the trash improvements, otherwise this testing would have caught the (number of) bugs mentioned in this thread. The only reason I was able to catch the trash cleanup not updating the databases (which a simple diff on the resulting database files would have caught **instantly** past merge-testing on your end) was because the monitoring system I use showed decreasing disk space, yet the nodes were still reporting full. I’m not being sarcastic: It is very evident where storj’s priorities are. We (as SNOs) can only follow those priorities. And the current priorities are: - make the product look pretty - test the possibility of having larger clients onboard by migrating data from the production satellites to the testing satellite What is NOT a priority: - making sure that nodes don’t constantly die left, right, above, below and center - keeping an accurate track of used, trash and free space - actually cleaning up the trash - expecting the team to open a bug internally with all the provided logs, df, du outputs already provided Some will still argue that what I’m saying above is not the case, not true or FUD. The quoted parts are there, as are all the replies. To each their own, other SNOs as well as I, are only trying to keep the (remaining) nodes online to the best of our abilities. --- _[View the full topic](https://forum.storj.io/t/a-new-logo-for-storagenode/26088)._