#Seirdy<audio> should support video tracks but not display the video, <video> should support audio (maybe display a waveform?), <img> should support <video> but make it non-interactive.
#[KevinMarks]Apple supports jpeg 2000, no one else does. Which is a bit of a shame as it had some nice characteristics
#[KevinMarks]Like reducing detail by truncating the bitstream
#[KevinMarks]So you could use the same file for multiple resolutions, just read enough as you need, though that would mean changing the fetch/render split in browsers.
#[KevinMarks]So that "blurry placeholder" thing that Medium vs others were dying a while ago could happen automatically.
#[KevinMarks]But you'd need to couple your http2 reading with the image size decision code.
#jamietanna[m]Yes thanks was good to see your thoughts ☺ will see if there's anything to apply into this version. Is Parse This hosteable somewhere? Would be good to have the same hosted service idea for it so others can consume it
#GWGjamietanna[m]: I host it inside every site equipped with it..I suppose that I could do a public instance
#jamietanna[m]Yeah I guess I'm thinking more a public way of sending an arbitrary url and getting the response in/from the various formats you support
#Loqi[snarfed] has 31 karma in this channel over the last year (62 in all channels)
#e-snaildo any regular chat users have a static site gen setup?
jacky joined the channel
#[schmarty]1e-snail: my site is primarily hugo-powered. i have a micropub endpoint based on https://github.com/skpy/micropub which writes files to a git repo. that git repo triggers a webhook on my "publisher". the publisher pulls the latest from git and does some updates to the hugo data, builds the site, syncs the changed output files, sends webmentions and websub notifications.
#Loqi[skpy] micropub: a minimal PHP micropub endpoint, with media support
#e-snail[schmarty]1: this is the kind of setup I'm envisioning (right now all I have is that commits to content repo auto-rebuild the site)
#e-snailI'm gonna be stealing a lot of ideas from you I think :)
#e-snailsomething I'm not clear on about webmentions: how are multiple sends dealt with? For my case, if I lose or mess up the cache, seems like that'd result in re-sending all the webmentions over again
#sknebellike, dont send webmentions for your entire site every time you do anything on it (not that people also haven't done that...), but yeah, receivers are expected to handle repeats. E.g. if you edit a post, you also inform linked sites that you did by just resending the same thing
#@marcthieleUnsubscribed from all RSS Feeds that only deliver their headlines or headline and a very small excerpt. Really like the idea of reading the whole post in the feed actually and being forced to visit the website and leave my reader. (twitter.com/_/status/1503679968580182023)
#Murray[d]e-snail: I have a couple of microsites that I consider all the same site, based on subdomains e.g. lp.theadhocracy.co.uk
#Murray[d]I built my main site in Gatsby, but by the time I started working on the other bits and pieces I preferred NextJS. This way, I can rebuild the parts of the site that make sense, rather than wasting build minutes on everything
#Murray[d]I've really liked this pattern and plan to continue breaking my site up. I'll likely split my journal and reviews out of my main site this year and use that opportunity to dig into Eleventy and web components a bit more
#Murray[d]thanks to Netlify's use of web hooks, I just have some buttons in my CMS (Craft) that will trigger the rebuilds that I need. I'm considering adding some automation to this in the future, but right now manually hitting those buttons works well enough
#e-snail[aciccarello]: thanks, I saw that; I'm hoping to find the intersection of those (and the other static* pages) and people who spend a lot of time in chat :)
#[aciccarello]Yeah, I just realized that I could add myself to that page today 😁
#jamietannae-snail I use Hugo, and for a while I was webmentioning everyone from every page, on every site deploy. It got better, but I think it's still in a bit of a broken state, sending more webmentions than needed
diegov joined the channel
#[schmarty]1for webmentions (and other things that should only happen on new/changed pages), i have been really happy with `rsync -i`
#[schmarty]1it outputs a line for each new/updated/deleted file with a little summary of what changed
#[schmarty]1so after the hugo build, my publisher does an rsync to the actual place the files are served from and rsync provides that nice list of what actually changed. the publisher then uses that list to only send webmentions, websub updates, etc. for new or updated pages.
#[schmarty]1(it would totally send out webmentions for every page if i made a template update that affects each page, though. i have a threshold check that skips webmentions if the changed files list is thousands long)
#LoqiWebmention is a web standard for mentions and conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web https://indieweb.org/webmentions