#dev 2025-07-09

2025-07-09 UTC
grufwub, troojg, bugliker020, rrix and veqq joined the channel
#
veqq huh, another big channel, nice
[snarfed]1, [mattl]1, jak2k and [pfefferle] joined the channel
#
perryflynn is it possible in css to start the underline of a text n pixels before the text without using non-breaking spaces?
duanin2, jak2k and [KevinMarks] joined the channel
#
[KevinMarks] I don't think there are properties for that. Medium used to do it in js and have some more control over it. Marcin wrote that up here https://medium.design/crafting-link-underlines-on-medium-7c03a9274f9
#
perryflynn I did it now with padding and border-bottom and removed text-docoration.
rozodru joined the channel
#
mandaris You might want to look at `text-underline-offset`. I use it on my website to give it a little more space than the default.
jtwoodhouse joined the channel
#
[snarfed] I've been talking with someone a bit about the difference between u-photo and u-featured for articles, and whether/when Bridgy Publish should include those images as attachments on its POSSE copies. https://github.com/snarfed/bridgy/issues/1934
#
[snarfed] (mf2 background: https://microformats.org/wiki/h-entry#u-photo , https://microformats.org/wiki/h-entry#Proposed_Additions )
#
[snarfed] right now, Bridgy Publish includes both u-photo *and* u-featured as attachments, but I'm thinking it shouldn't do that for u-featured. thoughts?
jak2k joined the channel
#
[tantek] [snarfed] pretty sure I made that request before, and I believe you rejected it saying that users wanted the featured photo to show up in their POSSE destinations (perhaps Twitter?)
#
[tantek] so it's good to see it come around. yes, u-featured should not be POSSEd on its own as a "photo" (attachment) in destinations that support showing an embedded photo.
#
[tantek] that is u-featured should not trigger making an attachment, but neither should it block it
#
[tantek] i.e. if someone has class="u-featured u-photo", that should still work, and ideally, all u-featured u-photo images should be attached *before* other u-photo images, which matters for image attachment limits, e.g. if the destination has attachment limitations (1 photo, 4 photos Twitter, 20 photos IG etc.)
[schmarty] and gRegor joined the channel
#
gRegor btrem, sorry for the bad news about gcal. I can relate to the frustration of it getting more and more complex.
perryflynn, [mattl] and GuestZero joined the channel
#
[snarfed] hah [tantek] looks like you actually asked for the opposite, ie attach u-featured if there's no u-photo 😆 https://github.com/snarfed/bridgy/issues/741
#
Loqi [preview] [tantek] #741 Bridgy Publish to Twitter should consider u-featured fallback for u-photo for article use-case
#
[tantek] 🙈
#
[tantek] and yet 😆 https://github.com/snarfed/bridgy/issues/741#issuecomment-293325007
#
Loqi [preview] [snarfed] done! for all silos, not just twitter. :P cc @miklb. (i ended up just adding `u-featured` onto the AS1 `image` field that `u-photo` already goes into.)
#
[snarfed] oh sure, I obviously did it 😁
#
[tantek] I should have been more explicit for Twitter-only is what I meant, not really having figured out the repercussions for doing it everywhere lol
#
[snarfed] I guess. product behavior for those silos has also evolved a lot over the last 8y, built in rich link previews are now much more common
#
Loqi +1
#
[tantek] another thing to capture is the reasoning of "this is here to overcome a current limitation" so that it can be re-evaluated when the limitation changes
#
[tantek] yep
GuestZero_, barnaby and GuestZero joined the channel
#
[KevinMarks] Having another day of "have I found all the ways that AWS is stopping these 2 servers communicating yet? Ah, not yet"
#
[KevinMarks] It's like the exact opposite of tailscale
#
[snarfed] sigh yup. sometimes I never figure it out, and have to resort to workaround like this from just yesterday 😕 https://github.com/snarfed/bridgy-fed/commit/3eeeb42d24175e14f528ec2b54765919bb84e244
oodani, thegreekgeek_, btrem and gregsarjeant joined the channel