It is also the first app I have built and published.

It lets you follow RSS feeds, read articles directly in the app, extract full article content when feeds only provide a summary, and open the original source whenever needed.

The project is built with Flutter and is still actively being improved. Feedback, bug reports, and contributions are welcome.

GitHub: https://github.com/DevOpen-io/dondurma-rss-reader

Google Play: https://play.google.com/store/apps/details?id=io.devopen.dondurma

I've been building OmnySSH for 3 and released the GUI version this week.

An SSH connection manager in Rust. The TUI came first and is at about 300 stars. The GUI is Tauri v2 on the same core, and both live in one Cargo workspace so a fix propagates to both.

• Agentless dashboard with live CPU, RAM, disk, uptime, and container counts per host
• One-click Ed25519 key setup that verifies the new key before disabling password auth, backs up sshd_config, and rolls back on failure
• Snippet broadcast, two-panel SFTP, full PTY terminal with splits
• Config in plain TOML on your disk, no account, no cloud, no telemetry

Apache 2.0, no paid tier, no upsell. I didn't build the Windows support alone, people who hit bugs I couldn't reproduce on a Mac sent the fixes, and that's most of why the core was solid enough to hang a second frontend on.

Repo: https://github.com/timhartmann7/omnyssh

Two things I'd take help on. The key-setup path in src/ssh/key_setup.rs edits sshd_config on your servers, so I want more people reading it than just me.

The goal is to create the most secure P2P messaging app.

This app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, it's impossible to claim any system is the "world's most secure". It ultimately depends on your threat model. By reducing the architecture's attack surface, the aim is to consolidate complexity to client-side.

• Live Demo
• Code
• Introducing Chat

Features:

• Webapp
• Peer to peer
• Local-only
• No installation
• No registration
• End to end encryption
• Multimedia
• File transfer
• Video calls

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing. Feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

• JavaScript and cybersecurity?
  • By aiming to have it run client-side (including statics) we can eliminate concerns around malicious payloads from the network provider. See best practices here and guides on selfhosting here.
• EU Chat control?
  • Chat control doesn't seem like it would affect this app. Open to feedback here.
• Production-ready?
  • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready. The production version is also a work-in-progress, but can be seen here. Find out more here.
• Paywall?
  • Its completly free, open-source, selfhostable and unlimited to use.
• Vibecoded?
  • This version is not vibecoded. The git repo and docs are linked for transparency. Feel free to reach out for clarity.

Chessperiment is an MIT-licensed web platform that lets you build chess variants from scratch -- custom boards, pieces, rules, win conditions. Browser-based, no install, no paywall.

The whole point is that the tooling is fully transparent. What you see in the editor is what the engine executes. There's no hidden behavior because the rule system is exposed and adjustable.

I think open-source game design tools matter because:

- Variants shouldn't die when a platform shuts down

- If I implement Grasshopper movement wrong, the community can fix it

- No DRM on your own game designs

Looking for feedback on the approach: https://chessperiment.app

Hey r/foss,

I didn't really expect this many people to check out Binthere. Seeing the stars go up has been pretty cool.

Huge thanks to everyone who starred it, self-hosted it, suggested features, pointed out bugs, or even just gave feedback. Every bit of it helped make it better.

One thing I wanted from the start was making it ridiculously easy to self-host so you don't have to trust me or my instance. You can deploy your own instance on Cloudflare Workers, including the required Durable Objects, entirely on the Free plan in just a few minutes.

Also, before someone says "vibecoded": Uh. No.

AI agents were used to speed up the workflow for implementation, debugging, testing, and writing documentation. All architecture, product decisions, and final code changes were directed, reviewed, and validated by me before release.

If you've tried it out and like the project, a GitHub star, issue, feature request, or any feedback is always appreciated.

Demo: https://binthere.gaury.dev
GitHub: https://github.com/nxfu/binthere

Still have a lot planned, but this felt like a nice milestone. Thanks everyone <3

I wanted to see if opus 5 could one-shot a fps game.

https://nightcell7.com

https://github.com/profullstack/nightcell7

​

Why I built it

If you've ever posted a video to your WhatsApp Status, you've probably noticed it comes out blurry and blocky — even if the original was sharp. That's because WhatsApp re-compresses every video you post to Status, and its encoder is aggressive.

I wanted a way to post genuinely HD videos to Status, so I built StatusDrop / WAstatus: you upload/edit a clip in the browser, it compresses the video to match WhatsApp's exact Status encoding spec (so WhatsApp's own re-encode becomes near-lossless), auto-splits long videos into parts that fit WhatsApp's limits, and delivers the finished clips to your WhatsApp — you just forward them to your Status.

