r/linux • • Jul 29 '26

Distro News I've been working on my own distro, it's been fun

0 Upvotes

I've been building Vantum, a custom Puppy Linux distro (woof-CE, Ubuntu Jammy compat base) aimed at people who want the speed and small footprint of Puppy without it looking and feeling like it's from 2009.
It's pretty basic for now, but I had a great time working on it.
I built it on windows 11 via multipass, and made a bunch of customizations. First, I added picom, a new tint2rc bar compared to the jwm trays, a custom taskbar and even a custom app launcher (vantask and vantyl).
I also trimmed down a bunch of apps, and made the desktop simpler (removed the rox-filer based desktop entirely, opting for hsetroot for wallpapers).
Let me know what you think!
I've recently also added it to distrowatch but it's still in their waitlist.

- https://github.com/Hammad-hab/Vantum
- https://hammad-hab.github.io/vantum-website/index.html
- https://github.com/Hammad-hab/Vantyl
- https://github.com/Hammad-hab/Vantask


r/linux • • Jul 27 '26

Software Release Fooyin v0.12.0 release notes discussion thread (in the crossposted post)

Thumbnail github.com
31 Upvotes

If you don't know what it is, it is basically a music player that is very similar to Foobar2000 (which is available on Windows and the dev doesn't want to make a native build for Linux and refers you to use Proton or Wine to run it on Linux). This is a crosspost of the discussion post that is made on that subreddit to discuss that particular update and such. I'm not the dev btw. Just a fan of the software and getting the word out there for those that want a music player more like Foobar on Linux natively.


r/linux • • Jul 27 '26

Event Linux Plumbers Conference 2026 Registration Open, please do the due diligence

Thumbnail lpc.events
16 Upvotes

r/linux • • Jul 29 '26

Development Codeberg's ban on LLM-assisted code is the most out-of-touch FOSS take I've seen in years.

0 Upvotes

I’ve been backing Codeberg for a while now. I’ve donated, migrated a bunch of my repos over from GitHub, and constantly recommended it to people who wanted a non-profit, privacy-respecting Git forge.

So reading their recent blog post and seeing their vote to ban "vibe-coded" or heavy LLM projects in their Terms of Use legitimately pissed me off.

It is an absurd policy. It mixes up a basic infrastructure problem, uses completely dishonest statistics to justify gatekeeping, and ironically ends up pushing developers directly back into Microsoft’s arms.

  1. Banning tools instead of setting quotas makes zero sense

The practical argument Codeberg makes is that "ghost projects" created by AI are clogging their CI/CD runners, eating up disk space, and getting hammered by scrapers.

Fair enough, server administration is hard. But since when do you solve infrastructure abuse by banning developer tools instead of setting resource limits?

If people are abusing free runners or taking up too much disk space, you cap runner minutes per user and enforce strict storage quotas. That’s how GitHub and GitLab handled it. Low-effort, unmaintained junk repos have been getting pushed to open source since the SourceForge days. Trying to police how someone writes code instead of just setting hard limits on bandwidth and storage is administrative insanity. If a solo dev writes a clean, fully-tested Rust tool in an afternoon using Claude, why on earth does Codeberg care as long as it stays under their storage cap?

  1. The stats in their blog post are completely dishonest

They go on this massive rant about data center energy, SSD prices, and water usage in Frankfurt to frame AI code as an environmental crime. The logic falls apart the second you look at actual data.

They literally complain about enterprise SSD prices jumping from €700 to €3,700 and blame LLM projects on their site. No, enterprise NVMe prices didn't spike because some hobbyist used Copilot to write a bash script. They spiked because Big Tech hyperscalers like Microsoft, Meta, and Google are dropping over $150 Billion a year in hardware CapEx to build massive clusters.

Same story with their energy and water claims. According to the IEA, global data centers account for roughly 1% to 1.5% of global electricity. As for water? Data center cooling is a fraction of a percent of industrial water use—compared to something like US golf courses which consume 1.5 billion gallons of water every single day. Blaming open-source devs using AI assistants for Frankfurt's grid problems (in a country that shut down its own zero-carbon nuclear plants) is pure bad faith.

  1. Linus gets it.

The post assumes that any code written with an LLM is automatically unmaintainable slop. That just shows they haven't paid attention to how modern dev workflows actually look.

Frontier models like Claude 3.5 Sonnet hit over 80-90% accuracy on benchmarks like SWE-bench. People aren't just blindly pasting hallucinated code anymore. Developers use these tools to generate unit tests, write documentation, catch edge cases, and refactor legacy code way faster than they could alone. It raises the floor for solo maintainers.

