#dev 2025-05-21
2025-05-21 UTC
jeremycherfas, grufwub and gRegor joined the channel
claudinec, GuestZero_, barnaby and jjuran joined the channel
# 
capjamesg [artlung] I now have https://playground.jamesg.blog/
jjuran and karjala joined the channel
barnaby joined the channel
# 
[jeremycherfas] I’m struck, once again, by how little I understand under the hood. Looking at `php_error.log` for one thing in particular, I notice all sorts of warnings and fatal errors that I never notice looking at my own sites. Now I wonder, is it worth tracking those things down and fixing them? And in general, how do people make use of `php_error.log` if they are not actively trying to fix something?
Guest6_, barnaby and btrem joined the channel
ttybitnik joined the channel
# 
[KevinMarks] You could read the code or step through it while it formats some examples https://github.com/moment/moment/blob/develop/src/lib/format/format.js
# 
btrem I did consider reading the code, but I don't know what I'm looking for, since I've never done anything like this. And I'm very much an amateur, so I think it'd be hard to recognize. Same thing with stepping through it. I know my editor can debug -- I can put stop points in code -- but I've never actually done it.
[tw2113] joined the channel
# capjamesg [tantek] I have written a blog post about the edit button browser extension: https://jamesg.blog/2025/05/21/building-an-edit-button-browser-extension
# capjamesg [edit] [tantek] I have written a blog post about the edit button browser extension: https://jamesg.blog/2025/05/21/building-an-edit-button-browser-extension
duanin2 joined the channel
# 
[tantek] Yup, it's part of Interop 2025: https://bugzilla.mozilla.org/show_bug.cgi?id=1948295
PsyLok joined the channel
# 
[aciccarello] btrem, is that a repo specific label?
# [aciccarello] I'm not sure what a lite bug would mean 😂
# [aciccarello] I'm thinking of fireflies now
# perryflynn Bug with low or none impact I guess? 🤷♀️
[aciccarello] joined the channel
gRegor and ttybitnik joined the channel
# btrem Here's the issue if you're interested: https://github.com/11ty/eleventy/issues/3788
# [aciccarello] Ah, here's the label description: "Debatable whether or not this is a bug. I mean, it’s not great but it’s not really broken either."
# [aciccarello] Zach is so chill 😆
# [aciccarello] Yeah, probably bigger than the tag description implies but not a show stopper for most people.
[schmarty] and NaomiAmethyst joined the channel
# 
[artlung] Working on a silly digital clock today. https://codepen.io/artlung/pen/gbbVggK Just the harness for clock parts now. Eventually I want to make it work with CSS only which I *think* will be possible.
duanin3 joined the channel
# perryflynn Cool. 👍
# [tantek] aaronpk I believe I found a bug in http://webmention.io maybe due to out of date mf2 parser! Compare https://pin13.net/mf2/?url=https%3A%2F%2Fartlung.com%2Flikes%2F923b8a5dec6db81dda6488c3ba5092a4 to https://ruby.microformats.io/microformats?utf8=%E2%9C%93&url=https%3A%2F%2Fartlung.com%2Flikes%2F923b8a5dec6db81dda6488c3ba5092a4 - note h-entry u-like-of property has an explicit 'value' in the latter with a URL and not in pin13 (and thus
# [tantek] this results in this like: https://artlung.com/likes/923b8a5dec6db81dda6488c3ba5092a4 being treated only as a "mention" by wmio when I call the API
# [tantek] this is due to the older parsers not knowing about how to handle u-* properties with an embedded object like h-cite, must re-use the u-url of that embedded object as the plain 'value' of the u-* property per “if that child element itself has a microformat ("h-*" or backcompat roots) and is a property element, add it into the array of values for that property as a
{ } structure, add to that { } structure: value: ” in# [tantek] This led down a rabbithole on http://microformats.io with several of the subdomains being broken in various ways, e.g. php. and ruby. (home page)
# 
aaronpk is the php parser out of date? the latest release is 0.5.0 which is what's on php.microformats.io https://github.com/microformats/php-mf2/releases
[capjamesg] and balintm joined the channel
# perryflynn I always use "found" / "temporary" because it screwed me multiple times in the past when I wanted to change a permanent redirect for reasons.
# perryflynn permanent redirects are cached in clients browser. so I can't change the behavior for a unspecified amount of time.
# perryflynn benefit is that the client is doing the redirect without talking with the server, so one redirect less, but that can be the problem at the same time.
# perryflynn if you want to change the redirect target.
# perryflynn maybe not a problem for permalinks. but...
# perryflynn *one request less
# 
balintm i'm thinking the way i'm managing permashortlinks now is stable enough to use 301. MDN says about 301 "Search engines receiving this response will attribute links to the original URL to the redirected resource, passing the SEO ranking to the new URL", which, not a *real* concern with the kind of traffic i'm driving through search (~0), but it still feels better in the long term to consider that
# perryflynn 👍
# perryflynn yw
# perryflynn Regarding CSS challenges, I created a Simon says clone some time ago: https://guenther.serverless.industries/
thegreekgeek and gRegor joined the channel
# 
gRegor Ah, the wm for that like was received before those updates too (I think?) 2025-05-02: https://webmention.io/api/mentions.jf2?target=https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland
# gRegor I just re-sent it and it shows as a like: https://webmention.io/tantek.com/webmention/F9-_NVIXhurndupKGDXK
# gRegor Oh, this is coming back to me a bit: https://indieweb.org/events/2025-05-14-hwc-americas
# gRegor Ah good, we did document that on /XRay "The instance of XRay run by Aaron Parecki at https://xray.p3k.app is used by webmention.io to parse comment text, and used by Loqi to display a text summary of URLs in the IRC channel."