Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.
If you’re a server admin, please defederate Meta’s domain “threads.net”
If you don’t run your own server, please ask your server admin to defederate “threads.net”.
If they want to hang out with us, they can make an account somewhere other than thread, bam, done!
“make another account somewhere” isn’t really what federation is about.
Indeed it is, they’re not saying you have to make an account on that person’s server, they’re saying that you can make it on a different server, that’s the point of federation you can join other servers that are connected to them. It’s not to be fully open without any limitations, because if it were then content moderation would be impossible.
Services like Nostr have this problem, they are like the wild West where anything goes and you can’t do anything about it. To some people that seems great but the fact of the matter is those services are filled with right-wing trolls and crypto scammers (likely plenty of other nasty stuff as well) because they cannot be moderated.
Mastodon, Kbin, the new Lemmy 0.19 release allow on a per user basis to block entire domains, so I don’t see how this is a “you can’t do anything about it” situation. Just let users decide.
What do you think it’s about? Because from my perspective changing instances is kind of the entire defining feature that separates it from commercial platforms.
Federation is about being able to communicate with other people even if they use a different platform.
It’s about connecting communities and having fail saves, not bullying.
I feel like that’s exactly how it was billed to me, find somewhere that federates with who you want, and if that changes, you’re free to move
The choice of email providers is not about which one can exchange mails with GMail.
Some of the time it is though. Like Gmail has a pretty large list of IPs it won’t deliver email from. When self-hosting, it’s something you really do have to worry about.
The reason most people don’t worry about it is that most people only use a handful of free emails and organizations that provide email addresses for their users spend time worrying about it so users don’t have to.
So erecting artificial walls is not positive then. Good we’re on the same page.
No. I definitely prefer email with good spam blocking. I’m not criticizing Google for blocking mail how they do. It’s pretty necessary. Which is also something you learn fairly quickly if you try to self host.
Google isn’t blocking, it’s moving suspected spam into the spam folder and users have the option to whitelist any false positives.
Blocking Threads completely with only “then fuck off” to the users is not what interoperability is about.