A #PHP developer who, in his spare time, plays #Tabletop and #VideoGames; if the weathers nice I #Climb rocks, but mostly fall off of indoor #Bouldering ones.

Pronouns He/Him
Blog https://realmenweardress.es
Photos https://pixelfed.social/pieceofthepie
Keyoxide https://keyoxide.org/606B2E3C103A443663DA82716B37390F365AADAA

  • 3 Posts
  • 30 Comments
Joined 10 months ago
cake
Cake day: August 23rd, 2023

help-circle








  • Been using Mastodon a while. Once you hit critical mass of people you follow you just sort of find new ones.

    If someone you enjoy reading boosts something someone else has said you go off and probably end up following them too.

    With Mastodon you have to be a bit more pro active about building (and pruning) your social network but I’ve found it worthwhile.










  • This is actually due to the way these platforms work. When a user comments on a comment or post on their instance it will be shown on their instance. It’s then sent on to the owning instance of that comment or post. That owning instance then forwards it on to all interested parties (magazine instance, commenters instance).

    Any instance in that chain can refuse to forward or broadcast that message due to a block, but the users own instance will likely always show that post. Ideally they would not do that and would be made aware of a block but that is a bit of a grey area in ActivityPub implementations.





  • The issue with orchestration is that you still need a way to share those small databases and config files.

    Docker has ok NFS support so you’d want to move the files to NAS shares and have them mount those. Without some way to centralise or spread the files out you won’t be covering your SSD failure case. Once you’ve got that going docker swarm will probably cover your needs just fine.

    You could go with K8S but based on you setup that’s a bit overkill (unless you’re doing it as a learning exercise, in which case go nuts).