aaronpkbut once I add the profile info and PKCE stuff, that's starting to look quite a bit different from previous versions, so do we make a new spec URL for the new version? or continue to treat indieauth.spec.indieweb.org as "current" and just keep snapshotting old versions at old URLs?
[tantek]Might want to take a look at WHATWG.org's workmode in how they keep their living specs "current" and some of the processes they use. Not to re-use, but rather just as ideas of things to think about for what you might want for IndieAuth (i.e. how much community consensus vs solo editor responsibility do you want for making different kinds of changes?)
[tantek]And it's worked reasonably well for getting community convergence on improvements and fixes. There's more improvements we can make, yet many of those are more explicit mechanisms (e.g. use of GitHub labels to help move the process along) rather than rethinking of process fundamentals
[tantek]GWG, re: authorship (moving thread from #microformats to here), take a look to see if https://indieweb.org/authorship-spec answers your question, and if not, file an issue!
[tantek]aaronpk, I've been liking the rule of three for publishers or consuming applications for any particular format or protocol (per mf2 parsing change control), it feels like the right balance of diverse voices/opinions yet still enables rapid experimentation/iteration by natural inclinations (or indication of lack of interest).
ZegnatI briefly saw something about h-cards last night, but I did not look closely at it. Did you write it down somewhere outside chat for me to have a read?
GWGAn h-card and an h-entry at the same level, they are the only items.... but nothing specifically tied them together... can I assume that the h-card is the author?
ZegnatIt sounds like it is a pretty safe assumption to make, GWG. Have you seen sites that would require this step. My only concern would be that it might make it harder for people to create entries that they want to not attribute. Because if they have a small h-card for themselves in the site footer, or whatever, this would then be impossible.
ZegnatGWG: then my question is really just around the case of unatributed entries. I do not know if anyone has a usecase for those. But if this change in authorship detection goes through, creating those might become a lot harder.
ZegnatI literally replied to manton in there 3 days ago, and my whole reply mentions only token endpoint as well. I do not know why somehow auth endpoint was just completely dropped from my thought process
[tantek]GWG, status as a property name is particularly overloaded already, though it may be something we could *maybe* generalize and make applicable (with the same meanings) in multiple contexts. issues, to-do items, and media consumption (book reading, movie/tv watching) are all things one puts on a list, perhaps starts doing/working on, makes progress on, and then finishes/closes.
[tantek]next question, since we have prior art from iCal to-do which we can look at, is there also prior art about "status" like that buried in the depths of the ActivityStreams2 vocabulary? (IDK, just asking, you may have looked, or certainly I know [snarfed] has spent time in the depths of those specs)
[tantek]This also feels like something someone (like out there on the web) should or would have done already. It's unlikely (though possible) that we're the first to discuss or create a Grand Unified Status Theory Overall
Loqistatus is typically short for status update, though may also refer to the use of post status in Micropub, or indicating whether an event is cancelled or has some other event status https://indieweb.org/status
aaronpk for example the march 2019 version is at https://indieauth.spec.indieweb.org/20190303/
[tantek] Might want to take a look at WHATWG.org's workmode in how they keep their living specs "current" and some of the processes they use. Not to re-use, but rather just as ideas of things to think about for what you might want for IndieAuth (i.e. how much community consensus vs solo editor responsibility do you want for making different kinds of changes?)
GWG https://github.com/indieweb/authorship/issues/1 - This talks about a list of h-entrys with an h-card at the same level, but not a single h-entry.
Zegnat It sounds like it is a pretty safe assumption to make, GWG. Have you seen sites that would require this step. My only concern would be that it might make it harder for people to create entries that they want to not attribute. Because if they have a small h-card for themselves in the site footer, or whatever, this would then be impossible.
Loqi status is typically short for status update, though may also refer to the use of post status in Micropub, or indicating whether an event is cancelled or has some other event status https://indieweb.org/status