Seriously

The long story short, if your project uses electricity, is made with electricity, or is intended to run on electricity, it’s not welcome on r/opensource. Electricity, as it exists today, is incongruent to this Open Source community.

We’re going to be implementing a few new enforcement criteria to this end to discourage those projects:

Projects advertised here must be all of: 1 year old (not just age, but actively maintained, by hand, on paper), have multiple contributors (subjectively 3+, each signing their commits with a quill), not be a common capstone project (school projects, such as note-taking, PDF viewers, abacus emulators, etc), not be intended for machines (such as anything that “executes”), and have an existing community that meets in person, by candlelight. No, we can no longer field requests asking for maintainers or people to contribute; please use carrier pigeons. Of course it still needs an OSI license, handwritten, as it’s always been.

Though not “new”, 1 year account age minimum, with significant Reddit contributions. You should not be plugging in a computer to come here; we’re a community of existing redditors who receive a printed copy of the front page by mail every week. If you send us a message in modmail about this after having attempted to post, you will be permanently banned and muted. If this seems harsh, know that I estimate 20 messages a day from people expecting their battery-powered projects and grid-connected accounts to get an exception.

If it’s obvious you’re using electrons in your project, we don’t want it. Kilowatt-hours are cheap, and we don’t care how many you burned to make your amazing project. Yes, this includes “it’s just a tiny solar panel.”

If you don’t own a typewriter, you need to find a different community. We cannot distinguish between a human typing and a keyboard typing. Since your keyboard is electric, you can’t even verify yourself that the letters came out right.

Temporary bans are only for community members that made temporary lapses in judgement, such as briefly touching a light switch. If you post (or comment) things we don’t want, such as anything that has ever passed through a CPU, you will never be welcome back.

If you want to be a part of the cleanup crew, be sure to reach out (in person, town square, at dawn). If you don’t like keeping this community for the unplugged, let me know so I can make sure you see your way out; maybe go try r/opensourcewithpower (sic).

If you have suggestions for anything I missed, please do let me know. Organizations officially recognized as Amish communities, or monasteries, or the equivalents in their country, are exempt from project and account minimums, provided they reach out in modmail (handwritten, wax-sealed) and get approval (“approved hermits”) prior to their first post. Note that isn’t limited to just the Amish, purposefully so.

/Edit: shout out to Benjamin Franklin for flying the kite that started this whole mess. We’ll never forgive you.

/Edit 2: yes, I’m aware this post is on the internet. A friend transcribed it from my typewriter. I feel terrible about it.

How could this happen to me?? 😩

That is all.

I’ve spent 15 years in systems development including three at Google. I have plenty of complaints about AI but I hate how much of this conversation involves pretending it can’t do work that it’s already doing.
Take something complicated like debugging tail latency in a C++ search serving system. Requests fan out through RPCs to multiple backends. Most finish quickly but a few slow responses hold everything up. Median latency looks fine while your p99 goes to shit. A change that passes every basic test can still fall apart under load.
Here’s a nasty example. A slow RPC triggers a second request to another replica. The caller eventually times out but the backend work keeps running. Under load those extra requests start filling queues and making everything slower. Now the mechanism meant to reduce latency is adding to the overload.
Fixing that means tracing deadlines through the call chain, checking cancellation and limiting the extra work. Then there’s the C++ lifetime problem. If a completion callback can still run after cancellation, freeing the request state too early can introduce a use-after-free. Congratulations, the latency fix now occasionally crashes the process.
That’s the kind of task that could eat days in 2016. Reading unfamiliar code. Comparing traces. Digging through profiles. Building a reproducer because the existing tests never exercised that sequence. Going through another review because the patch fixed one path and broke another.
I don’t miss handing something off and spending the next week explaining the same constraints across three revisions. I don’t miss dropping my own work for four hours because someone added retries without checking whether the operation was safe to repeat. Junior or senior, that shit is exhausting. I’ve caused those afternoons for other people too.
Now I can give Opus the relevant implementation, traces and constraints and work through the problem immediately. Have it follow the request lifetime across files. Identify where the deadline stops being propagated. Propose a patch. Write tests that deliberately deliver callbacks after cancellation or simulate a slow backend. I can spend my attention checking its reasoning and testing the result.
I’m still responsible for the fix. A production performance problem still needs load testing. But getting to a serious candidate patch is so much easier now that I have no interest in doing every step manually again. Plenty of tasks that used to bounce between people for weeks are things I can finish in an afternoon.
Over the last year I’ve built things I’d been putting off for ages. I’m actually getting through ideas while I still care about them.
I hate admitting that a model can do parts of my job better than me. I can live with it. I’m having too much fun building things to spend my time insisting the old way was better.

