Comment by amiga386
2 days ago
That's likely to end up Balkanized like the fediverse, where every instance has a list of other instances they refuse to federate with, often because politics or petty drama. Though to be fair to the fediverse, sometimes it's because those other instances are full of child porn and most people just don't want to see that.
It amuses me that Mastodon Central uses corpo-friendly labels for the sites they won't federate with, e.g. (https://mastodon.social/about)
tsundere.love Suspended (Hate speech)
you**.**ve Suspended (Inappropriate content)
Whereas the more free-wheeling sites, like the ones Mastodon Central blocks, tell it exactly how it is: (https://tsundere.love/about)
nadeko.pw CP
mk.fedcast.ch Spam
youjo.love hosts at least one admitted pedo
A lot of such issues could likely be resolved by a better thought out protocol. There are certainly plenty of self righteous people who would refuse to federate purely on principle but more typically the issue is simply that one does not wish to be exposed to or traffic in any way the content in question. A well thought out self categorization system could largely address that need - you'd only need to refuse to peer with those who failed to apply it. AI also makes any such effort easier than ever.
Doesn't work. People from different geographical areas just can't agree on categories. So even correctly applied labels are useless.
You'd think "no lolis" would be reasonable. It falls apart when people look 14 into 50s, to you and your local police, but not to themselves.
weirdly enough that reminds me of wattpad and ao3, where wattpad uses much nicer sounding terms while ao3 uses as accurate terms as possible. (which makes ao3 seem more "degenerate")
If you want to follow some CP poster on nadeko.pw then you can ask your admin on tsundere.love to unblock it and he will probably just ban you for admitting you like CP.
Where did we get this idea that federated instances should never block anything? Even warez sites have rules.
> Where did we get this idea that federated instances should never block anything?
I'm not sure, but the OP was postulating that Forgejo instances could federate to solve the problem that the Dutch government runs its own instance to develop its software (including using AI extensively) but wants to engage with the wider community so is currently hosting things on Codeberg's centralised instance of Forgejo, and Codeberg's administrators hate AI.
Adding federation doesn't solve that problem, it just moves it one level up. To collaborate with the Dutch government, you either need to directly register on their site, or set up an entire copy of Forgejo, publicly hosted, so you can federate your one-user instance with them, or you need to find a different instance that someone else hosts, and be at the mercy of that instance's admins, who may be even more cruel and capricious than Codeberg's.
What I predict is a future codeberg.org/about saying
And a future code.overheid.nl/about being full of dodgy Forgejo instances that host porn games
Codeberg's AI position was about resource waste. Single-user AI projects were spamming their CI/CD as if they were KDE or the kernel.
They don't care if someone wastes their own resources.
2 replies →
Why should a fallible, biased human “admin” be able to block an individual from communicating with another individual or group of individuals? This just creates weird social silos and echo chambers. It’s made worse because the people who choose to be jannies are often deeply broken people.
The Fediverse has the whole model backwards as a result of its design. Either individuals need to run their own instances, or identity needs to be completely ephemeral and flow through many servers as it does in Nostr. A Nostr admin can choose not to host data from a given identity, they could even use an identity whitelist, but users normally subscribe to multiple relays. In the end, the data gets through, while the relay admin can keep their own hands clean if they have a problem with the data.
Note that having this freedom does not preclude you from voluntarily signing up for blocklists. But this is an active choice, and it can’t be suddenly imposed on a set of users.
Do you have an email account without a spam filter?
1 reply →