@tchambers
Do you have an update on this article, Tim?
Conversation
Notices
-
Embed this notice
HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Thursday, 25-Jan-2024 09:51:04 JST HistoPol (#HP) 🥥 🌴 -
Embed this notice
Tim Chambers (tchambers@indieweb.social)'s status on Friday, 26-Jan-2024 01:08:17 JST Tim Chambers @HistoPol @ploum I don’t yet: will likely update it as big structurally new things occur….
-
Embed this notice
HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Friday, 26-Jan-2024 01:13:05 JST HistoPol (#HP) 🥥 🌴 @tchambers
Any ideas on their (#Threads) game plan for the #Fediverse?Why are they moving so slowly now?
-
Embed this notice
volkris@qoto.org's status on Friday, 26-Jan-2024 03:47:19 JST volkris @HistoPol I really think Fediverse presents huge technical and managerial challenges to the centralized systems, and it takes time to sort all of it out, to sort out if it’s even possible to integrate.
Technically, ActivityPub is not a lightweight protocol. It takes a lot of resources to manage all the streams going left and right without the computational efficiency of just operating in-house.
Managerially, I don’t think any centralized service has really figured out how to integrate the Wild West into the more controlled environment their users expect, not even getting into moderation issues.
I think they’re moving slowly because there are real challenges and problems that have to be solved, and it takes time to solve them.
-
Embed this notice
HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Friday, 26-Jan-2024 03:50:37 JST HistoPol (#HP) 🥥 🌴 @volkris
That sounds like a very reasonable analysis of the corporate SM giants' tech challenges in the face of the #Fediverse.
Thank you, Volkris.
Good to hear from you again.🤗
@tchambers @ploum
-
Embed this notice