When you press a button on this revolutionary machine, it will automatically left click for you!

A combination of heaters and being mostly deployed in warmer environments, I’d assume.

Also, KOReader adds a bunch of extra features and functionality.

Kindles are really hard to root. Use XDA Developers forum for this kind of thing. https://xdaforums.com/t/fire-hd-8-2018-only-unbrick-downgrade-unlock-root.3894256/, which is what that guide is based on, looks like it only works for the 2018 version and seems way more difficult and risky than most ROM installations. Also, that won’t install Linux, just a different Android version.

Honestly, an actual ereader might work out better for you if that’s all you plan to do.

You can’t do that. Installing custom ROMs on Android devices is very different than installing an OS on a desktop/laptop. Most devices don’t allow changing the OS at all, most of the ones that do don’t have any Linux builds, and then you’ll be stuck with whatever distro you’re given (probably UBPorts or maybe PostmarketOS) rather than choosing your own.

What do you think an API is? They have reverse engineered the iMessage API and are using that to connect to the iMessage servers. It is literally impossible to do as you suggest (use entirely their own resources) because iMessage is centralized and cannot federate with any other server, even if one did exist.

And that’s what they’re doing.

How? It’s not a MitM or anything like that, it’s connecting exactly how an Apple device would connect. Everything is still E2EE, just one of the ends can now be an Android device.

I think their RSS feed has a placeholder title for this.

Vivaldi does too. It’s nice.

From what I understand, their guess is that Apple is now checking if the device also has support for other services, such as FaceTime. Beeper Mini and pypush don’t pretend to support FaceTime, so it breaks.

Their hope was that they got close enough to an actual Apple device that breaking it would break Apple devices. It turns out they weren’t close enough, but they could be with a few improvements.

Because they can’t break that. It’s using real Macs, so if they break iMessage for Beeper Cloud, they break it for their customers.

Yes. Why?

Yes. They have a fork of Synapse that they can continue to use even if the license prevents them from using upstream (which doesn’t seem true, but I could be wrong).

Kind of, but it’s more complicated. I’m not sure if the app itself will be open source, but currently, the method they use is. Either way, the hardest part is already done, but you still need a client (maybe; they might open-source it) and a notification server. I’m planning to attempt to build a Matrix bridge if I have enough time and it’s not beyond my skills, but if you don’t want the messages to be decrypted by the server, making the notification server and maybe client would be really difficult.

Intentional ineptitude resulting from malice is still malice.

That’s to prevent multiple entries by one person. Their security is very good, with audits and their products being largely open source (for this, PyPush. For Beeper Cloud, their Synapse fork and their bridges.). Only the parts that don’t matter to security (the clients, mostly) are closed source.

No, they know that a message has been received, but the phone is what decrypts the message. Beeper can’t see it.