|
Top-level
 Top of my #Fediverse wish list: A single-document Fediverse interop #spec that, when I have written the code for all that's in it, my code will interoperate in some basic fashion with all other #Fediverse software that has implemented this document. Right now, I have to understand and sometimes reverse-engineer every single fediverse app, and that is simply not viable. Who has time for that? And do it again as soon as new versions come out. #ActivityPub is underspecified for this. 4 comments
@ramsey #ActivityPub #test suite is actually number two on my list. There used to be one, but it's unmaintained and apparently not quite recoverable. But we need both: a single spec, and a corresponding test suite. That should be the foundation. And #3 on my #Fediverse wish list is a branding program. If your product passes the minimal test suite, you get to put a sticker on it. Sort of like the "Validated HTML" logo we used to have when HTML was new, or the "Bluetooth" logo: If a prospective user comes across a product displaying the brand, they will know it will interoperate. Geeks may not care, but IMHO it's really important for broader consumer adoption. |
Gregory's Server
@J12t @tchambers Instead of a document, a single test suite you can use to test your implementation would be nice.