[dmitshur]I've realized there's a usability problem with just letting people sign in with their URL is that if they've previously left reactions, they'll lose all that state because their IndieAuth URL would effectively be a completely separate account.
[dmitshur]Ideally, I would have some UI where you can explicitly choose your preferred identity out of many (e.g., "example.com" or "github.com/user"), but perhaps I can take a UI-less shortcut by using the heuristic: if you sign in as X (instead of Y), then X is your current identity until you sign in via Y.
KartikPrabhu, [manton], [Michael_Beckwit and [dmitshur] joined the channel
[dmitshur]On a different but related note, "https://example.com/user" and "https://example.com/user/" are technically different URLs. It seems weird to let 2 completely different people differ only by a trailing slash. But https://indieauth.spec.indieweb.org/#url-canonicalization allows it.
[dmitshur]Marty's website claims he is "https://github.com/martymcguire/" (note the trailing slash) on GitHub. I think I should handle that no different than if he left out the trailing slash, since that URL does show his profile. I wonder what I should do if someone has a rel="me" url="https://github.com/example/repo-or-some-such"... I imagine I would reject that, since a repository isn't a GitHub user.
aaronpkyou will probably have to make special cases for GitHub or sites with usernames if they serve the profile page from multiple URLs without redirecting. Check if they use rel=canonical tho
[schmarty]dmitshur: good tip about canonical GitHub URLs! I have it in my head that they are inconsistent about when they allow or disallow trailing slashes. 🤔
[dmitshur][aaronpk]: Thanks! I'm fairly aware of redirect following (although implementing much of that is still a known TODO), but it doesn't help with GitHub because they don't redirect.
[dmitshur]Great idea about rel=canonical though. I checked, not seeing it, but there is a meta property="og:url" which might be usable instead? Going to read about it.
[dmitshur]Do you agree it's reasonable not to accept someone's GitHub profile if their rel=me link doesn't point to the profile but another page (e.g., their repo)
[dmitshur]in practice, I'm not going to need it for now because it's just easier to add special case for github. For now at least, I'm going to use GitHub API to fetch the user info including their HTMLURL, rather than doing an HTTP get.
[dmitshur]the possibility of a trailing-slash difference between two different legitimate users is slightly unfortunate, but thinking more about it, it seems very unlikely to come up in practice.
aaronpkYeah with indielogin.com I switched to using the silo APIs to get user info instead of dealing with URL normalization and it really cleaned things up
[KevinMarks]I hope they don't change their urls at dinner point, or do it carefully. Didn't twitter switch to having an @ in the canonical url after a few years?
[dmitshur]at first I thought I'd just ignore errors, but now I'm thinking I'll report them to user and prevent from logging in. so they'll be motivated to fix (or remove) their broken/misconfigured stuff.
[dmitshur]I'm thinking about how to handle error cases when a user signed in successfully via IndieAuth but their user info is misconfigured/erroneous.
@hankchizljawI’d really like something that will ping me for each webmention so I can approve it or reject it. Are there any existing services that do that?
(Please say yes I don’t need more side projects) (twitter.com/_/status/1216105178526617601)
@sil↩️ how are you getting and storing the webmentions now? If I want notifying about something, most of the time I just punch out an RSS feed for it and then subscribe to that, if that's a useful approach (twitter.com/_/status/1216108772453732359)
[tantek]aaronpk, good point about "#!". Maybe fragmention should explicitly disallow "#!" fragmentions and note that such URLs are reserved for single page app routing (per that old Google advice ages ago). Then we can tell anyone who breaks (like WebMD) that they are violating Google's standard for single page app routing, and they should fix their site 😄