sparseMatrixthat was awesome... the hcard I had in place had rel/me and authorization endpoint(s) configured for my new(er) micropub server effort. I attempted to log in to the wiki with my my newer hcard uri, and indieauth.com redirected me to the auth endpoint at the dev site.
sparseMatrixnot exactly handy for logging in right now, given it's barely started, but it gave me a perfectly clear picture of what my flask app needs to do next.
sparseMatrixso I have been really struggling to articulate to myself with precision what it is I want my new service to do, beyond very generally saying, you know, microformats/micropub.
sparseMatrixSo essentially anyone would be able to use the endpoints on the server, so long as they could authenticate according to any of the accepted methods.
barnabywaltersmgdm: probably not, but it depends a bit on exactly what th content is. typically, if it has content and a published datetime, it could be a valic h-entry
mgdmIt's just my blog. https://mgdm.net/weblog/ is the index, I was going to add h-entry markup to the pages linked from there, but wondered if I could do something on the index
oodaniis there a clear way to indicate "this is the summary h-entry, there's a more detailed version of this h-entry at u-url"? that seems to be a common pattern
barnabywalterse.g. I’d recommend putting h-feed on the <body> element, p-author h-card on the a.header-link for a minimal authorship h-card, and h-entry on each of the ul.post-list li elements
barnabywaltersbtw mgdm I just realised that you have very similar content on https://mgdm.net/, the same h-feed markup would also work fine there, but you could additionally mark up your bio as part of the author h-card, and mark up “Weblog” as the p-name of the h-feed, which is used as a human-friendly feed name in some reader UIs
barnabywaltersbtw [KevinMarks] etc, there are very few real-world examples on https://indieweb.org/feed, feel free to add yours, noting things like only publishing summaries etc
barnabywaltersis there a “why are the authorization_endpoint and the token_endpoint different when the indieauth spec assumes that they’ll usually be part of the same service” explainer anywhere?
barnabywaltersis the fact that tokenless login information can be obtained from the auth endpoint also based on OAuth2, or is that a simplicity/backcompat addition carried over from the earliest indieauth implementations?
aaronpkanother way to say it is the authorization endpoint outputs HTML and deals with cookies and such, the token endpoint only responds to simple HTTP POST requests and outputs JSON
barnabywaltersthe fact that both endpoints can in theory be separate services, and that how they interact isn’t covered in detail in the spec, never fails to confuse me
barnabywaltersam I right in thinking that micropub endpoints must not accept access_tokens via a query string parameter, e.g. on GET q=config requests where they can’t provide a request body?
jamietanna[m]Snarfed sorry, so I sorted the authentication issue I had, but now it looks like I've got a threading issue 😂 hopefully will get some progress on it this weekend
[tantek], [tw2113_Slack_] and aaronpk joined the channel
[tw2113_Slack_]wrong twitter account and everything
[tw2113_Slack_], [tantek]1, jamietanna, [chrisaldrich], themaxdavitt, peterrother, stacktrust_, jbove, ludovicchabant and sparseMatrix joined the channel