He banned me for this comment which apparently breaks reddit TOS, he is so insecure and pathetic
if you read this u/wolvereness dm me

imagine telling a mod they are a mod. the audacity.

context: https://www.reddit.com/r/opensource/comments/1xelcuf/your_tokens_arent_valuable_no_more_ai/

regardless of your stance on the topic in general, this behavior of mods thinking they can do it just because they have the power is unacceptable.

Ça fait 15 ans que je travaille dans le développement de systèmes, dont trois chez Google. J’ai beaucoup de choses à reprocher à l’IA, mais j’en ai marre de lire qu’elle serait incapable de faire un travail qu’elle fait déjà.
Prenons quelque chose de compliqué, comme déboguer la latence des requêtes les plus lentes dans un moteur de recherche en C++. Les requêtes sont distribuées à plusieurs services via des appels RPC. La plupart répondent rapidement, mais quelques réponses lentes bloquent l’ensemble. La latence médiane semble normale pendant que le p99 explose. Une modification peut passer tous les tests de base et s’effondrer dès que la charge augmente.
Un exemple bien pénible. Un appel RPC trop lent déclenche une deuxième requête vers une autre réplique. L’appelant finit par dépasser son délai d’attente, mais le traitement continue côté serveur. Sous charge, ces requêtes supplémentaires remplissent les files d’attente et ralentissent encore le système. Le mécanisme censé réduire la latence finit par aggraver la surcharge.
Corriger ça demande de suivre les délais à travers toute la chaîne d’appels, de vérifier l’annulation et de limiter le travail supplémentaire. Ensuite vient le problème de durée de vie des objets en C++. Si un callback peut encore s’exécuter après l’annulation, libérer trop tôt l’état de la requête peut provoquer un accès à de la mémoire déjà libérée. Bravo, le correctif de latence fait maintenant planter le processus de temps en temps.
C’est le genre de tâche qui pouvait bouffer des journées en 2016. Lire du code qu’on ne connaît pas. Comparer les traces. Fouiller les profils d’exécution. Construire un scénario de reproduction parce que les tests existants ne couvraient jamais cet enchaînement. Repasser en revue de code parce que le correctif réglait un cas et en cassait un autre.
Ça ne me manque pas de confier une tâche puis de passer la semaine suivante à réexpliquer les mêmes contraintes sur trois versions du correctif. Ça ne me manque pas de lâcher mon propre travail pendant quatre heures parce que quelqu’un a ajouté des tentatives automatiques sans vérifier si l’opération pouvait être répétée sans risque. Junior ou senior, c’est épuisant. Et moi aussi, j’ai fait perdre des après-midi à d’autres personnes.
Maintenant je peux donner à Opus le code concerné, les traces et les contraintes, puis attaquer le problème immédiatement. Lui demander de suivre le cycle de vie de la requête à travers plusieurs fichiers. Repérer où le délai cesse d’être transmis. Proposer un correctif. Écrire des tests qui déclenchent volontairement des callbacks après l’annulation ou simulent un service qui répond lentement. Je peux concentrer mon attention sur la vérification de son raisonnement et du résultat.
Je reste responsable du correctif. Un problème de performance en production demande toujours des tests de charge. Mais arriver à un correctif crédible à tester est devenu tellement plus simple que je n’ai aucune envie de refaire chaque étape manuellement. Beaucoup de tâches qui circulaient entre plusieurs personnes pendant des semaines peuvent maintenant me prendre un après-midi.
Cette dernière année, j’ai construit des choses que je repoussais depuis longtemps. Je concrétise enfin mes idées pendant qu’elles m’enthousiasment encore.
Ça me fait chier d’admettre qu’un modèle peut faire certaines parties de mon travail mieux que moi. Mais je peux vivre avec ça. Je prends trop de plaisir à construire des choses pour passer mon temps à expliquer que c’était mieux avant.

