I know this is (quite explicitly) targeting a rather specific usecase, but I wonder if it could also have value in terrestrial security measures; even truly accidental bit flips are a problem even on the ground (with https://en.wikipedia.org/wiki/Bitsquatting as perhaps the best example), but it looks like this would probably protect against intentional ex. rowhammer. At the very tiny cost of 200-300% overhead, of course:)
Is that a stringly-typed enum? Is that not... unidiomatic?
r0nlt · 8h ago
Thanks. Good tips! Im cleaning it up right now. Just need some time to look it over.
yjftsjthsd-h · 4h ago
Honestly it looks very polished, especially so for something just published but frankly you're doing better than many projects already. Like, the actual tech is interesting, but you've really landed the stuff around it; if every project had this amount of detail for things like the Contributing section, life would be much easier. (Also, I was serious about the stringly-typed enum, but that is a minor nitpick on a solid project.)
r0nlt · 4h ago
Thank you for the kind words! Im just looking to get noticed, it sucks when you study this hard for four years in college and the job market just glances at you like a nobody. Im just hoping this helps me get out of unemployment and eternal doom at my mom's house in the middle of nowhere.
I know this is (quite explicitly) targeting a rather specific usecase, but I wonder if it could also have value in terrestrial security measures; even truly accidental bit flips are a problem even on the ground (with https://en.wikipedia.org/wiki/Bitsquatting as perhaps the best example), but it looks like this would probably protect against intentional ex. rowhammer. At the very tiny cost of 200-300% overhead, of course:)
Also, a nitpick:
Is that a stringly-typed enum? Is that not... unidiomatic?