You just made that up. Go back to your config files 😂

"ai prompts" are downloading a full fledged GUI office suite for editing documents? 🤔 Seems like an overkill to me. Thoughts on this people?

Tuxdle #40 5/6 🟩🟨⬛⬛⬛⬛ 🟨⬛⬛⬛⬛⬛ 🟨🟩⬛⬛⬛⬛ 🟩🟩🟩🟩⬛🟩 🟩🟩🟩🟩🟩🟩 Test your Linux knowledge at tuxdle.com/

Are you in favor of AI being at the core of a Linux distro or against it?

LibreOffice has record 9.4 million downloads in the past two months. No matter how much people criticize LibreOffice, it remains a popular choice among Linux, Windows and even macOS users.

Setting up printer in Linux can still be used as a free mental state check excercise.

Drop a ❤️ for Tux!

The list covers desktops, X servers, and a Wayland-hosted X11 layer. Basically, projects that are resisting a Waylan-only Linux future. itsfoss.com/projects-keeping…

The small SBC brings a 6 TOPS NPU, Wi-Fi 6, a Pi-compatible 40-pin header, and up to 32GB RAM, starting at $153. itsfoss.com/news/armsom-sige…

A privacy-first DNS resolver just chose to leave an entire country rather than lie to its users. Quad9 is shutting off its free DNS service in France on November 24, after a French court ordered it to block domains that BeIN Sports claimed were facilitating sports piracy. Quad9 refused. "We categorically refuse to alter or lie to you about the DNS responses you receive in a way that opposes your expectations." The court had actually reduced the fine to just €1,000 per day. Quad9 still walked away. Because the real problem was not the fine. It was the precedent. Complying would mean either applying French copyright law to Quad9's global DNS infrastructure, or using geo-blocking methods that Quad9 considers technically unreliable and ethically compromised. Either way, the integrity of the service breaks. This is what it looks like when a privacy tool takes its mission seriously. Most services would have quietly blocked the domains and moved on. Quad9 chose to exit instead 👏

The Linux Foundation Research survey also found that only 35% of projects have a formal policy permitting AI contributions. itsfoss.com/news/red-hat-lf-…

Aimed at hardware exposed to radiation, like satellites, BeamFS can repair data without keeping a second copy. itsfoss.com/news/beamfs-linu…

Tuxdle #38 4/6 ⬛⬛🟨⬛ ⬛⬛⬛🟩 ⬛⬛⬛🟩 🟩🟩🟩🟩 Play at 👇️ tuxdle.com/

A new kernel and a new Ubuntu release are here. itsfoss.com/newsletter/foss-…

Instead of trying to emulate traditional terminal editors, TTT provides a modern, GUI-like editing experience in the terminal with virtually no configuration required. itsfoss.com/terminal-text-ed…

Over 100 vendors. Weeks of coordination. A Friday release window everyone agreed on. Chainguard threw it all out the window. When PHP's security team was quietly working with more than 100 downstream vendors to simultaneously patch two critical remote code execution vulnerabilities (php2shell), Chainguard unilaterally published patched container images more than six hours before the coordinated release. That single decision handed attackers a working blueprint. They could diff Chainguard's fixed images, reverse-engineer the vulnerability, and start exploiting unpatched servers long before most organizations even knew a patch existed. This is how coordinated disclosure is supposed to work: everyone patches at the same time, so there's no window where attackers know and defenders don't. Chainguard reduced that window to zero for its customers and blew it wide open for everyone else. PHP's maintainers said Chainguard "disregarded weeks of work by many parties." That is a polite way of saying one company's act overrode the security of the entire web. Responsible disclosure is a community contract. When one party breaks it, everyone outside that party's customer base pays the price.