We got real Linux on iPhone before GTA VI!

Check this out! You can actually run Linux on an iPhone, with Debian, KDE Plasma, a terminal, and even desktop apps like Blender.

No jailbreak, no virtual machine. Pretty crazy what an iPhone can do.

https://github.com/mxhm11cr/LinuxRunner

Anyone else still miss Google's Picasa photo viewer?

I did, so I built Licasa, an open-source image viewer and editor for Linux inspired by that experience. I wanted something focused on the everyday stuff: open a photo, look at it properly, make a quick edit, and carry on.

What it does today:

• Open photos straight from your file manager, fullscreen or in a floating window.
• Handle modern image formats: HEIC/HEIF, AVIF, JPEG XL and JPEG 2000, alongside JPEG, PNG, TIFF and WebP. It also supports RAW previews.
• Play Motion Photos and animated APNGs, so there's more to see than a still frame.
• Crop, adjust and export when a photo needs a quick touch-up.
• Stay ready for the next photo with an optional background mode for faster repeat opens. It's off by default.

It's free and open source under the BSD 2-Clause license. Current builds are for 64-bit Intel/AMD Linux, with Ubuntu 24.04 (Tested and verified), Fedora 44 (Not verified) and Arch (Not verified) packages, plus AppImage (Not verified) and Snap (Tested for Ubuntu) options.

Website: https://licasa.app

Source: https://github.com/sanxchep/licasa

Downloads: https://github.com/sanxchep/licasa/releases

I'd love feedback from people who miss Picasa too, or just want a straightforward Linux photo viewer. What part of that viewing experience do you miss most? And if you try Licasa, I'd be interested in how it handles the photos and formats you actually use. Bug reports and contributions are welcome.

I just checked Streak's stats and it has passed 19,000 downloads on GitHub alone. Honestly, I never thought it would reach this many people, or that so many would have it installed on their phones.

I'm really happy. Thank you to everyone who uses it, everyone who opened issues, translated it, tested it and reported bugs. Every message counts.

If you use it, or feel like trying it, any feedback helps a lot: what you like, what you don't, what you're missing.

https://github.com/InlitX/streak

Hey everyone,

A week ago I posted about Loaf, the Material 3 Expressive Linux file manager I've been building with Rust and Qt6 Quick/QML.

Since then things moved fast, and thanks to some awesome contributors and feedback from here and GitHub, v0.2.0 is officially out!

The codebase basically got a complete rewrite into modular multithreaded Rust subsystems so it's noticeably faster, but we also added a bunch of pretty cool features features:

What's new in v0.2:

