I think it's kind of a dangerous idea, but has anyone worked on a shared blocklist for user accounts? I realize that the current best practice is to block the whole server, but in some cases with very large sets of users it might be preferable.
Like, "This person is extremely toxic and even letting them know you exist is a mental health hazard" levels of blocking.
@thisismissem@evan@zuck that is, unfortunately, true. There will be a lot of really good people on Threads and blocking the whole thing because of a subset is dumb.
Hmm - I wonder if threads actually has to be just threads.net. Why can’t it appear as many federated servers and people can choose which one they belong to?
@rachel@thisismissem@evan the dumb subset believes meta corporation does not belong to the fediverse. No one forbids you to go use threads if you like it, but interoperability is not required.
@f4grx that "dumb subset" happens to be the people involved in creating the software you use to participate in the fediverse, and are actively working to try to ensure that the fediverse remains safe in the future.
You may not what threads here, which is fine, but others will, you can always block the threads domain.
Meta won't be the last big company to want to participate, and it's an open network and open protocol, so more will.
I mean yea but get back to me when it's a two way street. I want governments, corporations, celebrities and especially journalists to know they can leave #xitter and have the freedom of their own server and be seen by everybody on #threads. that's the gamechanger moment imo. and once lots of those people do that, #threads will be locked into maintaining full federation. that will be our Netscape vs AOL moment.
Add comment