recalendar.js VS remarkable-hacks

There's also https://recalendar.me/ that does something similar and is open source. It does struggle with larger documents, but everything happens locally.

Also there's https://recalendar.me

- Oh, it also this is a great tool if you like calendar/date based organization. https://recalendar.me/

I use one of my own fabrication, and prefer single-month PDFs. This is probably the best starting-point I can give you (highly customizable!): https://recalendar.me/

If this is news to you, there is a fantastic free and open source project at https://recalendar.me/ which you can check out (which sadly seems relatively abandoned).

Take a look at https://recalendar.me/. It's not habit specific but for calendars. But it is free and customizable. If this doesn't get you what you want, try Etsy.

https://recalendar.me/ customizable and free

Does anyone know if there is something similar to a bookmark feature (2.x software and https://github.com/ddvk/remarkable-hacks) for 3.x software? Anything ongoing for the next releases?

If you go the actual ddvk github page (here : https://github.com/ddvk/remarkable-hacks), you can read immediately that : Latest version supported:

Lots of info on Reddit. Link to GitHub https://github.com/ddvk/remarkable-hacks

You can have both using the switch.sh script to flip between partitions configured for 2.15 and 3.x but you can't use the same notebook. See here for latest on ddvk for 3.x.

I'm using the reMarkable 2 using reMarkable hacks for some extra utils that don't come on the stock app.

I just got my RM2 and this irritated me enough that I downgraded my firmware and installed remarkable-hacks, which has an option to disable zoom.

It doesn't officially support the 3.x software yet but you might want to keep an eye on https://github.com/ddvk/remarkable-hacks if you're looking to augment the software (especially if your rM2 still has the 2.15 software)

I know the binary patching for remarkable-hacks needs to be updated, but since the rmfakecloud just uses ssl proxying (afaik anyway) I wasn't sure if this still worked.