That’s a very good idea.
Beside the number of permutations it gives, another benefit of using three words is they could form the border of the QR code, with the fourth side being the domain name

Paper may be old-fashioned but I need something light for the carrier pigeon

My biggest bugbear relating to this is the lack of a short text alternative for QR codes, especially with long URLs.
If the URL is too long to fit into a QR code, then it’s also too long for me to type in manually!

I find it handy for writing down a URL on paper

expired SSL cert

I think it’s interesting that the phrase “ARM-free” roadmap is being used. I had no idea there had been so much market penetration of RISC-V already

I’m really grateful for the introduction to deceptive patterns here.
I was not aware of it, and I think it’s important to have language that can describe specifically how tech companies are trying to coerce people.

Cool!
It’s up to you how you do it but I just threw myself into writing with it. You can write something simple to post to the community if you like!

Even if English didn’t completely switch over, there are some fascinating possible uses for something like Shavian as a second alphabet. For example, it could be used as a pronunciation aid like furigana in Japanese, or in a novel it could be used to represent speech, and capture the accent of the speaker.
Well it’s fun to play around with anyway!

Ah that really sucks 🙁

I’ve been using it for about two weeks now, and as a British English speaker, I feel it can capture my accent when writing the vast majority of the time. My minor complaints about it so far are the places where I feel it isn’t unambiguously capturing my accent (the other commenter mentions 'R’s, that’s one of the issues).
Perhaps another important metric to measure it by would be whether people can reliably hear my accent when I write too.

I looked a bit into Quikscript, but I think that with the traction that Shavian has (unicode support is a big deal), and the fact that I’m not particularly interested in writing by hand, I thought Shavian would be a good start.

There’s a 1920 x 1200 non-touch display option, which will surely get you better battery life than OLED. But what’s most interesting about it is the 1-120 Hz variable refresh rate, which Dell says is a first to for this model. That extremely low refresh should help save power when static images or text is on the screen.

Ah yeah, I should have read the rest of the article. I didn’t know about that feature though, that’s cool

1 Hz display option: like an e-Ink display?

(it says 120Hz in the article)

She had to pick what to read too!
I think I’d last a week in that job, I’d end up choosing weird stuff and getting fired

Feels like a variation on this old quote:

The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.
origin unknown

I’m working towards something like that. I’m hoping to ultimately drop the smartphone altogether, and I’ve set my current phone’s end of life (2027ish?) as the goal.
I think the other thing that’s necessary to keep the same sense of connectedness is a device to receive notifications, and I have an open source smartwatch I want to program for that. I’ve been working on a notification server too (kind of like Gotify), but at the moment it’s a work in progress

By layers I mean image layers when manipulating an image in an image editor. So I guess what you’re saying is an image would be flattened before being passed to a compression algorithm?

I wonder if hypothetically, AI could do the same with a box over text, even if it was 100% opaque. For example, if the data from the layer containing text was part of the image data passed to an image compression algorithm, and that data was somehow reflected in the output

Misread as Pelletburo, now sad there’s no pet feeder called that

I think they had a RISC-V CPU as an experimental option for a while, but I couldn’t see it on their site recently.
Not sure what happened with that

EDIT: my mistake, it was an emulated RISC-V CPU, running on an FPGA (source)