The admins to perform upgrades, monitoring, fixes, etc… will require root access to the database. That means they can alter all your posts to say *blah blah blah" if they wanted.
Similarly passwords will be encrypted within the database and encryption algorithms have to be able to go in both directions. Normally they need a seed value to start random generation. The admin defines the seed as a result an admin can decrypt everything in the database.
This is traditional British food, bangers is slang for Pork Saussage (Cumberland Saussage I am guessing)
Your posting this on KBin which implements the twitter style fediverse API and federates with Mastodon.
Click the microblog button … Behold twitter replacement
This could be achieved within the UI and seems like a good idea.
Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.
Having the UI retrieve all local posts with the same magazine/community name (e.g. m/[email protected] c/[email protected]). Wouldn’t be hugely difficult, I believe Kbin uses postgres database as the local store. The community/instance should be columns you can search for, it would be a small SQL change.
Even if that wasn’t an option, there is a means to get all of the magazines/communities from the kbin UI and retrieve all posts for a specific magazine/community. So you could do it entirely in a web client.
The combined view wouldn’t change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).
The solution here would be to default to the local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop downso users can choose.
If you signup to social media it will pester you for your email contacts, location and hobbies/interests.
Building a signup wizard to use that information to select a instance would seemto be the best approach.
The contacts would let you know what instance most of your friends are located (e.g. look up email addresses).
Topic specific instance, can provide a hobby/interests selection section.
Lastly the location would let you choose a country specific general instance.
It would help push decentralisation but instead of providing choice your asking questions the user is used to being asked.