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.
Not necessarily, however there are questions on compliance with the EU’s Digital Markets Act which went into effect in May,. So the platform has been delayed until Meta determines or gets guidance from the EU to comply with the law.
The whole reason Threads was launched had everything to do with how Musk has been mismanaging Twitter over the past few months, and most especially the past week. This is why the platform is partly unfinished. Zucks took the opportunity to move up launch to capitalize on Twitter’s mistakes.
And it looks like it worked.