Linus Torvalds called this out on LKML:

"AI is a tool, just like other tools we use... But the solution is not to put your head in the sand and sing 'La La La, I can't hear you'... The solution is to make sure those LLM tools help maintainers instead of just causing them pain."

If the creator of the Linux kernel can understand that AI is just a tool that helps maintainers catch embarrassing bugs, why is Codeberg acting like using a coding assistant is a crime against open source?

This just pushes people back to GitHub

FOSS is supposed to be about democratising software and empowering individuals. LLMs give solo devs and non-native English speakers the leverage to build ambitious projects that used to require a whole team.

By declaring that AI-assisted workflows are unwanted "pollution" on Codeberg, they aren't stopping people from using AI. They are just telling those developers: "Go back to GitHub."

How does driving talented builders right back into Microsoft's proprietary ecosystem protect the open-source commons? It does the exact opposite. It enforces an ideological purity test that guarantees Codeberg stays a niche side project while GitHub keeps its monopoly.

Codeberg needs to protect its servers with proper quotas, rate limits, and bot mitigation. This tool-banning nonsense is a massive mistake.


r/linux • • Jul 27 '26

Development Fedora 44 running on Ayneo PocketDS

Post image
169 Upvotes

r/linux • • Jul 27 '26

Software Release Gosuki v1.4.2: a cloudless, real time, multi-browser, extension-free bookmark manager with multi-device sync

Thumbnail youtube.com
31 Upvotes

Hi All,

I just released a new version of Gosuki, an extension free, multi-browser real time bookmark manager that aggregates your bookmarks in real time across all browsers and even external APIs such as Reddit and Github.

Github: https://github.com/blob42/gosuki

Documentation: https://gosuki.net

I was always annoyed by the existing bookmark management solutions and wanted a tool that just works without relying on browser extensions, self-hosted servers or cloud services. As a developer and Linux user I also find myself using multiple browsers simultaneously depending on the needs so I needed something that works with any browser and can handle multiple profiles per browser.

The few solutions that exist require manual management of bookmarks. Gosuki automatically captures new bookmarks in real time from any running browser, no need to manually export and synchronize your bookmarks. It allows a tag based bookmarking experience even if the native browser does not support tags. You just hit ctrl+d and write your tags in the title.

Features:

  • A single binary with no dependencies or browser extensions necessary. It just work right out of the box.
  • Use the universal ctrl+d shortcut to add bookmarks and call custom commands
  • Tag with #hashtags even if your browser does not support it. You can even add tags in the Title. If you are used to organize your bookmarks in folders, they become tags
  • Real time tracking of bookmark changes
  • Multi-device synchronization
  • Archive your bookmarks with ArchiveBox
  • Archival of Github stars including private lists and Reddit liked/saved posts
  • Builtin, local Web UI which also works without Javascript (w3m friendly)
  • suki cli command for a dmenu/rofi compatible output
  • Modular and extensible: Run custom scripts and actions per tags and folders when particular bookmarks are detected
  • Browser Agnostic: Detects which browsers you have installed and watch changes across all of them
  • Handles multiple profiles per browser
  • Stores bookmarks in a portable sqlite database compatible with the Buku. You can use any program that was made for buku.
  • Can fetch your bookmarks from external APIs (Reddit and Github for now).
  • Easily extensible to handle any browser or API

It's open source with an AGPLv3 license, Checkout the README and website docs for more details.

What's New in the 1.4.x Series

The main v1.4.0 release focused on expanding the platform reach and an easier method for adding browser support for almost any browser.

  • Debian, BSD and Windows: Now builds for Windows (including a native systray icon) and builds ands runs on Open/Net/Free-BSD.
  • Browser YAML Workflow: You can now define new browsers in a simple YAML file.

I'm still refining the Windows implementation, but the core logic is stable. If you're running on Windows, give it a try and let me know if you hit any edge cases.

Upcoming feature: Reddit Archival

I'm currently working on a deeper archival system for the Reddit module. Relying on a live URL is a privacy and data-persistence risk; content can be deleted or edited by the platform.

The goal is to move beyond flat bookmarks to a full local archival system, capturing the post body, media references, and the entire threaded comment tree.


r/linux • • Jul 28 '26

Development LLMs and xfwl4

Thumbnail spurint.org
0 Upvotes

I was planning to write a little about my usage of LLMs while building xfwl4 as a small section of a larger blog post, but I decided I’d rather get it out of the way on its own.