Paul KinlanNov 22, 2022

One thing that the recent rise of Mastodon and the ecosystem around ActivityPub has taught me is not everything on the Web has to be integrated in to the Browser for it to be successful.

The fact that there is plenty of web software being built that is interoperable and scalable through the standardisation process has been eye-opening.

I should probably ground myself in the real-world more.

Gemma LNNov 22, 2022
Show threadJeffrey Yasskin
@paul This is an important question to keep iterating on as the #W3C moves into its new era of having a board of directors, and the #W3CAB starts focusing more on their Vision work (https://github.com/w3c/AB-public/tree/main/Vision). Us browser folks have been biased toward "practical" #WebStandards that get implemented in browsers, but #ActivityPub is proof that the more aspirational server<->server ones can be important too.
AB-public/Vision at main · w3c/AB-public

Advisory Board repository for materials not meant to be restricted to W3C Members - AB-public/Vision at main · w3c/AB-public

GitHub
Nov 22, 2022 at 7:12pmWeb
Show threadPaul KinlanNov 22, 2022
@jyasskin thanks for sharing. It's super useful.
Show threadPaul KinlanNov 23, 2022
@jyasskin I will say - documentation and test suites, seem, err, sparse.
Show threadbkardellNov 23, 2022
@paul @jyasskin for about half of the web's lifetime you could have said the same of the practical ones in browsers - that's changeable
Show threadPaul KinlanNov 23, 2022
@bkardell @jyasskin yeah, exactly. It's potentially a good area of focus
Show threadbkardellNov 23, 2022
@paul @jyasskin to me, it's pretty important that the lessons go in that direction as well. The W3C spent a long time focusing almost mainly on that stuff and it's definitely not without problems - but surely there are lessons to be learned here on both ends