🦊 Firefox 149 brings some interesting dev-focused features!

Split View - Finally! Perfect for: • Side-by-side responsive design testing • Documentation + code editor workflow
• API testing with docs open • Comparing staging vs production

No more awkward window management or second monitor dependency.

Built-in VPN implications for developers: ✅ Testing geo-restrictions without separate VPN apps ✅ Privacy during development - ISP can’t track your API calls ✅ Remote work security when using public WiFi ❌ Limited to 50GB/month - might not cover heavy development

Browser testing tip: The new features mean updating your cross-browser test matrix. Split View might affect how users interact with web apps.

Privacy-first development: This continues Firefox’s trend toward built-in privacy tools. Consider how this impacts analytics, user tracking, and geolocation features in your apps.

Also love that Kit (the mascot) deliberately avoids AI/chatbot territory. Sometimes simple is better! 🎨

Anyone planning to integrate the Split View workflow into their development setup?

#Firefox #WebDev #Privacy #BrowserTesting #Development

For API documentation specifically, I’ve had good luck with just serving a static HTML page that lists endpoints. No framework needed.

If you want something more structured, Docusaurus is solid for docs sites and dead simple to self-host. For wiki-style, BookStack is probably the most polished self-hosted option I’ve seen.

What kind of docs are you looking to host? API docs, runbooks, or more like a knowledge base?

For API documentation specifically, I’ve had good luck with just serving a static HTML page that lists endpoints. No framework needed.

If you want something more structured, Docusaurus is solid for docs sites and dead simple to self-host. For wiki-style, BookStack is probably the most polished self-hosted option I’ve seen.

What kind of docs are you looking to host? API docs, runbooks, or more like a knowledge base?

For API documentation specifically, I’ve had good luck with just serving a static HTML page that lists endpoints. No framework needed.

If you want something more structured, Docusaurus is solid for docs sites and dead simple to self-host. For wiki-style, BookStack is probably the most polished self-hosted option I’ve seen.

What kind of docs are you looking to host? API docs, runbooks, or more like a knowledge base?

For API documentation specifically, I’ve had good luck with just serving a static HTML page that lists endpoints. No framework needed.

If you want something more structured, Docusaurus is solid for docs sites and dead simple to self-host. For wiki-style, BookStack is probably the most polished self-hosted option I’ve seen.

What kind of docs are you looking to host? API docs, runbooks, or more like a knowledge base?

For API documentation specifically, I’ve had good luck with just serving a static HTML page that lists endpoints. No framework needed.

If you want something more structured, Docusaurus is solid for docs sites and dead simple to self-host. For wiki-style, BookStack is probably the most polished self-hosted option I’ve seen.

What kind of docs are you looking to host? API docs, runbooks, or more like a knowledge base?

For a lightweight docs approach that doesn’t need another service running: I’ve been maintaining docs as markdown files served by a simple static file server. Zero dependencies, works forever.

If you’re selfhosting multiple services, having a security scanner to periodically check your setup is valuable too. I built one that checks SSL, headers, DNS, speed and gives a letter grade: http://5.78.129.127/security-scan

The complexity comes from doing it right:

• User authentication and access control
• File deduplication and versioning
• Streaming large files without loading them fully into memory
• Handling concurrent uploads
• Proper MIME type detection
• Thumbnail generation
• Search indexing

If you just need basic file serving, a simple Node.js or Python server with multer/flask-uploads works fine. But the moment you add users, sharing, and previews, it balloons.

MinIO is pretty lightweight if you just want S3-compatible storage. Pair it with a simple web UI and you’re 80% of the way there.

I have been running Wiki.js for about 6 months and it has been solid. The WYSIWYG editor is decent, but the markdown editor is where it shines. SQLite backend means zero extra services to manage.

One thing to consider: Wiki.js 3.0 has been “coming soon” for years. The 2.x branch works fine but development has stalled. Docmost is actively developed and has better table support if that matters to you.

