ComptitiveSubset

This is great news. Algorithm optimized social networks are poison to society.

Dune. You can’t capture the complexities of that book in a movie. You can smudge a lot details into scenes of Timothée Chalamet staring intensely at beautiful CGI scenery, but it misses a lot.

Supporting both is in order. As one is pointless without the other

A design that scales. Forwarding every like, post and comment to all federated servers will not scale well.

Mastodon exists. It’s pretty good. Using 2 apps is fine.

I write down everything I built so for plus future plans in OneNote. This kind of defeats the purpose of self hosting but I want to keep a written copy complete off site in case if a complete loss. Plus I like OneNote. It’s actually a well designed product. Scripts, docker compose files and such are in GitHub.

Wow that’s a great idea

For app data, Borg as backup/restore software. Backup data is then stored on Hetzner as an offsite backup - super easy and cheap to setup. Also add healthchecks.io to get notified if a backup failed.

Edit: Backup docker compose files and other scripts (without API keys!!!) with git to GitHub.

For app data, Borg as backup/restore software. Backup data is then stored on Hetzner as an offsite backup - super easy and cheap to setup. Also add healthchecks.io to get notified if a backup failed.

Edit: Backup docker compose files and other scripts (without API keys!!!) with git to GitHub.

It feels like it is possible to have a conversation here. In Reddit I felt like my comments were getting buried

OP is correct. We have very little to to gain and everything to lose.