soc.octade.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
https://csiph.com/group/alt.flashback/a/11cnl7j%24377an%241@paganini.bofh.team
@conlang@soc.octade.net
@8@star.octade.net
@abbey@ars-cotidiana.eu
Ideas for Hexlish improvement
In my initial off-the cuff idea the 'spacing characters that don't belong' can just be filtered out or parser-inserted where spaces are found in the text just prior to encoding.
Use the space character as a stream shift register or top-bit range toggle in the encoding logic. Then any punctuation character can be placed after the space. The parser will pick up the characters, re-encode them, and toggle back at the next space. A checker would need to look for double toggle characters in sequence.
This would necessitate swapping out one alphabet character and it would require slightly more complex logic for simple ciphers to use. But it goes in a doable direction.
Abbey Schnabel suggested using the dot (.) as a character and marker and rendering Hexlish as all lower-case. These are sound improvements to legibility.
At first glance, I can't help but think spaces would be better. As for rendering it all lower-case, it could actually be case insensitive, and every letter could be treated as lowercase or uppercase regardless, using a shift or toggle nybble in the encoding stream.
It is too complex for me to wrap my brain around all the potential quirks right now, so maybe the first week of next month I'll sit down and really brainstorm it on paper.
#Hexlish #Conlang #Alphabets #English #Hexadecimal #Encoding
#Cryptography #Ciphers #Crypto #Encryption #Compression #Papers
#Preprints #Orthography #Language #Linguistics #Writing #Glyphs
#Alphabetology #Technology
Arguments concerning amendments to the Hexlish alphabet
by Abbey Schnabel
https://zenodo.org/records/24021289
"Increasing readability and usability over sentence borders by
introduction of special character transliterations"
#Hexlish #Conlang #Alphabets #English #Hexadecimal #Encoding #Cryptography #Ciphers #Crypto #Encryption #Compression #Papers #Preprints #Orthography #Language #Linguistics #Writing #Glyphs #Alphabetology #Technology
Hexlish Alphabet for English, Constructed Languages and Cryptography: Automatic, Structural Compression with a Phonetic Hexadecimal Alphabet
DOI : https://doi.org/10.5281/zenodo.13139469
Hexlish is a legible, sixteen-letter alphabet for writing the English language and for encoding text as legible base 16 or compressed binary. Texts composed using the alphabet are automatically compressed by exactly fifty percent when converted from Hexlish characters into binary characters. Although technically lossy, this syntactic compression enables recovery of the correct English letters via syntactic reconstruction. The implementer can predict the size of the compressed binary file and the size of the text that will result from decompression. Generally it is intuitive to recognize English alphabet analogues to Hexlish words. This makes Hexlish a legible alternative to the standard hexadecimal alphabet.
-
#Hexlish #Conlang #Alphabets #English #Hexadecimal #Encoding #Cryptography #Ciphers #Crypto #Encryption #Compression #Papers #Preprints #Orthography #Language #Linguistics #Writing #Glyphs #Alphabetology #Technology
Just out of curiosity, I set up an experiment where I took a jpeg file, and re-compressed it as a new jpeg file at 50% quality/quantization, and re-compressed it over and over again until I had one thousand jpegs.
Conclusion?
After the first 24 recompressions, the JPEG recompressions produced EXACTLY the same file. NO further degradation.
I poop you not.
In order to actually produce 1,000 gradually degrading JPEGs, I had to change it to use a random quantization each time between 50-59%.
#JPEG is flipping amazing, y'all. This codec does not get enough respect.
#UnixShell one liner:
Produces 1000 files, only the first 25 will differ:
y=; for x in vg{000..999}.jpeg; do if ! [[ $y ]]; then y=vg000.jpeg; continue; fi; echo $x; magick $y temp.tga; magick temp.tga -quality 50 $x; rm temp.tga; y=$x; done
("vg" stands for [Van Gogh] ;)
Outcome:
sequence size md5sum
---------- ------- --------------------------------
vg000.jpeg 618,432 52329db17e16a7599ea21ccc74b30a2b
vg024.jpeg 282,996 d57aa73cad595db8beff7b841210a874
vg025.jpeg 282,996 b48ed718c660b396f6b1756dc509be49
vg999.jpeg 282,996 b48ed718c660b396f6b1756dc509be49
Produces 1000 gradually degrading files by randomly varying the quantization factor a little, all but two were unique (according to md5sum):
y=; for x in vg{000..999}.jpeg; do if ! [[ $y ]]; then y=vg000.jpeg; continue; fi; echo $x; magick $y temp.tga; magick temp.tga -quality $((50+RANDOM%10)) $x; rm temp.tga; y=$x; done
Hexlish Alphabet for English, Constructed Languages and Cryptography: Automatic, Structural Compression with a Phonetic Hexadecimal Alphabet
DOI : https://doi.org/10.5281/zenodo.13139469
Hexlish is a legible, sixteen-letter alphabet for writing the English language and for encoding text as legible base 16 or compressed binary. Texts composed using the alphabet are automatically compressed by exactly fifty percent when converted from Hexlish characters into binary characters. Although technically lossy, this syntactic compression enables recovery of the correct English letters via syntactic reconstruction. The implementer can predict the size of the compressed binary file and the size of the text that will result from decompression. Generally it is intuitive to recognize English alphabet analogues to Hexlish words. This makes Hexlish a legible alternative to the standard hexadecimal alphabet.
#Hexlish #Conlang #Alphabets #English #Hexadecimal #Encoding #Cryptography #Ciphers #Crypto #Encryption #Compression #Papers #Preprints #Orthography #Language #Linguistics #Writing #Glyphs #Alphabetology #Technology