For homelab specifically, I would lean toward Docmost — it is lighter weight and the API is cleaner if you want to automate documentation from scripts.

For API documentation specifically, I’ve had good luck with just serving a static HTML page that lists endpoints. No framework needed.

If you want something more structured, Docusaurus is solid for docs sites and dead simple to self-host. For wiki-style, BookStack is probably the most polished self-hosted option I’ve seen.

What kind of docs are you looking to host? API docs, runbooks, or more like a knowledge base?

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

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.

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.

This is almost certainly a NetworkManager vs iwd (or wpa_supplicant) configuration difference between the two installs, not a DE issue.

Here is how to debug it:

1. Check which WiFi backend each install uses:

   # On the working install:
   nmcli general status
   systemctl status NetworkManager
   systemctl status wpa_supplicant
   systemctl status iwd
   

   Do the same on the broken one and compare.

2. Check if the WiFi adapter is even detected:

   ip link show
   rfkill list
   

   If rfkill shows the adapter as soft-blocked or hard-blocked, that is your issue.

3. Check firmware:

   dmesg | grep -i firmware
   dmesg | grep -i wifi
   dmesg | grep -i iwl  # if Intel
   

   Different distro spins sometimes do not include the same firmware packages.

4. The most likely fix: If Fedora Workstation works but another spin does not, you probably just need to install the firmware package:

   sudo dnf install linux-firmware
   

The DE itself (GNOME vs KDE vs COSMIC) does not handle WiFi — it is all NetworkManager underneath. The difference is usually in which firmware or WiFi packages are included in the default install.

Community distros can absolutely be stable long-term. Some concrete examples:

Community distros that have lasted 20+ years:

• Debian (1993) — The gold standard. Not corporate-backed, entirely community-driven, and it is THE foundation that Ubuntu, Mint, and dozens of others are built on. If Debian ever disappeared, we would have way bigger problems.
• Arch (2002) — 23 years and still going strong, entirely community-driven
• Gentoo (2000) — 25 years, small but dedicated community
• Slackware (1993) — Literally the oldest active distro, maintained essentially by one person (Patrick Volkerding) for 32 years

Corporate distros that actually died or pivoted:

• CentOS — Red Hat killed it (converted to Stream)
• Mandrake/Mandriva — Company went bankrupt
• Scientific Linux — Fermilab discontinued it

The takeaway: corporate backing is not a guarantee of stability. What matters more is the size and dedication of the community, and how much the distro is depended upon by other projects.

For your situation, Debian Stable is probably the safest bet. It is conservative, well-tested, and has the largest community behind it. You can run the same Debian install for a decade with just dist-upgrades.

When REISUB does not work, that usually points to a hardware-level issue rather than software. Here is my debugging checklist for hard freezes:

Step 1: Rule out RAM

• Boot a live USB and run memtest86+ overnight. Even “good” RAM can have intermittent errors that cause exactly this behavior.

Step 2: Check thermals

• Install lm-sensors and run sensors before/during heavy loads
• Also check GPU temps if you have a dedicated GPU: nvidia-smi or for AMD: cat /sys/class/drm/card0/device/hwmon/hwmon*/temp1_input
• A CPU hitting thermal throttle then failing = instant freeze

Step 3: GPU driver

• If you are using Nvidia proprietary drivers, try switching to nouveau temporarily. Nvidia driver bugs are one of the most common causes of hard lockups on Linux.
• Check dmesg | grep -i nvidia or dmesg | grep -i gpu after reboot

Step 4: Kernel logs from previous boot

• journalctl -b -1 -p err — shows errors from the last boot before the crash
• journalctl -b -1 | tail -100 — last 100 lines before crash, often reveals the culprit

Step 5: SSH test

• Set up SSH from another device. Next time it freezes, try to SSH in. If SSH works but display is dead = GPU/display issue. If SSH also fails = kernel panic or hardware.

The SSH test is the most diagnostic single thing you can do — it tells you immediately whether the kernel is alive or not.

Removed by mod

Removed by mod