atomicthumbs

remote sensing practicioner

gregarious canid. avatar by ISANANIKA.


Website League address
@wolf@forest.stream
send me an email
atomicthumbs@wolf.observer
twitter but hopefully i only post photos there in the future
twitter.com/atomicthumbs
newsletter!! this one will let me tell you where i go
buttondown.com/atomicthumbs
newsletter rss same thing
buttondown.com/atomicthumbs/rss
Website League (centralized federation social media project)
websiteleague.org/
Push Processing (Website League photography instance)
pushprocess.ing/
88x31 button embed code
<a href="https://wolf.observer/88x31"><img src="https://wolf.observer/images/wolf-88x31.png" style="display: block; margin-left: auto; margin-right: auto;"></a>
forest.stream (general admission website league instance)
forest.stream/
bluesky (probably just for photos)
bsky.app/profile/wolf.observer
this will be a cohost museum someday
cohost.rip/

just had an idea for a keyboard-chat radio mode for use over bandwidth-constrained radio links that achieves usable text transmission rate for weak signals through grammar compression.

just turn each sentence fragment into a frame with FEC, have a pre-shared dictionary for given languages between clients. either assign more common words to take the fewest possible bits, or go farther and do word pairs. put as much logic in the clients as possible with the assumption that nobody is going to try to decode this on something with 4mhz and 16kb of ram.

build the dictionary by using wideband WebSDRs to analyze every conversation amateur radio operators are engaging in using PSK31 around the world, 24/7, until you have enough data. maybe even build different dictionaries for time of year, time of day, and region.

all sentences must be structured and terminated properly punctuation-wise to fit maximum information in limited bits. words and symbols that aren't in the dictionary get dropped down to UTF-8 with associated reduced speed/decode performance


You must log in to comment.

in reply to @atomicthumbs's post:

Brotli compression is a little like this, in that it also uses a dictionary of tokens commonly seen on webpages (https://en.wikipedia.org/wiki/Brotli#Algorithm)

The corpus they constructed leans strongly toward english, and the dictionary isn't often updated iirc. Zstd similarly you can train a dictionary ahead of time to make runtime compression much faster if you have predictable data

but yeah, if input text is normalized (like how you mentioned structure enforcement) and users operate them using designated structure and tokens (idk like radio nerds probably love to do anyways), a little finite state transistor with nodes at the end storing the symbol for the token, you could deffo make a really tight little compressor :)

I think for text compression in most irl scenarios, more general compression algorithms win out over fixed-grammar state machines iirc because language is so so variable