Omg this list is hilarious https://www.threads.net/moderated_servers
-
@matthieu_xyz @liaizon @CaptMorgan
yes, as far as I know you are right, I would bet dollars to donuts many of these servers are blocked by all the main masto instances
-
@failedLyndonLaRouchite @liaizon @CaptMorgan
I didn’t look too deep into it, but from what I can see. They basically blocked nazis and nudity. -
@matthieu_xyz @CaptMorgan @failedLyndonLaRouchite look deeper then
-
@ivy it was someones Job (that they got payed for!) to add all those queer and anarchists servers to the block list tho. I think they care enough to put that list up, which is honestly even weirder then not caring
-
Hi @liaizon, how would one do the privacy-policy discovery properly? #Webfinger? https://www.rfc-editor.org/rfc/rfc7033#section-4.3 like https://seppo.social/.well-known/webfinger?resource=https://seppo.social&rel=privacy-policy
Naturally, nobody implements this to date. What for? (I didn't until 10min ago)
Update: the url should just be in the regular jrd response.
-
@mro I think threads is just looking at this URL https://mastodon.social/privacy-policy or instance name.com/privacy-policy
-
I'm expecting most of our instances will end up there because we have a privacy policy at a different URL and a public feed is optional (default disabled). Ironic because the public feed is where one finds 99.999% of the rubbish that they're ostensibly trying to prevent. And I would also bet they are looking for that in whatever URL Mastodon uses for that purpose - so of course they won't find it; even on a site that enables it.
The joke's on them. They aren't federating with the fediverse at all. Only a restricted number of Mastodon sites and a few Mastodon copycats.