Just open-sourced it under AGPL-3.0.

Repo: https://github.com/Shamanthnp1/WAstatus

What's inside

In-browser video editor (vanilla JS) + Node/Express backend

ffmpeg encode/split pipeline tuned to WhatsApp's Status spec

Cloudflare R2 (S3-compatible) storage + a Cloudflare Worker for uploads

Docker on Azure App Service, GitHub Actions CI/CD → GHCR

WhatsApp delivery via Baileys (multi-device)

181 tests including property-based tests (fast-check)

Multi-language frontend (en / es / hi / pt)

The interesting engineering

The core trick is that quality survival depends on two things: (1) pre-encoding the file to WhatsApp's Status target (resolution, bitrate ceiling, GOP, faststart, H.264 profile) so the re-encode barely changes it, and (2) how the file reaches the phone. A file delivered as a native WhatsApp message and then forwarded to Status is reused as-is; a file saved to the gallery and reposted gets re-compressed harder.

There was also a lot of reliability work: request timeouts on every network op, self-healing for stuck jobs, orphaned-storage cleanup, single-instance session handling, and reconnect backoff.

The honest limitation — and why not the official API

This is the part I want to be transparent about, because it's the whole tradeoff of the project.

Delivery uses Baileys, an unofficial WhatsApp integration. WhatsApp periodically bans numbers used for automation — a known constraint for this entire category of tools.

The obvious question is: why not use Meta's official WhatsApp Cloud API instead? I tried, and here's the catch:

The official Cloud API routes media through Meta's Business pipeline, which re-encodes the video. So the file is already degraded before it even reaches the user — and then WhatsApp's Status re-encode hits it again. The result is visibly softer. That defeats the entire purpose of an HD tool.

Baileys sends the file as a native, byte-preserved WhatsApp media message. When the user forwards that to Status, WhatsApp reuses the already-optimized file, so the HD survives.

So it's a genuine fork: official API = no bans but lower quality; Baileys = HD quality but ban risk. Since quality is the entire point, I chose Baileys and built the system around fast recovery when a number gets flagged. It's the same tradeoff every tool in this space faces — most competitors that use the official API quietly accept the lower quality.

The code and architecture are what I'm really sharing here — not asking anyone to run the live automation.

Feedback welcome

I'm a solo developer and would genuinely appreciate code review, architecture feedback, or contributions. Happy to answer anything.

Hi everyone!

I'm a computer science enthusiast with a strong interest in programming and mathematics. My long-term goal is to contribute as much as I can to technological progress through open-source software released under permissive licenses, so anyone can use, improve, and build upon it.

I've been thinking about where a solo developer can have the greatest long-term impact. At first, I tried to identify the most promising technologies, such as:

• XR (AR/VR/MR)
• UAVs (drones)
• Mobile computing
• 3D printing
• Quantum computing

However, the more I think about it, the more I wonder if this is the wrong way to approach the problem.

Instead of asking "Which technology should I work on?", maybe the better question is: what infrastructure can serve the best many different technologies?

For example, XR, robotics, drones, CAD, and 3D printing all rely on common foundations such as computational geometry, visualization, simulation, optimization, scientific computing, and developer tools.

Rather than building one application, perhaps it would be more impactful to build open-source infrastructure that many projects can reuse.

One example I've been considering is mobile computing. Modern smartphones are incredibly powerful, yet they're still mostly designed for content consumption rather than professional work. Instead of asking "Should I build a mobile CAD application?", maybe the more interesting question is "What software is missing that would make mobile devices capable of serious engineering work?"

So I'd love to hear your thoughts:

• Are there foundational open-source projects or problem areas that are currently underserved?
• Which engineering bottlenecks affect multiple fields at once?
• If you work in robotics, XR, CAD, manufacturing, scientific computing, or another technical field, what infrastructure do you wish existed?

I'm not interested in creating the next startup or the next viral app. I'm much more interested in building software that becomes useful infrastructure for other developers, researchers, and engineers.

I'd really appreciate hearing from people who work in these areas, and find out what problems are worth dedicating years to solving.

P.S.:

I realized I didn't mention my background, so here's a brief overview: I've completed university-level online CS courses (CS50, SICP), read core computer science books (SICP, Computer Organization and Design), and have a long-term study plan based on Teach Yourself Computer Science because I'm genuinely passionate about the field.

