

Next Year:
Breaking: Google will now only release Android source code once a year.


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.


With a long enough hosepipe he could fly over buildings.
Just wait for rain
I don’t know but try it: https://abrahamjuliot.github.io/creepjs
And all that’s left is your fully trackable browser fingerprint.


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.


It’s reminders all the way down


our right
It helps but it’s too expensive to distribute to everyone.


Yeah I tried just now and it diesn’t seem to be working (anymore?) could’ve sworn that worked.
You can still kexec the installiers directly, I followed the netboot.xyz scripts and got the links they use. Here’s Debian as an example:
From the scripts: https://deb.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/ looking at the boot config debian-installer/amd64/grub/grub.cfg
submenu '... KDE Plasma desktop boot menu ...' {
set gfxpayload=keep
menuentry '... Install' {
set background_color=black
linux /debian-installer/amd64/linux desktop=kde vga=788 --- quiet
initrd /debian-installer/amd64/initrd.gz
so we need to download those two files and take the netboot.xyz cmdline arguments then
$ kexec --command-line="desktop=kde vga=788 mirror/suite=stable initrd=initrd.magic console=ttyS0,115200n8" --initrd=initrd.gz -l linux´
$ systemctl kexec
and it boots.
also here’s an example for the nixos netboot commands, more on that in the nixos manual:
$ kexec --load bzImage \
--initrd=initrd.gz \
--command-line "init=/nix/store/n37nmcvbrblk9ahfzj9nxy01axs7zsf6-nixos-system-nixos-kexec-25.11pre-git/init nohibernate loglevel=4 lsm=landlock,yama,bpf"
$ systemctl kexec
Edit:
No console access
If that means that you can only connect to SSH and have no VGA/video then this will be limited, you could setup an automated install but that requires a lot more knowledge than what your guide requires.
To understand recursion, first you must understand terminal capitalism.