This seems like a decent guide on how to set it up:

https://www.cyberciti.biz/faq/how-to-set-up-wireguard-firewall-rules-in-linux/

It’s very similar to the config I’ve got. The nat iptables stuff in step 1 is what enables wireguard to be used as a VPN exit node. (+ net.ipv4.ip_forward=1)

This feels like it has validated my decision to just use plain wireguard and hardcode my client list. It’s really not too hard to set up, barely different that configuring authorized_keys or ssh.

I guess someone stole the 1 and 3 off the sign in OPs picture, they’re there on street view. That’s wild you found this

That would be the AI denoising that basically every phone runs automatically, and pretty much the entire reason I bought a standalone camera…

What confuses me as someone who hasn’t written PHP in ages, is why is it supposedly so easy for a request to hit the memory limit? Does this only work on servers that accept user uploads and other large request payloads? People are saying a static PHP page can be exploited, but I don’t understand how if it’s behind even a basic nginx instance with default request limit of 1MB.

Neat, I might have to set this up for myself. It sounds like it could get around some of the VPN blocking I’ve seen while traveling through airports.

Flood pain is right… Best of luck getting that sorted.

It’s honestly impressive what you can do with under 3W of power these days

I wish I could give you a second upvote, that’s hilarious 😂

I guess swap can still be useful for background browser tabs and apps. I haven’t run swap on my machines for years now, so I can’t really remember how and when it decides to start moving stuff there.

The last few times I ran into OOM killer it’s been from compiling/linking some huge project that used up 90% of my ram on its own… so I’ve probably been having a different experience than most people.

That sounds to me like it’s basically the same as turning off swap. I don’t think oom killer activates until you fill up your swap as well.

I guess it could still be useful since it’s more tunable than the kernel oom killer.

With how big the cab is, it almost looks like they took an SUV and bolted on a tiny truck bed sticking out the back. The proportions are very strange.

It’s got 50% more range, so it’s probably got a bigger battery. Lithium is expensive.

Apart from static discharge, or a broken power supply, I don’t think there’s anything your computer could do to the SSD to actually break it. Worst case you just need to reformat it.

(I guess if it writes to it constantly it could wear out, but that’s different than a hard shutdown)

Since I already host a bunch of stuff, it hasn’t been a big burden for me. I get to laugh any time one of the popular instances goes down or has some admin/mod controversy, but the tradeoff is I have to manually subscribe to everything since I don’t have an “All”.

I mostly did it because this is the only way to truly own your lemmy identity. I hope one day it will be possible to link accounts on different instances together so that migrating doesn’t lose your history.

and if a display driver can’t be written in 1 line that doesn’t make the thousands of lines unmaintainable slop

That’s not what I’m saying.

I’m saying if there’s 1000x more lines of code than necessary, it’s unmaintainable slop. I could understand 2x or even 10x the lines of code just being a difference in architecture, but even 100x is getting crazy.

I think only EnterpriseFizzBuzz surpasses the 1000x inefficiency metric that this meme is implying.

Selfhosting Lemmy has been surprisingly nice

You made an assumption that the user was at fault

I made an assumption about what your goal was, and made no claims of fault or right/wrong. You can do whatever you want with your own computer. Bye

Look, I was trying to understand your issue, since I’m a developer and am curious about this kind of thing. I stated my assumptions to try and make my initial point of view clear and give you the opportunity to provide more information if my assumptions were wrong.

From what you’ve stated I don’t believe your problem is related to DCC/CI at all, and is likely something else with sleep states failing. Whatever is failing on your system is extremely unusual and is not something that I would expect a “Grandma” to ever encounter. If anything, older hardware should be better supported.

I’ve not experienced any of this across many different linux systems… The default screensaver and lock screen work perfectly fine in KDE Plasma, and my monitors turn off when they should. I’ve even had no issues with HDR and variable refresh rates. (And the DCC/CI brightness controls for my TV work out of the box unlike windows).

I’m sorry you haven’t had the same experience. It almost seems like there could be something broken with your hardware if your monitor is continuing to detect a signal after things are asleep.