The USA has no problem bulldozing housing to build highways.

I’m at the age that the first train to the event being full is enough to make me go home.

To all the people who bought anything from Sony after the 2005 rootkit fiasco: what the hell did you expect?

Please provide any input or alternative options on this,

The post asked for alternative options. I suggested an alternative option. It is not knee-jerk, and it is not noise.

Alternative: make a separate “selfhosted-ai” community for the sloperators.

Working at home: mpd + ncmpc on my personal laptop.

At the office: mpd + malp on my phone.

No streaming. I buy CDs and vinyl and rip them and download live recordings, and only listen to entire albums or concerts.

ssh -L 1234:localhost:1234 remote_server binds the RPi’s localhost:1234 to remote_server’s localhost:1234. You want to bind the port to something on the RPi that the TV can hit, so something like ssh -L 192.168.1.5:1234:localhost:1234 remote_server, where 192.168.1.5 is the RPi’s address.

I think you also want -N on the ssh command.

Can you provide more detail? What are the networks/routers/vlans? Which network is the RPi on? What is your ssh command? Is that ufw command on the RPi or the router?

Github is like the Microsoft of 3rd party forges.

“self hosting is important because …”

Uses github.

Don’t use Gnome.

While his perceptions of other people’s motives and meanings may be suspect, his technical analysis seems pretty spot on.

The only time I have compiled a kernel in the last 10 years was to bisect to determine what change introduced a bug affecting my particular hardware combination.

Are you sure L2 is 192.168.1.0/24 and not something larger that includes 192.168.30.0, e.g.: 192.168.0.0/16?

What does ip route show before and after connecting to WG?

Are you testing DNS via dig @<nameserver>? or just with ping? Are you running systemd-resolved?

Nothing in the Qualys report nor the Ubuntu page for the CVE indicate that there is something to be fixed in systemd, only that you can create systemd-tmpfiles rules that will expose the vulnerability in snapd.

What do you think systemd-tmpfiles needs to do differently?

Yet another critical vulnerability in systemd

This is a critical vulnerability in snapd, not systemd. It sounds like it could also be exploited if something other than systemd deleted the files in /tmp/. Or if /tmp/ was not mounted.

No LLM use is benign. The effects on the environment, the internet, and society are real, and that cannot be ignored.

You can make the argument that in some cases it is justified, e.g.: for scientific research.

No.

If your home IP does not change often, you can use a dynamic DNS service. But your services will be unavailable from the time that your IP changes and the time the DNS record is updated and the cached responses expire.

Servers are all Debian. Family member’s laptops are all Debian. I used Debian on my laptops for 20 years, but when Steam Deck switched to Arch, I switched my laptop to Arch to force me to learn it. I have a file with notes of differences between Debian and Arch. Next time I buy a new laptop, I will probably go back to Debian.