The reaction by some Mastodon instance admins in joining a ANTI-META FEDI PACT to block Meta's Threads joining the Fediverse is hypocritical. They are essentially acting as gatekeepers to prevent alleged possible gatekeeping. Here's a list of instance admins/mods who have agreed to block Threads:https://fedipact.online/

Avoid these instances. Quoting John Gruber on BlueSky:

Masto zealots: We’re open, federate with us!
Instagram: Great, we’re building a new thing to join you.
Masto zealtots: Not that kind of open!

Author:Khürt Williams

A human who works in information security and enjoys photography, Formula 1 and craft ale.

2 thoughts on “”

    1. @chronocide There is no issue for me. I want an #openweb.

      But when Meta added #ActivyPub support to Threads to allow federation between Threads and Mastodon there was a kneejerk response from some Mastodon instance admins. They blocked Threads federation.

      I want an #openweb. This is why I transitioned from and stopped my financial support to photog.social and moved to indieweb.social. photog.social is blocking Threads federation.

      Links:
      https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/

      https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/

      https://www.theverge.com/24107998/threads-fediverse-mastodon-how-to

      Reply

I want to hear from you. Leave a comment.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Feel free to comment on this story directly above, but you can also go to links/summaries posted to social media, and reply to or comment on them there.

IndieWebCamp: To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)