This sounds great, but I would like them to see them fix bugs first, like this 6yr old one, with over 160 comments: https://github.com/openzfs/zfs/issues/9130 Every new feature, esp a complex one like this, creates a potentially huge amount of new bugs. Love ZFS, but would never run it without backups. Haven’t had data lose, but needed to restore from backups to get around constant panics.
I have created something "almost the same" but different.
I call it zquickinit - it's basically a bash script that generates initramfs - but adds in things like ZFSBootMenu, a proxmox installer, etc. I patched ZFSBootMenu so that I can securely boot/unlock the ZFS root boot, which holds the unlock key for the 2nd stage ZFS data pool.
I did this so that my ZFS install can have 0 keys in it. I use tailscale or ssh to access it in pre-boot mode, enter my key, and continue-on with boot.
Sounds very similar to how SyncThing. I would if the SymcThing discovery and NAT traversal could be combined with wireguard and the ease of tailscale, but distributed mesh and no headscale. And all the other things that tinc does.
A QR code on a yoghurt that I bought couple of months ago came with some interstitial ad due to an unpaid fee. It made me double check the yoghurt's expiration date.
Fun to imagine in the abstract. I used to take classes in a building designed to have a certain appearance from above, and the user experience was definitely the worse for it
Error correction doesn't make it impossible to change a message by flipping bits, you just have to change enough bits, and know which bits to flip. I wouldn't rule out, that if you are being smart about it, you might be able to change it into a different valid url, without having to change too many of the squares. You might even be able to use the error correction to your advantage to an extend.
You could use an unnecessarily big QR code for extra correction bits to mitigate this somewhat (up to the maximum correction standard (30%?) even if that means 41 cell code instead of a 33 cell one). For URLs another size hack is to include meaningless extra data (a qstring parameter or anchor that won't be interpreted). This doesn't increase the error protection in itself, but gives the fancier more data to work with so it can produce better visual results without losing more of the signal correction strength. Using the generator at https://qrbtf.com/ someone linked above, try the “C2” style with https://qrbtf.com/ and https://qrbtf.com/#some-extra-data-to-increase-the-image-siz... to see the difference this makes.
The issue with artsy QR codes often isn't the individual bit flips, but that they often include large areas of all black or all white which can make it harder for the reader to pick up the actually correct bits if the viewing angle and lighting aren't perfect. The standard includes 8 mask patterns that you can freely choose from, the intention being that you pick the one which gives most black/white variation in the final result, so there is as few low-contrast areas as possible. With improvements in cameras and processing built into QR scanners these days this is becoming less of a concern, but if you need your code to be reliably readable by older devices, probably stay away from the fancy tricks.
The fancy tricks are cool though, worth all the caveats if they match your stylistic needs.
I love seeing companies blindly encoding massive URLs into QR codes that end up being ridiculously detailed images. Like they would be impossible to scan unless you were right up close with a good camera because the individual dots are so small.
Enjoy your time there -- a lot of people complain about it but I truly loved RIT. I hope they've maintained some of the feel of the campus among all the development which has happened... I can't believe that the Riverknoll apartments are apparently still in use!
I recommend picking up a philosophy class with Dr Selinger if you've got a free elective hanging around.
PS the semester system is bullshit, quarters forever
I end up back on campus now and then, despite having graduated and moved away ten years ago - it's definitely just as interesting to see what's changed as what _hasn't_ changed.
I graduated right before the quarter-to-semester conversion happened, and heard more than my share of horror stories about lagging 10-week classes getting taught in 15, or worse, two 10-week classes smashed into a 20-week class, then taught in 15. Luckily, the writing was on the wall, so I ended up taking 32 course credits off-campus, and providing three years of pay stubs so that I could count part-time work as a co-op block, just so that I could graduate early.
Could you scrape/pre-parse every article and comment on your own server, and then create your own better REST api for your app? One that doesn’t need as much parsing. Maybe you can even charge $ for access (for other apps)
Unfortunately not. Since my app allows voting, commenting, favouriting etc, doing that on my server side won’t be possible as I don’t have access to the user authentication cookies.
Do what my psychologist told me: read “Your Brain's Not Broken: Strategies for Navigating Your Emotions and Life with ADHD” by Tamara Rosier, PHd. This book will help you confirm (or not) that you have ADHD. This book was SO life changing and eye opening. I wish I had known this 20yrs ago. (I’m 42)
