#Zegnat/relmeauth and /RelMeAuth link to different things. The first is a PHP library, the second the building block. This part of the IndieWeb documentation is one giant ball of yarn :/
#aaronpkwow that's a great new version of the IndieAuth page!
#aaronpki wonder how many other duplicate pages we have
#sebselI was confused by the double section of 'Self-Hostable Implementations', maybe change that to something like 'Self-Hostable Token Endpoint Implementations' etc.?
#ZegnatI think I cleaned up /IndieAuth#Issues now, so I am going to copy what is left to my new IndieAuth page
#ZegnatThey are clearly nested, see the ToC sebsel. I don’t really like how minute the difference between h3/h4 is on indieweb.org though. They are quick to run into eachother
#sebselI see they are nested, but I needed a few looks for that, because the h3/h4-difference is so small.
#sebselMaybe remove 'The Three Parts of', and get them h2/h3?
#ZegnatI am also not sure if I should say indieweb.org is using IndieAuth. I don’t think it is? We simply use IndieAuth.com as an authentication provider, right? And IndieAuth.com just happens to support both RelMeAuth and IndieAuth… Still kept that in.
[shanehudson] joined the channel
#aaronpkhm that might be a good reason to update the mediawiki plugin to actually speak the indieauth protocol itself
j12t joined the channel
#Zegnatsebsel how are these small CSS tweaks on the headers? Better?
#Loqizegnat has 14 karma in this channel (119 overall)
#Zegnataaronpk, what to do with those Feature Requests? They aren’t indieauth.com specific, but they aren’t auth related either? They are more akin to e.g. when using Facebook to login somewhere and allowing that place access to certain information.
#sknebelaaronpk: is Web sign-in now everything that uses your own url or specifically RelMeAuth? if the first, I'd restructure the page to clearly present that it's the concept name behind differnet things
#ZegnatI would like to edit “web sign-in” to broadly mean signing in with your own URL. But sknebel is right that my use might be wrong.
#ZegnatWe still need cleanups of the endpoint pages, and possibly a proper write-up of the technical spec. But this should at least get people started understanding IndieAuth-the-protocol and get rid of IndieAuth.com-the-service contamination of the page.
#Zegnattantek, I would be super grateful if you reviewed the new page too!
#tantekaaronpk it's user feature vs plumbing distinction
#Zegnatanother reason why I was cleaning up the /IndieAuth page: it now no longer mentions rel-me (I think)
#aaronpktantek: is the intention that "web sign-in" is the user feature name for RelMeAuth?
#aaronpkor that it broadly means using your website as your identity
#tantekno, user-feature first, RelMeAuth was just the plumbing that implemented it
#tantekthe point was to give a user-friendly name to something that is easy to implement
#aaronpkin other words, if I take away all the rel=me links from my website, but still support the indieauth authorization endpoint, and can sign in to the wiki and telegraph etc, does that mean I still support "web sign-in"?
#Zegnatin other words: is OpenID another example of “web sign-in”?
#tantekthat's an even better question, and there are advantages to yes and no
#tantekOpenID has so much baggage (hard to setup, get working etc.) that it's better to *contrast* (say no) with OpenID
#tantekOTOH, to say, OpenID was an older plumbing technique for implementing Web Sign-in which has better techniques now, does a good job of generalizing beyond OpenID
#tantekOpenID advocates tried to get the same term used (marketed) for both the user-feature and the plumbing which was a mistake IMO
#sknebelZegnat: see last edit to your page for what I meant with my note. feel free to revert if you disagree
#Zegnatsknebel, I dont really disagree. I was mostly trying to keep the how to’s as short as possible. Because that’s the feedback we have been getting.
#ZegnatYeah, that’s all fine tantek. The question was is “Web sign-in” was still the correct term, because the mf wiki seemed to describe it only with RelMeAuth.
#tantekthe point of Web Sign-in was to provide a user-facing term for something simpler to use and implement than OpenID for users and developers
#ZegnatThis is the “short how to to get people going”, which I would rather not clog up with information about how stuff works. sknebel. Just trying to make sure people don’t start thinking of rel-me as IndieAuth again.
#aaronpki am thinking that we're beyond the point of making "IndieAuth" refer to the protocol, because people think of it in relation to the rel=me links already
#tantekthis is precisely why I rejected all the OpenID thinking / setup crap
#tantekand documented Web Sign-in and relmeauth as simple as possible
#tantekaaronpk, the way is to start with user focus, always
#ZegnatIndieAuth has NOTHING to do with any rel="me". IndieAuth lets people specify an authentication endpoint they want to use. Possibly being their own website.
#ZegnatRelMeAuth lets you login with just rel="me".
#tantekthe protocol must support the simplest possible UX, not the other way around
#ZegnatTwo completely different things. 100% different. If you want to support RelMeAuth and not IndieAuth, that is fine, tantek. But don’t merge them now.
#ZegnatNo. IndieAuth.com-the-service. IndieAuth-the-protocol-that-the-wiki-page-is-about does not
#sknebelno, it doesn't. It shows the quickest way to get an IndieAuth endpoint on your site: by using the one provided by IndieAuth.com. which does RelMeAuth
#sknebelhm. My impression from HWC was that if you make the distinction clear from the beginning (which really would be helped by renaming one of them) it's not an issue
#aaronpktoo bad webauth .com .net and .org are already taken
#tantekanything with "Auth" in it should not be user-facing, that should be obvious
#sknebelif a "less indie" name helps publishing it as a spec, I guess rename the spec, although it'll take ages to update all the documention of all the software using it, rename the libraries and plugins, ...
#ZegnatSure, but that’s a *different* rewrite of /IndieAuth then. This page I wrote today is specifically about the protocol.
#sknebelI guess the key question from me about a rename of the protocol would be a) how do we transition all the existing references to it and b) how do we prevent getting the same confusion under a new name? Because if we don't do that, and sticking with the name and slowly trying to reduce the confusion is just as good
#tantekI'm saying you don't get to rename anything related to IndieAuth singularly - you're going to have to document how people interpret what, document some alternatives, and make it a longer discussion that will hopefully resolve over time
#tantekif there was a quick fix, aaronpk would have done it ages ago
#tanteksknebel: distilling key questions is good. writing them on the wiki is even better to at least capture current state of understanding
#tantekunlikely to get resolved today or when people are still keeping this chat in their head
#ZegnatEither people have been doing it correctly, using IndieAuth as a name for the protocol (almost nobody did that apart from a handfull of implementers), or used IndieAuth as a catch-all term for logging in through IndieAuth.com (almost everyone did this). The solution seems to me to rename the protocol (as aaronpk came up with) and possible redirect
#Zegnat/IndieAuth to /IndieAuth.com for clarity amongst those who have been using the term that way (unknowingly) already. Makes sense to me.
#ZegnatBut I am off to kill some monsters in D&D now :)
#tanteksknebel, Zegnat, better to capture the nature of all this confusion somewhere on /IndieAuth#Issues that attempt to fix it all in one chat
#sknebelI honestly thought after Nuremberg (where aaronpk and sebsel started reworking pages, and aaron talked about renaming IndieAuth.com to lessen this confusion) the goal was clear (otherwise I wouldn't have asked about reworking the pages)
#sknebelbut apparently that's suddenly not the case anymore
#sknebel(Nuremberg not necessarily being a fixed date, but the place I where I heard about it)
#sebselyeah, tantek, we have been doing this rename since Nuremberg. So it's not a one-chat thing. But sure, it needs time.
#sebselAnd aaronpk was thinking about the rename before that even.
#tanteksebsel, point being, capturing the iterations on the wiki is necessary, otherwise it will appear to be a series of disconnected one-chat things
#tantekso unless you can point to where that is happening on the wiki (the capturing of the discussion on an ongoing basis), then very little actual progress will be made
#sebselThat's where the discussion keeps going: someone (myself included) who suggests a new name based on what domains are free.
#sebselBut I agree with tantek that that does not bring us much further.
#ZegnatI just realised that https://indieweb.org/IndieAuth#How_it_works already specifies that an app goes “looking for an Authorization Endpoint”. It is literally only “Set up using IndieAuth.com” that omits this.
#sebsel'How it works' was added by me in the IndieWebWeek train :o
#sebselThat's already an attempt to steer to IndieAuth-the-protocol for that page.
#jjuranIIUC, consensus is that protocol and service require separate names. Tantek says users shouldn’t see “auth” in the name, so IndieAuth can be the protocol name and the service needs a new name, and hence a new domain name.
#tantekjjuran see above about capturing the nature of all this confusion somewhere on /IndieAuth#Issues
#sebselif you define IndieAuth as 'the thing that IndieAuth.com does', than IndieAuth is both the OAuth extention and RelMeAuth, and it's a great idea and service, but very hard to decentralize.
#tantekboth of those are worth mentioning on that issue 78!
#tantekjust did a search for http://indiewebcamp.com/ in his Firefox history (7550 items!) and is doing a mass delete - so none of those URLs autocomplete anymore
#tantekIndieWebCamp kit is a small minimum set of supplies that help to run an [[IndieWebCamp]] such as large sticky notes and Hello My Name Is name badges.