Google is causing incalculable damage to the global web with its search indexer not respecting Accept-Language and Content-Language and encouraging webmasters to detect language preferences by IP geolocation instead of respecting the user agent's explicitly provided preference.
Example: just because I am accessing a Google site from an IP geolocated in Japan does not mean I want content localized in Japanese. Especially if my browser is already telling the web server I want it in English. Which it is.
This is particularly silly because Chrome itself even handles the Google Translate integration by observing a combination of Content-Language and the lang attribute of the HTML tag. So some parts of Google seem to recognize this standard, while the search indexer uses fucking content heuristics and separate IPs to detect content language, and totally ignores the standard headers and html features.
@trysdyn yup. It really speaks volumes to the imperialist mindset of tech companies assuming the world is divided cleanly by state borders with singular "native" languages.
@shaderphantom Google needs to die.
Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.
While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.
Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!