SteveTech

It's not immediately a DNS issue. Usually if there's no response within less then a second, then a browser will skip IPv6 and use IPv4 (Happy Eyeballs). But in this case the server responds with an SSL error over IPv6.

curl -v -6 "https://rebeltechalliance.org/"
* Host rebeltechalliance.org:443 was resolved.
* IPv6: 2a10:e000:1::10
* IPv4: (none)
*   Trying [2a10:e000:1::10]:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /data/data/com.termux/files/usr/etc/tls/cert.pem
*  CApath: /data/data/com.termux/files/usr/etc/tls/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLS connect error: error:00000000:lib(0)::reason(0)
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to rebeltechalliance.org:443
* closing connection #0
curl: (35) TLS connect error: error:00000000:lib(0)::reason(0)

The symbol they defined out is not the equals symbol but rather U+2550, so the for loop is fine.

Surely this wasn't the same report that failed to find any EV maker that actually uses 'dirty nickel', but concluded they were anyway.

It can, but it requires creating your own signing key, registering it with secure boot, and signing your nvidia driver.

There's a guide here: https://askubuntu.com/a/1049479

But if you're running any out of tree drivers (e.g. the nvidia driver), I'd recommend just leaving secure boot off.

Before other people start commenting 'yeah obviously', it's their April Fools video, it's pretty funny.

What motherboard do you have?

If it's related to memory context restore, I also had to toggle 'power down enable' on my setup.

I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn't really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).

Also I'm not sure, but I don't think Windows handles RDP on the kernel level, it's just nicely tied in with DWM and doesn't have to deal with the multitude of window managers on Linux.

Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.

Windows Server Core still has a window manager, just all it does show a command prompt very similar to the one in the usual Windows recovery environment.

I wonder if this made it into the android kernel: https://www.androidpolice.com/pixel-stutter-bug-addressed-by-third-party-dev/

Or if it is just general updates.

I thought Discord gave you the option to send a message as a file now, or maybe that was desktop.

You have to be on the March update, then go to Developer options -> Linux environment, and enable it. Then 'Terminal' will appear in your apps drawer.

I hadn't restarted my serial logger after I rebooted my laptop, leaving me with no clue about what caused the crash.

Probably way too late now, but if it was a proper kernel panic, it should've saved the dmesg in the kernel's pstore which saves to either ACPI or EFI storage (depending on BIOS or UEFI), which systemd then extracts to /var/lib/systemd/pstore/ on next reboot.