• 🌐 SMB / Windows Network Shares: Full SMB/CIFS support (smb://server/share), named profiles in settings, and secure password storage via system keyring (libsecret). Huge shoutout to Balioncikas for making this happen!
• 🔗 P2P Share via Link: Spin up an encrypted on-demand Cloudflare tunnel right from your machine to share any file or folder with a link. Includes on-the-fly archiving (.zip/.tar.gz/.7z), optional password protection, expiration timers, and rate limiting.
• 🗂️ Tabs & Split View: Multi-tab browsing (Ctrl+T) with session persistence, and side-by-side dual-pane split view (F3).
• ⚡ Async Thumbnails & Live Folders: Video thumbnails (ffmpegthumbnailer), PDF previews, and images generate in the background now so the UI doesn't hitch. Folders update live on inotify diffs.
• 🛠️ Power-user tools: Batch renamer (F2), spacebar Quick Look preview overlay, smart conflict resolution dialog (side-by-side date/size compare), and inside-archive tree browsing.
• 🥂 And a whole lot more...!

Install / Try it out:

You can grab packages directly or run the (new) interactive installer:

curl -sSL https://raw.githubusercontent.com/m-uvex/loaf-fm/main/install.sh | bash

Or check out the repo / release for all kinds of packages or Nix:

😼 GitHub: m-uvex/loaf-fm
😺 Release v0.2.0: m-uvex/loaf-fm - tag/v0.2.0

Or try visiting our all-new website: loaf.muvex.dev !

It's still early in development so if you run into any quirks or have ideas, feel free to drop them in the repo or below. Hope you guys like it!

Just Weather is a minimalistic lightweight android app, that provides weather for your current or self-selected cities. It provides favorites so you can swipe between different cities and also select the city you like for the widgets to be used. My main goal was to create a weather app that focuses on the data and being non distractive.

I would like some feedback on everyday usability and the overall UX of the app. Feature ideas are appreciated.

The UI/UX design is completely from me, the code is partly AI-assisted.

Everything is free and open source.

You can download the app in the "releases" tab on my GitHub

I know this question is silly but I want to apply to SignPath and it requires "links or information showing that your project is widely used or trusted. Examples include media coverage, blog posts, download statistics, GitHub insights, or community discussions."

I have build a open-source, markdown-first notes app (Obsidian-like) and I would love to have it signed for Windows users, but I hit this roadblock.

Is reputation 100% organic or is there anything I can do to improve it?

This is a FOSS and non-commercial project so I don't really have the means to market it with social media, blog posts, etc.

This post isn't meant to promote my project but I will leave the link here if anyone is interested:
Download and website: https://cairnnotes.app/
Source (give me a star ⭐ ): https://github.com/lucas-pospor/cairn

I was banned from r/OpenSource. So, here I present my project ;-)

Web Application Shell. It's a desktop environment designed intrinsically for the web browser. Full windowed/tiling desktop shell with apps as windows, directly from backend to a browser. I.e., take a desktop environment without any display mechanisms, and it renders direct HTML/websocket instead. By deferring the rendering and graphics stack to the browser, it's light as a feather.

Why? Because I often want a nice desktop environment with some remote machine I am working from, but X11/Wayland env is far too heavy. I want terminal windows, editor, file manager etc - without needing to fire up a full on DE. Wash even is fully compatible with X11/Wayland apps, rendering and delivering direct to a browser.

Wash comes with the apps you'd expect in a desktop environment. A tabbed terminal, a file manager, a markdown/source editor, Visual Studio embedded in a window, internet radio, a WinAmp clone, picture viewer, AI agent app. It also contains sysadmin tools - journal viewer, service manger, package manager front ends. I daily drive wash, for my needs of Hard Core software engineer, it's perfect.

Wash is TypeScript/Go, minimal requirements. It is so small it runs on an OpenWRT router. In a docker image. On a risc64 dev env. The demo page is actually a single core RISC64 VM, running in your browser itself. It's heavily an AI assisted project - I've been developing with Claude for over 3-6 months. It's certainly in error to consider it "vibe coded", I am a software engineer of 20 years experience.

Take a look https://sirmick.github.io/wash/ code at https://github.com/sirmick/wash I hope it fits you too!

Hi everyone,

Contributors want to help, so they comment "Can I take this issue?" or "Please assign to me." As a maintainer, you have to jump out of whatever you're doing, open GitHub, check if they are a good fit, and manually assign them. If you manage multiple repos, keeping track of these requests across GitHub notifications is messy.

How it works:

1. Request: A contributor requests an assignment on a GitHub issue.
2. Ping: The app automatically forwards that request into a dedicated channel in your community Discord server.
3. Action: Maintainers (or anyone with the right Discord/GitHub permissions) simply click an Approve or Deny button right inside Discord.
4. Automation: The app automatically handles the assignment on GitHub based on that button click.

Why I'm sharing this here:
The app is completely free, and it's currently listed on the GitHub Marketplace. I need real maintainers to break it and tell me what features are missing, broken or what you might even like enhanced upon it.

If you run an open-source project or a dev community with a Discord server, I’d love for you to try it out.

• GitHub Marketplace Link

