Hank G ☑️ on Nostr: I feel an inner cognitive dissonance on the topic of Threads joining the fediverse by ...
I feel an inner cognitive dissonance on the topic of Threads joining the fediverse by federating with ActivityPub. Contempt for FAANG and Facebook in particular brought me here many years ago. I’ve seen many an EEE campaign by companies in their position of power. But I’m glad they are federating and using an existing open standard and not trying to invent their own like BlueSky. I’m glad I’ll be able to interact with IRL friends/family/associates whom I could never get to join the fediverse (or they never got beyond account creation and one hello post). My excitement for the pluses don’t negate my worry beads. But those worry beads aren’t leading me to reflexively block Threads on the server I run. I'm adding BlueSky access through their client API once the next Friendica goes into production as well. I had Twitter integration before the API was nuked. So integrating with Threads is consistent with that. The fears them becoming the defactor ActivityPub standards setters the way Mastodon is now is my biggest practical worry. It could torque it in a bad direction and then when it doesn't work not care because Threads can stand on its own but the rest of the fediverse servers cannot. So we could be stuck with a steaming pile and an exodus of users as a consequence. #Threads #fediverse #ActivityPub
Published at
2023-12-16 11:36:35Event JSON
{
"id": "783594268948f99e9e3773c1850c32c93ea1351f8e9addf6540725603e40722f",
"pubkey": "ea39d7cd8e6e2cc2d994e2118577756f1f227394b34d84fb90f4bb447a9100a9",
"created_at": 1702726595,
"kind": 1,
"tags": [
[
"p",
"ff0d21995d2aa704006c487c83fde7091a2596527e6b98e1ef9ed4ae9e42b7d1",
"wss://relay.mostr.pub"
],
[
"t",
"fediverse"
],
[
"t",
"ActivityPub"
],
[
"t",
"threads"
],
[
"proxy",
"https://friendica.myportal.social/objects/e65e1095-6565-7d8b-c369-366746536984",
"activitypub"
]
],
"content": "I feel an inner cognitive dissonance on the topic of Threads joining the fediverse by federating with ActivityPub. Contempt for FAANG and Facebook in particular brought me here many years ago. I’ve seen many an EEE campaign by companies in their position of power. But I’m glad they are federating and using an existing open standard and not trying to invent their own like BlueSky. I’m glad I’ll be able to interact with IRL friends/family/associates whom I could never get to join the fediverse (or they never got beyond account creation and one hello post). My excitement for the pluses don’t negate my worry beads. But those worry beads aren’t leading me to reflexively block Threads on the server I run. I'm adding BlueSky access through their client API once the next Friendica goes into production as well. I had Twitter integration before the API was nuked. So integrating with Threads is consistent with that. The fears them becoming the defactor ActivityPub standards setters the way Mastodon is now is my biggest practical worry. It could torque it in a bad direction and then when it doesn't work not care because Threads can stand on its own but the rest of the fediverse servers cannot. So we could be stuck with a steaming pile and an exodus of users as a consequence. #Threads #fediverse #ActivityPub",
"sig": "ab4487e05b741c6056b3f4c7516a2f2fd5cc7b8ba8a4af7fa1777f06a8fa0a6322f72e0055bb83848b1e197bb875715cf0d231faed3d4a7ecb1f5230ccdce588"
}