#dev 2023-03-01
2023-03-01 UTC
AramZS_ and geoffo joined the channel
#
[KevinMarks] Right, that's what I was thinking. Yet there are lots of parallel implementations of popup notes, footnotes and sidenotes. It's a bit like a details/summary with the details being detachable, but that doesn't work with the nesting. Or maybe like a <ol><li> where the <li>part can appear elsewhere.
#
[KevinMarks] It feels more like a missing html element than a markup pattern. The consuming case is if you have a layout model that does that already. Looks like there is an epub pattern https://www.heliconbooks.com/?id=blog&postid=EPUB3Footnotes
#
[KevinMarks] So the noteref and footnote attributes match your pattern broadly
#
[KevinMarks] So epub uses <aside> for the contents, but you still need to track the links and ids yourself
#
[tantek] footnote << Brainstorming: how to mark-up, prior example, EPUB3 https://www.heliconbooks.com/?id=blog&postid=EPUB3Footnotes ([[js;dr]]) <blockquote>For the link… <br/><a href="#n1" epub:type="noteref" >1</a><br/>…<p>Note the use of epub:type="noteref" this tells the reader that this link is not a standard link but a link to a note.</p><p>The note itself should be inside a new HTML5 semantic tag</p>…<aside id="n1" epub:type="foo
#
Loqi ok, I added "Brainstorming: how to mark-up, prior example, EPUB3 https://www.heliconbooks.com/?id=blog&postid=EPUB3Footnotes ([[js;dr]]) <blockquote>For the link… <br/><a href="#n1" epub:type="noteref" >1</a><br/>…<p>Note the use of epub:type="noteref" this tells the reader that this link is not a standard link but a link to a note.</p><p>The note itself should be inside a new HTML5 semantic tag</p>…<aside id="n1" epub:type="foo" to the "See Also" section of /footnote https://indieweb.org/wiki/index.php?diff=86835&oldid=86763
[timothy_chambe] joined the channel
#
[tantek] footnote << ^ docs with consuming code example: https://help.apple.com/itc/booksassetguide/en.lproj/itccf8ecf5c8.html <blockquote>You use two elements to create a pop-up footnote: an anchor (<code><a></code>) element that triggers the popup and the <code><aside></code> element that contains the footnote text. Both elements have an <code>epub:type</code> attribute to identify their purpose: <code>epub:type="noteref"</code> to trigger
#
Loqi ok, I added "^ docs with consuming code example: https://help.apple.com/itc/booksassetguide/en.lproj/itccf8ecf5c8.html <blockquote>You use two elements to create a pop-up footnote: an anchor (<code><a></code>) element that triggers the popup and the <code><aside></code> element that contains the footnote text. Both elements have an <code>epub:type</code> attribute to identify their purpose: <code>epub:type="noteref"</code> to trigger" to the "See Also" section of /footnote https://indieweb.org/wiki/index.php?diff=86837&oldid=86836
#
[tantek] Thanks [KevinMarks], added: https://indieweb.org/footnote#How_to_markup_semantics
geoffo joined the channel
#
[tantek] aaronpk, [KevinMarks] semi-dev related, glad I'm not worrying about supporting writing blog posts from the Moon in my software: https://www.nbcnews.com/science/space/moon-time-zone-rcna72459
lockywolf joined the channel
bterry, geoffo and jjuran joined the channel
#
IWDiscordRelay <capjamesg#4492> Websites that took all the right vitamins."
#
IWDiscordRelay <capjamesg#4492> "Progressive Web Apps
#
IWDiscordRelay <capjamesg#4492> - web.dev
geoffo joined the channel
bterry joined the channel
#
IWDiscordRelay <capjamesg#4492> It is developer documentation, though.
oodani joined the channel
#
IWDiscordRelay <person#1903> Thanks for the tips KevinMarks and Murray! I'll look into Grids.
#
IWDiscordRelay <capjamesg#4492> James is thinking about standard avatar routes.
#
IWDiscordRelay <capjamesg#4492> It is technically redundant with microformats but interesting.
#
IWDiscordRelay <capjamesg#4492> (/avatar/ redirecting you to someone’s avatar)
gRegor and lagash_ joined the channel
#
@theshawe ↩️ hi @mappletons thanks for tweeting this. you're website is super inspiring. love seeing webmentions and the indieweb movement in thought. big up @joshm for helping hightlight your tweet into my feed! (twitter.com/_/status/1630841749537996800)
lagash, wagle and jjuran joined the channel
#
[KevinMarks] Did we have a newer version of https://microformats.org/2014/06/20/microformats-org-turns-9-upgrade-to-microformats2 listing all the failed silo metacrap?
gRegor and IWSlackGateway joined the channel
rocto_, pharalia, jan6, wagle, klez_, saptaks, sivoais, Kaja, oxtyped, [Murray] and [schmarty] joined the channel
#
[schmarty] Oof
#
[schmarty] (Oof for the owncast web UI rewrite into a huge React stack)
[jacky] joined the channel
#
[schmarty] React is good at being popular! And sometimes popular is needed.
[KevinMarks], [tantek] and geoffo joined the channel
#
[schmarty] The maintainer was using Preact earlier and, according to the post, not attracting contributors
[snarfed] joined the channel
#
IWDiscordRelay <jacky#7226> yeah ^
#
IWDiscordRelay <jacky#7226> I'm just griping tbh
#
[schmarty] my understanding is that using native HTML UI is far from the first thing React (and similar) frameworks teach. most from-scratch stuff is going to be div-soup in terms of markup. Beyond labeling there tends to be a lot of show/hide and focus-related behavior that requires extra layers of understanding and handling.
#
Loqi It looks like we don't have a page for "OpenUI" yet. Would you like to create it? (Or just say "OpenUI is ____", a sentence describing the term)
#
[schmarty] i am griping because owncast felt _almost_ in a state where i'd want to use it (i really want to be able to shut off or reduce the server usage when the stream is offline), but the knowledge that there's a big React stack waiting if i want to customize is something i am prejudiced against. :}
#
[schmarty] tantek: i don't believe the "pretty" was the main goal so much as streaming video putting the emphasis on _Single-Page_ in SPA.
#
[tantek] Aaronpk, https://open-ui.org/
#
[schmarty] (which is why the Islands Architecture doesn't go far enough, and why we should return to framesets. in this talk I will-)
geoffo and gRegor joined the channel
#
@TonyVlcek #Webmention: Nice example of how a very simple protocol can be used to do cool things.
Here's an article with more details: https://nicolas-hoizey.com/articles/2017/07/27/so-long-disqus-hello-webmentions/#how-does-it-work-on-this-site
When I get around to revising @SnoofaSoftware's blog, this will definitely get pulled out of my back pocket. (twitter.com/_/status/1630982864811458561)
gRegor, [pfefferle], cambridgeport90, [aciccarello] and [campegg] joined the channel
#
@SanSYS ↩️ Благодаря этому узнал, что такое web mentions и индивеб: "Webmention is a simple way to notify any URL when you mention it on your site"
https://www.w3.org/TR/webmention/#h-abstract (twitter.com/_/status/1631001689854541847)
geoffo joined the channel
#
IWDiscordRelay <capjamesg#4492> [ender] I'll maybe release Trackback support in IndieWeb Utils in the next week.
#
IWDiscordRelay <capjamesg#4492> [ender] https://github.com/capjamesg/indieweb-utils/pull/90
#
IWDiscordRelay <capjamesg#4492> Does anyone have any feature requests for IndieWeb Utils?
#
IWDiscordRelay <capjamesg#4492> Should profile photo discovery be in there?
jjuran joined the channel
#
IWDiscordRelay <capjamesg#4492> IndieWeb Utils has broader scope than mf2util.
#
IWDiscordRelay <capjamesg#4492> It isn't exclusively for mf2 tasks, and even mf2 tasks often have a lot of helper work that goes on (endpoint discovery, validation, etc.).
#
IWDiscordRelay <capjamesg#4492> (Where "validation" refers to things like URL canonicalization, checking status codes from responses, etc. It doesn't do mf2 validation to be clear.)
gerben joined the channel
#
IWDiscordRelay <capjamesg#4492> [barnaby]
