Correct. In fact many, many companies have ASNs. Little companies all the way up to large ones. The key difference for an ISP is they allow you to route traffic through them. Almost every company that has an ASN blocks traffic from being routed through them, assuming they know how to configure that and that they have different peering points. Valve most certainly does not allow you to route through their network, they already have enough traffic just doing their own CDN stuff.

I think you’re still misunderstanding how this would work. So this battery swap setup is like the equivalent of going to the gas station. Basically, when your battery is close to being dead, you head to this place and get a fully charged battery. So it doesn’t matter that the battery is used, you just keeping swapping batteries out when you need it. Sure it would be annoying to know that when you bought the car, it came with a fresh battery that would get swapped out with an older battery, but you would have bought the car to get into the swapping system since this is mainly for folks that can’t do charging at home.

I think the battery swap is more like this.

https://www.youtube.com/watch?v=hNZy603as5w

No need to worry about pervious owners or anything. The system charges and maintains the bank of batteries you swap with.

If I don’t own the product after purchase, the button shouldn’t say “buy/purchase” it should say “rent”.

I do like the idea of industry standard license.

My thoughts are:

• They need to limit EULAs to something like 600 words.
• Make them binding and non-changing to the product purchased, only newly purchased products can get the updated EULA.
• They should make a Ethics Policy (things like no cheating, be kind, no swearing, etc.) separate from the EULA. This Ethics policy can be updated whenever.

“I’ll show you a gateway to heaven!” punch

How is it fiddly for Windows users?

What do you mean by that? Generate a new private/public key pair every time you setup a new TPM? Or when you boot the system or something?

You can’t do that since vulnerability is the connection between the TPM and the CPU, you need to encrypt that path.

The private key would have to stored in clear text somewhere. Potentially if you had non volatile space on cpu that to store the private key, that might work. But if you’re going to do that, might as well just use an ftpm.

Holy crap yes, honestly I get so tired of these firefox posts. I only get a Lemmy once a week or so now just cause every post is literally just how bad Chrome is and why you should switch to Firefox. XD

I’ve always envisioned this type of utopia to be robot based, with a few machines thrown in for sure. I’ve thought if you can robots plant, grow and harvest the raw food. Then have autonomous trucks drive that food to processing plants that then have robots and machines processing it. You then again have autonomous trucks drive it to the grocery “store” that then have robots placing the product you could in theory make all food free*. (add a billion asterisks to that last statement) Making the food free would probably require the entire economy to migrate to robot workers as much as possible or at least have it be where the robots make other robots so at least they are low cost/free to make. It’ll never happen, we’re totally destined for a Cyberpunk future instead of Star Trek future, but it’s at least fun to think about.

deleted by creator

I think the main issue with initial Led bulbs was their color was wrong. Incandescent bulbs emit light at 2700K, a nice warm white. Early LEDs emitted light at more like 5000K or there abouts, which is a really white light. Same with CFLs. Elderly people didn’t like that at all. Honestly it wasn’t just them, lots of people hated them for their too white of light.

Today you can get LEDs that are 2700K and/or are adjustable to what ever color you want.

Hell yeah, brother! 🤙

When v2 gets removed, why wouldn’t it be possible for ungoogled-chromium to just re-add it (or not remove it in the first place)? The more I think about it, the more silly it becomes that downstream forks would not be able to re-add v2 support. I mean, it’s all open source right? The code is right there. I guess it could be technically impossible, or perhaps the fundamental aspect of Chromium changes so much that you could not be able to do it.