Post #2346326

2026-05-06 06:08 UTC

@uriel@x.keinpfusch.net > Here in the ActivityPub ecosystem, though, "my own take on the standard" is rampant—and the spec simply isn't precise enough to prevent it. Fair cop. Sounds like you could be a valuable invited expert in the W3C Social Working Group, which was recently commissioned to prepare an updated version of the AP spec; https://socialhub.activitypub.rocks/t/how-to-participate-in-the-w3c-working-groups-on-ap/8479?u=strypey @evan@cosocial.ca @cwebber@social.coop @Mastodon@mastodon.social

Replies (1)

@uriel@x.keinpfusch.net 2026-05-06 06:46

@strypey@mastodon.nzoss.nz @evan@cosocial.ca @cwebber@social.coop @Mastodon@mastodon.social I'm afraid, my social skills aren't good enough for this. And since English is not my first language, I know that I will sound too aggressive or confrontative, just when I just want to be clear. Quite often I need to edit using an AI, to be clear without looking aggressive. But I can't do it in person. What I'm saying is, the standard should be completely exhaustive, so that we don't discuss how to implement things, we just implement things. Whether a variabile should be 32 or 64 bit long like a discussion between Pleroma and Mastodon, should be specified in the standard. Cannot be that Eugen Rocko decides it is 64, and others must adapt, cause "If you heard about our documentation changing to specify IDs as 64 bit numbers yesterday…". In the telecommunication field, this is pure nonsense. You must be able to have a call with ANY phone device, ANY company, ANY country.

Open ##2346327