Today the W3C standards organization announced a new working group to advance the ActivityPub and Activity Streams standards. The Social Web Foundation, as a W3C member organization, will be partic…
That’s because AP as it is implemented today is crap, it’s a superficial compatibility layer on top of a proprietary (as in, doing non-standardized stuff) platform. We need to take it on its head and make AP the actual core then build on top
The mastodon api, or the lemmy api, or the xyz api. Eagh platform has its own. Being public doesn’t make it standard, hence the “proprietary” qualifier
Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too.
NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.
That’s because AP as it is implemented today is crap, it’s a superficial compatibility layer on top of a proprietary (as in, doing non-standardized stuff) platform. We need to take it on its head and make AP the actual core then build on top
What is this proprietary layer you speak of?
The mastodon api, or the lemmy api, or the xyz api. Eagh platform has its own. Being public doesn’t make it standard, hence the “proprietary” qualifier
Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too.
NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.