Some people will still argue that hating Epic for how it handles its games is unfair.

Proxmox is my number one choice. It’s based on Debian, and has an excellent, extremely straightforward web UI for managing virtual machines and LXC containers.

I can’t imagine living without a numpad.

It’s perfectly reasonable from the perspective of corporate scum: take away a standard feature, then sell it back as an extra. As far as I know, the modem still had UPnP for applications that rely on it.

No, I got it from the horse’s mouth: my WAN address was publicly routable all along, the ISP just disabled those NAT-related features remotely.

I finally got my ISP to enable bridge mode on my modem.

I also learned that I didn’t lose port forwarding and related services because I had been moved behind CGNAT or transitioned to IPv6 – they simply no longer offer port forwarding to residential customers. Ruminate on the implications of that statement so I’m not the only one with blood pressure in the high hundreds.

Even in the open source community, the libre-ness of a product is just one of many factors. The fitness for a purpose, the initial difficulty of the setup, the continuous difficulty of operation and maintenance, the pace of development (if applicable), the professional or community support structure, the projected longevity of the product or service, and the general insanity of the people involved are all important factors that can, and often do outweigh the importance of open software.

Local Unbound with Tailscale’s split DNS has been solid for me. I use it as an OPNsense service with the web GUI, but the standalone YAML config looks simple enough.

I’ve never used Linkwarden, but the /data folder is often used by Docker containers to store the application’s data, so it’s likely an internal path. You’ll have to create a volume that exposes the internal /data path to the host filesystem, then whatever is written into that directory will be made available to both the container and the host system. Any file or directory in the container can be exposed this way.

I usually put my data volumes in /srv (where my large RAID array is mounted) and config volumes in /config, into a subdirectory named after the service, and with the minimal necessary privileges to run the container and the service. You could, for example, create volumes like this:

/srv/linkwarden/postgres_data:/var/lib/postgresql/data
/srv/linkwarden/linkwarden_data:/data/data
/srv/linkwarden/meili_data:/meili_data

The volume path (left side of the colon) can be anything. The right side is where the services expect their files to appear inside the container.

The Lemmy backend, the default web frontend, the Jerboa app, and the lemmy.ml instance are all owned by the same person.

I don’t know which label is the most accurate, but he supports Putin’s war, which lands him in the “shitbag” category. Being technically not fascist does not negate supporting the military invasion of a sovereign country, the ethnic cleansing of its people, and the rape, murder, and torture committed by the invaders.

You are literally on Lemmy. The project owner’s views are well-known.

on limewire

Not only has this made me realize how fucking old I am, but I also got curious about how Limewire is doing, and…

In September 2025, LimeWire acquired the Fyre Festival brand, including its intellectual property, trademarks, online domains, and social media assets, from Billy McFarland via an auction held on eBay.

…according to Wikipedia. At this point, my 2025 bingo card would serve better as kindling.

You make a new normal, non-root user specifically to run Radicale processes. The user should have write access only to Radicale’s directories, nothing else.

Same deal with Apache and the www-data user.

There is a world of difference between a bug that doesn’t get reported because its impact is minimal and a bug that doesn’t get reported because people can’t be bothered to make the report and just live with it. The latter category is where the general complacency of 94.2% of players makes a negative impact.

Steam also supplies its own shared libraries, many of which are 32-bit. It does a lot of fuckery with LD_PRELOAD to load its own stuff instead of system libraries. The steam-native-runtime package in the multilib repository replaces those with system libraries, and provides the steam-native command that runs Steam without said fuckery. I can’t guarantee it’ll work at all.

Processes launched from Steam run in an altogether different runtime environment compared to Lutris. When Steam launches an application, it uses several wrapper processes that you can see in btop’s process tree. Pressure Vessel (pv-adverb) and Bubblewrap (srt-bwrap) are sandboxing solutions by Valve and Flatpak respectively, and Reaper is responsible for tracking and cleaning up Wine processes when the game is closed.

This is what the process tree looks like when I launch Warframe:

Enrico Weigelt. He’s also an anti-vaxxer moron. To quote his own words on the LKML: https://lkml.iu.edu/hypermail/linux/kernel/2106.1/04542.html

And I know a lot of people who will never take part in this generic human experiment that basically creates a new humanoid race (people who generate and exhaust the toxic spike proteine, whose gene sequence doesn’t look quote natural). I’m one of them, as my whole family.

So yes, sure, nobody can stop people that think the pandemic is over (“we are vaccinated”) from meeting in person.

Pandemic ? Did anybody look at the actual scientific data instead of just watching corporate tv ? #faucigate

The only benefit I see in Xlibre is that it will attract idiots like him and and draw them away from projects with real merit.

Only KDE calls it “meta”. Everywhere else it’s either “super” or “mod4”. The left Alt is sometimes called “meta” or “mod1”.

They should sponsor HGL. No need to reinvent the wheel, and the project could always use the money and fame.