If you really, absolutely want to continue using Mastodon, support this: <a href="https://github.com/mastodon/mastodon/issues/28554">https://github.com/mastodon/mastodon/issues/28554</a>.<p>If you just want to run a single-user instance on the cheap: forget Mastodon! Takahe [0] does not require one whole server for each user and it has substantial lower TCO. A "small instance" for Mastodon can not be realistically be found for less than $10/month today , while I can offer Takahe for $39 per <i>year</i> [1].<p>But if you want to make the Fediverse really, really cheap to operate, lets rethink the whole server-centric approach and put some effort to develop applications that are primarily based on the client [2]<p>[0] <a href="https://jointakahe.org" rel="nofollow">https://jointakahe.org</a><p>[1] <a href="https://communick.com/takahe" rel="nofollow">https://communick.com/takahe</a><p>[2] <a href="https://raphael.lullis.net/a-plan-for-social-media-less-fedi-more-webby/" rel="nofollow">https://raphael.lullis.net/a-plan-for-social-media-less-fedi...</a>
I am in your comments telling you that federated server is still just someone else's computer.<p>But there are systems where user is sovereign, defined by their key, not dependent on any masters. One such system is Nostr:<p><a href="https://nostr.com/" rel="nofollow">https://nostr.com/</a>
This would all be solved if we treated P2P social media as ephemeral. That's a much more tractable problem.<p>Imagine that you have 48 hours to converse on a thread and grab its content, then it's gone. Third party software could archive if you wanted, but it wouldn't be an infrastructure requirement.<p>It'd be so much easier to serve that peer nodes could easily be stood up on residential / commodity hardware and could reasonably be expected to handle serving large portions of the discussion graph.
Currently I support an instance only minimally, but probably enough to pay for the cost incurred by my usage. If every user did it, not instance owner would ever have financial worries. However, I would support more, if I got some guarantees, that media is also hosted on some bare metals or so, away from S3 or Fastly or similar services, that put data i to the hands of big players.
I always thought Pleroma solved this problem much more elegantly: proxy the media from the origin, and cache a set amount of data.<p>Also respects other people deleting their servers/media and prevents someone posting CSAM becoming a problem for everyone.