Post AaU5oyZd1v9Op2Nu2S by maffeis@mastodon.social
 (DIR) More posts by maffeis@mastodon.social
 (DIR) Post #AaU5owaGQaTEeQfNke by maffeis@mastodon.social
       2023-07-25T16:59:27Z
       
       0 likes, 0 repeats
       
       It’s clear to me some folks don’t know/understand the difference between protocols and services. #Threads is (allegedly) going to support federation via the #ActivityPub protocol, meaning that users on other services implementing the protocol, like Mastodon, will be able to interact in some form.That doesn’t mean you’ll be able to use Threads with your Mastodon client. Clients don’t implement the protocol directly, they instead use Mastodon’s API which is specific to Mastodon.
       
 (DIR) Post #AaU5oxi6EwKg91L9bU by voxpelli@mastodon.social
       2023-07-25T18:56:57Z
       
       1 likes, 0 repeats
       
       @maffeis I like how the #IndieWeb is approaching this with #MicroPub and #MicroSub:* https://indieweb.org/Micropub* https://indieweb.org/MicrosubClients can chose to implement one or both of those.A typical social media app would implement both.An app that’s meant only for authoring posts picks just MicroPub and an app that’s simply meant for consumption picks just MicroSub.I find the #Fediverse / #Mastodon focus on #ActivityPub as the one and only API to be a bit lackluster in that regard.
       
 (DIR) Post #AaU5oyZd1v9Op2Nu2S by maffeis@mastodon.social
       2023-07-25T16:59:41Z
       
       0 likes, 0 repeats
       
       It goes without saying Meta has no incentive in offering a public, Mastodon-compatible API to access Threads via third-party clients, so forget about that!But, if everything goes well, we’ll be able to follow Threads users from Mastodon, and viceversa, and that’s a pretty big deal if you ask me.