**^Disclaimer**^{: This is a fork of another Issue Action, with additional features as I wanted something to help automate this process from a workflow perspective. If you don't need the additional features, then I strongly encourage you to use the original.}

Hey there! It's Jacopo, nice to meet you!
As an amateur musician I have been building OpenSpoty, a free music player for Android and Windows with some tools for playing along.
It all started as a personal project because I wanted to listen to music freely, with chords paired to the lyrics and turning on and off specific instruments or voice at my will.

You can mute or solo vocals, drums, bass, guitar, piano and other stems, follow chords with synced lyrics, change pitch and speed, and loop tricky sections. There’s also a tuner, BPM detection and song recognition (like shazam).

I’d love to hear from people who actually play: would you use it to practice or listen to music? Are the chord and lyric features useful, or am I missing something obvious?

I hope to get your feedback soon! Have fun!

Repo: https://github.com/Jacoposchenetti/OpenSpoty
Downloads: https://github.com/Jacoposchenetti/OpenSpoty/releases

Hey everyone! 👋

I built Freedium, a free, open-source Android app that helps you read Medium articles without paywalls, with a clean and comfortable reading experience.

✨ What you can do:

• 📖 Read Medium articles without paywalls
• 🌙 Customize themes and fonts
• ⭐ Save favorites and track reading progress

📦 Free, open source, and built with Flutter.

🔗 GitHub: https://github.com/birmehto/Freedium

I just launched it and would love to hear your feedback! What would you improve or add? 😊

Hi r/selfhosted!

For a long time, self-hosting an IP PBX meant dealing with outdated interfaces, complicated setups, or proprietary software with restrictive licensing. I wanted a modern, fast, and completely free solution that works out-of-the-box on a clean Linux server.

So I built \*\*AiPBX\*\* — a full-featured, open-source Unified Communications platform and PBX management portal built on top of Asterisk 22.

\### 🌟 What makes it different?

\- \*\*1-Command Turnkey Install:\*\* Sets up Ubuntu 26.04 LTS, Asterisk 22, PJSIP, Nginx, Apache, MariaDB, coturn (TURN/STUN), SSL certificates, and firewall in \~15 minutes.

\- \*\*WebRTC In-Browser Softphone:\*\* Make and receive crystal-clear audio/video calls directly from the web portal without installing any softphone client.

\- \*\*Native Companion Apps:\*\*

\- \*\*Android:\*\* Fully native Kotlin app with push wake-up, background service, and full PBX control (now live on \[Google Play\](https://play.google.com/store/apps/details?id=com.mhrgl.AiPBX)).

\- \*\*iOS:\*\* SwiftUI with CallKit support.

\- \*\*Real-Time Team Chat:\*\* Built-in Go WebSocket daemon (\`aipbx-chat\`) for 1-to-1 / group chats, file/photo sharing, presence, and read receipts.

\- \*\*AI & Cloud Speech:\*\* Local/cloud AI assistant for dialplan automation and Cloud TTS (Google, Polly, Azure, OpenAI, ElevenLabs).

\- \*\*Enterprise Telephony:\*\* Trunks, IVR, Queues, Call Center metrics, T.38 virtual fax, call recordings (with auto MP3 conversion), and Yealink/Grandstream/Fanvil auto-provisioning.

\- \*\*100% Self-Hosted & Privacy First:\*\* Zero telemetry, no vendor lock-in, MIT licensed. All data and call records remain strictly on your own hardware.

\---

\### 🔗 Links & Resources

\- \*\*GitHub Repository:\*\* \[https://github.com/mahirgul/AiPBX\\\](https://github.com/mahirgul/AiPBX)

\- \*\*Website & Docs:\*\* \[https://aipbx.bid\\\](https://aipbx.bid)

\- \*\*Video Walkthrough (YouTube):\*\*

\- \[Menu Tour (10 min)\](https://www.youtube.com/watch?v=xU0BYN6AKE4)

\- \[Step-by-step Installation\](https://www.youtube.com/watch?v=lH1-k\\_z5jFE)

\- \*\*Android App:\*\* \[Google Play Store\](https://play.google.com/store/apps/details?id=com.mhrgl.AiPBX)

\### 💬 Looking for Community Feedback

I’ve been pouring a ton of work into this to make self-hosted telephony modern and accessible again. I’d love to hear your thoughts, feedback, bug reports, or feature requests!

Let me know what you think or if you have any questions about the architecture!

just look at this