We don't need a new GPL.. ML creating a derivative work is still a derivative work. So if said derivative work ends up in a non gpl compatible code base, that code base is then violating the license. I would assume that GitHub/Microsoft would have had the forethought for this, but who knows. And in any case, I am not a lawyer...
We'd love to hear about these zero days over at security@pidgin.im so we can fix them or you can just keep spouting about stuff that afaict doesn't actual exist.
Gtk3 has a Quartz backend and Pidgin 3 will be native on Mac OS. It builds and runs now, but packaging has been a pain so I haven't worked that into our CI yet.
not to mention that a git branch is NOT your typical VCS branch. It's an ephemeral named head, nothing more than a tag (that lives outside of the normal tag interface).
So to be "safe" and "secure" we can only have strings 256 characters long, or we need to waste a few bytes repeatedly for short strings. Sounds like the UTF-8 vs UTF-16/32 debate..