That’s called wakeonlan <MAC address>
That’s called wakeonlan <MAC address>
Tbh I had no issues with synapse.
The problems that persist: Very rare issues with decrypting (as I rarely encounter it, while being in encrypted chats with 150+ users, it’s not an issue for me), apart from after you changed clients, slow image loading (a bit annoying, but ok if you multitask anyway) and clients all having different feature sets (some of which you can also hackily make work in others).
Started at mount stupid, went to know nothing and am now stuck on valley of dispair. Also actually bricked my MB.
You are, by installing it in the first place.
From the beginning, the goal was not building an actually decentralized social media, but building an unmoderated hellhole for extremism.
No. That’s the point.
Abandoning Discord-only friends and using almost anything else is the true way.
Ez fix: sudo pacman -Rns discord && echo “127.0.0.1 discord.com *.discord.com” | sudo tee -a /etc/hosts
I prefer the arch wiki as a source: https://wiki.archlinux.org/title/Certbot#Nginx
Doesn’t certbot with the nginx plugin on the host just work?
Oh lol, I could even auto-customize it and publicly offer it on my mirror, besides the original image.
And I try to keep my ISOs up to date at all times. Though I sometimes forget it.
bash everywhere. Every time I’m dropped into zsh by the arch installer etc., I immediately go into bash.
The best part of the upper setup is Linus himself. Kinda hot tbh.
Just offer downloading the dependencies explicitly as well as the system ones lol
Just write your own PKGBUILD. It’s easy.
So not backups, but snapshots.
cut --help
andman cut
can teach you more than anyone here.But: “|” takes the output of the former command, and uses it as input for the latter. So it’s like copying the output of “echo […]”, executing “cut -d ‘/’ -f 6”, and pasting it into that. Then copy the output of “cut”, execute “base64 -d” and paste it there. Except the pipe (“|”) automates that on one line.
And yes, cut takes a string (so a list of characters, for example the url), split’s it at what -d specifies (eg. cut -d ‘/’ splits at “/”), so it now internally has a list of strings, “https:”, “”, “link.sfchronicle.com”, “external”, 41488169.38548", “aHR0cHM6Ly93d3cuaG90ZG9nYmlsbHMuY29tL2hhbWJ1cmdlci1tb2xkcy9idXJnZXItZG9nLW1vbGQ_c2lkPTY4MTNkMTljYzM0ZWJjZTE4NDA1ZGVjYSZzcz1QJnN0X3JpZD1udWxsJnV0bV9zb3VyY2U9bmV3c2xldHRlciZ1dG1fbWVkaXVtPWVtYWlsJnV0bV90ZXJtPWJyaWVmaW5nJnV0bV9jYW1wYWlnbj1zZmNfYml0ZWN1cmlvdXM” and “6813d19cc34ebce18405decaB7ef84e41”, and from that list outputs whatever is specified by -f (so eg. -f 6 means the 6th of those strings. And -f 2-3 means the 2nd to 3rd string. And -5 means everything up to and including the fifth, and 3- means everything after and including the third).
But all of that is explained better in the manpage (man cut). And the best way to learn is to just fuck around. So
echo "t es t str i n g, 1" | cut ...
and try various arguments.