Myself? I want to talk about what's on my #Fediverse wish list at #Fediforum, which is actually longer than the 8 points I blogged about here, but I gotta stop somewhere.
https://reb00ted.org/tech/20230425-w3c-activitypub-wishlist/
Myself? I want to talk about what's on my #Fediverse wish list at #Fediforum, which is actually longer than the 8 points I blogged about here, but I gotta stop somewhere. https://reb00ted.org/tech/20230425-w3c-activitypub-wishlist/ 17 comments
@J12t @tchambers Instead of a document, a single test suite you can use to test your implementation would be nice. @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. @drq that tends to be difficult in practice, if we are talking moving data from one app to another app (not just one app instance to an instance of the same app somewhere else). Which did you have in mind there? @drq if you “only” want full data migration between instances of the same app, isn’t that simply an app feature then, like a mastodon feature or lack thereof, rather than a fediverse feature? @J12t That's what we need to find out, I guess. Zot network has no problem with nomadic identity. But that's probably because the only engine on there meaningfully is Hubzilla, AFAIK. @narF Yes I'm aware. There are certain things FEPs can do, and cannot do. Just writing a document has generally never solved much :-) @narF The problem is not specs. The problem is common movement forward. A spec becomes valuable if many people implement it and it enables interop between many pieces of software. Everything else is just dead trees (or maybe bits ...) |
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.