New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for one-level deep links like /contact #48
Comments
This reverts commit 3dd4070. It turns out that indieauth doesn't currently support this use[1] so I'm reverting to link from my homepage only for now. [1] https://github.com/aaronpk/IndieAuth/issues/48
I also ran into this issue. My main page (www.foad.me.uk) has a rel=me link to my profile page (julian.foad.me.uk) which has the rel=me links to Twitter & Github. For this test, one of those links back to www.f.m.u and the other back to julian.f.m.u. Indieauth.com(julian.f.m.u) works fine, but indieauth.com(www.f.m.u) reports "julian.foad.me.uk/ ... is not a supported authentication provider". (That is an earlier failure than the original report, perhaps because of changes in indieauth.com, or is it because my contact page is on a different domain from my home page?) The spec says this should be supported, doesn't it? |
What I care about is the bad impression this gives of IndieAuth: one tries to set it up according to the spec, and it doesn't work, one wastes time trying things and eventually discovering there's a bug report about it here. (I don't care at all about whether it works for me on my site; my site is experimental and I'm happy to do things a different way. In fact IndieAuth already works fine for me: I just specify my contact page as my sign-in URL.) So one possible resolution to this bug would to make IndieAuth.com say clearly "This site is not a reference implementation of the spec. It has gaps, which are: (1) multiple rel-me hops not supported; (2) ..." Another possible resolution would be remove this from the spec. |
Per RelMeAuth: users with separate contact pages.
This is already mentioned on the IndieWebCamp wiki but it took me a long time to determine that this was a known limitation (having first tried to authenticate with my site where the homepage links to my about page). GitHub issues feels like a more natural place to capture this to me.
Current behaviour:
The text was updated successfully, but these errors were encountered: