Easy Pong – A Retro Classic Re‑imagined in Flutter
https://github.com/adeeteya/EasyPong

https://redd.it/1n5lmcl
@r_opensource

Downlodr is now on Mac! 🍎🍎 (Free, open source video downloader)

Exciting news! After a lot of requests, Downlodr is now officially available for Mac users. This app leverages the robust yt-dlp backend and pairs it with a minimal, user-focused design. The aim: ethical, open software that puts transparency and privacy first.

# What sets Downlodr apart:

Absolutely no ads, bloatware, or sneaky redirects
Modern interface supporting batch downloads
Powered by the reliable yt-dlp framework
Now runs on macOS and Windows, with Linux support in the pipeline
Plugin system for added customization—now cross-platform
Clear telemetry and privacy controls

Downlodr is completely free, open-source, and built with the community in mind. If you want to give it a spin, here are the relevant links!

Download: https://downlodr.com/
Source: https://github.com/Talisik/Downlodr
Try it, and let us know what you think in r/MediaDownlodr! We’re always looking to improve!

https://redd.it/1n5mlg5
@r_opensource

Do you remember Metamod for Counter-Strike 1.6? I updated my own server mod that still works after more than a decade

Metamod used to be a server-side plugin engine for GoldSrc engine games, such as Counter-Strike 1.6. In mid-late 2008 I first started to create my own server-side hack (technically it's the correct name), but that codebase was extremely ugly.

In around 2013 or 2014 I started creating a new one from scratch, but I wanted to make it in a way others could use it and base their own creations on it.

I now revisited the project and it still works. last time I played CS 1.6 was over a decade ago, so this was also the last time I checked if the server-side hackbase works.

What can I say, it still works and so I spent the last 2 days building some features into it.

GoldSrc is very outdated and despite CS 1.6 being one of the top games of the 2000s (when Steam launched and replaced WON servers), I have to say it's still fun to goof around with that stuff. Just freak out a little in your own local match, like this:

https://www.youtube.com/watch?v=1Gbx-zXN7wM

Even tho the engine is dated, I must say that it's very enjoyable to build on it. The architecture is simple, you can do much stuff via engine and DLL functions and it's actually pretty simple to accomplish stuff.

So, in case you want to unlock some core memories and dwell in nostalgia, the sourcecode of my "Apocalypse Server" is open-sourced (MIT license) and available on GitHub.

Have fun. :D

NOTE: This only works via a game server (HLDS, listenserver) and is only for educational purposes.



https://redd.it/1n5mzzj
@r_opensource

Clickhouse MCP Agent
https://pypi.org/project/clickhouse-mcp-agent/0.7.0/#denoscription

https://redd.it/1n5mscy
@r_opensource

This is a mind-blowing Open Source React library to build high-performance 3D Apps!

\- Lightweight & Fast

\- Works Seamlessly with React

\- Perfect for Interactive 3D Experiences

If you're into 3D web development, this is a must-try!

Source 🔗: https://github.com/playcanvas/react

Hope this helps ✅

https://redd.it/1n5qbu9
@r_opensource

PewDiePie Joins GitHub - What’s the YouTube Star Coding in Open Source?

YouTuber PewDiePie just launched his [GitHub profile](https://github.com/PewDiePie-archdaemon)! After switching to Linux and self-hosting on a Steam Deck, Felix is diving into the open-source world.

What projects might he contribute to?

* A meme generator for his videos?
* A Minecraft mod for his community?
* Something totally unexpected? Share your thoughts—what could a creator like PewDiePie bring to open source?

https://redd.it/1n5ryvl
@r_opensource

Dingent: UI-configurable LLM agent framework with MCP-based plugin system

Dingent is an open-source, MCP‑style (protocol-driven) agent framework: one command spins up chat UI + API + visual admin + plugin marketplace. Focus on your domain logic, not glue code. Looking for feedback on onboarding, plugin needs, and MCP alignment.

GitHub Repo: `https://github.com/saya-ashen/Dingent` (If you find it valuable, a Star ⭐ would be a huge signal for me to prioritize future development.)

# Why Does This Exist? My Pain Points Building LLM Prototypes:

Repetitive Scaffolding: For every new idea, I was rebuilding the same stack: a backend for state management (LangGraph), tool/plugin integrations, a React chat frontend, and an admin dashboard.
Scattered Configuration: Settings were all over the place—.env files, JSON, hardcoded values, and temporary noscripts.
Tool Friction: Developing, installing dependencies for, and reusing Tools was a hassle. There was no standard interface for capability negotiation.
The "Headless" Problem: It was difficult to give non-technical colleagues a safe and controlled UI to configure assistants or test flows.
Clunky Iteration: Switching between different workflows or multi-assistant combinations was tedious.

The core philosophy is to abstract away 70-80% of this repetitive engineering work. The loop should be: Launch -> Configure -> Install Plugins -> Bind to a Workflow -> Iterate. You should only have to focus on your unique domain logic and custom plugins.

# The Core Highlight: An MCP-Style Plugin System

Dingent's plugin system is heavily inspired by (and progressively aligning with) the principles of MCP (Model Context Protocol):

Protocol-Driven Capabilities: Tool discovery and capability exposure are standardized, reducing hard-coded logic and implicit coupling between the agent and its tools.
Managed Lifecycle: A clear process for installing plugins, handling their dependencies, checking their status, and eventually, managing version upgrades (planned).
Future-Proof Interoperability: This architectural choice opens the door to future interoperability with other MCP-compatible clients and agents.
Community-Friendly: It makes it much easier for the community to contribute "plug-and-play" tools, data sources, or debugging utilities. (If you're interested in the MCP standard itself, I'd love to discuss alignment in the GitHub Issues).

# Current Feature Summary:

🚀 One-Command Dev Environment: uvx dingent dev launches the entire stack: a frontend chat UI (localhost:3000), a backend API, and a full admin dashboard (localhost:8000/admin).
🎨 Visual Configuration: Create Assistants, attach plugins, and switch active Workflows from the web-based admin dashboard. No more manually editing YAML files (your config is saved to `dingent.toml`).
🔌 Plugin Marketplace: A "Market" page in the admin UI allows for one-click downloading of plugins. Dependencies are automatically installed on the first run.
🔗 Decoupled Assistants & Workflows: Define an `Assistant` (its role and capabilities) separately from a `Workflow` (the entry point that activates it), allowing for cleaner management.
🛠️ Low Floor, High Ceiling: Get started with basic Python, but retain the power to extend the underlying LangGraph, FastAPI, and other components whenever you need to.

# Quick Start Guide

Prerequisite: Install uv (pipx install uv or see official docs).

# 1. Create and enter your new project directory
mkdir my-awesome-agent
cd my-awesome-agent

# 2. Launch the development environment
uvx dingent dev

Next Steps (all via the web UI):

1. Open the Admin Dashboard (http://localhost:8000/admin) and navigate to Settings to configure your LLM provider (e.g., model name + API key).
2. Go to the Market tab and click to download the "GitHub Trending" plugin.
3. Create a new Assistant, give it instructions, and attach the GitHub plugin you

Dingent: UI-configurable LLM agent framework with MCP-based plugin system

Dingent is an open-source, MCP‑style (protocol-driven) agent framework: one command spins up chat UI + API + visual admin + plugin marketplace. Focus on your domain logic, not glue code. Looking for feedback on onboarding, plugin needs, and MCP alignment.

**GitHub Repo:** [`https://github.com/saya-ashen/Dingent`](https://github.com/saya-ashen/Dingent) (If you find it valuable, a Star ⭐ would be a huge signal for me to prioritize future development.)

# Why Does This Exist? My Pain Points Building LLM Prototypes:

* **Repetitive Scaffolding:** For every new idea, I was rebuilding the same stack: a backend for state management (LangGraph), tool/plugin integrations, a React chat frontend, and an admin dashboard.
* **Scattered Configuration:** Settings were all over the place—`.env` files, JSON, hardcoded values, and temporary noscripts.
* **Tool Friction:** Developing, installing dependencies for, and reusing Tools was a hassle. There was no standard interface for capability negotiation.
* **The "Headless" Problem:** It was difficult to give non-technical colleagues a safe and controlled UI to configure assistants or test flows.
* **Clunky Iteration:** Switching between different workflows or multi-assistant combinations was tedious.

The core philosophy is to **abstract away 70-80% of this repetitive engineering work**. The loop should be: Launch -> Configure -> Install Plugins -> Bind to a Workflow -> Iterate. You should only have to focus on your unique domain logic and custom plugins.

# The Core Highlight: An MCP-Style Plugin System

Dingent's plugin system is heavily inspired by (and progressively aligning with) the principles of **MCP (**Model Context Protocol**)**:

* **Protocol-Driven Capabilities:** Tool discovery and capability exposure are standardized, reducing hard-coded logic and implicit coupling between the agent and its tools.
* **Managed Lifecycle:** A clear process for installing plugins, handling their dependencies, checking their status, and eventually, managing version upgrades (planned).
* **Future-Proof Interoperability:** This architectural choice opens the door to future interoperability with other MCP-compatible clients and agents.
* **Community-Friendly:** It makes it much easier for the community to contribute "plug-and-play" tools, data sources, or debugging utilities. (If you're interested in the MCP standard itself, I'd love to discuss alignment in the GitHub Issues).

# Current Feature Summary:

* 🚀 **One-Command Dev Environment:** `uvx dingent dev` launches the entire stack: a frontend chat UI (`localhost:3000`), a backend API, and a full admin dashboard (`localhost:8000/admin`).
* 🎨 **Visual Configuration:** Create Assistants, attach plugins, and switch active Workflows from the web-based admin dashboard. No more manually editing YAML files (your config is saved to `dingent.toml`).
* 🔌 **Plugin Marketplace:** A "Market" page in the admin UI allows for one-click downloading of plugins. Dependencies are automatically installed on the first run.
* 🔗 **Decoupled Assistants & Workflows:** Define an `Assistant` (its role and capabilities) separately from a `Workflow` (the entry point that activates it), allowing for cleaner management.
* 🛠️ **Low Floor, High Ceiling:** Get started with basic Python, but retain the power to extend the underlying LangGraph, FastAPI, and other components whenever you need to.

# Quick Start Guide

**Prerequisite:** Install `uv` (`pipx install uv` or see official docs).

# 1. Create and enter your new project directory
mkdir my-awesome-agent
cd my-awesome-agent

# 2. Launch the development environment
uvx dingent dev

**Next Steps (all via the web UI):**

1. Open the **Admin Dashboard** (`http://localhost:8000/admin`) and navigate to **Settings** to configure your LLM provider (e.g., model name + API key).
2. Go to the **Market** tab and click to download the "GitHub Trending" plugin.
3. Create a new **Assistant**, give it instructions, and attach the GitHub plugin you

just downloaded.
4. Create a **Workflow**, bind it to your new Assistant, and set it as the "Current Workflow".
5. Open the **Chat UI** (`http://localhost:3000`) and ask: *"What are some trending Python repositories today?"*

You should see the agent use the plugin to fetch real-time data and give you the answer!

# Current Limitations

* Plugin ecosystem just starting (need your top 3 asks)
* RBAC / multi-tenant security is minimal right now
* Advanced branching / conditional / parallel workflow UI not yet visual—still code-extensible underneath
* Deep tracing, metrics, and token cost views are WIP designs
* MCP alignment: conceptually in place; still formalizing version negotiation & remote session semantics

https://redd.it/1n5ri36
@r_opensource

Looking for interesting side projects to contribute to which solves real world problems or specific use cases.

Note 1: I would prefer if the project is open source

Note 2: I am skilled in front end development and server side of things, I am currently upskilling continuously and have experience with the HTML,CSS, JS, TS, REACT, GSAP, NEXT.JS, Responsiven Design, Prisma, ZOD, NextAuth, Complete sector of UI/UX. And currently working on learning REST API, REDUX, REDIS, EXPRESS.

Note 3: I won't be able to help much in backend other than the basics of querying and operations on the database.



Hello, I am a web developer and UI/UX designer, Currently working on my skillsets everyday and pursuing a degree of BTECH in IT.

I am currently contributing to an open source project and wish to do more of the contribution with other people on cool and useful projects so if anyone is taking on peers for their work would love to join in.

I thrive in creating creative and intuitive frontends with good user experience so if you need someone who can handle the visuals I can be of good help.

I am currently working on projects which are headed by me so it is gonna be a good change for me to work on other people's projects which is where I can focus totally on the codebase and design instead of worrying about the dynamics and the marketting.

(Won't be able to work on projects outside the React ecosystem)

https://redd.it/1n5pwqn
@r_opensource

Bear is now source-available
https://herman.bearblog.dev/license/

https://redd.it/1n66nwp
@r_opensource

Meet Elysia: A New Open-Source Python Framework Redefining Agentic RAG Systems with Decision Trees and Smarter Data Handling
https://www.marktechpost.com/2025/09/01/meet-elysia-a-new-open-source-python-framework-redefining-agentic-rag-systems-with-decision-trees-and-smarter-data-handling/

https://redd.it/1n68nbn
@r_opensource

I built OSINTGraph — an open-source tool that maps a target person’s Instagram network and integrates an AI agent for data analysis and investigations.

**OSINTGraph** maps a target’s entire Instagram network — followers, followees, posts, comments, and likes — into a single interactive social graph.

It comes with an AI agent that assists your investigation. You can ask questions like:

* "Show me every comment by john\_doe made in April this year"
* "Who are their mutual followers between jane\_doe and john\_doe?"
* "Find all comments from post XXX that mention 'concert'"

The AI runs the queries, helps you find the data you’re looking for, and even performs reasoning to provide insights about your target.

Ideal for OSINT investigations, research, or exploring digital connections.

👉 [github.com/XD-MHLOO/Osintgraph](https://github.com/XD-MHLOO/Osintgraph)

If it’s useful, don’t forget to star the repo! ⭐

https://redd.it/1n6ch6a
@r_opensource

The Hidden Vulnerabilities of Open Source
https://fastcode.io/2025/09/02/the-hidden-vulnerabilities-of-open-source/

https://redd.it/1n6e8cn
@r_opensource

I built an open source trading journal focused around Indian markets (for now)

As a retail trader in India, I was frustrated.

Most journaling tools were built for US markets. Indian brokers? ❌ Barely supported.
And even if they worked, they’d cost ₹2.5k–₹4k/month, while still needing manual trade uploads.

I couldn’t justify paying that much for something that didn’t even integrate with my broker.
So for months, I just tracked my monthly PnL in Excel with two charts - cumulative PnL curve and monthly PnL bars.

Eventually, I decided to build a proper tool that actually worked for us.

It's called Arthveda and it's GitHub repo.

🧠 What it does today:

✅ Import trades via Excel from Zerodha, Upstox, and Groww. More brokers integrations in development.
🔄 1-click sync for Zerodha. Fetches today’s trades and syncs instantly.
📊 Get insights like Cumulative PnL over time, PnL over time (grouped by daily, weekly, monthly), charges, win/loss stats, streaks, R-factor, etc. More insights in development.
📁 Explore positions with powerful filters. Quickly drill down to exactly the position(s) you’re looking for.
🔍 Dive into any position \- view entry/exit trades, holding period, charges, notes, and more. More powerful journal with features like rich text editor, uploading screenshots and tagging trades in development.

I built it for myself and others who care about tracking their performance and improving over time.

https://redd.it/1n6ho85
@r_opensource

Are opensource licenses enforcable?

I am preparing my app for launch and my plan is to make it opensource, but as a lot of people who are in similar position, I am also worried about the future of the app. It's possible that one of the big companies can take the source code and push it down their larger distribution channel and essentially make my app redundant.

I haven't researched this part properly, but I know there are some licenses that, on paper, prevents scenarios like this. I am not so worried about a company making this app their internal tool, but it would be nice if a company larger than certain size does this they have to purchase some sort of license to do so.

I guess my question is can I enforce such limitations on my open source apps using licenses so a big company neither distribute the product on their own or adopt it internally without any license.

https://redd.it/1n6icyt
@r_opensource

What do you get back from your project?

I am wondering how people with an open source project keep it up? I've recently saw a meme where a company takes a open source project and just sell it as being it their own.
So it made me wonder what do you get in return? do you receive any sponsoring? are you getting a referral bonus? And is this enough?

https://redd.it/1n6hvvi
@r_opensource

How a market-leader open source software was born

I was working as an architect of a specific technical domain in a fairly big company. I was young and idealist, and loved my work. You know, the type of guy who only accepts the job if the copyright and confidentiality part of the contract is changed to allow to develop open source. I had to use some closed components, but my hand was mostly free (after quite an amount of discussion, it was probably around the time when the term Open Source was born) to use free software.

There was a specific functionality which needed interoperability between different flavors of unixen (yeah, at that time Linux was considered unreliable and primitive, not the only unix which any sane tech guy even think of. I used it nevertheless, because in reality it was already better than the others), and all the implementations were either utterly unreliable or not interoperable. I have found an open source implementation with a BSD license which had the right specification... And also practically unuseable. I persuaded my boss that this is the right way to go, we should hire someone to fix it.

Remember, it was a big company, where every software project needed miles of red tape and at least 5kUSD. My boss said yes, so I wrote an email to the Linux mailing list of the country searching for someone doing it. A guy answered. He happened to be studying in the same university, where I came from, just one year younger (yes, I was that young as well). He knew me, but I didn't remember him. So we talked, and he gave an offer. Of 100USD. I happily told it to my boss, who nearly got an instant heart attack. The boss told me that he is afraid this will be low quality, and the guy can ask for more, but make sure that everything is perfect. So I went back to the guy, and told him that. So we got a new offer. Of 250USD😁

So we made the contract. I put in that it should be delivered both as source code and as packaged for the unix flavors and Linux distros we use. I also put in that the source should be GNU GPL. If you can close a BSD software, you can open it as well, right?

The software was delivered and working great. But the maintainer of the software we fixed - and the BSD community in general - was not too happy. They said we cannot modify the licence. That we have stolen it. I said if closed vendors can change the licence, why we cannot. We gave credit where credit is due. Bazsi - the dev guy - said that he thought about how the internal structure of the software can be made better and he does not want conflict, so he rewrote the whole stuff from the ground up, making it even better in the process. It went so well that for a time it became the default package for the job in multiple Linux distribution, hence the market leader.

This is how syslog-ng was born.


https://redd.it/1n6krsr
@r_opensource

ReqRes - native HTTP(S) traffic monitor & debug tool for macOS

Hey everyone,

I'd like to share with you the ReqRes. It's a native HTTP(S) traffic monitor & debug tool for macOS. You can find the app here: https://github.com/OloApps/ReqRes

The app allows you to investigate and manipulate the network traffic on your macOS. In case you're a Software Engineer, there are multiple use cases when you can find this app useful. For instance, the app can overwrite the original server's response for testing purposes, including responses with static files (Map Local tool).

Any feedback is much appreciated, and I hope you find the app useful.

https://redd.it/1n6ncf8
@r_opensource

How to acquire any open source project?

I am building something similar to Twilio but only for WhatsApp.

For my Product, my target audience is software developer or a CTO.

Now as a developer, I personally hate any kind of marketing targeted to me.

So for my Product, I am thinking of acquiring few open source project in some kind of messaging space and improve it by adding resources to it.

I am not quite sure how acquisition happens for open source software.

https://redd.it/1n6o1gd
@r_opensource

I created Ducky, a free, open-source networking tool with a tabbed terminal, topology mapper, and security scanners. What should I build next?

Hey everyone, So, like a lot of you, I spend my days jumping between PuTTY, a subnet calculator, Nmap, a separate notes app, and a dozen other little utilities just to get my work done. It got pretty frustrating. I decided to do something about it and started building Ducky, a free, open-source "all-in-one" tool for Windows that puts everything in one place. It started as a personal project to scratch an itch, but it's gotten to a point where I think it might actually be useful to others.

Right now, it has:

A tabbed serial terminal (so you can connect to multiple routers/switches)
Network scanner/topology mapper (still basic, but it finds devices)
Subnet calculator
Ping, Traceroute, and a Port Scanner
A few basic security tools (CVE lookup, password strength checker, hash tool)
A dockable notepad for scribbling down configs.

My real question for all of you pros and hobbyists is: If you could have any feature in a tool like this, what would it be? What’s that one thing you always find yourself wishing your terminal could do? Or a check you constantly have to run from a separate noscript? I'm looking for ideas to make this actually useful for the community. No idea is too big or too small. I'd love to hear what you think. Thanks for taking a look!

https://redd.it/1n6p6q8
@r_opensource