I reference OAuth a lot in my talk, and I can already tell that @aaronpk's discussion of OAuth 2.1 is going to be of interest to anyone who wants to develop the "suite of community apps" pattern from my presentation.
https://conf.tube/videos/watch/32351956-89d7-4887-b6b0-f1a32f91dc36
@cwebber and I noticed several common themes as we per-screened the talks, so I put together this handy bingo card for #apconf2020
Play along at home!
"OAuth 2.1 and ActivityPub" by Aaron Parecki
Q&A Session: Sat October 3rd, 16:30 UTC #apconf2020
https://conf.tube/videos/watch/32351956-89d7-4887-b6b0-f1a32f91dc36
A spot-on summary of where we’ve ended up with web components.
Web Components had so much potential to empower HTML to do more, and make web development more accessible to non-programmers and easier for programmers.
But then…
Somewhere along the way, the space got flooded by JS frameworks aficionados, who revel in complex APIs, overengineered build processes and dependency graphs that look like the roots of a banyan tree.
Alas, that’s true. Lea wonders how this can be fixed:
I’m not sure if this is a design issue, or a documentation issue.
I worry that is a cultural issue.
Using a custom element from the directory often needs to be preceded by a ritual of npm flugelhorn, import clownshoes, build quux, all completely unapologetically because “here is my truckload of dependencies, yeah, what”.
