GWGI just finished the security and bug fixes on my location code, so I'm doing a run through the Static Maps API PHP repo I took over from aaronpk. Since he has Atlas, I'm taking this version in a slightly different direction as I fix map support for tile servers that changed, and add some features because bots are pummeling my instance.
GWGI'm also adding a config.php file to allow easy updating of the tile server configs separate from the main file, adding a simple query API to return what tile servers are configured, moving the API key option into there...
ulhar4409In theory, if I have some OAuth provider I also want to use for indieauth, would I just need to copy its details to a json file and link to that with rel=indieauth-metadata ? Because I'm a little tempted to do some tinkering with that
Xe, cotsuka, Xe_, ghorsey_mobile, owls, hypha, strugee, rMdes-bnc and barnaby joined the channel
wturrellanyone want to offer a second opinion on <cite> vs <i> vs <em>? My current rule of thumb is: <cite> for names of works, e.g. article, blog post, book, play, whatever, but NOT a newspaper, magazine it might appear in, which I would style with <i> (if I want to), because there's no "stress" implied that would justify using <em>
offeringofpiemaybe <cite> with class periodical for newpapers/magazines/etc, with `font-style: italic;` in it. Keeps it semantic. but yes <i> could work too, to not apply stress on the text
wturrellyep, that's the impression I got. re-reading MDN; hadn't paid enough attention to the "idiomatic" section (you can probably pretty much guarantee everyone sees <i> and thinks "italic"…)
ulhar4409managed to find a github repo that does pretty much exactly what I was wanting to do (bridge indieauth <--> openid connect), it has a few rough edges but seems workable
GWGThat seems like the reverse.. I'd want to log into oidc supporting sites with my indieauth endpoint. But I suppose I might just have to make it support oidc as well as indieauth for that.
aaronpkpart of my goal with the recent indieauth spec changes are to make it more closely compatible with OAuth/OIDC so that adding full OIDC support is a very small addition on top
LoqiOpenID Connect is an authentication protocol built on OAuth 2.0, that in practice is not implemented to provide open (portable) identifiers across systems, nor does it have anything to do with OpenID (1 or 2) except in name, but instead, identities are tied to a specific identity provider https://indieweb.org/OIDC