>>Groxx+obc
I would forgive quite a lot of the software decisions if they just let me export the snap-to-text highlights without the use of a third party tool. Many e-ink devices have had this feature for years now.

I currently use RCU (Remarkable Connection Utility) to extract my highlights: https://www.davisr.me/projects/rcu/

>>svat+Jic
SSH in and you have access to basically everything. The stock setup has two partitions for the OS (it toggles between them when you update, or toggles back if it fails to boot a few times) so you can:

Dual boot (disable updates and install any two you like): https://remarkable.guide/tech/dualboot.html

Some lower level details here: https://github.com/ddvk/remarkable-hacks/issues/304

And installing a specific release is largely automated: https://github.com/ddvk/remarkable-update

Last time I did it, I just did it manually - back up the OS version you want over ssh, then restore it whenever you want (on the non-active partition). And screwed it up the first time, and had to do a recovery: https://github.com/ddvk/remarkable2-recovery (requires using the contact pads on the spine for USB access - not too hard to solder up a pogo pin thing, but might take some time to get the parts).

So I'd recommend the automated way, though I haven't tried it yet :)

There's a (single) relatively active discord server if you want specific Q&As with other people too, or to double check whatever the current recommendations are (probably do that, as I'm somewhat out of date): https://discord.com/invite/nQ6nHwfDfc

And do definitely back up your data partition before making any major version movements tho, in case something doesn't work right and you need to roll back. I forget if/when that's necessary, but it's a good safety net just in case. And <8GB isn't much to store just in case.

>>scheme+cVc
The display driving code is part of their "xochitl" binary, which is not GPL (and might not be allowed to be, eink-the-company is rather protective of their tech and waveforms). ~All modding happens by reverse engineering the binary to call into that code, either to change behavior (rmhacks) or to act like a display driver for other software: https://github.com/ddvk/remarkable2-framebuffer

The rest has been released a few times, though last I checked it was quite out of date. Far from ideal, but still significantly better than most companies: https://developer.remarkable.com/