Skip to main content


The Fedipact table showing which servers are blocking Threads is not accurate!

For example, it says that atomicpoet.org is blocking Threads when, in fact, this is not correct. So view this entire site with skepticism.

fedipact.veganism.social/

@fediversenews

reshared this

in reply to Chris Trottier

They also don't appear to have cast a very wide net when collecting those inaccuracies. 😆

Fediverse News reshared this.

in reply to Chris Trottier

Not the first time: hear-me.social/@admin/11214028…

Just the first example that came up in a search.


@kommaKucken @thomkennon
hear-me.social is showing as blocking Threads.net. This is not true. We are limiting them. There are no plans to block them.

We never had them blocked and we never signed any fedipact agreement.

Can you tell me who provided you with this incorrect information?

Thanks


in reply to Chris Trottier

I am listed as being part of fedipact, which I did sign onto, but I then reconsidered. There doesn't appear to be a way to remove my name from the fedipact.
in reply to Chris Alemany🇺🇦🇨🇦🇪🇸

@chris @onepict @nm It was also incorrectly reporting my instance as not blocking Threads while the endpoint that lists blocked servers was not public, I reported the issue yesterday.
This entry was edited (1 year ago)
Unknown parent

akkoma - Link to source
Chris Trottier
@tokyo_0 @nm Point is, I never blocked Threads. How many other servers can say the same?
in reply to Chris Trottier

given how inaccurate it is, I have to wonder what the intent was. Cause it certainly doesn't seem to be meant as an accurate portrayal of which sites are and aren't federated w/ threads.net ...
Unknown parent

akkoma - Link to source
Chris Trottier
@183231bcb @nm @tokyo_0 Oh, well I’m not talking about the official Fedipact, just the table.