vikanezrimayaGWG: as a Russian, I'd say Yandex could potentially abuse its trust as a Google-tier corporation and become shady. They've already shown that they're doing shady stuff, like having their trackers on our e-government website and generally engaging in monopolistic practices.
vikanezrimayaThey also decided to engage in price gouging on their cloud services after all the competitors stopped being able to accept Russian credit cards (thanks MasterCard! /s And yes I'm still sour about that)
vikanezrimayaGWG: In that case, I think it's mostly fine. Have you considered OpenStreetMap as a data source, or am I misunderstanding the term "location provider"?
GWGvikanezrimaya: My personal instance generates maps from OSM Map Tiles. But I'm not going to suggest other people set up a tile server. So I supported a few APIs for them to choose from
vikanezrimayaIf people have choice in this matter when setting up the software, I think there's no reason to artificially shrink that choice down by removing an option, at least.
[manton]Yeah, indieauth-metadata is relatively new, added to the spec just in the last year. Not sure how widely it’s supported yet, so clients should fall back on authorization_endpoint too.
omz13I don't have the exact stats of the top of my head, but most people implement -metadata via the wordpress plugin... and there are <10 other implementations in the wild
aaronpkyes, that and the metadata document describes the indieauth server, not the user's website, which is the reason for moving all those other properties there instead of defining them from the user's website