That sort of horrible abuse only happens in areas where some provider has strict monopoly, but that’s an aberration and with Starlink’s availability there’s an upper bound nowadays.

Residential network access is oversold as everything else.

The only difference with storage is there’s a theoretical maximum on how much a single person can use.

But you could just as well limit backup upload speed for similar effect. Having something about fair use in ToS is really not that different.

Low profile scissors are a compromise. They are tactile but it's for once functional as it compensates for the obvious lack of travel. The result is a mediocre but still above average experience. You can type fast on them but with more fatigue than high-profile linear.

Marketers want you to believe there's at least three different distinct switch types for different purposes because they want to sell you the same keyboard twice or thrice. But in reality there's linear and stupid. And some of them make unnecessary noise. Some of them make really sweet nostalgia noises like Alps switches but it's still a worse typing experience.

The most popular type of switch is brown because it's essentially a linear switch that is not marketed towards gamers. It's just sad.

Marketing made up this story about linear switches being for gamers. So now every mechanical keyboard needs to make unnecessary noise and offer extra resistance for harder bottom out or you're not a serious typist.

But that's not inherent to the keyboard. Linear switches are not any louder than cheapo office high-profile membrane.

Some distros already do set lower defaults, e.g. pop os:

https://github.com/pop-os/default-settings/blob/master_noble...

Bazzite: https://github.com/ublue-os/bazzite/blob/main/system_files/d...

If we can’t mount a strong defense of free speech on principle alone then it’s doomed anyway.

That has been the successful strategy for e.g. NRA w/ regard to 2nd amendment and they have been proven correct every single time.

If only it would be that simple :)

In EU you have different procedures for B2C and B2B transactions. For B2B you need to verify the VAT number in VIES system and it’s not responsive like 50% of the time. I swear Germans literally turn off their servers when they go to sleep. If a customer provides a VAT number the flow might take even 12h+ to verify it. If you can do that verification you can use 0% VAT rate but if not you need to use a different VAT rate.

For B2C you need to support several scenarios: if company is outside of EU it needs to register for IOSS, if it’s a EU company that sells to other EU countries it needs to register for OSS or in each EU country for VAT separately but also a mix of both is possible. You can decide to no register to OSS special procedure but then there’s a sales limit before you have to register and you need to track it. Otherwise, you need to maintain special OSS registry with sales records and three pieces of proof that customer is based in the member country. Some EU countries have XML invoices (Italy, Romania, Germany soon) or mandatory invoice APIs (Poland), of course there’s actually no common EU standard so it depends on where the company is based.

Finally you need to choose a VAT rate for that country and they also change occasionally, e.g. Slovakia, Romania and Estonia all changed their highest rate just last year.

This is the bare minimum you need to support. There’s a lot of edge cases, e.g. it matters what country you actually ship from, and if you use e.g. fulfillment there are special procedures for that as well, or if you resell in B2B there are chain transactions which have their own set of spaghetti rules.

The computers are not secure and they should only be able to run “verified” operating systems using attestation mechanisms. This was always where this was ultimately going. The idea has been fermenting since the DVD players had copy protections.

It’s the planet destroying asteroid. We know the trajectory, we always knew it was coming for us. But once you can see with the naked eye it’s too late to do anything.

Sure, it might start out that way, but once adoption reaches anything critical the PII will be required to squash free speech as soon as possible. But by then the interaction flow will be familiar, hardly anyone will even notice, never mind care.

The EU has the best frog boiling experts in the world.

GrapheneOS presently doesn’t do anything different in this case, they pull it from AOSP without modifications. However you can disable it using the frontend app (SIM Toolkit) as someone pointed out, but as far as I can tell this requires the applet on SIM card to cooperate (offer the opt out).

Otherwise you can disable the STK altogether with ADB but that will also block you out of other SIM card interactive functions, which might not be a big deal however.

Edit: "We plan to add the ability to restrict the capabilities of SIM Toolkit as an attack surface reduction measure. (2022)"[2] and open issue[3].

[1] https://wladimir-tm4pda.github.io/porting/stk.html

[2] https://discuss.grapheneos.org/d/1492-blocking-sim-toolkit-m...

[3] https://github.com/GrapheneOS/os-issue-tracker/issues/875

Hopefully I explained it clearly. I haven't seen this idea anywhere else so I would be curious if someone smarter actually tried something like that already.