![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
You’re right which is why our freezer is out in the garage rather than in the house.
Shine Get
You’re right which is why our freezer is out in the garage rather than in the house.
Another thing you can do is buy an ice vest - a vest with waterproof pockets for ice packs. They usually come with a load of extra ice packs so you can freeze and cycle through them. They’re great if you have to go outdoors for something.
AC is expensive but the freezer is already on so I’ve been rather creative with its use haha.
Doggo also enjoys a rubber bone thing that I fill with water and freeze so he can chew and stay cool. Also love freezing ice cubes full of berries and stuff too.
If you have a freezer and a fan, freeze a bunch of water bottles and then put them right behind your fan blades for a cheap AC-like chilly breeze. If you have enough bottles, you can cycle through them and refreeze as they thaw out.
He’s been here the whole time!
People forget that the research behind those vaccines had been going on for 30+ years. What was accelerated was the trials and the gathering and analysis of efficacy and safety data. The actual vaccine technology had been in existence for around a decade at the time.
Especially since, to calculate current location, it needs an input of initial location (i.e. it needs GPS coordinates to begin with so it can track direction and velocity relative to that initial position). You can’t replace something you depend upon.
We will find out when they push the update.
Only Google’s proprietary extension has encryption. The actual industry standard specification of RCS has no encryption defined at all.
Edit: It turns out Apple have refused to use Google’s proprietary encryption implementation and are instead working with GSMA to update the RCS Universal Profile specification to finally have encryption defined and standardised so that any RCS client can handle encrypted payloads (whereas only Google Messages today can do encrypted RCS and requires other users to be exclusively using Google Messages otherwise messages are sent unencrypted).
Because everyone is too distracted by “Apple bad” to realise how truly awful RCS is.
Bingo. RCS is yet another proprietary protocol, one controlled by Google (GSMA who originally designed it have practically forgotten about it for a decade) and without an open specification. RCS also doesn’t have a standardised approach to encryption as it’s designed for lawful interception.
So unless Apple have licensed Google’s implementation and extended version of RCS, this will be a shitty, insecure way to communicate between the Apple Messages and Google Messages apps and nothing more.
Google did an impressive job applying pressure and suggesting RCS was a perfect solution when in fact it’s just putting more control in Google’s hands. RCS is not an open “industry” standard. You nor I as individuals can implement it without paying license fees to see the specification and fees to have our implementations tested and accredited.
And Google have extended GSMA’s RCS with their own features (such as encryption) which is not part of the official standard and they haven’t made open either.
If Apple had been pressuring Google to implement the iMessage protocol or whatever, we’d have been up in arms (and rightfully so).
But instead of us all collectively hounding Apple and Google to ditch proprietary protocols and move to open ones such as Matrix, Signal, XMPP, etc (ones where we could all implement, use open source software clients, etc) we’ve got this shit:
Proprietary, insecure, non-private communication protocols baked into the heart of hundreds of millions of devices that everyone is now going to use by default instead of switching to something safer, private, public, open, auditable, etc etc.
BleachBit is a great alternative and it’s open sourced under GPLv3.
I’m European
0.63 Empire State Buildings. So yeah, quite a bit.
“Even more reason to switch to Linux!”
Linus Torvalds
Michael Scott
AMD began submitting Zen 5 patches for Linux this time last year and have been steadily submitting in anticipation of Zen 5 / Ryzen 9000.
So technically they’ve already released Linux support.
Edit: Proof from kernel.org showing Zen 5 named specifically.
Edit: I’m a dumbass. Ryzen AI 300 isn’t on Zen 5 but XDNA 2. XDNA support has been open sourced by AMD on GitHub and, according to a developer, they are trying to get it upstream too. The are committing to that repo all the time so I wouldn’t be surprised their XDNA 2 branch is merged in time for release.
Even more reason to switch to Linux!
Linux has lots of flavors; and just like ice cream, you can have a scoop, see if you like it, and try another one later.
I’ve been through so many Linux and Unix flavors over the years, it’s borderline absurd. But what was great is that I found a flavor just right for me and my needs, like finding your ideal car. Don’t worry about making the right decision on a flavor at the start, just dive in.
Ubuntu, Fedora, Mint, Pop! OS, Manjaro, elementary OS, Zorin etc are great starting points. You’ll hear people bigging up Arch, Nix, Gentoo, Slackware, Void, etc. There’s are all great in their own way and very well might be the right thing for you but don’t feel pressured to jump in the deep end (unless you love that thing, then be my guest - Arch was a lot of fun getting it up and running for the first time).
The best decision I can suggest is learning about mount points and having a drive dedicated to your files and simply mounting that drive inside your home directory. It means you can wipe and try another distro wherever you like without having to copy your files off and on over and over again.
Ignore the email, go to Google via your browser, sign in, reset your password, and move on.
Conway’s Law applies in this respect; the mess in governance of Nix has produced a product that reflects that mess. Nix started a beautiful movement but like many first movers, they rarely reap long-term rewards.