Input lag, non-paper feel and heavy cloud-pushing are not the case with Remarkable. Documents can be uploaded and downloaded locally via a browser. Here is a good starting point with what can be done with a modded device, including self-hosting a replacement for Remarkable’s cloud services and installing a package manager to make installing further community software pretty easy. And for someone comfortable with the terminal, the Entware system lets you choose from a whole bunch of standard open-source packages you can add.

This isn’t going to give you what you’d think of as “a Linux desktop” or even Android-like experience, but OP wasn’t asking for that.

I hated this look at the time. I was wrong.

A11 is 18x26mm. Maybe you’re thinking more like A4?

ReMarkable devices would seem to fit what you’re asking, as document viewing and markup are practically all they do, they run Linux (not Android) and, I believe, are cloud-optional.

BTW, you can also ask in !ebookreaders@lemmy.zip

I’m Brian and so’s my wife!

No/F/Cali

Of course, how else are you gonna do a bidet battle?

No, two toilets per household, minimum!

How does the genie define “steak”? Are any potential future steaks also considered steaks? What I’m getting at is, if I mishandle the blade, do I turn delicious and nutritious for myself and others who may handle the blade in the future?

Read past the title and you’ll see OP listed other qualities they like in Reacher. It’s not hard to imagine that they might appreciate a good suggestion based on those.

Librera is for people who are Android users

I’d reword this a little, to

Librera is better for people who are Android readers exclusively

Because if you’re the type who uses a dedicated e-ink device for reading, also having the same application and book library on your phone has some obvious benefits. But if your phone is your one reading device, you’d probably try the Android version of KOReader and be like “wtf is with this UI?”

, and forced every single day.

That head/tail thing is kind of a goofy argument. For one thing they aren’t duals; tail is naturally more complex because the end of a file often changes and the application can optionally keep showing you the new output. Also, the fact that they’re separate applications in the first place is arguably better than the a one-application approach, which would always require a command line switch to select between outputting the start or end of a file. And finally, while I guess this could vary between implementations of head and tail, mine has identical switches for all the common options.

The license they’re looking for may not exist at all, but at the very least doesn’t exist within the Creative Commons world. They specifically don’t want attribution back to them to be required, and attribution at minimum is part of all the ‘traditional’ CC licenses. Deselecting attribution from the CC chooser forces you into a public domain license, which will allow anyone to do commercial stuff or charge for it, the other thing they don’t want.

Dang I thought this was linuxmemes for a sec.

I did too, for multiple secs, no joking. Capitalize proper nouns (outside of a terminal), folks!

Well, not anymore.

I feel like it’s yet another a thinly-veiled rant disguised as a question. Which is not to say I disagree with their premise, but there has to be a better community for this soapbox stuff.

When naming something, not only should you make sure it clearly describes the thing but doesn’t describe anything else. “AI pollution” sounds just as much like something that pollutes AI (for example, training it with false information), much like how “air pollution” is stuff that pollutes air.

Debian Testing doesn’t get timely security updates.

For starters, do you know if your laptop does S3 sleep or S0? I feel like the latter introduces a lot of uncertainty.

Another vote for Thunder, though I’m also kind of warming up to Summit.