[tantek]Zegnat, shall we define a page for "browser extensions" that's more general than /WebExtensions and includes current IndieWeb friendly extensions like snarfed's new Bridgy extension?
ZegnatI have a feeling all IndieWeb friendly extensions will be examples of WebExtensions unless someone is doing macOS development building binaries for Safari
ZegnatThat might mean browsers will start to diverge a lot more again, then it could make sense to have a different page speaking of extensions in general, so /WebExtensions can be more about the spec and the differences.
LoqiIt looks like we don't have a page for "browser extension" yet. Would you like to create it? (Or just say "browser extension is ____", a sentence describing the term)
ZegnatThose are the only ones I can remember right away, [tantek]. I might go in and clean the page in MediaWiki later if i have time and expand with short summaries :)
ZegnatSo in general, apart from some naming, it is still pretty good. And I seem to recall in some cases Chromium and Firefox having made the exact same divergence from the spec. Meaning extensions are still compatible cross-browser, it is then only the spec that is wrong, not weird seeing how the spec has been dormant for a good while now.
ZegnatThat, IMO, also shows WHATWG is doing the right thing by writing the spec following implementation and use, with people who know implementation status from different browsers.
aaronpkit's really funny especially when i had only 100 subscribers, people would always reply to my comments like "how are you verified with only 100 subs??"
[tantek]tbh I think part of it was motivated by the morbid experience of learning of people suddenly passing away and then checking what was the last thing they tweeted to try to see what happened 😕
hoschiHi @aaronpk I would like to help finish up translation of https://indieweb.org/principles-de . It seems like the link to duolingo is broken. Now what to do?