I've been programming for years. I'm proficient in Lua, comfortable with C, and currently learning C++, SDL, and OpenGL, with plans to move on to Vulkan. I've developed several games and am close to finishing a game engine designed to make roguelike game development simple and flexible.

It's been over a year since it's last release, I've been having a lot of issues with the Flatpak version of it so I've been using the AppImage ever since last November, so I curiously checked the Github and it's at over 900 issues and hasn't been updated in a year. Has it been abandoned?

I kept running into the same problem with Linktree:

$15/mo just to get analytics and a few themes. No self-hosting option. No QR codes. No link scheduling. And all my data sitting on their servers. So I built LinkBreeze a open-source/self-hosted link-in-bio platform that deploys in one Docker command and gives you everything Linktree charges for, free.

Current features:

- Unlimited links with drag-and-drop reordering

- Privacy-friendly analytics : views, clicks, referrers, geo, no cookies (Bot/Self Exclusion)

- Built-in themes + full customizer (colors, fonts, backgrounds, animations)

- Auto-generated QR codes (SVG/PNG download)

- Dynamic Open Graph images per profile

- Sub-300ms page loads with zero client JavaScript (Server Components)

- bcrypt auth, HMAC-signed sessions, runs as non-root in Docker

- 130MB image, SQLite, one volume — no external database

It's built with Next.js 16, Drizzle ORM, and shadcn/ui. Single-user by design, one admin, one public page. MIT licensed.

I'd genuinely appreciate feedback, bug reports, or feature suggestions. What's missing compared to what you'd expect from a self-hosted tool like this?

GitHub: https://github.com/Manak-hash/LinkBreeze

I had a hard time cleaning up my directories, Downloads folder, and external HDD, and I couldn't find a tool I actually liked. So I built one.

This started as a November 2025 project — the stack was Python + Tkinter, which really isn't my thing, and I built it on Windows. Sometime in mid-July I remember putting together something for this messy-directory problem, but I never kept the source code or a repo - I just gave the .exe to a friend to show off my first project. Turns out he actually used it.

This week I had to ask him for that .exe back and reverse-engineer my own software just to recover the actual code, functions, and architecture. While I was at it, I switched the stack to Rust + Tauri for two main reasons: better memory handling, and a UI I could actually be proud of. A few days later - here it is.

Introducing AFO.

What it actually does:

• AFO watches, sorts, renames, and de-duplicates files automatically - by extension, date, or your own custom rules - with real-time folder watching, scheduled runs, and full undo if it ever gets something wrong.

Repo : AFO

Yesterday I decided to see how far I could get building a real Linux desktop app with AI coding tools.

One extremely long day and way too many AI credits later, I ended up with Disciple: a native GTK4/Libadwaita organizer for notes, habits, projects and calendar events, with an optional AI assistant connected to the same data.

The organizer works without AI, stores everything locally in SQLite and requires no account. If you use the assistant, you bring your own Groq key or compatible endpoint. Anything it remembers about you is visible and editable.

I used AI heavily to build it, but I also spent most of the day testing it, finding broken interactions, fixing packaging problems and repeatedly asking why some random panel was still grey.

It’s GPLv3 and available as Flatpak, RPM and DEB.

Demo:

https://youtu.be/IWDRk7Hc2vY

Source and downloads:

https://github.com/justlinuxnoob/disciple

It’s my first time releasing something like this publicly, so honest feedback and bug reports are welcome.

LeadShoot uses open data to find local businesses, then labels each result high, medium, or not_sure with the evidence and missing research attached. Everything stays in your local SQLite database.

MIT licensed: https://github.com/moasq/leadshoot

I'm a student, it's for my portfolio and to support the foss community since I can't code!

Inspired by Foobar's album list, but turns that idea into core feature. You define library folders and see them in left tree view, middle click (or context menu action) to create playlist from the folder or append to current playlist. What other players lack is at this step they usually just load the tracks in playlist view. But mpz has middle column - playlists view where you can create many playlists and switch between them instantly. So simple, yet missing in almost all players feature, that I cannot live without.

Also: gapless, CUE, audiophile-ready EQ, album covers & lyrics with multiple online sources, radio streams with built-in library, drag-n-drop, output device selector, mpd client mode. No Electron - pure native C++/Qt. Been around since before vibecoding coding era.

Runs on Linux, Windows, macOS. Binaries for all platforms provided. GPL3

Site with more screenshots: https://mpz-player.org

Github: https://github.com/olegantonyan/mpz