vsz on Nostr: nprofile1q…lkxk4 nprofile1q…6jkcn If only the transition to native Unicode ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqp450apv3j8jmqjct3ddfklzusxyfkkyqpzxx4p33u099xjzvfwwsjlkxk4 (nprofile…kxk4) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq04e6xt23sdp5z9nlfv9cukey28ahtzjsrewuwjqv9v7y89tjqj4q86jkcn (nprofile…jkcn) If only the transition to native Unicode wouldn't be a gargantuan undertaking. The world isn't UTF-16, so these interfaces need to be identified (with their encoding/codepage) and a conversions put in place. Windows UTF-8 support could be a solution, but it's stuck in beta, with issues. Switching the official curl build to Unicode is an option, but there are unresolved issues, e.g. string encoding in the libcurl API is undefined. I wish this would be easier.