Booooo.

Prime example of why you don’t ask an LLM for actual information.

1. Samsung Odyssey G9 cannot drop to below v1.4, not to mention any display port mode over 1.4 should understand mode, so this isn’t necessary.
2. There is no ‘Y’ in /sys/module/<some graphics driver>/modeset, it is 0 for disabled, 1 for enabled, and 2 for headless.

I know you think you’re helping, but it’s just muddying the water.

STOP ASKING LLMS FOR ACCURATE INFORMATION.

Eleventy works for me.

Most of what you do is a web app.

deleted by creator

Blueray have anti-copying built into non-data areas, plus Cinavia DRM on the content most of the time. This means your 1-to-1 copies won’t play.

If you are hoping to make a playable bluray, use one of the tools that reads past both and creates a non-drm image.

Depending on where you live, this likely breaks copywrite, but isn’t illegal.

This isn’t the same thing as making VCRs cheap enough that every home has one. There is no FOMO wirh AI at the consumer level, no one knows what to do with it. The only people who want it are the ones who male it!!

🎶🎵 Just Follow the Moneeeyyy… 🎵🎶🎵

deleted by creator

Op specifically asked for resources for learning and not sparse answers from users.

research on your own

Come on, man. Did you even read the post.

Really narrow view of knowledge.

The danger of catapulting an entire generation into ai-fed answers isn’t the amount or quality of knowledge, it’s training people to ask and NOT verify, a pillar of attaining wisdom and true expertise.

I’ll have to check this out, I use Kobo sync extensively.

I had some catastrophic docker updates that destroyed my wanderer instance, forcing me to revert to backups. Twice, I’ve had to export all my tracks, reinstall, and re-import the tracks. Both times, the web component broke.

Have these breaking changes been addressed?

Oooh, good one.

And I did not say that I chose Arch-based for the nvidia driver, but for the more up-to-date drivers.

But that’s what I mean… It’s not to do with being arch-based, but what the distribution chooses to ship. Bazzite is Fedora based and also ships with the almost-newest proprietary nvidia drivers.

For the record, I don’t have an opinion on your choice of distro, use what works for you. I just see so commonly from arch users that they have access to the latest drivers, but that is true of anything running a recent Linux kernel. I was just wondering what about arch makes this belief so strong.

because of the better supported and newer nvidia drivers as well as automatic hardware detection

What?

I don’t understand why arch users always say this… It’s still Linux? You can install nvidia drivers on debian or fedora, and most of the rest are baked into the kernel (most of the time), so I don’t get this.

From a security perspective, it’s a big mess of inputs and can have really inappropriate access to local filesystem on the web server unless you really know what you’re doing. Combine that with Perl (also a pita to secure), and it’s now a liability.

These are good tech, I used them a lot myself. But the structure of a language and how it builds things is important too, and that’s why very few ppl bother with Perl or CGI now (besides them also being fails on certain security audits.)

Sorry, no disrespect intended, but I’m shocked. It’s like hearing someone say they drive a 1988 Toyota Cressida because it’s great… It was great at the time, but we’ve moved on and the smokeping website should tell you how ancient it is; sponsors from 2007 by companies that don’t exist anymore.

Still alive & still maintained

Alive, maybe. I think any maintenance is down to bodges to keep it running in modern environments. Neither Toby nor Niko have worked on sp in over a decade.

Smokeping is fine if all you do is look at its own graphs and you have enough traffic to see patterns in latency.

But:

• more or less unmaintained for a long time
• cgi scripts and scraping
• jitter is estimated from rping, not calculated with real values from more than one point on a route (that means a lot when you have a DMZ)
• Perl
• rrd tool is… Not great. Not very configurable, also unmaintained, lua support is not good, etc
• difficult to customize unless you use their submenu system
• no reporting, you get what you get with smokeping

I had to retire 2 smokeping monitors because their CGI implementations were security risks. That was 2015. Not a good reason for homelab, but CGI is a pretty ancient and insecure way to interact with the web server.

Smokeping is good in a big organization with lots of traffic and a few broadcast domains. It isn’t really great at monitoring remote sites because ICMP doesn’t tell you what segment in route is causing the issue, even with rping.

I used smokeping a lot in my career from about 2005 to 2015, when security audits made me retire it. Just even using rrdtool with an exporter and graphana would be preferable to smokeping itself.

I pick mad max. In the end, it will come down to oil.

Smokeping? In 2026? Jesus…

I deploy with ansible keys and install ssh with a keys-only config and only ansible access.

Then I run some standard installs and configs with ansible and all future updates to apt, apk and docker are done with one ansible playbook.

I don’t include the ansible host itself in the automation, nor my workstation, just to prevent everything from being broken at once if something goes wrong.