#ActivityPub is getting its first formal update path since 2018. I wrote about why this matters, how this leads to some strange and funny power dynamics, and about who actually participate
https://connectedplaces.online/reports/fediverse-report-148-on-protocol-governance/
@fediversereport So, I think this is a really interesting article, and I agree that participation and representation matter here.
I hope that more ActivityPub implementers step up to become W3C members. There are several funded nonprofits and commercial organizations that could probably afford it. I'd recommend that people who use ActivityPub software let the software creators know that they should participate in the WG process!
"there is a good change [sic] that Meta has no interest in actually participating."
***
Probably a good change indeed.
@fediversereport If they are smart they will fix a raft of fundamental UX pitfalls in current ActivityPub by defining a protocol handler for it.
Email needed its protocol handler spec while it was getting established – and arguably still does – and I do think this is one of the ways in which ActivityPub is "like email".
Finally—a formal update path could fix ActivityPub’s messy UX and interoperability issues. if more funded orgs join the W3C workgroup, we might actually get consistent patterns across the fediverse instead of every client doing its own thing.