When doing a UserLookup I seem to be getting the User.Location back in a different language each time. For example:

User.Location Request 1 → 日本 神奈川県
User.Location Request 2 → Kanagawa-ken, Japan
User.Location Request 3 → 日本 神奈川県
User.Location Request 4 → Kanagawa-ken, Japan

Any reason why this might be happening?

What’s the User ID / screen_name? What endpoint & library are you using? is this users/lookup or users/show?

One example is this account: @coderyi9

I am using anaconda, but even on the Twitter profile page refreshing the page says ‘Beijing’ briefly before changing to Chinese.

This is users/lookup.

Anaconda is a package manager, which would install some libraries for you to use, not the library that interacts with twitter itself - do you have a code snippet, with the import statements?

@IgorBrigadir Anaconda, the golang twitter client: ChimeraCoder/anaconda

1 Like

Ah sorry i assumed Anaconda the Python distribution! Didn’t know about that Go library - thanks!

I noticed on the web interface it does the thing where it changes - i think this is just a weird web client thing.

The underlying data does not seem to change (i’m checking using twurl). I’m consistently getting

...
"location": "Beijing",
...

in the json.

My guess is that it’s some sort of eventual consistency issue? Either way, the location seems to be the same, except one is localized and the other is in English. No idea why that is!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.