#dev 2025-11-21

2025-11-21 UTC
CrimeWave, gRegor, grufwub, barnaby, Kupietz, lanodan and PrehistoricWeeb joined the channel
#
[artlung] Kicking it old school and amplifying a stackoverflow question about algorithms rss feedreaders use. https://stackoverflow.com/questions/1140307/what-are-the-valid-html-tags-in-rss-feeds https://xoxo.zone/@artlung/115585601176576221 https://bsky.app/profile/artlung.com/post/3m64e7rjowk2i
DanQ, [Trevor_Morris], srazkvt, GuestZero, vriska and [marksuth] joined the channel
#
dibblethewrecker Previously used this iOS shortcut to get an IndieAuth token (it uses POST) but I reckon the IndieAuth spec has changed since I last used it because it fails with:
#
dibblethewrecker `Missing parameter(s): code_challenge, code_challenge_method`
#
dibblethewrecker So far I've managed to partially fix with `code_challenge_methods=S256` but no idea what I need to do put in `code_challenge=`
#
dibblethewrecker [edit] Previously used this iOS shortcut to get an IndieAuth token (it uses POST) but I reckon the IndieAuth spec has changed since I last used it because it fails with:
#
dibblethewrecker So far I've managed to partially fix with `code_challenge_methods=S256` but no idea what I need to put in `code_challenge=`
#
dibblethewrecker `Missing parameter(s): code_challenge, code_challenge_method`
thegreekgeek joined the channel
#
dibblethewrecker The process for getting a token has obviously completely changed! I'll report back...
barnaby, Dryusdan, jak2k, sp1ff and vidak joined the channel
#
aaronpk that's PKCE, I am not sure the best way to do that with an iOS shortcut...
[schmarty] joined the channel
#
[schmarty] just hardcode a challenge and it's sha into the shortcut 😎
#
aaronpk 🙈
#
aaronpk https://example-app.com/pkce
#
[schmarty] 👏😎
#
aaronpk just for the record, this will work, but I do not endorse it 😂
#
[schmarty] Shortcuts could also work with a tiny web endpoint. A GET generates the verifier. POSTing a verifier returns the hashed and encoded challenge.
#
[artlung] I am looking at how my indienews entry shows in the newsletter and it seems off. I also notice there are two url values. https://pin13.net/mf2/?url=https%3A%2F%2Fartlung.com%2Fblog%2F2025%2F11%2F17%2Fhwc-eastern-weds%2F
#
[artlung] https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fartlung.com%2Fblog%2F2025%2F11%2F17%2Fhwc-eastern-weds%2F
#
[schmarty] Ooh, here is someone who has gone through some PKCE + Shortcuts pain. https://www.reddit.com/r/shortcuts/comments/nejwrs/why_does_shortcuts_sha256_andor_base64_give_me/
#
[artlung] Can anyone make a recommendation for a fix?https://artlung.com/blog/2025/11/17/hwc-eastern-weds/
DanQ1 and Ren1 joined the channel
#
aaronpk just commented on that thread schmarty
#
[schmarty] ooh, nice! aaronpk++
#
Loqi aaronpk has 53 karma in this channel over the last year (132 in all channels)
[social]2, [tantek]2, [morgan]1, [Trevor_Morris]1, geoffo, vriska_, [jeremycherfas]2, Xe_, ben and Maxpm joined the channel
#
[artlung] I was looking at my indienews post from october vs the one this week and I don't see a difference, even though on the most recent one doesn't pick up the title right
#
[artlung] https://pin13.net/mf2/?url=https%3A%2F%2Fartlung.com%2Fblog%2F2025%2F10%2F07%2Ffresh-028%2F (worked)
#
[artlung] https://pin13.net/mf2/?url=https%3A%2F%2Fartlung.com%2Fblog%2F2025%2F11%2F17%2Fhwc-eastern-weds%2F (didn't work)
#
[artlung] https://artlung.com/blog/2025/11/17/hwc-eastern-weds/
#
[artlung] https://artlung.com/blog/2025/10/07/fresh-038/
#
Loqi [preview] [Joe Crawford] Announcing Front End Study Hall #038
#
[artlung] anyone have an idea as to why and if there's something I can do about it - it affects how it displays in the newsletter, is the reason I ask
shoesNsocks and gRegor joined the channel; shoesNsocks left the channel
#
[tantek]2 👀 taking a look...
barnaby and opencircuit joined the channel
#
[tantek]2 very curious, the microformats (h-entry) do look correct or just fine [artlung]
#
[artlung] I note mine is not the only entry whose titles did not come through to the display.
#
aaronpk i should just take out this code at this point
#
aaronpk it's removing the "name" property because the text of the "name" property is the same as the start of the text in the "content" property
#
Loqi +1
#
[artlung] Fascinating. I will make an adjustment and retry.
#
[tantek] sorry I followed up in #indieweb-meta
#
aaronpk it's a holdover from the implied p-name parsing rules which i think we abandoned a long time ago
#
[tantek] yes edit the post content
#
[tantek] aaronpk, I don't think we abandoned them, I think they're still in post type detection
#
[tantek] start content with something like "Homebrew Website Club/Eastern is at 6pm EST on Wednesday …" as a slight variant of the article name
#
aaronpk hm yes it is in there, but i thought it was there because of a mf2 parsing rule that is no longer there
#
[tantek] right, separate issue aaronpk, probably needs its own issue in GH to track
#
aaronpk ah true
#
[artlung] updated. I am so glad I didn't make any markup changes to chase this
#
[artlung] [tantek]++ thanks to you both [aaronpk]++
#
Loqi [tantek] has 36 karma in this channel over the last year (155 in all channels)
#
Loqi [aaronpk] has 54 karma in this channel over the last year (133 in all channels)
#
[tantek] nailed it [artlung], just in time: https://news.indieweb.org/en
#
aaronpk [artlung]: if you're ever curious about what things like indienews or aperture are doing with your post, run it through https://xray.p3k.app/ instead of the mf2 parser, that's where all the "business logic" like post type discovery happens
#
[tantek] makes me think the h-entry validator in http://IndieWebify.me should provide this information
#
aaronpk when i put your post into xray it was missing the "name" and that was the clue
#
[tantek] e.g. https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fartlung.com%2Fblog%2F2025%2F11%2F17%2Fhwc-eastern-weds%2F
#
[artlung] I am guessing this code is to account for those micro posts which don't *really* have titles but were forced to so include a substring from the front.
#
[tantek] IMO the h-entry validator is the place to put "smarts" like that with more prose explaining what is going on
#
[tantek] [artlung] this practice is from the need for publishers to put a non-empty name (title) on a post so their posts don't "look bad" in certain legacy RSS readers
#
[artlung] "but were forced to so include a substring from the front _because of legacy RSS readers_" - or other syndication use cases I presume. yes.
#
[tantek] so the way to publish a "note" post with maximal reader compatibility (don't punish your users) was to put enough of the content of the note into the "name" property so "something" sensible shows up in their feed readers
#
[tantek] yes I do this on my notes
#
[tantek] p-name and e-content on the same element
#
[tantek] again, for compatibility with some readers
#
[artlung] my tale as old as time was that my posts from Blogger did not have titles and when I did my import to WP (decades ago) I made changes to accommodate that and I started with replicating the first sentence as the title.
#
[tantek] yeah! part of the point of notes was to follow the footpath from Blogger of no-title posts!
#
[tantek] in this case though, that first "sentence" (words terminated by a period) is not actually grammatically a sentence. it's a noun phrase, which makes sense for an article name/title but not (or rarely?) for the first "sentence" of content.
DanQ and barnaby joined the channel