Replying to ec55841e...

Here's an interesting question. To me, anyway :-)

As the #fediverse grows, and an ever-broader set of apps talks #ActivityPub and extensions to #ActivityPub, how do we ensure that the overall architecture of the system remains consistent?

Example from the past: WebDAV used HTTP extensibility as it was intended, but arguably they deviated from the architectural principles. (A consequence: it remains a niche and many apps that could've used it don't)

Who else is worrying about things like that?
Avatar
Hrefna (DHC) 2y ago

nostr:npub1u27r9h3j9pvrplaffsmpn698e8xhmuqhdgcxldv67ammql9pumnqha3qfq I definitely do. It's one of what I think of as the big existential threats.

Specifically what I am less concerned about is how extensions get used and more that that integration requires Θ(n^2) testing. It encourages lack of interoperability: it's one thing to say "I am doing something deliberately a bit odd," it is another to need to _either_ do a lot of odd things just to talk to anyone else _or_ just say "screw it we're integrating with mastodon and others can figure it out."

Reply to this note

Please Login to reply.

Discussion

ec
ec55841e... 2y ago

nostr:npub14q6a856gru3kjnrw3m3st0u5vxlls9a2redvsdd9u3gke8d4ucxs0a4za2 ideas what we can do? Somehow we need to aggregate stuff (people, issues, best practices …) to be able to identify and strive for globally better options than if everybody just were to work independently and thus just optimize locally for whatever the world looks like from their point of view.