BCsven

Volkswagen probably wanted the charging/discharge readings to be faked, unless plugged in /s

I enjoy both stages. The softened substrate version, and the overly hard dried out stage later

Glory

Then the boot entry is probabl messed up. You can try switching to legacy boot, instead of EFI just to see if you have luck but sounds like you will need to have a live USB stick to boot and repair your drive

My dad: Tumeric on potatoes is as "hot" as he can stand. Me, it's 5 Thai chillies ground up in the curry sauce, and since the coconut milk smooths out the heat I really could add a few more

Are you using efi boot. You may need to remove the windows selection and point it to the Linux efi selection in the boot options.

If you mean wipe windows OS off the SSD but keep your data such as music and photos that was on the same drive, that will be tricky if you had all your windows and data on one partition.

You could shrink the windows partition and create a new one to copy all your data to, then wipe the windows one, then grow the new partition...but there are a lot of steps where you could accidentally delete your data. Might be better to mount the windows drive and copy any necessary data to your new Linux drive first.

Personally I don't, I don't have facebook, I'm degoogled, I self host my images on an immich server, etc. But we should nt be victim blaming, companies like meta should be accountable and develop better policies

Besides application specifics, its how the internet works currently to give low latency. AWS, Azure, Linode etc have data centers across the globe to replicate data near where the people are.

Clean, easy distro to directly displace Windows. There next step is releasing Grid, which they claim will be a way for company admins to manage company wide deployments, configuration and updates.

It uses GNOME but they customized the backend so it doesn't look or act much like GNOME

Oh right, I skipped a part. It is not really a dev complexity prep issue. You build the database that serves the comments etc in as of in one place, then you deploy cache servers for scaling. They self replicate, so a comment in California gets commited to the dbase, the server in new York pulls the info over from the Cali change, it sends back that it is synced with the change. And vice versa. The caching servers do the work, not your program.

Caching servers, they self replicate when a change is committed, then send back a signal to main server that task has completed