LoqiRSS is a set of XML feed file formats of varying degrees of use for syndicating time-stamped content from web sites, and sometimes used to refer more broadly to feed file formats as a whole including Atom, or even more broadly in vernacular as a synonym for feed file or even feeds or syndication as a concept https://indieweb.org/RSS
gRegorI'm working on IndieAuth server for ProcessWire and was wondering what people thought about the flow when the person isn't logged in to the CMS yet. Should I combine the login + consent in one screen? Or prompt for login like normal, then follow that with the consent screen?
ZegnatI would also split it up. In part because of what sknebel mentioned with 2FA. But also because maybe the CMS can have other plugins modify the login flow behaviour and you should not be getting in the way of that
ZegnatHere is another one: some password managers might remember checkbox states etc and auto-fill those when filling in passwords. This could potentially really mess up consent screens
LoqiAn authorization endpoint is an HTTP endpoint that micropub and IndieAuth clients can use to identify a user or obtain an authorization code (which is then later exchanged for an access token) to be able to post to their website https://indieweb.org/authorization-endpoint
Loqiconsent screen is the page you see during an OAuth flow that asks whether you want to allow the application you're logging in to to be able to access the data it's requesting https://indieweb.org/consent_screen
jamietannaZegnat re "1 hour" = "shortlived", I've worked with APIs with a much smaller lifetime. And I guess going to refresh straight away if the token isn't used often can make sense