Eeems

It's an eInk screen, so yes-ish.

We get around this by just piggybacking on the build in application's screen display routines[0]

https://github.com/ddvk/remarkable2-framebuffer

I know I reacted hard to this statement:

> Going further down the rabbit hole, the toltec GitHub page mentions that it works on top of the Entware distribution, and recommends what is basically “wget | bash”. I’m not a fan of this. Could I install my own rsync?

We made sure that the toltec install process includes a hash of the install script to prove that it isn't modified by a man-in-the-middle. Toltec itself requires the use of SSL to connect after the fact, which lowers the risk after it's been installed. We are also exploring the implications of adding package signing[0].

0. https://github.com/toltec-dev/build/issues/14

Pretty sure they still do for some software they sell ;)

User friendly encryption is being worked on: https://github.com/toltec-dev/toltec/pull/318

You might be interested to see some more OSS that can be deployed on it:

https://github.com/reHackable/awesome-reMarkable

https://toltec-dev.org/

Not locked at all[1]. The rM2 is not quite as known as the rM1, but it seems to still be just as open if you have the right hardware to tell it to get into recovery mode[2]

[1] https://github.com/ddvk/remarkable-uuuflash [2] https://github.com/ddvk/remarkable2-recovery

Wacom touchscreen or pen input? I don't know of any eReaders that have pen input.

Also, are these devices properly GPL compliant?

You already have root access to the reMarkable devices. Plus they are GPL compliant, so you have access to source for most of the software.

What do you mean by this? Are you asking what bootloader it uses?

Knowing a bit of his personal history I can kind of understand why he acts the way he does, and has the opinions he does. Doesn't excuse some of it, but at least I kinda get why.

I just wish his name would stop coming up for me tied to opinion pieces like this. I'd rather just see things about how some project he's working on is doing great and being widely adopted.

Yup, been throwing this link throughout the thread as well.

It is, but we are still working on sorting out the screen. You can follow progress here: https://github.com/ddvk/remarkable2-framebuffer

https://github.com/koreader/koreader/issues/6792 If you'd like to follow the progress.

To follow up on the other comments about changing the suspend image: https://remarkablewiki.com/tips/splashscreens

Well the reMarkable isn't an eBook reader. That is something it can do, but it's more aimed at note taking. You also have root access out of box, which is not something that eBook readers give you.

It's not official, but you could always use https://www.npmjs.com/package/remarkable-typescript or write your own thing to work against https://github.com/splitbrain/ReMarkableAPI/wiki

Anything that uses the screen on the reMarkable will not work on the rM2 yet. https://github.com/ddvk/remarkable2-framebuffer is being worked on to address that.

It's being worked on https://github.com/koreader/koreader/issues/6792

There should be a video available soon that you can follow along with soon. I'll make sure this comment is replied to with a link when it's up.

They just recently released their toolchain for the reMarkable 2 https://github.com/reMarkable/linux/issues/7 The toolchain for the rM1 has been out for a long time. Since it's just a linux device, there is a ton of existing documentation on how to work with it.