 Turns out around 700 GB of media storage on mastodon.social was being consumed by multiple Twitter "bridges" running on different domains, reposting Twitter users' tweets into the fediverse as far as I'm aware without their (the Twitter users') participation or knowledge. That's 10% of our media storage accumulated over 6 years. At least cross-posters set up their own accounts, that's still legit use. This, it just feels so wasteful. How Twitter even gives out API keys for this, I don't know. 17 comments
 Heh, that's why Smithereen stores remote media in a LRU cache of a configurable limited size, instead of storing permanently. The downside is that it takes noticeable time and way too many roundtrips to load each remote image when it's first accessed. @grishka Our cache isn't permanent either, but the eviction is a manual process. Well, manual unless you put it in cron. But that's not the point. It's still wasteful, it still costs money and processing power even if it gets removed eventually, and for what - ghost accounts  @Gargron Block 'em... I post the same content on 13 different social media platforms but... I do it intentionally... I choose to post on each of them because I want my words read by as many people as possible... and Just using FaceBorg and Twitter ignores hundreds of my followers... I limit my mastodon posts because I have some respect for this platform... Unlike Twitter... I spam them like crazy!  Can I make a polite request to improve Masto’s media deduplication at some point for dealing with just this sort of stuff?   @eonity It's fine, you're obviously here and reposting of your own volition. It's the third-party bots that really bother me. |
Gregory's Server
@Gargron Pff, that's a load..
How often do you clean external media on .social and .online?