#jackyalso IIRC video streaming has gotten better w.r.t load with things like HLS
#GWGIn light of the current feelings on Russia, wondering if I should remove Yandex from my code as a location provider
#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.
#vikanezrimayaThat alone is a good reason to consider staying away from them.
#GWGvikanezrimaya: I also have Google Maps, Bing Maps, Mapbox, Here Maps, TomTom, MapQuest, and a few more.
#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)
#GWGI don't use them, but I want to have redundancy on map display.
#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: They don't provide static maps. They do provide reverse geocoding, and they are my default option for that.
#GWGOddly enough, despite it not being the default, most people seem to go for Google Maps.
#vikanezrimayaAh, so you're pulling map tiles from them?
#vikanezrimayaI'm sorry, I just drank a cup of coffee after not drinking some, and my brain is a little bit slow.
#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
#vikanezrimayaI think using Yandex for map tiles is a small enough use to not be considered evil.
#GWGI just wonder if 9 different choices is enough.
#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.
#vikanezrimayaGWG: I think it's more than enough, considering one could also do the same as you and set up a tile server.
#GWGI'm about to do my yearly...check all the apis are up to date test
#Seirdyanyone know why rel=authorization_endpoint was replaced by rel=indieauth-metadata?
#Seirdyoh wait nvm, i see that it's a bit different
#Seirdyi.e. it has more data, including the auth endpoint
[manton] joined the channel
#[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.
#[manton](I still haven’t gotten around to support -metadata.)
#capjamesg_I think I implemented support for the authorization_endpoint value.
#Seirdyi'm not sure how useful it is, given that the metadata can also be picked up from the microformats.
#omz13with -metadata, it brings IndieAuth in-line OAuth2; also it means adding new endpoints is easier as they are simply added into the -metadata file
#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
#Seirdyhmm i think generating the file from microformats could be interesting
#[Jamie_Tanna]The new token introspection endpoint, for instance, is only in there
#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
jacky joined the channel
#[tantek]^ this is a VERY GOOD thing to explicit describe in a "Scope" section