#dev 2026-08-04

2026-08-04 UTC
ax562, grufwub, [tw2113], [Mike], jjuran, d1s1nf3c1, d1s1nf3ct, [tantek], [jeremycherfas], thatoddshade, oxtyped, vidak, paultibbetts, [schmarty] and deathcomestotime joined the channel
#
[snarfed]
hi all! I'm working with IndieAuth, and I'm trying to determine if a logged in user is authoritative for / controls the whole domain itself, not just a single user on it
#
[snarfed]
ideally i'd just check if me=https://[domain]/ ... but it seems like lots of big IndieAuth providers still return individual users on the domain, eg https://[domain]/author/[name] for wordpress
[pcarrier] joined the channel
#
[pcarrier]
[snarfed] technically IndieAuth is per-URL not domain. When would you expect multiple users on a root?
#
[snarfed]
right, I know. still my use case though ๐Ÿ˜
#
[pcarrier]
So accept only /?
#
[snarfed]
I don't have examples offhand but there are multi-user IndieAuth sites out there. it's how the WP plugin works by default
#
[pcarrier]
right but each user gets a different path right
#
[snarfed]
yeah but I suspect the pattern of always returning a non-root path is common enough that I'd block out many sites
#
[pcarrier]
wellโ€ฆ what's the property you're after? owning the domain would be having auth on / no?
#
[snarfed]
right. so, I expect one common case is a WP single-user site where its IndieAuth plugin currently returns non-root me ๐Ÿ˜•
#
[snarfed]
ideally I could just check that IndieAuth returns the root URL as me. but again, I suspect that's not widespread enough right now
#
[pcarrier]
sorry what do you mean by "me"?
#
[snarfed]
the me field in the access token response, which identifies the authenticated user. https://indieauth.spec.indieweb.org/#access-token-response
#
[pcarrier]
OK so you have auth providers on / that let multiple users claim they control /, but with different `me` fields on the access token, and you don't want that to be possible?
#
[snarfed]
the auth provider doesn't let multiple users claim they control / . each user will have a different `me` field that identifies them. the auth provider is expected to return a different `me` URL for each user
#
aaronpk
the only thing i can think of is check if me == https://[domain]/ OR make up some new thing that describes user role
#
[snarfed]
aaronpk yeah agreed
#
[snarfed]
I pinged the WP people in #indieweb-wordpress, I'd like to normalize returning root as me more often for single-user sites, but that may be a difficult change to drive
#
[snarfed]
I can't even get WP to return root as me _at all_ right now ๐Ÿ˜•
[Trevor_Morris] and doesnm_ joined the channel
#
[tantek]
[snarfed] re: "a native mastodon post, https://indieweb.social/@snarfed/117033435495271439 , has the same problem, the numbers-only hashtag isn't recognized" โ€” have you tested similarly on Bluesky? Curious if it behaves the same way
#
[tantek]
[snarfed] also noticed your numbers-only hashtag post in Mastodon results in an *unlinked* hashtag for that case, whereas in my post, the numbers-only hashtag is linked but goes to a 404 page on Mastodon.
#
gRegor
looks like you're publishing actual links to indieweb.social tag pages inside your `e-content`, so those are preserved in the Mastodon post, separate from the tag metadata, which appears under the Mastodon post. I don't see any of the latter on your Mastodon posts.
#
gRegor
If you search my profile on indieweb.social and see my blaugust post, my tags aren't in the e-content and show up underneath the link preview
#
gRegor
Same applies to notes
#
[tantek]
fascinating
#
gRegor
I would still expect BF to be processing your `p-category` tags and sending them through, though. Odd.
#
[tantek]
I think BF is doing that, [snarfed] looked at the AS2 JSON and confirmed that I believe.
#
gRegor
I think I have an older example where I did link a hashtag in the post, then also included the p-category *outside* of the content, and it showed up both places. Let me search.
#
[tantek]
I think there are two things going on. 1. Mastodon is "filtering" a numbers-only hashtag at text-entry UI, not linking it or turning it into a tag in its internal representation. and 2. Mastodon is refusing to create a page for a numbers-only hashtag that it received from another server
#
[snarfed]
here's the equivalent Bluesky test. looks like it requires at least one letter. https://bsky.app/profile/did:plc:3ljmtyyjqcjee2kpewgsifvb/post/3msbmqtaqec2m
#
gRegor
Agreed, but the thing I'm interested in is your non-numeric hashtags aren't showing up in the regular tag metadata area, only in the content. Like I would expect a #Blaugust link under the link preview of your Dark Knight post, in addition to the one that does show up in the content.
#
[tantek]
none of my hashtags are showing up in the "regular tag metadata area" on indieweb-social
#
[snarfed]
also that Mastodon difference between "no results" and "404 not found" isn't specific to number hashtags. here are non-numeric examples: https://indieweb.social/tags/asdfqwer 404s, https://indieweb.social/tags/asdfqwer shows no results
#
gRegor
exactly, which is odd
#
[tantek]
[snarfed] interesting, I wonder if that's a decision or oversight. Since it means Bluesky supports fewer hashtags than Mastodon, I suspect oversight and if pointed out they'd fix it
#
[snarfed]
oh sorry, pasted the wrong url. https://indieweb.social/tags/snarfed shows no results
#
[tantek]
ok that's just weird
#
[snarfed]
maybe based on whether the instance has _ever_ seen a given tag, even if it's now deleted or aged out
#
[tantek]
and we don't care about twitter/x right? or did you also test there? wondering where else it makes sense to test
#
[snarfed]
I haven't tested elsewhere yet
#
[tantek]
[snarfed] looking more closely at BF to Bluesky, any idea why the poster image showed up for my Odyssey post but not my Dark Knight post on https://bsky.app/profile/tantek.com.web.brid.gy ? The markup is identical AFAIK, and both showed up in their Mastodon versions
MD87 and doesnm joined the channel
#
[snarfed]
interesting! actually no, the poster isn't an attached image on the Dark Knight fediverse post in Mastodon either. what you're seeing there is a link preview, which Mastodon generates, not BF
#
[snarfed]
[tantek] your odyssey post has u-photo but the dark knight post doesn't
#
[tantek]
fascinating ok that's weird, I'll have to do some investigation of how that happened
[rose] joined the channel
#
[tantek]
tracked it down. my code is only marking up the image as a u-photo if it's the first URL in my post. in the Dark Knight post I had linked to the Wikipedia article before the poster
#
[tantek]
and that's probably what's altering the link-preview behavior on Mastodon as well
doesnm and srazkvt joined the channel
#
[tantek]
[snarfed] another (positive) data point. I updated the number-only hashtags to use _ between the YMD components, and the updates made it to Mastodon, AND Mastodon tag pages for those now work! e.g. https://mastodon.social/tags/2026_07_18
#
[tantek]
with that test passing, I feel pretty confident about proposing that syntax for datetags
#
[tantek]
Bluesky will eventually fix it on their end and catch-up
#
[tantek]
[snarfed] the reason I thought the photo was being federated is because even the alt text shows up from my post on Mastodon! (e.g. at the above masto social tags link, click on the little black [ALT] button on the bottom right of the poster image, and it shows the text from the alt attribute in my post!
#
[snarfed]
right! the photo in the odyssey post *was* federated
#
[tantek]
[snarfed] and yet another positive "update" datapoint: I moved the Wikipedia link to the end of my Dark Knight post, refederated with BF, and it picked up the image, which now also shows up on Mastodon with the alt! So you can add an image and have it show up in an update. Top post in https://mastodon.social/tags/TheDarkKnight right now
#
gRegor
awesome
#
[tantek]
found an example in my past posts of using #YYYY_MM as well so that's going into the proposal
thatoddshade and joshproehl joined the channel