Submitted 2 days ago by undefined@lemmy.hogru.ch to nostupidquestions@lemmy.world
As an avid VPN user it’s infuriating that multilingual websites insist on using the client’s IP address to determine their language and country when web browsers have been sending the Accept-Language HTTP header since the mid-90s.
I understand that you can work out more or less where someone is located based on their IP address but it was never meant to be a geo-based marker. Why not go the simple route and use the header?
It’s also such an broken idea that I can only imagine it comes from american tech bros who have a childish view of the world.
“Yes this area is germany people in germany speak german so websites must german problem solved”
No:
Dieses Suchenwiegenflassen gewürst fleinmescht bitte
As a native speaker of German: lol
I mainly notice this with YouTube ads when in a foreign country. YouTube, you have my viewing history, you know I don’t watch videos in Italian or Hungarian because I don’t understand those languages well, so why are you advertising to me in those languages just because my IP geolocates to Italy or Hungary???
I so hate the bad translations. Please just give me the app in whatever native language it was built in. And if I can’t understand that language, let me switch to English. It’s awful to use an app and have to translate everything yourself back to the native language to figure out what they actually meant and what went wrong in the translation.
And it’s especially annoying when errors and such are also translated. These often make even less sense and when trying to search the internet, it really helps if the error is in the language of largest user base.
I’m an American tech worker (not bro thankfully) and I’ve seen the poor translation issue firsthand: using Google Translate on the backend to transparently translate the website on the fly.
I also happen to be multilingual and it’s just unbearable watching some of this stuff play out. Storing translations and switching between them at a technical level isn’t really hard. I wish companies would invest in translation services instead of relying on Google or some other equally bad service.
using Google Translate on the backend to transparently translate the website on the fly.
This is what they call “modern cloud-based solutions”. Except, now it’s “modern AI-based solutions” - same shit with a different label.
I am now trying to imagine how that works. Every time a client calls the website with an unseen (and IP-based of course) language? Do they at least cache whatever google returns?
Storing translations and switching between them at a technical level isn’t really hard.
Esp. as you yourself pointed out, the internet has been multilingual for decades now.
I’ve been complaining about this for years. And since the large influx of vpn use (esp US I think), I expected this to become a more pressing and widespread issue along people, leading to more urgency to fix it. But no, even google sites seem to not give a shit IIRC
As a user it’s annoying because I have to hunt down the language/region settings. And as a developer it would cost me a lot more to hunt down those values based on the client IP address.
Probably because it’s easier to track people that way.
Sure, but that could be decoupled from language/regional preferences.
When I travel to another country my smartphone doesn’t change its language to match that of the host country, so why don’t websites respect the user-defined preference defined in the header?
It was not that long ago when Android changed my on screen keyboard to a different layout whenever I was in a different country. Really annoying - I don’t suddenly type in Danish when I’m on a business trip to Lyngby (near Copenhagen)
No one is spending money to cater to a miniscule audience.
Especially bad for counties with multiple official languages, they just pick one at random
I’ve noticed that too, it’s so dumb especially when your browser’s language is set to one of them in the first place.
It’s to annoy you into not using a VPN.
I would assume because ur hitting the geolocated cache which will be IP based. I would assume its not doing a location check its simply that the site is being served by the nearest (IP routing wise) provider and that cache is configured to serve only the local language.
Excellent point on the local cache explanation! I hadn’t thought of that.
As a web developer myself I’m into detecting it automatically then redirecting to a URL that includes it (like /en/products). Then of course users can manually change it by signing in and/or using cookies.
You’re doing the Lord’s work. As someone who lives in a country where I can barely speak the language this is a constant frustration.
I also hate how hard it is to override location for other searches. I travel back and forth to my native country regularly, and so I’m often trying to search stuff or buy things for a different country than the one I’m literally in. If Google is so keen on making money from me, why can’t I tell it to do a Product search in a specific country, instead of forcing me to use a vpn to trick it?
Because they don’t make, or give a flying flip any you and vpn users. You are an not an important population to optimize around.
I’m not arguing that I am. I’m arguing that using an IP address to determine language settings is stupid, regardless of whether I’m using a VPN.
Accept-Language is usually used for localizations. The 2 main ways that are used to gather location information are the location permissions and IP’s.
The reason IPs are used primarily is they don’t need user consent since it’s being sent to the server. It allows an easy way to determine a close enough location for search results since it can get down to a metroplex or city.
Is user consent needed for the Accept-Language header? That would be kind of insane. I realize that it could be considered identifiable but that still feels strange to me.
I’m thinking mostly of localization, primarily language.
Localizations are used to convert between different languages. Just having a country code inside a header doesn’t give enough context where you are. For example states/provinces and their respective cities. Most of that is easily collected from the GeoIP information to give you local results for your area.
I’m in England and my language is set to English, yet for some reason when I was browsing AliExpress a few weeks ago it was stuck in German and I couldn’t see how to change it. Go to the homepage - German. Click on a result from a search engine - German.
I don’t know where it got that from, it wasn’t the IP either as from a computer on the same address it was fine.
AliExpress in particular is terrible with however they’re going about language selection. I have had this happen countless times and I don’t even travel or use a VPN. Like it’s based on a merchant you viewed or some other nonsense.
One reason is that IP’s can be more granular as another user pointed out. OTOH that doesn’t always work so well, either - I often get pinpointed to a location some 100km from where I actually am.
Another reason could be to circumvent people’s privacy or rather anonymity settings.
And since others brought up search engines etc., there’s a third reason: I always use English on my computer, but I am not in England. It’s nice to still get localised results (DDG has a drop-down to change this on the fly though).
Yaky@slrpnk.net 9 hours ago
Honestly, plain old ignorance. (and some anglo-centrism)
I am a software dev, worked on two translation projects at different points in time, and both of them were kind of a mess. In one case, translation team was all Americans (US company), and I was the only person who spoke another language and had firsthand experience with bad translation in media. When I asked how to switch the language in their app, senior dev told me to switch my OS language. Translations themselves often sounded overly verbose, robotic, or plain weird in other languages.
And then, the typical oversights like not leaving enough screen space for longer translated text, using ambiguous terms without providing context, badly splitting phrases. Text-in-image, etc.