"Modular design hinges on the simplicity and abstract nature of the interface definition between the modules. A design in which the insides of each module need to know all about each other is not a modular design but an arbitrary partitioning of the bits."
https://www.w3.org/DesignIssues/Principles.html
This is one of the big criticisms of #ActivityPub. It's not enough just to implement the spec, I'm told. You have to test it against other implementations and tweak yours until it does what you expect.
@strypey pages looking different on IE and Netscape?
@volkris
> pages looking different on IE and Netscape?
Wow, you did deep for that one. Neither of those have existed for years 😆
@strypey I mean I just pulled up the grand old headliners.
Today we are having the same issues looking at different renderings between chromium and the various programs related to edge and whatever Mozilla is putting out.
Just today I was reading about the issues with Mozilla's current and future browsers.
@volkris
> different renderings between chromium
... is an example of a related but separate problem. Which is implementations not following the specs. Mastodon using its own client-to-server API instead of the one in the AP.
@volkris
> But this has been an eternal criticism when it came to Internet technologies. Including the Web
Has it? Got any examples?