#meta 2025-06-15

2025-06-15 UTC
aaronpk joined the channel
#
Loqi [github] Successfully deployed aaronpk/IndieNews to https://news.indieweb.org
#
Loqi [github] Successfully deployed aaronpk/IndieNews to https://news.indieweb.org
#
Loqi [github] Successfully deployed aaronpk/IndieNews to https://news.indieweb.org
#
aaronpk ok we now at least have the infrastructure to block URLs and domains from indienews. no UI for it tho
[schmarty] joined the channel
#
[schmarty] aaronpk++
#
Loqi aaronpk has 34 karma in this channel over the last year (117 in all channels)
#
[tantek] aaronpk++
#
Loqi aaronpk has 35 karma in this channel over the last year (118 in all channels)
barnaby, c3project, strugee, San, balintm and Guest6 joined the channel
#
jak2k.eu edited /GitHub (+86) "/* Self-hosted alternatives */ Add Forgejo" (view diff)
#
jak2k.eu created /User:Jak2k.eu (+90) "Created page with "Hi, I'm [https://jak2k.eu Jak2k]. My previous profile is [[User:jak2k.schwanenberg.name]]."" (view diff)
barnaby, balintm and [artlung] joined the channel
#
gRegor [artlung], Possible FrESH topic I just got curious about: best practices for `alt` when using `picture` element. In some of the MDN examples I only see it on the `img` tag, wondering if that works for screenreaders if one of the `source` tags are used, though.
#
[tantek] ^ maybe a variant of that too, like how do / should mf2 parsers (in addition to screen readers) see / associate such alt attribute best practices?
#
[artlung] Fine idea(s)!
#
gRegor Some discussion on mf2 in https://github.com/microformats/microformats2-parsing/issues/54 (and linked issues from there)
#
Loqi [preview] [Seirdy] #54 Support `<picture>` element
#
[tantek] Yes thank you for the link!
balintm and [manton] joined the channel