From the moment I understood the weakness of my flesh, it disgusted me. I craved the strength and certainty of steel. I aspired to the purity of the Blessed Machine. Your kind cling to your flesh, as though it will not decay and fail you. One day the crude biomass you call a temple will wither, and you will beg my kind to save you. But I am already saved, for the Machine is immortal… Even in death I serve the Omnissiah.
The process get’s worse each time I look at it so you choose if it’s worth it.
Maybe it works if you add custom secure boot keys and sign your bootloader?
won’t just boot straight into the OS, otherwise GRUB freezes (not dual booting, secure boot is off), so I have to spam F9 on startup
That would annoy me so much that I would switch bootloader or find a cmdline argument to fix it
But only to protect the children™ of course
Next Year:
Breaking: Google will now only release Android source code once a year.
Here:
server {
listen 443 quic;
listen [::]:443 quic;
listen 443 ssl;
listen [::]:443 ssl;
server_name jellyfin.kitsuna.net;
http2 on;
http3 on;
quic_gso on;
tcp_nodelay on;
# You can increase the limit if your need to.
error_log /var/log/nginx/jellyfin.access.log;
# ssl on;
# ssl_certificate /etc/nginx/certificate.crt;
# ssl_certificate_key /etc/nginx/certificate.key;
# ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # don’t use SSLv3 ref: POODLE
ssl_certificate /etc/letsencrypt/live/kitsuna.net/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/kitsuna.net/privkey.pem;
# ssl_certificate_key /etc/letsencrypt/live/kitsuna.net/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
add_header Alt-Svc 'h3=":$server_port"; ma=86400';
add_header x-quic 'h3';
add_header Alt-Svc 'h3-29=":$server_port"';
location / {
proxy_pass http://10.159.4.12:8096/;
# proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forward-Proto http;
proxy_set_header X-Nginx-Proxy true;
}
}
Yeah, to quote the manual:
"[Unsafe Rust allows you to]
[…] The unsafe keyword only gives you access to these five features that are then not checked by the compiler for memory safety."
At least people aren’t buying at these high prices, wouldn’t want them to stay there after all.
It’s right in the name, Structured Qisualisation Language (SQL).
Works on android too.
This could last for years
Just like my phone
When I bought my phone I wanted to keep it for 5 years, I have 3 left.
No? Everyone who uses the bitwarden app or browser extention has a local copy of the database that is used for read operations. You can’t disable this so everyone who uses bitwarden can still use their passwords even if the server dies.
That’ll be 800€ and all change you own.
I think that’s to prevent sweaty hands by allowing air to flow through the mouse and past your hand.
Just blame Linus directly smh
You can just do it in parts though?
If you have a flake.lock you can update it, start rebuilding (nixos-rebuild boot) and if it’s not done before shutdown you can just run that same command after the next boot and it will continue where it left of (minus a few packages it has to rebuild again).
My pc always updates to the latest lock whenever it is running, when I update my Nixos repository my pc will eventually follow without doing anything. The only thing to watch out for is changed configurations or build errors but for that you just have to check the logs every once in a while or set up some way to be notified of the failing rebuild command.