I am getting somewhat confused about this. That website seems to be equating (semi-?)-reasonable measures with monstrosities such as banning or effectively banning e2ee.
I don't think there are any particularly reputable brands of featurephones anymore. Nokia/HMD certainly isn't one: they have obnoxious bugs, they drop calls, and lack basic modern-day compatibility features like emoji in text messages (they display only an "unknown character" box) and group MMS.
However, it does not necessarily mean there is demand for a quality featurephone: it might be that the demand is so low that it does not make sense to manufacture one.
At least a while ago Element X broke bridging in a pretty annoying way, since all chats with more than 2 members were classified as groups, even if they were marked as DMs.
I think it's the conventional unemployment benefit system that should show measurable benefits, not other way around. All the tracking, surveillance, reporting and interviewing costs money, and should not be done for the sake of it.
Looks nice. Reminds me of MessagEase[1] and clones, such as ThumbKey[2]. I use the latter for my mobile text input needs. However, that method is sometimes prone to typos, since one key may have up to 9 different characters assigned to it, and it is easy to swipe slightly wrong way. QWERTYmini could be better in that aspect, since there are only 2 characters per key.
I think it is precisely because they are more distracting. When the most addictive thing in phones was the snake game, kids did not bother to insist in using their phones all the time. Now, when you try to tell a pupil to put the phone away, it often results in a huge arguments, so eventually teachers gave up.
If that "disaster" was so "inevitable", it would have happened ages ago.
It's not like it was somehow possible to accidentally sideload apps. You have to first find the correct option from the system settings to enable sideloading, and then approve the specific app source you want to install from.
It is not like how things are/were on Windows. Back in the turn of the millennium, it was easier to catch malware than it was to install useful apps. For former, you only needed to double-click on an email attachment, for the latter, you needed to actively to go look for the website of the app developer, and download it from there.
Android already was pretty much at the sweet spot between security and freedom, what it came to sideloading. What Google should have done was to crack down on the scam apps in Play Store. However, they are not going to do that, since it would cut their profits.
What those "people-who-don't-understand-the-risks" will do then, with more money left? I think they will give their money to all sorts of political populists, who will cause danger not only to themselves, but everyone.
One of my biggest grievances with typst is that it still does not natively support locale-aware decimal separator formatting[1], and thus requires various kludges to present decimal numbers properly in non-English languages. Not that LaTeX is any better in that, though.
I think this should be solved quicker, because if it requires some sort of changes to syntax, we will have problems if the "legacy" syntax becomes entrenched, so this sort of decisions are better to be made sooner than later.
However, most my experiences with typst have been highly positive. It is much, much faster than LaTeX, and way easier. I am looking forward to see it to become more common.
It is an official flavor[1], that is, maintained as a community effort, but endorsed by Ubuntu. The related packages are hosted in Ubuntu's universe repository[2]. There is indeed a risk of reputation damage.
I did use it some time ago, but I remember the user experience being somewhat confusing, since there are multiple similarly named tools around, which don't seem to be interoperable. Still, a cool concept.
In addition to the issue of microchips being inherently difficult to tamper with, smartcards have various hardware and software based anti-tampering measures, that are designed to destroy the chip, if someone attempts to extract the keys from the chip. That kind of security measures are never totally impermeable, but defeating them requires advanced equipment and skilled labour, and the R&D costs of the cracking devices need to be offset, too.
> We will also regularly publish security updates for as long as AOSP 14 is supported by Google.
That won't be for very long. We are at AOSP 17 now. It is sad that they design new phones with so old software.