albertlast

From a techincal pov is ``2001:abc:123::2002`` -> ``2001:abc:123:0000:0000:0000:0000:2002`` based on this the existing logic work ``2001:abc:123::*`` -> ``2001:abc:123:0000:0000:0000:0000:0000`` a. ``2001:abc:123:0000:0000:0000:0000:ffff`` ``2001:abc:123::*:*`` -> ``2001:abc:123:0000:0000:0000:0000:0000`` a. ``2001:abc:123:0000:0000:0000:ffff:ffff`` ``2001:abc:123:*`` -> ``2001:abc:123:0000:0000:0000:0000:0000`` a. ``2001:abc:123:ffff:ffff:ffff:ffff:ffff``

Maybe a help text with further information would be helpfull?

> AFAICT, a double-colon expands to zero, so shouldn't `2001:abc:123::*` expand from `2001:abc:123:0000:0000:0000:0000` to `2001:abc:123:0000:ffff:ffff:ffff`? Since ``2001:abc:123::1234`` expand to ``2001:abc:123:0000:0000:0000:1234``, i don't think so, that the wild card operate differently....

still i don't believe that the common admin is known of subnet, so your pov is minority and most see the input mask als ip address where you mention behavior...

In my eyes would be this a huge uplift to redurce the complexity, by force everthing to be utf8mb4 AND to raise the min mysql version to 5.5. So I...

in my eyes smf 2.1 should run only in mb4 mode and should drop mb3 support, since it get again mysql and pg similiar and you don't had the struggle...

> I brought this current, in case folks wanted to test. I incorporated most feedback above. This required a rebase due to many layers of conflicts. > > I have...

From my pov the whole topic didn't exists in pg.

Whst is with "Convert HTML-entities to UTF-8 characters" is part of the migration or had the user run this by hisself after the mb4?

From where they know, that they had to doit?