Yes, that dangerous effect is indexed as GWP - global warming potential.
CO2 has a GWP of 1 in this context, while other refrigerants are worse - for example, R32 has a GWP of 675 (so 675x worse if it escapes), not sure about R290 (Propane), which I believe is either about 40 or 14…
Regarding EoL: At least around here, household appliances such as fridges are brought to a recycling yard and are properly taken care of in that regard… and as for heatpumps - those are only to be installed by certified professionals, for this very reason.
The global warming potential of hydrocarbons as such is generally overblown, since they oxidize into CO₂ in the atmosphere with a half-life of a decade or two.
That’s actually a good thing to me, wasn’t going to get another Apple Watch anyways - now that’s an even firmer decision now.
My reasoning so far was that I absolutely didn’t get the use out of it I envisioned and, to my even bigger surprise, the integration between Watch and iPhone wasn’t even that good…
A small icon that blends into the background of the UI and easily missed when driving, is not the same as a pop-up/audio cue informing the driver their location is currently/recently being accessed remotely.
> Seat position profiles is a great feature, making it automatic is completely unnecessary.
Driving a Model 3, I disagree - having seats and basically everything else adjust as soon as you open the door is the biggest boon I can imagine. I totally wish the rearview mirror would adjust as well…
I think the difference is that, on Windows, there are background services that constantly ping Microsoft with the device ID. A device ID on its own is not really harmful if it's not exposed to the internet.
Right, the danger here isn't stable unique data itself--there's already plenty of that--but the OS "telemetry" which steals [0] it and reports to Big-Brother along with too much other betraying information. Every site you visit, every program you run, the serial numbers of all your hardware, etc. Even if the GDID were totally absent, it would still be a correlate-able privacy nightmare.
Ultimately there's no informed consent here: The average consumer is disbelieving and surprised if you tell them what kinds of stuff Microsoft has/can put into a dossier. Nobody thinks: "Ah, Edge on a fresh Windows install, I'm glad Microsoft knows every site I visit, and can tell I'm a friend with someone because we use the same bluetooth speaker."
[0] It seems wrong to use the verb "leaks" when it's so obviously intentional.
I mean, there's a ton of unique identifiers on machines already tied to hardware and disks, but that must be a systemd thing since my Devuan machine does not have it.
But given there's no cloud accounts on linux I would imagine it's trivially changed just like a NIC's MAC
Also, seems unlikely it would be used for any single-signon with cloud services.
You're right. I have no idea what it's for, but I'm guessing for distinguishing between deployment images. I'm certainly not going to get too concerned about it.
The issue with the microsoft account was not unique IDs - tons of unique things on a machine.... it was a unique thing tied to an account and shipped to remote places.
There are _some_ cloud accounts for linux such as Ubuntu One, which I would fear could have similar identification capabilities if ever forced by to do so by a 3-letter agency
Any sort of online service you're logged into is going to have your IP and account correlated with a timestamp. Dropbox, GDrive, and even your e-mail provider. While a device identifier might be more useful it's not like the lack a device ID will keep you from being tracked.
reply