#microformats 2021-04-28
2021-04-28 UTC
[KevinMarks], [tw2113_Slack_], [mapkyca], jeremy, Seirdy, hendursaga, [Rose], jalcine[m], jamietanna[m], batkin[m], [Murray], [grantcodes] and barnabywalters joined the channel
# 
barnabywalters !tell snarfed is there a way to get bridgy to re-try sending failed webmentions, or to filter the list of detected mentions to show only the failed ones? I just fixed an old bug in my webmention endpoint, and ended up scrolling through many pages of twitter reactions to find and manually resend the failed ones
# barnabywalters ah oops I’m in the wrong room again :( still not used to IRC
# barnabywalters !tell snarfed (apologies for the message in the wrong room, should have been in -dev)
# barnabywalters sknebel: nice that the list is marked up, but it’d take longer to do that than to just scroll through and manually resend, at least in my case where there were only about 20 missed mentions
# barnabywalters fortunately I don’t have a very large twitter following
[schmarty], [snarfed] and [aciccarello] joined the channel
# barnabywalters yep, back when I was up to date on how mf2 parsing worked. I just had to check the spec to fix an error in my markup
# barnabywalters in this case it was a detail about how implied u-url is parsed, where no implied properties are parsed if any explicit properties are given
# barnabywalters and I had <a class="h-card" href="…"><img class="u-photo" src="…" /> Name</a>
# barnabywalters the explicit u-photo was preventing the implied u-url from being parsed
# barnabywalters so either that’s new (as in, happened in the apst 5 years) or php-mf2 only recently correctly implemented it
# barnabywalters nope, that makes sense though, as does the change to parse out the id attribute
# barnabywalters hmm yeah that must be a tricky issue
# barnabywalters I vaguely remember wanting to have an option on php-mf2 which included references to DOMElement objects within the parsed structure, so that users could get additional information like this out of the DOM from within the parsed structure
# barnabywalters tbh I had completely forgotten that srcset existed
[tantek] joined the channel
# barnabywalters the one use case which comes to my mind immediately is profile photos, which get displayed in many different contexts and could actually benefit a lot from offering different options
# barnabywalters maybe I’ll mark up my profile photos with srcset to add to the list of real-world examples
# barnabywalters hmm anyone know if it’s necessary to use @srcset and @sizes together? because @sizes seems to only allow for switching between sources based on the screen width, not the size of the <img>
[calumryan] joined the channel
# barnabywalters https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images implies that they must be used together for the multiple sizes use case
# barnabywalters hmm but according to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-srcset the user agent will pick from srcset at its discretion
# 
sknebel https://github.com/microformats/microformats2-parsing/issues/7 <- actually, last state was "looking for example implementation" missed that development
# barnabywalters so it looks like @sizes is only there to offer more control
# barnabywalters oh looks like sknebel already mentioned the srcset/sizes thing in that issue
[schmarty] and [KevinMarks] joined the channel
# 
[KevinMarks] I did do srcset in the profiles on willsomeone when that was up
# [KevinMarks] though that was using the 1x 2x 3x 4x syntax
# [KevinMarks] <img class="u-photo" src="/i/109952187676595057153?width=190" srcset="/i/109952187676595057153?width=380 2x, /i/109952187676595057153?width=540 3x" width="190px">
# barnabywalters okay, I now have srcset on my profile h-card at https://waterpigs.co.uk/, and new notes and articles from now on will also have srcset attributes on their pages
[grantcodes] joined the channel
# 
[grantcodes] I have a use case for srcsets (I think) - I have galleries of images which I upload full res and automatically resize, but it makes sense to expose the full res images to machines. I did this and caused crashes in peoples readers because it loaded a huge set of large images. Now I deliberately hide the full res image from microformats.
# [KevinMarks] didn't realise that was still running 6 years later
# barnabywalters [KevinMarks]: heh, I had a similar realisation today, when I discovered that my indieweb yahoo pipes clone prototype was still running
# barnabywalters so both of those beat the average google product https://reclaimthenet.org/average-life-google-product/
# barnabywalters hmm interesting, on this page, my profile photo is used both in the reply context and the note author h-card. the reply context has no srcset and loads the largest version of the profile photo. the author h-card photo has a srcset which includes the already-loaded larger image, but firefox chooses to load a new, smaller image too https://waterpigs.co.uk/notes/5CRDG2/
# barnabywalters so more data is being loaded than would be if srcset wasn’t in use
# barnabywalters in this case where @sizes isn’t used (and therefor the art direction use case most likely doesn’t apply), I’d expect browsers to reuse images they already loaded rather than load smaller ones additionally
# barnabywalters think it’s worth making a FF bug report for this?
# barnabywalters ah, true, the second request isn’t coming from there, it’s coming from the profile photo in the top left
# barnabywalters …and there was an error in that URL anyway. looks like FF works as predicted and the problem was with my site
# barnabywalters no surprises there
tomlarkworthy joined the channel
# barnabywalters re how to document the philosophical change to how microformats are developed on the wiki (from indieweb-chat)…
# barnabywalters a practical method might be to make a “see also”-style template which we can put at the top of pages like http://microformats.org/wiki/species, saying something like “This page is outdated and inactive, and no longer represents the current approach to microformat development. For more information, see [link to page describing current values]”
jamietanna joined the channel
# barnabywalters ah yeah /process is the perfect page to link
# barnabywalters it looks fairly up-to-date
# barnabywalters huh, still no indieauth login on the microformats wiki
# 
[tantek] barnabywalters now captured in its own section at least: https://microformats.org/wiki/admin-to-do#IndieAuth_login
# barnabywalters created /Template:inactive (+253) "Created, draft of template for old, inactive pages" (view diff)
# barnabywalters ^^^ is that dramatic enough, do you think?
[chrisaldrich] joined the channel
# barnabywalters edited /species-brainstorming (+14) "Added inactive template per discussion in IRC" (view diff)
# [tantek] barnabywalters, we do already have a /Template:warning — perhaps consistent styling with that?
# barnabywalters good idea
# barnabywalters although the one I made is a bit more readable. the contrast on /Template:warning is a bit nasty
# barnabywalters okay, will do
# barnabywalters hmm I also just noticed that http:// doesn’t redirect to https://microformats.org
# barnabywalters it’s minor, but might be another thing for the admin to-do list
# barnabywalters ah, okay
# [tantek] we need to update https://indieweb.org/HTTPS#Level_3_security accordingly
# barnabywalters edited /Template:warning (+54) "Changed styles for readability, consistency with Template:inactive" (view diff)
Seirdy joined the channel
tomlarkworthy1, [Ana_Rodrigues], [tw2113_Slack_], [calumryan], Seirdy, [snarfed], [chrisaldrich], tomlarkworthy and [aciccarello] joined the channel