albertlast

I got no direct issue with that, i saw the issue on smf side where we fixit and notice that you use the same logic -> same issue. The problem...

This are result of the issue that the cookie exists but is not more "valid" and the stuff get more complex when you now login because the cookie exists than...

in my eyes the right way. maybe you should go one step further, and force strict mode on mysql setups.

VACUUM and ANALYZE both run when the threshod is reached: https://www.postgresql.org/docs/9.5/static/routine-vacuuming.html#AUTOVACUUM From this point is no need to run by his self this commands (you should change the config of...

All information how identifier a person are personal information -> ip address (specialy ipv6) are persoal information.

intresting solution, but one thing is concerning me. This is the lock() thing, if i understand correctly: this mean you cant read data so long the data is generated. One...

This information was missing to me: // Check to see if the cache missed, which could mean that it either didn't // exist or was stale. If another process is...

Based on the description, The issue exists only in MySQL. In MySQL could be a workaround convert the database to mb4 and change the parameter in sub mysql file.

What i mean, smf is already prepared for this, since i added some time ago this parameter, which can be changed by hand: https://github.com/SimpleMachines/SMF2.1/blob/bb7f39482ba05b0d7d209f302e682d01e6a9fbd9/Sources/Subs-Db-mysql.php#L60

when i see this correctly ``2001:abc:123::ffff`` and ``2001:abc:123::0000`` are valid, but i guess the intention of the user is not this?