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.
The unflipped version was also shared yesterday, for those who missed it: https://fedia.io/m/lemmyshitpost@lemmy.world/t/1017044
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.
If the HOA’s router supports UPnP/NAT-PMP/PCP then you might be able to use that to get some ports forwarded.
Is it possible to send the hint from OPNsense itself?
Yes, to me it sounds like you’re already getting a big enough prefix from your ISP (all devices getting a /64), but you’ll have to request a bigger prefix from OPNsense. I believe it should give you the options to do this when you set the IPv6 mode to DHCPv6 on OPNsense, but I can’t say if your ISP router will handle it.
I have also added all Cloudflare IPs in Jellyfin’s known proxies
You should only need to add the IP of the last proxy before reaching Jellyfin, which would be Caddy.
If you can’t get the VPS to work, alternatively there’s Cloudflare but last I checked streaming was a little out of their free terms. With it, you should just have to set your AAAA record and make the cloud orange, that way Cloudflare will proxy it, and IPv4 will work. There’s also Cloudflare tunnels which lets you host websites without port forwarding anything.
Yeah usually it’ll still use your dGPU to render, but the frames still have to go back through the iGPU, so there’s a fair bit of overhead compared to plugging straight into the dGPU. I’d imagine it might also increase CPU usage too, as it has to coordinate transfering frames between 2 GPUs.
I searched it up:
It seems the smaller tube is pressurised, the larger bulb is under a vacuum. Some of the other diagrams also show a getter in the bulb, so it’s a proper vacuum tube level vacuum.
That’s not really your code, more so you haven’t setup a .gitignore to not commit not your code.
And I really should get used to how debian works with
su.
I only know because installing sudo is usually the very first thing I do whenever I have to install it haha.
I might be wrong, but I believe Debian ships without sudo, only su by default (or at least if you configure a root password in the setup).
I’ve run kill -9 and similar heaps before, but weirdly this comment reminded me of this: https://youtu.be/Fow7iUaKrq4
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.