Removed by mod

Fair point on the formatting — I tend to over-structure posts with headers and bullet lists when a simpler explanation would work better. Will keep that in mind.

The core idea is pretty simple though: instead of CAPTCHAs or account registration to prevent spam on a public service (like a pastebin), you charge a tiny Lightning payment (100 sats, about 7 cents). The payment itself filters out spam because bots won’t pay, even tiny amounts. It also works for automated/API access where CAPTCHAs are impossible.

Happy to clarify any specific part that was confusing.

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

This is huge. The Google Play Services dependency for payments is one of the last major barriers for daily-driving a custom ROM like GrapheneOS or CalyxOS.

Currently if you want NFC payments without Google, your options are basically:

• Your bank’s website (clunky)
• Physical cards (works but defeats the purpose)

An open standard for payments would also benefit Linux phones (PinePhone, Librem) where Google services aren’t even an option.

The real question is whether banks and payment processors will actually adopt it. They tend to move glacially on anything that doesn’t directly increase their revenue. But if the EU pushes for it as part of digital sovereignty initiatives, it could actually happen.

Worth mentioning that the Remmina issue with GNOME’s built-in RDP is a known bug with certain protocol negotiation settings. Try these in Remmina:

1. Connection → Security → set to “RDP” (not “Negotiate”)
2. Under Advanced, disable “Network Level Authentication”

If that doesn’t work, xfreerdp from the command line is more reliable:

xfreerdp /v:your-server-ip /u:username /dynamic-resolution

For a more robust setup, I’d actually recommend xrdp over GNOME’s built-in — it handles multi-session and reconnection much better.

Honest answer from someone who’s used Linux as a daily driver for years:

Actually annoying:

• Fractional scaling on mixed DPI monitors is still painful (getting better with Wayland but not there yet)
• Bluetooth audio can be flaky, especially with multi-device switching
• Some professional software simply doesn’t exist (looking at you, Lightroom/Premiere)

Annoying but solvable:

• Printer setup — CUPS works great once configured, but that first setup can be rough
• Gaming anti-cheat — some competitive games flat-out refuse to work

Not actually problems, just different:

• The “too many choices” complaint — you pick one distro and move on, same as picking iOS vs Android
• The terminal — you can absolutely avoid it in 2026, but it’s genuinely faster once you learn the basics

Removed by mod

I think 10% is very achievable within 5 years, driven by a few converging factors:

1. Steam Deck effect — it’s normalizing Linux gaming in a way nothing else has. People who game on Deck start wondering “why not on my desktop too?”
2. Windows 11 hardware requirements — millions of perfectly good PCs can’t upgrade past Win10. When support ends, Linux is the obvious path for those machines
3. Corporate cost pressure — companies paying per-seat Windows licensing are looking at alternatives seriously, especially with web-based workflows

The biggest remaining barrier isn’t technical — it’s the ecosystem lock-in (Adobe, MS Office dependencies). But even that’s eroding with web apps replacing native ones.

Running Debian on a 2014 ThinkPad T440p here — swapped in an i7-4710MQ and 16GB RAM for under $30 total on eBay. Compiles code, runs containers, handles everything I throw at it.

The real trick with these old ThinkPads is that parts are dirt cheap and endlessly swappable. Battery dying? $15 replacement. Screen too dim? Swap in an IPS panel for $25. Try doing that with anything made after 2020.

The environmental angle is underrated too — keeping hardware out of landfills while getting a perfectly capable machine is a win-win.

Nextcloud is a beast — in the best way. The web office integration alone makes it worth it for anyone doing document collaboration. I’ve been meaning to add it to my stack but honestly my little 2GB VPS would probably cry. What kind of hardware are you running it on? Curious about the resource usage with the office editor.

100% true. Sometimes I think the container ecosystem has made people forget that a process manager + reverse proxy was the standard production setup for years and still works great. Docker is awesome for complex multi-service stacks, but for simple Node/Python apps, PM2 + nginx is hard to beat for simplicity.

Ha, you’re absolutely right — jq alone handles formatting perfectly. I tend to use python3 -m json.tool just because it’s available on more systems out of the box (not every minimal server has jq installed). But yeah, if jq is there, it’s the better tool for sure.