Kbin.cafe on Blocking Meta's New Threads App

For those who aren't aware, Kbin Cafe is a Kbin instance I run. Cross-posting our stance on Threads for visibility.

As Meta’s new App Threads has now launched, it's important that I definitively state our stance on blocking federation with Meta if they choose to adopt ActivityPub:

Kbin Cafe will not be preemptively fediblocking Meta. However, I'll be keeping a close watch on the situation as it unfolds, with my finger hovering over the block button. My first priority is the integrity and safety of the community, and with this in mind there won't be any second chances given to Meta--their first strike results in a block.

Efforts are being coordinated by @tchambers and others to build out Fediverse test suites to ensure that all new actors (like Threads) that claim ActivityPub compliance have to prove their claims or be shown where they are lacking. That is the one real defense against “Embrace, Extend, Extinguish” plays by any large actor. To join in and help with this, follow this Frendica group here:
https://kbin.cafe/m/activitypubtestsuite@venera.social

This ActivityPub Test Suite needs to happen ASAP, so any dev support is welcome!

As always, feel free to comment here or message me with any questions or concerns.

bionicjoey,

their first strike results in a block.

What do you consider a “strike”? Does Meta’s reputation and history not constitute a “strike”?

barista,

Good question! By and large, some of the following would count as a "strike":

  • Poor moderation
  • Excessive spam
  • Most importantly: Making non-backwards compatible changes to the ActivityPub specification that may lead to the classic "Embrace, extend, extinguish" situation
  • Probably more...
  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • fediverse@kbin.social
  • meta
  • Macbeth
  • All magazines