All that stuff you talked about in the tabletop lore is literally talked about in the game. It’s not hitting you in the face in the main quest line, but if you play the side quests you find tons of fucked up shit that the corps are doing.

Because they would be the ones actually entering it, you would just say some numbers out loud.

But probably the smarter thing to do would be to leave the wipe code on a sticky note inside the phone case and hope they try it.

Because instead of unlocking, everything would get deleted when they entered the code.

I wonder though, if you had that set up and the cops ask you for the code to unlock and you told them the code to wipe and they end up wiping the phone. Would they be able to charge you with evidence tampering?

As if managers even know what RISC-V is

Its the server world that is demanding it. For most consumers 4.0 is more than enough, but servers are already maxing out 5.0 and will probably immediately max out 6.0 when devices actually become available.

the NSA (which lacks a mandate to act on US soil, and CF is a US company)

They absolutely do have a mandate to operate on US soil, that is actually the main mandate and there is a separate military agency (CNMF) that operates on foreign soil. They are both headed by the same guy though so they might as well just be one agency.

the thing about Recaptcha is that it didn’t always gate keep a google provided service, so that logic doesn’t really work. i agree though that we all benefit from less bots.

yahoogle

There is one extra step. I have an 6700xt, and with the docker containers, you just have to pass the environment variable HSA_OVERRIDE_GFX_VERSION=10.3.0 to allow that card to work. For cards other than 6000 series, you would need to look up the version to pass for your generation.

Here’s an example compose file that I use for ollama that runs ai models on my 6700xt.

version: '3'
services:
  ollama:
    image: ollama/ollama:rocm
    container_name: ollama
    devices:
      - /dev/kfd:/dev/kfd
      - /dev/dri:/dev/dri
    group_add:
      - video
    ports:
      - "11434:11434"
    environment:
      - HSA_OVERRIDE_GFX_VERSION=10.3.0
    volumes:
      - ollama_data:/root/.ollama

volumes:
  ollama_data:

have you tried the rocm docker containers that amd makes for your needs? it pretty much makes installing rocm on the base OS unneeded for me. https://hub.docker.com/u/rocm https://github.com/ROCm/ROCm-docker

it doesn’t, what this is suggesting is the vpn was routing traffic through it so they could analyze snapchat traffic. not the contents of it but essentially meta analysis of the traffic. how often it was sending data, how much data, where it was going etc.

just a small correction, /etc does get snapshotted when upgrades happen and will roll back along with everything else. you are correct though that home does not get snapshotted and is fully mutable.

I don’t have an answer to your nvidia question, but before you go and spend $2000 on an nvidia card, you should give the rocm docker containers a shot worh your existing card. https://hub.docker.com/u/rocm https://github.com/ROCm/ROCm-docker

it’s made my use of rocm 1000x easier than actually installing it on my system and was sufficient for my uses of running inference on my 6700xt.

We are talking about the non consensual circumcision of infants. Of course if an adult wants one done, they should be allowed to go do it, or if it is actually deemed medically necessary. 99% of these circumcisions are not though in the US. That’s what needs to be banned.

Except its not even, at least for christians. Its actually even considered a sin for catholics. https://catholicism.org/ad-rem-no-283.html

It became popular in the US because it was thought that it would stop people from masturbating. That’s why its an American thing and not a religious vs non religious thing (except for jewish people).

Immutable isnt really the best word for these distros. Its why fedora is changing the name to atomic, as in changes made to the system are done atomically like git. This also means changes can be rolled back just as easily as they were made.

The trick was to install VSCodium from the Toolbox

Another option you can try that I use is the dev containers extension which allows you to move your workspace to different containers from within vscode. I will say however, i have tried many times to get it working in vscodium and have been unsuccessful and it only seems to work in vscode proper.

With fedora atomic, lets say i wanted to try out kde desktop for a while. i would first pin my current build so i can roll back to it if i dont end liking kde with

$ sudo ostree admin pin 0

Then i would rebase to the kde branch with

$ rpm-ostree rebase fedora:fedora/39/x86_64/kinoite

Then just reboot. That’s literally it and i would have a kde system with all my layered packages and i could roll back to my old system at anytime.

all changes in etc are snapshotted with each update so you could just roll back to your previous version and it would fix it.

I assume you meant you messed up permissions in your home directory, and yes that is pretty much the only place you can permanently mess something up with silverblue.