I think there’s room for philosphical differences here though. One can acknowledge Meta being evil but not advocate for defederation.
The standard federation analogy is to that of email. Google has shown themselves to be evil at times (prone to enshitification at the very least). But if my email provider drops support for any email from gmail.com, well… that’s kinda not a good thing.
Obviously ActivityPub is not email, but still, I think it’s a somewhat nuanced issue.
And with regards to the EEE issue, I’m personally not convinced of any threat. Slack embraced IRC then killed support, and no harm was done that I’m aware. XMPP always gets trotted out as an example, but I think it’s a weak argument at best, disingenuous at worst.
I don’t want ads getting federated to my instance.
There’s not any room for philosophical debate on that point for me.
There’s a lot of other reasons to not federate with Threads, but that one is the only one I need to cite to realistically appeal to literally any and all fediverse users with at least a couple neurons in their skulls. And it’s definitely the only argument I need to cite to an instance admin who’s running a lemmy container on their home server.
Oh, for sure. But you missed part of what I was saying.
Regardless of where you fall on the political ideological spectrum or how you use social media - or really, anything else about you - I’m pretty confident that nobody wants to have ads force fed to them, so that’s a very easy point to unify on.
You can block communities that attract problem users.
You can even block entire instances of communities that attract problem users (on your own, without the instance choosing for you).
The Fediverse isn’t completely unmoderated, but it’s not hella huge either. Plenty of moderation issues due to lack of having mods available 24/7 already exist. Just a few weeks ago, CSAM was being spammed all over the place and it took almost an entire day for action to be taken.
I for one am not in favor of giving my ability to curate my experience myself up to have someone else choose for me, so in almost every case I would be against defederation from the admin level.
Of course. I’m not advocating for Threads to not be blocked by those who don’t want it. I’m just not in favor of someone else making that choice for me. If they become a problem, I can block it myself. I don’t need or want to be babied by the admins/instance operators.
I think there’s room for philosphical differences here though. One can acknowledge Meta being evil but not advocate for defederation.
The standard federation analogy is to that of email. Google has shown themselves to be evil at times (prone to enshitification at the very least). But if my email provider drops support for any email from gmail.com, well… that’s kinda not a good thing.
Obviously ActivityPub is not email, but still, I think it’s a somewhat nuanced issue.
And with regards to the EEE issue, I’m personally not convinced of any threat. Slack embraced IRC then killed support, and no harm was done that I’m aware. XMPP always gets trotted out as an example, but I think it’s a weak argument at best, disingenuous at worst.
I don’t want ads getting federated to my instance.
There’s not any room for philosophical debate on that point for me.
There’s a lot of other reasons to not federate with Threads, but that one is the only one I need to cite to realistically appeal to literally any and all fediverse users with at least a couple neurons in their skulls. And it’s definitely the only argument I need to cite to an instance admin who’s running a lemmy container on their home server.
Ads are the absolute least problematic thing about Meta.
Unmoderated content, a literal firehose of absolute vile stuff is my biggest fear.
Oh, for sure. But you missed part of what I was saying.
Regardless of where you fall on the political ideological spectrum or how you use social media - or really, anything else about you - I’m pretty confident that nobody wants to have ads force fed to them, so that’s a very easy point to unify on.
That’s what the block function is for.
You can block the problem users.
You can block communities that attract problem users.
You can even block entire instances of communities that attract problem users (on your own, without the instance choosing for you).
The Fediverse isn’t completely unmoderated, but it’s not hella huge either. Plenty of moderation issues due to lack of having mods available 24/7 already exist. Just a few weeks ago, CSAM was being spammed all over the place and it took almost an entire day for action to be taken.
I for one am not in favor of giving my ability to curate my experience myself up to have someone else choose for me, so in almost every case I would be against defederation from the admin level.
Instances like threads.net?
Moderation might be lacking now, but it will become unmanageable after.
Of course. I’m not advocating for Threads to not be blocked by those who don’t want it. I’m just not in favor of someone else making that choice for me. If they become a problem, I can block it myself. I don’t need or want to be babied by the admins/instance operators.
So make your own instance then?