Hey Fedi Admins, y'all federating with this?  #FediPact
@ErikUden Last I checked mastodon.social was.

@aral thanks to Dansup's and Nume McAaroon's tools it's very easy to check:

https://fedipact.veganism.social/?v2

https://fedidb.org/current-events/anti-meta-fedi-pact

#Fedipact - The instances blocking Zuckerberg's Threads.net

An interactive list to see which ActivityPub (Matodon, Lemmy, FireFish, etc) instances are federating with Threads.net

@ErikUden oh shit I'm in one of the "federated" and didn't know it. Welp, I'll have to migrate soon...
@hawyer @ErikUden You can personally block Threads, too, I did it immediately. Hope my instance will come round...

@hawyer @ErikUden @TomSwirly
I need to look into this.

I’ve 3 mastodon logins, & this one has been great for all-my-other-broad-interests as opposed to my ham radio account & my art appreciation account.

So I wanna keep this login, but also throw up a double bird-flip to Fark Muckerberg & the mElon-head.

@kelvin0mql @hawyer @ErikUden @TomSwirly there's also an issue to do with Authorized_Fetch, which regards how other instances are able to look up and serve your profile content. So if you're on an instance that blocks Threads but doesn't have authorized fetch enabled, then your content can still be shared with Threads via federation with other servers who DO federated with Threads. & personal blocking of the instance also has similar privacy issues that it personal blocking doesn't solve.
@kelvin0mql @hawyer @ErikUden @TomSwirly so in addition to defederating with Threads, an instance also needs to enable authorized fetch to fully protect user data. Personal blocking can't do that.

@itsmeholland @kelvin0mql @hawyer @ErikUden I know about that, and I would prefer to have Authorized Fetch enabled, but my server isn't doing that yet.

Sometime in the new year I'll bug 'em.