#meta 2017-07-18

2017-07-18 UTC
tantek, [miklb], dougbeal|mb1, dougbeal|mb1`, strugee_, [pfefferle], j12t and sl007 joined the channel
#
Zegnat
https://indieweb.org/User:Vanderven.se_martijn/IndieAuth - could I get some eyes on this? aaronpk, sknebel? Would be really sweet to get /IndieAuth cleaned up as our focus on /building_blocks is growing throughout our events.
j12t joined the channel
#
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 :/
#
aaronpk
wow that's a great new version of the IndieAuth page!
#
aaronpk
i wonder how many other duplicate pages we have
#
sebsel
Zegnat++
#
Loqi
sebsel: sl007 left you a message 5 days, 4 hours ago: - if you want, https://indieweb.org/2017/Dortmund/Guest_List - let's add the tent emojis then …
#
Loqi
zegnat has 13 karma in this channel (118 overall)
#
sebsel
sl007 lol
#
Zegnat
I keep finding pages I did not know about that include yet another small piece of the puzzle
#
Zegnat
E.g. /distributed-indieauth nicely documents adding endpoints to your <head> :/
#
sebsel
I was confused by the double section of 'Self-Hostable Implementations', maybe change that to something like 'Self-Hostable Token Endpoint Implementations' etc.?
#
Zegnat
I think I cleaned up /IndieAuth#Issues now, so I am going to copy what is left to my new IndieAuth page
#
Zegnat
They 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
#
sebsel
I see they are nested, but I needed a few looks for that, because the h3/h4-difference is so small.
#
sebsel
Maybe remove 'The Three Parts of', and get them h2/h3?
#
sebsel
maybe that's not the solution..
#
Zegnat
I 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
#
aaronpk
hm that might be a good reason to update the mediawiki plugin to actually speak the indieauth protocol itself
j12t joined the channel
#
Zegnat
sebsel how are these small CSS tweaks on the headers? Better?
#
aaronpk
need an IndieWeb Examples section!
#
aaronpk
listing personal sites that support indieauth
#
Zegnat
Isn’t that “Supporting Sites and Clients”? Or you mean people who have added the endpoint rels?
#
Zegnat
I’ll start on a section for the latter!
#
aaronpk
no, i mean specifically "IndieWeb Examples" to match the rest of the wiki, only for personal sites
#
aaronpk
that could list both people who have added the rels as well as personal sites you can sign in on
#
aaronpk
it's good to call out personal sites separately from services
#
aaronpk
what's especially good to see is who is running their own IndieAuth authorization endpoint
#
Zegnat
So is there anything in this FAQ that shouldn’t be moved to /indieauth.com? https://indieweb.org/IndieAuth#FAQ
#
Zegnat
Or maybe I should ask if there are any questions in there that should be kept on /IndieAuth
#
Zegnat
I am not seeing them
#
aaronpk
"Why not OpenID Email etc" should be kept on /IndieAuth
#
Zegnat
Oh, “Why is the IndieAuth verification response form-encoded instead of JSON” should probably stay too
#
Zegnat
Though the form-encoded discussion could potentially go under #Issues too
#
aaronpk
yeah better in #Issues
#
Zegnat
The “Who not OpenID Email etc” is a valid question. But really sounds like a [[Web sign-in]] question more than a question about IndieAuth?
#
aaronpk
good point
#
Zegnat
Especially since the answer is just “see Web-sign in”
#
aaronpk
well then maybe it's worth keeping on IndieAuth
#
aaronpk
since it's probably there because someone had the question while reading about IndieAuth
#
Zegnat
I expect it might have been filed as a question re IndieAuth.com-the-service: e.g. why can’t I use OpenID there?
#
aaronpk
that could be
#
Zegnat
I am just not sure if it makes any sense to read the IndieAuth page and then go: “nice protocol, but what about email?”
#
aaronpk
move it to /indieauth.com then i think
#
Zegnat
goes to do more moving and will ask questions afterwards~
tantek joined the channel
#
Zegnat
Alright, I think #Issues and #To_do are cleaned up now, and I copied them over to my draft page on my user account.
#
aaronpk
Zegnat==
#
aaronpk
Zegnat++
#
Loqi
zegnat has 14 karma in this channel (119 overall)
#
Zegnat
aaronpk, 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.
#
aaronpk
which features?
#
Zegnat
Hmm, maybe rewrite them to an issue. Something like “requesting additional user data”
#
aaronpk
interesting
#
aaronpk
also sounds related to /private_posts
#
Zegnat
Yes, but I can see why people bring it up for IndieAuth. Especially when you ask implementors to move away from e.g. login with Facebook.
#
Zegnat
goes to rewrite!
j12t joined the channel
#
sknebel
aaronpk: 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
#
Zegnat
I 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.
#
aaronpk
tantek might have some thoughts about that, since it's also on the mf wiki http://microformats.org/wiki/web_sign-in
#
Loqi
Web sign-in
#
Zegnat
I am otherwise pretty done copying over stuff from /IndieAuth. Please review https://indieweb.org/User:Vanderven.se_martijn/IndieAuth . If people like it I would like to replace the current /IndieAuth with mine.
#
Zegnat
We 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.
#
Zegnat
tantek, I would be super grateful if you reviewed the new page too!
#
aaronpk
(definitely a proper writeup of the spec)
#
tantek
did you come up with a new name for th service?
#
sknebel
Zegnat: I'd add a one sentence explanation to "set up using IndieAuth.com" what indieauth.com is
#
aaronpk
no this is just fixing up how the wiki pages refer to the protocol and spec
#
tantek
Zegnat, I'm confused by "would like to edit “web sign-in” to broadly mean signing in with your own URL" - http://microformats.org/wiki/web_sign-in already does that
#
Loqi
Web sign-in
#
aaronpk
protocol and service
#
aaronpk
right now the microformats wiki is treating "web sign-in" specifically as RelMeAuth
#
Zegnat
tantek, no, the mf says you need to be set-up for it using rel="me"
#
sknebel
tantek: but the next part of the site clearly only describes RelMeAuth
#
Zegnat
Which is RelMeAuth, not IndieAuth.
#
tantek
aaronpk it's user feature vs plumbing distinction
#
Zegnat
another reason why I was cleaning up the /IndieAuth page: it now no longer mentions rel-me (I think)
#
aaronpk
tantek: is the intention that "web sign-in" is the user feature name for RelMeAuth?
#
aaronpk
or that it broadly means using your website as your identity
#
tantek
no, user-feature first, RelMeAuth was just the plumbing that implemented it
#
tantek
the point was to give a user-friendly name to something that is easy to implement
#
aaronpk
in 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"?
#
tantek
that's a good question
#
Zegnat
in other words: is OpenID another example of “web sign-in”?
#
tantek
that's an even better question, and there are advantages to yes and no
#
tantek
OpenID has so much baggage (hard to setup, get working etc.) that it's better to *contrast* (say no) with OpenID
#
tantek
OTOH, 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
#
tantek
OpenID advocates tried to get the same term used (marketed) for both the user-feature and the plumbing which was a mistake IMO
#
sknebel
Zegnat: see last edit to your page for what I meant with my note. feel free to revert if you disagree
#
Zegnat
sknebel, 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.
#
Zegnat
How IndieAuth.com-the-service works as RelMeAuth wrapper for the endpoint is mentioned in https://indieweb.org/User:Vanderven.se_martijn/IndieAuth#Third_Party_Services
#
Zegnat
But I don’t mind the extra explanation. I might try to shorten it though :)
#
tantek
really need a name for that service :)
#
sknebel
understandable, but someone going for the "as short as possible" then thinks IndieAuth is rel=me links
#
Zegnat
is also setting up D&D night, this was probably the worst timing to start this rewrite project
#
tantek
right, and people will do that
#
Zegnat
Very good point, sknebel! Didn’t think of that, because *I* know what IndieAuth is...
#
tantek
people look for the simplest explanation to get started
#
tantek
instead of the most through
#
tantek
*thorough
#
Zegnat
So if we accept the use of web sign-in; any other complaints with replacing the old page?
#
sknebel
Zegnat: your page LGTM
#
sknebel
I can take a shot at making the web-sign in page clearer later
#
tantek
Zegnat, one of your favorites, see https://indieweb.org/Web_sign-in specifially "Web sign-in supersedes OpenID. " :)
#
tantek
so the current answer is no, OpenID is not a form of Web Sign-in because we have drawn a contrast
#
Zegnat
Yeah, 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.
#
tantek
the 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
#
sknebel
And we have the term RelMeAuth
#
tantek
right, RelMeAuth is the plumbing that makes Web Sign-in easy to setup and implement
#
sknebel
if the term is a user-facing pattern, then I'd list RelMeAuth, IndieAuth and (discouraged) OpenID as ways of achieving it
#
tantek
OpenID is not because it is also a user-facing term, that's the problem
#
tantek
Another way to think of it would be to say IndieAuth is a way to implement RelMeAuth
#
aaronpk
but it's not
#
aaronpk
you can implement IndieAuth without RelMeAuth
#
tantek
but it is
#
sknebel
by that logic, IndieAuth also is a way to implement OpenID (afaik cweiske does that)
#
tantek
the fact that you can do other things does not negate that IndieAuth is a way to implement RelMeAuth
#
aaronpk
if you want to be able to say that then we need a new name for the protocol that extends OAuth 2.0
#
tantek
definitely
#
aaronpk
IndieAuth is having an identity crisis
#
tantek
has had for a long time
#
aaronpk
#irony
#
Zegnat
sknebel, I tweaked the description a bit, hopefully clearing things up without refering to other specs and stuff: https://indieweb.org/User:Vanderven.se_martijn/IndieAuth#Set_up_using_IndieAuth.com
#
sknebel
Zegnat: if "without refering to other specs and stuff" is the goal then LGTM
#
aaronpk
considers WebAuth
#
tantek
for the protocol?
#
aaronpk
formally as a OAuth 2.0 extension
#
tantek
makes sense
#
tantek
Zegnat why do you need step 3?
#
Zegnat
This 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.
#
tantek
I don't do that and it works
#
tantek
don't include any non-required steps like that in the first How to
#
Zegnat
you are not using IndieAuth then tantek
#
Zegnat
You are using RelMeAuth
#
tantek
Zegnat - no that makes no sense when step 1 is add rel-me links
#
sknebel
then you only can log into sites that use IndieAuth.com
#
tantek
I think that distinction is only adding confusion
#
sknebel
since sites doing the IndieAuth protocol look for the authorization_endpoint first thing
#
aaronpk
adding the rel=me links means you can log in to any sites that implement RelMeAuth
#
sknebel
and don't necessarily do anything else if that isn't there
#
tantek
and should fallback to using "the service"
#
Zegnat
IndieAuth.com offers an authorization_endpoint based on RelMeAuth. It wraps RelMeAuth to become IndieAuth compatible.
#
Zegnat
It is confusing in all ways, tantek ;)
#
tantek
so you don't burden every user with an extra step
#
tantek
otherwise you're making the same mistake (one of) that OpenID folks made
#
tantek
putting extra work on the user just to make the definitions cleaner / purer
#
Zegnat
If we don’t let them set the authorization_endpoint they can’t login to IndieAuth supporting websites :/
#
tantek
zegnat: "don't let them" !== "don't force them"
#
Zegnat
authorization_endpoint = *must* for IndieAuth sites
#
tantek
is kind of weary of the logical flaws in the discussions here
#
sknebel
nothing in the existing indieauth documentation says anything about falling back to a central service
#
sknebel
and none of the libraries I've looked at implementing it do that
#
tantek
so that should be fixed
#
aaronpk
nothing about IndieAuth the protocol should include falling back to a central service
#
tantek
to make it easier on users
#
Zegnat
Please don’t make IndieAuth centralised by hard-linking a protocol to a website!
#
tantek
otherwise, you end up with OpenID purity arguments -> worse experience for setup
#
sknebel
indeed, don't
#
tantek
right, you're thinking purity over UX
#
Zegnat
No. I am thinking of the protocol.
#
tantek
which is the wrong prioritization
#
Zegnat
The protocol CANNOT work without an endpoint declared by the user.
#
tantek
no you're working on "How to"
#
Zegnat
Unless we centralise it.
#
tantek
pick one
#
tantek
if you want to write technical protocol docs that's one thing
#
tantek
but if you're writing a "How to" on the indieweb.org, you prioritize UX
#
tantek
not purity
#
aaronpk
i 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
#
tantek
this is precisely why I rejected all the OpenID thinking / setup crap
#
tantek
and documented Web Sign-in and relmeauth as simple as possible
#
Zegnat
So... you reject IndieAuth, tantek? Cool.
#
tantek
no I reject forcing users to do an unnecessary step
#
tantek
just because of "protocol"
#
tantek
that's plumbing-centric/first thinking and it's wrong
#
sknebel
It is not unnecessary if we want to have an actually "indie" protocol without a central service
#
aaronpk
i wish i had a good way of laying all this out
#
tantek
sknebel that's the kind of "purity" statement I'm talking about
#
tantek
"actually ... without a central service"
#
tantek
aaronpk, the way is to start with user focus, always
#
Zegnat
IndieAuth has NOTHING to do with any rel="me". IndieAuth lets people specify an authentication endpoint they want to use. Possibly being their own website.
#
Zegnat
RelMeAuth lets you login with just rel="me".
#
tantek
the protocol must support the simplest possible UX, not the other way around
#
Zegnat
Two completely different things. 100% different. If you want to support RelMeAuth and not IndieAuth, that is fine, tantek. But don’t merge them now.
#
aaronpk
already has registered webauth.rocks
#
tantek
Zegnat - the How to on the page you linked merges them
#
Zegnat
Yes, because the IndieAuth.com-service uses rel="me" to verify you own the site
#
aaronpk
that "how to" section is actually about indieauth.com so should be moved there
#
tantek
right, IndieAuth is using RelMeAuth - which is what I've been saying
#
aaronpk
*indieauth.com* is using RelMeAuth
#
tantek
so no that page is not ready
#
Zegnat
No. IndieAuth.com-the-service. IndieAuth-the-protocol-that-the-wiki-page-is-about does not
#
sknebel
no, 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
#
tantek
because it's still confusing
#
tantek
just here in this conversation
#
aaronpk
haha this is a nightmare
#
Loqi
awesome
#
tantek
sknebel: "quickest way" is how people will understand something
#
tantek
you have nearly zero chance of explaining that it's actually not the case
#
sknebel
tantek: which is why I just asked to clarify that section so this is clearer
#
tantek
adding more text will not help
#
tantek
as long it says add rel-me links, it will look and sound like RelMeAuth
#
Zegnat
Renaming to WebAuth now …
#
sknebel
Zegnat: same problem according to tantek
#
tantek
right, that doesn't change the problem noted above
#
sknebel
(not that I necessarily agree, but it doesn't help the discussion)
#
sknebel
(one of the two should be renamed to make the distinction clearer, but I'm not sure renaming IndieAuth instead of Indieauth.com is better)
#
tantek
or both
#
aaronpk
the more i talk to people the more i realize that "indieauth" is already cemented in relation to RelMeAuth
#
tantek
and keep IndieAuth as the full suite of what IndieWeb uses for signing in
#
aaronpk
so I am not opposed to calling the OAuth 2 extension spec something else
#
tantek
aaronpk: are you keeping track of that somewhere discoverable?
#
tantek
(i.e. gh issues are not discoverable for this because you have to know where to look)
#
tantek
(which repo / named thing to look at)
#
aaronpk
no, this is just in-person conversations
#
sknebel
hm. 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
#
aaronpk
too bad webauth .com .net and .org are already taken
#
tantek
anything with "Auth" in it should not be user-facing, that should be obvious
#
sknebel
if 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, ...
#
tantek
per techno jargon blah
#
tantek
so IndieAuth is a fine name for the protocol, except that in practice people already conflate it with incorporating RelMeAuth
#
tantek
(because that's how 99% of people use IndieAuth, via RelMeAuth and IndieAuth.com-the-service)
#
tantek
use defines meaning
#
tantek
Zegnat, that doesn't really help, that's the point of the discussion above!
#
Zegnat
Why would that not help? The entire page details exactly how the OAuth extension protocol works.
#
Zegnat
And now the howto of indieauth.com makes more sense, as it is clear we do not talk about indieauth-the-rel-me-thing
#
Zegnat
If we want to use the term IndieAuth for something else now, we can write a different page for that
#
sknebel
Zegnat: we still have an entire ecosystem bound to the name, so not quite ;)
#
tantek
exactly, you don't get to singularly make such a decision
#
tantek
you have to look at how existing use has already evolved
#
tantek
and do your best to adapt
#
tantek
is doing wiki history archeology
#
Zegnat
Sure, but that’s a *different* rewrite of /IndieAuth then. This page I wrote today is specifically about the protocol.
#
sknebel
I 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
#
tantek
I'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
#
tantek
if there was a quick fix, aaronpk would have done it ages ago
#
tantek
sknebel: distilling key questions is good. writing them on the wiki is even better to at least capture current state of understanding
#
tantek
unlikely to get resolved today or when people are still keeping this chat in their head
#
Zegnat
Either 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.
#
Zegnat
But I am off to kill some monsters in D&D now :)
#
tantek
sknebel, Zegnat, better to capture the nature of all this confusion somewhere on /IndieAuth#Issues that attempt to fix it all in one chat
#
tantek
along with questions / proposals there
#
tantek
not going to happen in one day/night. this will take iteration over several days (if not weeks)
#
tantek
*don't attempt to fix it all in one chat
#
sknebel
I 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)
#
sknebel
but 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)
#
sebsel
yeah, tantek, we have been doing this rename since Nuremberg. So it's not a one-chat thing. But sure, it needs time.
#
sebsel
And aaronpk was thinking about the rename before that even.
#
tantek
sebsel, point being, capturing the iterations on the wiki is necessary, otherwise it will appear to be a series of disconnected one-chat things
#
tantek
so 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
#
jjuran
logusin.{net,org} are available. :-)
#
jjuran
But I don’t read that as “log us in”. My brain tries to read “logus” as a blend of “Logan” and “lotus” and gets confused.
#
jjuran
Also, possible trademark issue with LogMeIn.
#
jjuran
websignin.{net,org} are available.
#
sebsel
That's where the discussion keeps going: someone (myself included) who suggests a new name based on what domains are free.
#
sebsel
But I agree with tantek that that does not bring us much further.
#
Zegnat
I 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
#
sebsel
That's already an attempt to steer to IndieAuth-the-protocol for that page.
#
Zegnat
Aah, haha, that explains that then :D
#
Loqi
Zegnat: lol
#
jjuran
IIUC, 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.
#
tantek
jjuran see above about capturing the nature of all this confusion somewhere on /IndieAuth#Issues
#
sknebel
added my understanding of the sitatuion to /IndieAuth
#
sknebel
(cc aaronpk)
#
aaronpk
oh thanks beat me to it
#
Zegnat
aaronpk how much are you leaning towards renaming the protocol/oauth-extension? Maybe worth adding a note about that?
#
aaronpk
i'll add a note
#
Zegnat
That would make clear wether we want to steer the IndieAuth name towards the protocol or not.
#
sebsel
Do we need a separate discussion page for this matter?
#
aaronpk
eh this section is fine for now
[miklb] joined the channel
#
aaronpk
if the spec isn't called IndieAuth, and indieauth.com gets renamed, then what exactly is IndieAuth?
#
jjuran
Anyway, I see “web sign-in” is already being used. It might be a good idea to grab the domain names.
#
aaronpk
oops edit conflict
#
Loqi
Aaron Parecki
#
sebsel
Where he says: I don't want to be Aaron Parecki on Facebook and Aaron Parecki on Twitter, I just want to be Aaron Parecki
#
Zegnat
IndieAuth could become either a generic term, e.g. synonymous for web sign-in, or we “deprecate” it?
#
sebsel
That is very use-case centric.
#
sebsel
And it describes the flow you can have with IndieAuth.com
#
jjuran
aaronpk: Yeah, I did a Show Changes and saw your new edits in the “before” side, and had to redo mine. :-/
#
aaronpk
wow 2012 talk
#
aaronpk
the description of that looks like it's about just indieauth.com the relmeauth wrapper
#
aaronpk
sebsel: did you find my slides from that? I found the original ppt file
#
sebsel
it is
#
sebsel
And no, I have only audio here now
#
Loqi
From OAuth to IndieAuth: Own your online identity
#
sebsel
nice :)
#
aaronpk
nice, i updated the opensourcebridge page to link to that
#
Zegnat
aaronpk, I didn’t check the talks yet :/ The articles section I moved to … RelMeAuth I think, as they seemed to all be about that
#
Zegnat
IndieAuth might even (almost) be treated as a synonym not for web sign-in but for RelMeAuth :/
#
aaronpk
whee and updated my post to include the description and audio file
#
Zegnat
updates++
#
Loqi
updates has 1 karma
#
aaronpk
#ownyourdata
#
sebsel
if 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.
#
sebsel
a post is never to old to change :)
[chrisaldrich] joined the channel
#
sebsel
I can link to the slides page 25, but back then, this was the way it was defined ;) https://seblog.nl/temp/media-endpoint/77a543-page25.jpg
#
aaronpk
that looks like it's describing the indieauth.com API
#
aaronpk
(which happens to look a lot like OAuth 2.0)
#
Zegnat
indieauth.com/auth is still an IndieAuth-the-protocol authorization-endpoint. So that slide seems right.
j12t joined the channel
#
sl007
Zegnat : The IndieAuth Poster is ready. How about a short url "ia" for now, similar to the other posters, so we can redirect ...
#
Zegnat
I am not sure linking to the wiki page helps people a lot, sl007. Read back today’s chat. Not sure what to do.
#
sl007
This is why I asked allthough gave up in the middle ;) Same here.
#
Zegnat
You might want to focus on “Web sign-in” instead. As that isn’t changing any time soon: logging in by simply entering your URL
#
tantek
indeed
#
sl007
Zegnat : That is a very generic name that nobody is used to (?). The term is used by many commercial services. E. g. https://wob.deutsche-bank.de/trxm/help/pu_help_log_websign.html - there are good proposals in https://github.com/aaronpk/IndieAuth.com/issues/138
#
aaronpk
websign?
#
aaronpk
RelMeAuth is solid
#
aaronpk
and indieauth.com is a great way to use it
#
Zegnat
Oh, yeah, RelMeAuth is definitely well established
#
Zegnat
sl007, “Web sign-in” isn’t a rename for IndieAuth. It is a description of logging into places with your URL: http://indieweb.org/Web_sign-in
#
sknebel
still true that it sounds fairly generic, and there didn't really seem to be consensus what exactly falls under the term
#
Zegnat
RelMeAuth then, as a building block, would be good.
#
sebsel
Nice thing about taking RelMeAuth is that, if you describe what IndieAuth.com does, the poster itself doesn't need to change much ;)
#
Zegnat
Time to clean up /RelMeAuth and maybe move /relmeauth :D Hehe
#
aaronpk
definitely those two pages should be consolidated hehe
#
tantek
wait what there are two capitalizations on the wiki?!?
#
Zegnat
One is a library, the other the standard
#
sknebel
what to move the second one to? themattharris-relmeauth?
#
Zegnat
Ran into that today when reading up on all the auth stuff we have
#
Zegnat
maybe relmeauth-php ?
#
tantek
yes the library should include the lang like that
#
tantek
ok to use the . as I think we do elsewhere
#
aaronpk
Oh I didn't realize one was about the library lol
#
sknebel
so I move it to relmeauth.php, update all links, and we then redirect /relmeauth to /RelMeAuth?
sl007 joined the channel
#
Loqi
[aaronpk] #78 rename the project
#
tantek
aaronpk, looks like a running theme for you ;)
#
aaronpk
i'm on the fence about that one actually
#
aaronpk
i don't think people are confused about whether the webmention spec is tied to webmention.io
#
tantek
fewer people are exposed to that term re-use
#
tantek
fewer people use webmention.io than use indieauth to sign into the indieweb wiki
#
aaronpk
that's true
#
aaronpk
also if you use it it's because you've found it and signed up
#
aaronpk
which is different from indieauth.com which you might use when you're signing in to a site you stumble across
#
tantek
indeed
#
tantek
both of those are worth mentioning on that issue 78!
#
tantek
just 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
strugee, [miklb], tantek and tbbrown joined the channel
#
tantek
yeah I think we need to bring back !block at least for admins/leaders
#
aaronpk
i need to fix how it works
#
tantek
for telling Loqi to stop showing things from certain accounts
#
tantek
and to unlink any old @-references to those accounts
#
aaronpk
unfortunately those two things are in totally different places
#
aaronpk
so it's kinda tricky
#
tantek
is kinda relieved Loqi is not monolithic and unified. yet.
tbbrown, tantek, dougbeal|mb1 and [miklb] joined the channel
#
tantek
what is a kit
#
Loqi
It looks like we don't have a page for "kit" yet. Would you like to create it?
#
tantek
what is an IndieWebCamp kit
#
Loqi
It looks like we don't have a page for "IndieWebCamp kit" yet. Would you like to create it?
#
tantek
IndieWebCamp 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.
#
tantek
aaronpk: check out and add to this from your experience: https://indieweb.org/IndieWebCamp_kit
#
Loqi
ok, I added "* [[IndieWebCamps#How_to_organize|IndieWebCamps: How to organize]]" to the "See Also" section of /Planning
#
tantek
IndieWebCamps << Planning
#
Loqi
ok, I added "[[Planning]]" to the "See Also" section of /IndieWebCamps
#
tantek
is iPod-brain-dumping