[bisq-network/bisq-website] [WIP] Remove flags in locale selector (#243)

[erciccione]

@wiz

I guess you keep missing my point. **Using flags to rappresent country specific locales is not a good idea**. Countries are not as defined as you are picturing them. So you have to choose between a "globe" flag and an arbitrary flag, which as i repeated many times, can create conflicts. I don't see a point in using a system that is not consistent and will only cause confusion (making people choose between different locales in many languages will only be confusing and mess up people who use Tor or a VPN). See below for an example of an ankward situation that could couse political problems, only because of the presence of a flag.

@m52go 

I think why i want to avoid flags in this case is not clear, i'll make an example as well: An user is from north Kurdistan, Kurdish is not a single language, but changes depending by the area. Also, Kurdistan is an "unofficial" country, but sits on 4 different countries. Now, you have to choose which flag to use to reppresent Kurdish Kurmanji, which is spoken in northern kurdistan (southern turkey). That's both Turkish and Kurdish territory, but choosing one flag or another will piss off people from one country or the other and using a globe flag won't help you (beside being non consistent).
In your 2-points choice i will definitely choose the 1st. I understand it's not the optimal choice for bisq (since it has "country" specific form of payments), but it's safe and hussle-free.

---

To summarize my objections:

1. **Flags should always be avoided when dealing with the localization of software**. I had to mediate conflicts sparked because of disagreements between translators on how to use *a single word*. Introducing flags only adds another layer of potential conflicts that could be simply avoided.
2. I think **moving to locales instead of languages will create more confusion than intended**. As i said before, people using Tor or VPNs will have a worse UX. Users could also be confused by the unconsistent way languages + locales are shown, because this is open source, not FedEx, we will not have translations for all locales, not even close. Also, contributors come and go all the time and locales will have to be reverted to languages continuously (again, what's the point in creating a system you cannot keep consistent?).
3. The vast majority of Bisq users trade Monero (>90%), if we assume these people are more privacy-centric than other users, **i don't think they will appreciate to be geo-tracked**, even if assured that their data is not stored, doing so will give a feeling of "being watched". We can also assume a significant amount of privacy-aware users will use a VPN or Tor, which take us to the problem i spoke above (wrong locales and the need to switch).

I hope my objection is clear now, but as i said, i don't wish to push these arguments further. I'm the last arrived to the Bisq project, if "older" contributors prefer to introduce a new system and i'm the only one against, i will just accept the decision :)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-website/pull/243#issuecomment-531162514
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190913/317a1a6e/attachment.html>