As much as I can see, the uLogin servie have added some tracking code to their authorisation backend. This have nothing to do with my hook, cause all it does is adding uLogin service to IP.Board using the API they provided. I'm neither owner, nor connected with uLogin in any way, and can't comment on why they did this, or is this safe or not to rely on this service. uLogin have "terms of service" on their site - http://ulogin.ru/rules.html - where they are stating the fact that they may collect statictic on usage. Installing this hook should probably mean acceptance of this policy. For clarify, and because of "shop.a108.net" insults, I think it will be a good solution to add this 2 statements into hook description:
Actually, a lot of people are still using uLogin and not considering visitor tracking as something harmfull. And so I do. But in the end - it's up to you to decide - is it safe to let this hook be in IPS Marketplace, or not.
$INFO['sql_charset'] was added as a small workaround for those, who don't know how to configure their servers well. If you create your new database with default collation set as ut8_general_ci (for example), an if you push "default-character-set=utf8" to my.cnf - there will be no need in $INFO['sql_charset'] at all. And actually that's the only correct way to configure your MySQL as IP.Board to work with UTF-8. Triggering "SET NAMES" on each query - isn't. That's why it's hidden by default, to be used only by those, who is using cheap shared hosting and can't reconfigure their servers.