I informed myself and just figured out that you don’t even really care about the weblist or anything else.
I still have ENOUGH reasons to complain about this issue!
I don’t give a single damn about the IP2LOC DB into the server. So I mean it’s still good, that you’ve done this step (1 from 2) but I honestly don’t understand, why you still stuck in the weblist with that problem.
Yup — and that’s possibly one of the the worst existing problem since more than 10 years. Didn’t you notice that? Holy crap!
WHY? Because it’s “hardcoded” or how you ever describe it? The developers don’t have enough working hours to do this? High priority to other things, like a lot stuff which never gets finished somehow? So «never»… just talking about a long time.
Yeah… that’s good. But when? In another 5 or 10 years, how long do we have to wait?
Here’s a temporary solution: Just remove IP2LOC from the Weblist and use something else (as example: MaxMind…).
According to my experience with TeamSpeak, there’s never going to be a fast way to fix this. Either you totally fix this after a few years (which makes no sense) or just find a temporary solution to fix this, to avoid such a «sh!t-storm» for the next years maybe.
Yes yes… not enough developers I guess. Or just some volunteer which have some free time to do this tiny little thing.
I’ve heard somehow that there was a ‹draft›-project about the weblist a few years ago from the TeamSpeak team. But it was discarded somehow. Why?
I’m sure that TeamSpeak is hiding something about this god damn weblist… nobody can tell me something else.
AMEN.
