This format’s from 2017 I’m pretty sure.

https://hepwori.github.io/execorder/

Running Windows is officially supported by Apple, yes most guides use bootcamp to set it up, but you should be able to create an install drive like a normal PC and boot from it by holding Option/Alt as you press the power button. Mac’s usually just use EFI like any modern PC under the hood.

Nah, bootcamp assistant is Apple’s dual boot setup tool, it is a native install, but it has to be started from MacOS.

ghost is just GitHub’s way of saying deleted user.

Not to defend them, but he did follow up with this:

This is referring to the technology we just released into BETA for premium subscribers, which delivers one of the lowest latencies for livestreaming (significantly better than YouTube’s latency).

This does not refer to encoding

https://xcancel.com/chrispavlovski/status/1856090182275215803

Although quality != latency, so idk.

TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process

They don’t even need to be the same process. I’m pretty sure that’s just a common practice if something needs both protocols, but there’s nothing stopping you from having a web server on TCP 443 and a VPN server on UDP 443. Ports are an abstraction brought by each protocol, they aren’t in anyway related.

For projects like this where they’re hooking into the compiled python binaries, you really want to match the version.

Like 3.11 and 3.12 were pretty much released a year apart, a lot can change implementation wise.

After reading their blog, it seems like it doesn’t support Python 3.12, and it looks like you’re using Python 3.12.

Also if you tap on the ‘kebab’ menu and press View Source, you can copy the message.

There’s The Serial Port, It’s not really ‘home networks’, but he finds and sets up very early (~80-90s) ISP gear and explains how it works and the history of it. Similar to how Ben Eater uses an ‘old’ 6502 to explain stuff.

I’ve seen some that activate an insane number of breakpoints, so that the page freezes when the dev tools open. Although Firefox let’s you disable breaking on breakpoints all together, so it only really stops those that don’t know what they’re doing.

I have no idea how CoW interacts with NTFS

With btrfs you can disable COW for specific files, that might give you a little performance boost.

Cloudflare tunnels uses a QUIC connection between the cloudflared on the server and Cloudflare itself, which is encrypted similarly to HTTPS.

Whatever protocol cloudflared uses to talk to your webserver locally is configurable through the Cloudflare access web UI (just change http to https). I’ve actually got it configured to use unix sockets, which lets me treat it differently in my nginx config.

It’s probably blocked for whatever reason (maybe less than 90 days old?)

My work and Uni do the same thing, they don’t do full SSL inspection, so most websites don’t need a custom certificate authority; but if the SNI is blocked then they need a custom certificate to hijack and display a blocked message, most browsers will detect this as a MITM and display a not secure message instead.

There’s a third one I’ve heard:

• Intel VPro (the thing that privacy people disable because runs at a lower level than the OS and does mysterious stuff), is being used to remove the broken file while the OS is booting/crashed.

IIRC the RTL chip inside them was originally designed for TV, so it works great! I’m actually using very cheap AliExpress clones for the TV ones, because they otherwise don’t work very well.

I’m also using the outdoor TV antenna on my roof (common in Australia, idk elsewhere), and a splitter and adaptors. And with that I get every channel with no artifacts, at 30% strength, but that’ll probably be higher with not awful SDRs.

I’ve got an interesting setup I’d like to share:

So I’ve got a Raspberry Pi with 4 RTL-SDRs, 2 for TV, 1 for radio, and 1 for plane transponders. That runs SatPi for the 2 TV SDRs, which TVHeadend running on my main server connects to, to record and stream. Jellyfin also connects to TVHeadend to properly index everything and for easy access to recordings and live TV.

Looks like 2x 4 pin fan headers:

But yeah I’ve got an AliExpress X99 board, which threw all sorts of hardware errors, had no fan speed control (100% all the time), no working hwmon sensors, and I ended up buying a used Supermicro board instead.

Will I see any performance increase?

Like others have said LLMs mostly use VRAM, they can use system RAM if you’re running them on CPU, but that’s ridiculously slow.

It will however increase the speed of your compile times, which is especially useful if you’re compiling something large like the Linux kernel on a regular basis.

I’m also worried about not having ECC RAM.

If you are using it purely for LLMs, if it’s going to get bit flips, it’ll happen in VRAM.

If you are compiling large things for customers, I’d recommend ECC, just in case, e.g. you don’t want a bricking firmware from a bit flip. But according to EDAC and my TIG stack, my server’s ECC RAM has never even detected an error in the past year, if I understand EDAC properly, so it’s really not important.

AFAIK fast startup only affects shutdown, clicking restart will always do a full reboot. Shift clicking shutdown will do a full shutdown like you said, but shift clicking restart will start recovery mode.