I'm beginning to wonder if the only solution to hate speech and harassment on the Fediverse might be allowlist-only instances.
-
-
@oliphant @jdp23 It looks like the Outpost idea you outline doesn’t allow people outside of the outpost to follow people inside of the outpost. What would you think about allowing for that? I imagine some people might want to have a broad reach, but not hear from everybody who tries to mention them.
-
@jsit @jdp23 This is basically the original idea I had, that doesn't use the "cold start" model, where you connect to an "approved" list of instances, that might even be something like mastodon.social, which would of course allow them to follow you back.
I might think more about that model as well, but I personally like a more closed or "alternate" network where you just create a new account rather than trying to get two different networks to "play nice" with each other.
-
Oliphantom Menacereplied to Oliphantom Menace on last edited by
-
It makes a lot of sense to start with the simple case. For a broader solution, I think @jenniferplusplus's thinking about multiple named federations is relevant as well. https://hachyderm.io/@jenniferplusplus/112887785292385896
-
@jdp23 @jenniferplusplus The allowlist subscriptions pending in GTS make something like this more possible, especially if multiple list subscriptions are allowed.
Either way, starting with an outpost/pod concept on the simple case would scale to this pretty quickly, even if the allowlists of the 'federation' are manual at first.
-
looking forward to seeing how it works out!FYI @julian something to keep an eye on here (although no short-term work required)
-
@jsit I think this is the major selling point actually, as you construct a new network that way. Bluesky has shown that there can be a lot of value in having a new network that is separate from the current main network.
-
@[email protected] @[email protected] where can I find more about these allowed lists?
Does it send an ETag so I can update as needed?
-
️
