Für die jenigen, die schon immer mal wissen wollten wie das deutschsprachige #Fediverse von innen aussieht: https://files.hetzner.com/360-tour/
Does anyone know which protocol is best for pushing a huge amount (300+ GB, ~200k individual files) of data and files into a Hetzner Storagebox?
@joho I run a fedi instance for myself and a few "playground" accounts, filled with some followings and my "poor man’s relay" (reading RSS feeds of hashtags from other instances with a script and injecting the stuff via Mastodon search API).
First I used #Mastodon (on a #hetzner cloudserver with 8G RAM). A Rails app is not a problem to install and run for me (that’s what I do for a living). But once it's running and federating, there is always something going on on the server that eats a lot of memory and creates surprisingly high CPU usage. And it fills your disc.
So I decided to use #GoToSocial (on a cloudserver with 4 G RAM) for the same stuff, with Postgres. The main difference is the Interface (I use #Phanpy instead of Mastodon’s web interface), of course. Some of the nice "bells and whistles" from Mastodon (like the automatic author attribution, automatic OG preview pics for links in the timeline and all the "trending" stuff, etc.) aren’t there, that’s okay for me.
I barely notice a system load with GTS. It also fills your disc, but you can use a short media purge time, because GTS can reload a pic or a video from its origin if it is already purged away. Something that Mastodon cannot do.
Irgendwie vom Regen in die Traufe
Informiere dich mal über #Hetzner (wikipedia und co)