kstenerud/safe-encoding
View on GitHub ↗ ★ 34 C
Binary-to-text encoding that is safe to pass through modern text processors
6 mentions on Hacker News by 1 person: 2 stories, 4 comments · first 2019-01-26 · latest 2024-06-12
20082026
-
…a "V"? a "U"? Is it case sensitive? Safe32 handles all that. Edit: Bleh, HN strips out the anchor. https://github.com/kstenerud/safe-encoding/tree/master/refer...
comment by kstenerud · 2024-06-12 · in Resilient Activation Codes with Safe32 -
▲ 1
Resilient Activation Codes with Safe32story by kstenerud · 2024-06-12 · 1 comment
-
I developed safe32 for this reason. https://github.com/kstenerud/safe-encoding/blob/master/safe3... Notably, confusable characters are interchangeable when being ingested (although a machine encoder MUST always produce canonical output).…
comment by kstenerud · 2024-06-05 · in You'll regret using natural keys -
…and then pass it through a binary-to-text converter designed to avoid confusing characters, like https://github.com/kstenerud/safe-encoding/blob/master/safe3... Then you don't leak information because it's all layered, encoded BEFORE you…
comment by kstenerud · 2019-03-04 · in Generating License Keys in 2019 -
…test for how they fare on uncompressed vs pre-compressed data when compressed with gzip: https://github.com/kstenerud/safe-encoding/blob/master/READM... radix-64 of course fares the best, but radix-85 isn't much different, and is 10%…
comment by kstenerud · 2019-01-31 · in What is the space overhead of Base64 encoding? -
▲ 7
Show HN: Binary-to-text encoding safe to pass through modern text processorsstory by kstenerud · 2019-01-26 · 0 comments