[tantek]there's definitely something there though, for comparing different services / projects, once you have picked an approach (service, CMS, your own project)
Loqijf2 is a working prototype of a simpler JSON serialization of microformats2 intended to be easier to consume than the standard Microformats JSON representation https://indieweb.org/jf2
sknebelaaronpk: I think my remaining questions are all mentioned (how to get it to clients, how to control which clients can access what, how does it work for access for many individual pages), and I'm not sure its easier once those are solved
sknebelaaronpk: to expand on the earlier comment: in both cases, to me the main complexity right now seems to be about a) the clients and b) managing the existing permissions and tokens, and I'm not sure either approach makes a big difference there once you get into renewal, revocation, ...
sknebeland it'd be interesting to what degree they can overlap. I.e. if I support both, and a client makes an AutoAuth request, I could consider giving it a token I got via ticket auth earlier. and reverse potentially. needs some fleshing out of those APIs
[fluffy]I just want to verify something: a successful IndieAuth code verification request must result in an HTTP 200 to be valid, right? 202 isn’t appropriate for something that returns an actual response body that is to be used?
[fluffy]I’m debugging an issue with someone who’s unable to login to my site with their IndieAuth endpoint and the issue is their code verification request is returning 202 Accepted (with the verification body) instead of 200 OK, and they say that they’re able to log in to a bunch of other sites with this implementation. But the IndieAuth spec doesn’t say what HTTP codes are allowed, it just implies 200.
aaronpklooks like indieauth isn't specific about the http code to return, but also the only thing oauth and indieauth say about http codes really is that errors should be returned with http 400
[fluffy]They’re “in stealth mode” and getting ready to launch it. I’m sure they’ll be making an announcement soon enough. I’m flattered they decided to use mine as a reference for verification. 🙂
@snellingioBeen thinking more about what I’d like in a social network.
You can create or follow any number of feeds (public or private).
All RSS compatible. No tracking. Comments via Webmentions only. No DMs (twitter.com/_/status/1279563564827713536)