@datacequia@evan is currently working on one now and there have been a few published in Japanese over the years and one was published in Catalan last year
All these folks tut-tutting about various #fediverse instances preemptively blocking #threads should be aware that many instances are taking this step because Threads is full of #transphobic and outright fascist types that #meta is either unable or unwilling to moderate and instance admins are just treating it the same way they would any other instance that has that issue.
90+% of instances should be blocking Threads just because of their normal moderation policy, not because "it's Meta".
The question people should be asking is, why aren't instances blocking Threads, when it clearly violates their content policy? (Lookin' at you Mastodon.social)
@darnell This is so awesome! Thank you for putting the time to pull this together Darnell. I've already sent this to my board in email and flipped it into the Flipboard Team Magazine which is our private mag where we share posts together as a team. Will come back to you with thoughts next.
I don’t believe the EEE narrative about Threads federation. The number of #fediverse citizens isn’t large enough to justify the (substantial) investment in Fedi/Masto/ActivityPub interop if the goal is just to bring them to Meta. @mosseri explicitly said that the goal was to enable people to move off Threads and I believe him, because…
…All the Big Techs are under considerable political pressure to be less lockin-y and more interoperable. Especially in the EU. If any Threads user is free to step over to some Masto/Akkoma/whatever instance, it’s hard for any regulatory agency or politician to make a case that Meta is locking people in.
New blog post: Understanding ActivityPub - Part 4: Threads
A first detailed look into how Threads implements ActivityPub. Learn about the data that is shared (or not), an interesting implementation of HTTP signatures, and Threads' take on quote posts in ActivityPub.
@crepels Nice article! In particular, this is the best explanation I've seen yet of the "infinite signature recursion" problem, and the way around it.
I haven't tried to talk to Threads from my own toy implementation yet. I have a suspicion that the "instance actor" requirement is going to give me a headache.
For me it was me looking up alternative social media platforms on Google, as I never had any liking towards the mainstream social media platforms in any way.
Then I chance upon this "Mastodon" and am intrigued by it.
I sign up for it....
I have been here 2 years and counting! :blobcatgiggle:
@frankie
I actually didn't use any of Facebook/Instagram or Twitter at all before coming here.
I might have heard of fedi via Reddit, I have interest in FOSS, decentralization and privacy, so it might have been from there.
Uff @linos kann es sein, dass ich noch etwas nicht verstehe? Offensichtlich haben Menschen an meinen letzten #activitypub Post kommentiert und die Kommentare sind auch am WordPress Beitrag https://www.videospielgeschichten.de/welche-konsole-ist-die-schoenste/ gelandet. Leider finde / sehe ich diese aber nicht im Fediverse am Post; was mache ich falsch?
@vsg_DE Was meinst du mit "Fediverse", auf deiner Mastodon-Instanz, während du eingeloggt bist? Es ist so wie immer: du siehst nur jene Kommentare, die auf deiner Instanz landen. Das tun sie nur, wenn jemand auf deiner Instanz den kommentierenden Account bereits folgt.
Mastodon founder, Eugen Rochko, praises Threads entry into the #Fediverse because it makes Mastodon “a far more attractive option.”
This is fairly obvious and basic network effects since both Threads & Mastodon become more valuable as their users can now share content across these services seamlessly.
This angers Mastodon admins for whom the fact that not a lot of people use Mastodon was a selling point. They do not want it to grow and be useful to more people.
Way more interesting and healthy fediverse news is happening in the shadows and is barely getting discussed! Which is: Discourse has federation between different instances of itself and other #fediverse software such as Mastodon working!
@liaizon Stuff like this will make engaging with new online groups much easier - no need to create a new account for every single place you want to comment at.
I moderate a forum (it uses nodebb) and spam is always a concern, but then the fediverse concept of distributed server moderation and banning entire untrusted servers should help to alleviate that somewhat.
Oh awesome, I open my app to find the #fediverse in a giant collective panic because a social platform owned by a giant company dares to join it.
Fedi: “I want an open platform where everything is standardized”
(#Threads enables ActivityPub)
Fedi: “NOT LIKE THAT ANYTHING BUT THAT”
If you declare an open standard and provide the clearly superior ecosystem, you relinquish control of who uses it just by it being open. You can’t have it both ways. Ever.
The proliferation of #ActivityPub is exciting. But don't dismiss those that want to defederate with corporate socials. The #fediverse was built by individuals escaping the harassment they faced on those platforms.
If you don't agree with your server admin's decision to federate with a specific domain, you can block it on your own. You have the power!
This seems preferable to an admin making the decision for all users.
With yesterday's announcement that Meta is starting to test Threads and ActivityPub integration, I see the #Fediverse is at an all time high again of whining and crying and being butthurt over it all.
I get stating your opinion about not wanting them here or whatever, but come on people, don't sound like a little 2 year old who lost their pacifier. It gets old, quick.
Just mute/block and move on and be done with it all. It's really that damn simple.
