this post was submitted on 26 Aug 2025
57 points (89.0% liked)

Fediverse memes

1891 readers
40 users here now

Memes about the Fediverse.

Rules

General
Specific

Elsewhere in the Fediverse

Other relevant communities:

founded 11 months ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] TootSweet@lemmy.world 14 points 6 days ago

So... is this a thing you're thinking shouldn't be the case?

If we were to agree this was a bad power for admins to have, then how, from a technical point of view, would we prevent admins from doing so? There's no real way to prevent an instance admin from, for instance, running a fork of Lemmy that has as a feature, for instance, the ability to prevent a local user from posting on remote instances' communities or a specific remote instance's community (even if the official upstream Lemmy repo developers/maintainers decided to remove that feature).

Theoretically, given that Lemmy is licensed under the AGPL, one could legally demand the source code of any specific Lemmy instance and from that source code obtain proof that it was a fork and what differences might be on that instance relative to the upstream official Lemmy repo.

I guess if I had to come up with another way to prevent a fork from preventing users from posting on remote instances' communities, I might suppose maybe one option would be for Lemmy officially to support logging into your instance 1 account from instance 2's domain. (Might require some OAuth fanciness to allow that without potentially opening up the user to their account being accessed by instance 2 if instance 2 happened to be maliciuos.) And if you did that, you'd be subject to instance 2's rules for being able or not able to post to a given community on instance 2 or instance 3 or whatever. That would undermine instance 1's ability to prevent you from posting on instance 2 or instance 3 or whatever.

Or maybe I'm misunderstanding you and you're not advocating for anything in particular. Just sharing information.