I cobbled together a wrapper setup to build Goo Engine on Linux
https://github.com/linuxnoodle/goo-engine-linux-wrapper/
https://redd.it/1pa955z
@r_opensource
https://github.com/linuxnoodle/goo-engine-linux-wrapper/
https://redd.it/1pa955z
@r_opensource
GitHub
GitHub - linuxnoodle/goo-engine-linux-wrapper: I'M GOOING IT SO HARD
I'M GOOING IT SO HARD. Contribute to linuxnoodle/goo-engine-linux-wrapper development by creating an account on GitHub.
Easy-Tools-Town :a free, open-source toolkit for PDFs, image & document
Looking for contribution to add more tools and make this platform good
https://github.com/Namit2111/Easy-Tools-Town
https://redd.it/1pae65m
@r_opensource
Looking for contribution to add more tools and make this platform good
https://github.com/Namit2111/Easy-Tools-Town
https://redd.it/1pae65m
@r_opensource
GitHub
GitHub - Namit2111/Easy-Tools-Town
Contribute to Namit2111/Easy-Tools-Town development by creating an account on GitHub.
Looking for core contributors to build a decentralized, privacy-first messenger (Rust/libp2p/Signal crypto)
**We’re assembling an early, core open-source team for FidoNext — a fully decentralized, privacy-first messenger built on libp2p with Signal-grade cryptography, zero servers, and strong metadata resistance.**
If you care about privacy, censorship-resistance, and modern distributed systems — read on.
We’re looking for collaborators (not corporate hires yet) across several key areas:
# 🟥 CTO / System Architect
Someone who can own the high-level architecture and long-term technical direction.
**You should be comfortable with:**
* secure distributed systems
* P2P overlay design & libp2p routing
* privacy posture, metadata resistance, DPI-evasion
* cryptographic protocols and secure key infrastructure
* scaling decentralized networks
# 🟧 Rust & P2P Engineers
You’ll work on the core messenger engine: routing, transport, crypto, reliability.
**Tech we use / value:**
* Rust async (Tokio)
* rust-libp2p
* QUIC / HTTP3 / MASQUE
* libsignal
* store-and-forward messaging
* Ed25519 / Curve25519 / AES-GCM
* GossipSub relays
* IPFS/Filecoin primitives
If you love building P2P protocols the right way — this is for you.
# 🟨 C++ / Qt UI Developers
For the desktop client and UI layer.
**Relevant stack:**
* Qt/QML (messenger UX)
* multimedia handling
* Rust ↔ C++ FFI (CXX / UniFFI)
* cross-platform builds (macOS, Linux, Windows)
# 🟩 Kotlin / Swift Mobile Developers
Building the iOS/Android clients with a Rust core.
**Relevant experience:**
* embedding Rust in mobile apps
* FCM/APNs push design
* secure enclave / keychain storage
* BLE/QR peer discovery
* messenger UX polish
# 🟦 Security / Crypto Engineers
If your brain lights up on protocol security and metadata-resistant communication — we need you.
**You might know:**
* libsignal-client
* MLS
* X3DH / Double Ratchet
* threat modeling
* metadata obfuscation
* MITM hardening
* audit preparation
# 🟪 Marketing / PR / Community
We also need people who can help shape the story, voice, and community.
**Looking for someone who can:**
* drive growth storytelling in privacy tech
* build an open-source community from scratch
* run SMM across X, Telegram, LinkedIn
* help shape our message for developers & early adopters
# 🔥 Who we’re looking for overall
People who:
* love decentralized systems & open-source
* care about privacy as a human right
* want to be early in something meaningful
* like solving real, deep technical problems
* can collaborate async and globally
* want to help architect the future of private communication
This is an **early-stage, contributor/open-source collaboration**, not a traditional paid-job structure — but future **core team**, **equity**, and **leadership** roles are very much on the table.
If you’re interested or want to learn more, **comment or DM me** — happy to chat, share architecture docs, and discuss the roadmap.
https://redd.it/1paet1u
@r_opensource
**We’re assembling an early, core open-source team for FidoNext — a fully decentralized, privacy-first messenger built on libp2p with Signal-grade cryptography, zero servers, and strong metadata resistance.**
If you care about privacy, censorship-resistance, and modern distributed systems — read on.
We’re looking for collaborators (not corporate hires yet) across several key areas:
# 🟥 CTO / System Architect
Someone who can own the high-level architecture and long-term technical direction.
**You should be comfortable with:**
* secure distributed systems
* P2P overlay design & libp2p routing
* privacy posture, metadata resistance, DPI-evasion
* cryptographic protocols and secure key infrastructure
* scaling decentralized networks
# 🟧 Rust & P2P Engineers
You’ll work on the core messenger engine: routing, transport, crypto, reliability.
**Tech we use / value:**
* Rust async (Tokio)
* rust-libp2p
* QUIC / HTTP3 / MASQUE
* libsignal
* store-and-forward messaging
* Ed25519 / Curve25519 / AES-GCM
* GossipSub relays
* IPFS/Filecoin primitives
If you love building P2P protocols the right way — this is for you.
# 🟨 C++ / Qt UI Developers
For the desktop client and UI layer.
**Relevant stack:**
* Qt/QML (messenger UX)
* multimedia handling
* Rust ↔ C++ FFI (CXX / UniFFI)
* cross-platform builds (macOS, Linux, Windows)
# 🟩 Kotlin / Swift Mobile Developers
Building the iOS/Android clients with a Rust core.
**Relevant experience:**
* embedding Rust in mobile apps
* FCM/APNs push design
* secure enclave / keychain storage
* BLE/QR peer discovery
* messenger UX polish
# 🟦 Security / Crypto Engineers
If your brain lights up on protocol security and metadata-resistant communication — we need you.
**You might know:**
* libsignal-client
* MLS
* X3DH / Double Ratchet
* threat modeling
* metadata obfuscation
* MITM hardening
* audit preparation
# 🟪 Marketing / PR / Community
We also need people who can help shape the story, voice, and community.
**Looking for someone who can:**
* drive growth storytelling in privacy tech
* build an open-source community from scratch
* run SMM across X, Telegram, LinkedIn
* help shape our message for developers & early adopters
# 🔥 Who we’re looking for overall
People who:
* love decentralized systems & open-source
* care about privacy as a human right
* want to be early in something meaningful
* like solving real, deep technical problems
* can collaborate async and globally
* want to help architect the future of private communication
This is an **early-stage, contributor/open-source collaboration**, not a traditional paid-job structure — but future **core team**, **equity**, and **leadership** roles are very much on the table.
If you’re interested or want to learn more, **comment or DM me** — happy to chat, share architecture docs, and discuss the roadmap.
https://redd.it/1paet1u
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
A tool that enhances privacy of pictures for Android
Source code and details: https://github.com/umutcamliyurt/PixelCloak
Features:
No permissions required
Reduces effectiveness of hash-based detection
Randomizes filename
Removes EXIF metadata
Censors any detected faces in picture
Written in Java
https://redd.it/1paggpg
@r_opensource
Source code and details: https://github.com/umutcamliyurt/PixelCloak
Features:
No permissions required
Reduces effectiveness of hash-based detection
Randomizes filename
Removes EXIF metadata
Censors any detected faces in picture
Written in Java
https://redd.it/1paggpg
@r_opensource
GitHub
GitHub - umutcamliyurt/PixelCloak: A tool that enhances privacy of pictures for Android
A tool that enhances privacy of pictures for Android - umutcamliyurt/PixelCloak
Looking for contributors: AWAS, an open standard for AI-readable web actions
Hey all, I’ve started an open-source spec called AWAS that lets AI browsers and agents interact with websites via a clean JSON action manifest. The idea is to allow existing websites to interact with AI agents and browsers without disturpting transitional browsing.
I’m looking for a few developers interested in AI agents, APIs, or web standards to help refine the spec, add examples, and test it on real sites.
Repo: https://github.com/TamTunnel/AWAS
I’d really appreciate feedback, issues, or small PRs from anyone building AI tools or modern web backends.
I am relatively due to open source so please be kind and forgiving !
https://redd.it/1pagy63
@r_opensource
Hey all, I’ve started an open-source spec called AWAS that lets AI browsers and agents interact with websites via a clean JSON action manifest. The idea is to allow existing websites to interact with AI agents and browsers without disturpting transitional browsing.
I’m looking for a few developers interested in AI agents, APIs, or web standards to help refine the spec, add examples, and test it on real sites.
Repo: https://github.com/TamTunnel/AWAS
I’d really appreciate feedback, issues, or small PRs from anyone building AI tools or modern web backends.
I am relatively due to open source so please be kind and forgiving !
https://redd.it/1pagy63
@r_opensource
GitHub
GitHub - TamTunnel/AWAS: Open-source standard for AI-readable web actions - enabling AI browsers to interact with websites efficiently
Open-source standard for AI-readable web actions - enabling AI browsers to interact with websites efficiently - TamTunnel/AWAS
Opensource licence, but limiting direct monetization
Hi,
I have an opensource gallery (pigallery2).
I'm currently using the standard github MIT licence: https://github.com/bpatrik/pigallery2/blob/master/LICENSE
I would like to keep the option that I can make money from it in the future by offering extra services around (eg.: bundling and shipping with hardware, SaaS, or premium features)
What is the best way to prepare this legally with the licence?
I was thinking that will add this cause to the license to prevent others building a direct business on my app (if a pro. photographer uses it to host photos is fine):
```
Commons Clause Restriction
The Software is provided to you by the Licensor under the MIT License,
subject to the following Commons Clause restriction:
You are prohibited from selling the Software. For the purposes of this
license, “selling” means practicing any or all of the rights granted to you
under the MIT License in exchange for a fee or other consideration, including
without limitation selling access to the Software, hosting or offering the
Software as a paid service, or selling derivative works of the Software.
This restriction does not limit your right to use the Software to operate
your own commercial or non-commercial services or websites. Only the original
author may sell or commercially license the Software itself.
```
https://redd.it/1pag0g7
@r_opensource
Hi,
I have an opensource gallery (pigallery2).
I'm currently using the standard github MIT licence: https://github.com/bpatrik/pigallery2/blob/master/LICENSE
I would like to keep the option that I can make money from it in the future by offering extra services around (eg.: bundling and shipping with hardware, SaaS, or premium features)
What is the best way to prepare this legally with the licence?
I was thinking that will add this cause to the license to prevent others building a direct business on my app (if a pro. photographer uses it to host photos is fine):
```
Commons Clause Restriction
The Software is provided to you by the Licensor under the MIT License,
subject to the following Commons Clause restriction:
You are prohibited from selling the Software. For the purposes of this
license, “selling” means practicing any or all of the rights granted to you
under the MIT License in exchange for a fee or other consideration, including
without limitation selling access to the Software, hosting or offering the
Software as a paid service, or selling derivative works of the Software.
This restriction does not limit your right to use the Software to operate
your own commercial or non-commercial services or websites. Only the original
author may sell or commercially license the Software itself.
```
https://redd.it/1pag0g7
@r_opensource
GitHub
pigallery2/LICENSE at master · bpatrik/pigallery2
A fast directory-first photo gallery website, with rich UI, optimized for running on low resource servers (especially on raspberry pi) - bpatrik/pigallery2
Personal email for opensource contribution
I would like to hear about your experiences with spam or any related issues, and whether you would recommend using a personal email address instead of a separate one. Additionally, I’m curious whether Outlook’s Safe Links feature has been beneficial for you (especially with an ad-free subnoscription) or if you believe it’s better to use Gmail instead.
https://redd.it/1pafw0o
@r_opensource
I would like to hear about your experiences with spam or any related issues, and whether you would recommend using a personal email address instead of a separate one. Additionally, I’m curious whether Outlook’s Safe Links feature has been beneficial for you (especially with an ad-free subnoscription) or if you believe it’s better to use Gmail instead.
https://redd.it/1pafw0o
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
I built this free yoga app, open to contributions!
https://simonschubert.github.io/YogaBase/
https://redd.it/1paknfe
@r_opensource
https://simonschubert.github.io/YogaBase/
https://redd.it/1paknfe
@r_opensource
simonschubert.github.io
YogaBase - Free Online Yoga Sessions and Pose Library
Access free yoga sessions for all skill levels from beginner to advanced. Explore our complete pose library with benefits and instructions.
Got way too tired of manually downloading every single PDF from Google Classroom, so I automated it
I built an open-source Python tool that uses the official Google Classroom API + Google Drive API to automatically download and sort all your course files.
GitHub: https://github.com/evanimenon/google-classroom-downloader
### Features
- Downloads every attachment from all courses (including active + archived)
- Converts Google Docs → PDF, Slides → PPTX, Sheets → XLSX
- Organizes files into clean per-course directories
- Skip-if-downloaded indexing (won’t re-download duplicates)
- 100% API-based (no scraping, no hacks)
If anyone wants to improve, optimize, or extend the code, PRs are very welcome.
https://redd.it/1pamft0
@r_opensource
I built an open-source Python tool that uses the official Google Classroom API + Google Drive API to automatically download and sort all your course files.
GitHub: https://github.com/evanimenon/google-classroom-downloader
### Features
- Downloads every attachment from all courses (including active + archived)
- Converts Google Docs → PDF, Slides → PPTX, Sheets → XLSX
- Organizes files into clean per-course directories
- Skip-if-downloaded indexing (won’t re-download duplicates)
- 100% API-based (no scraping, no hacks)
If anyone wants to improve, optimize, or extend the code, PRs are very welcome.
https://redd.it/1pamft0
@r_opensource
GitHub
GitHub - evanimenon/google-classroom-downloader: Google Classroom doesn’t let you bulk download files, so I wrote a tool that does…
Google Classroom doesn’t let you bulk download files, so I wrote a tool that does it for you. - evanimenon/google-classroom-downloader
stopslopware.net: a small resource for pushing back against the slopware projects polluting FOSS spaces
https://stopslopware.net
https://redd.it/1panpr9
@r_opensource
https://stopslopware.net
https://redd.it/1panpr9
@r_opensource
MacOS is painfully slow at realizing when you go offline or back online, so I built a small utility that reacts immediately to network changes
https://github.com/FI-153/QuickNetStats
https://redd.it/1paprte
@r_opensource
https://github.com/FI-153/QuickNetStats
https://redd.it/1paprte
@r_opensource
GitHub
GitHub - FI-153/QuickNetStats: A Menu Bar utility to display network informations to determine if the machine is connected to the…
A Menu Bar utility to display network informations to determine if the machine is connected to the internet and its IP addresses - FI-153/QuickNetStats
OpenRGB doesnt detect my keyboard
Im using Linux mint 22.2 Cinnamon. So i have a GIGABYTE Aorus K1 and it doesnt show up in the supported list. The proprietary software (RGB Fusion) is only made for Windows and i cant figure out how to run it in Linux either through Wine or Bottles. Does anyone know another software i could use or perhaps how to force OpenRGB to detect my keyboard?
https://redd.it/1papb20
@r_opensource
Im using Linux mint 22.2 Cinnamon. So i have a GIGABYTE Aorus K1 and it doesnt show up in the supported list. The proprietary software (RGB Fusion) is only made for Windows and i cant figure out how to run it in Linux either through Wine or Bottles. Does anyone know another software i could use or perhaps how to force OpenRGB to detect my keyboard?
https://redd.it/1papb20
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Sports Ad Muter chrome extension using ollama and qwen3-vl:2b
https://github.com/ethanwheatthin/Sports-Ad-Muter
https://redd.it/1paqun0
@r_opensource
https://github.com/ethanwheatthin/Sports-Ad-Muter
https://redd.it/1paqun0
@r_opensource
GitHub
GitHub - ethanwheatthin/Sports-Ad-Muter
Contribute to ethanwheatthin/Sports-Ad-Muter development by creating an account on GitHub.
My open source LaTeX Editor supports LuaLaTex and XeLaTeX now
https://github.com/octree-labs/octree
https://redd.it/1pauqp1
@r_opensource
https://github.com/octree-labs/octree
https://redd.it/1pauqp1
@r_opensource
GitHub
GitHub - octree-labs/octree: Octree - Open Source AI LaTeX Editor
Octree - Open Source AI LaTeX Editor. Contribute to octree-labs/octree development by creating an account on GitHub.
Audinspect: An audio inspector made for music producers, A&R teams, labels, reviewers, and people who want to quickly inspect music.
https://github.com/404oops/Audinspect
https://redd.it/1papig3
@r_opensource
https://github.com/404oops/Audinspect
https://redd.it/1papig3
@r_opensource
GitHub
GitHub - 404oops/Audinspect: An audio inspector. Made for quick viewing of audio files. Built with Electron + React and wavesurfer.js
An audio inspector. Made for quick viewing of audio files. Built with Electron + React and wavesurfer.js - 404oops/Audinspect
Convincing my employers to keep my libraries open-source
Hi all,
TL;DR: I created open-source libraries, joined a startup, and now they want to restrict the code. How can I keep them open-source?
I developed 2 open source libraries (BSD 3-clause) that are starting to get some traction and are recognized in the field (motion analysis for research, sports, medicine, animation, etc). They are not huge (500 and 170 stars, respectively), but they are cited, used, and growing. I've got a small Discord community (about 120 members), provide some active support, and spend time examining feature or pull requests. I'm thrilled that people are interested, but it is taking a lot of unpaid time.
At the end of a post-doc, one of my supervisors decided to create a start-up targeting professional sports teams and offered to hire me. I was pretty happy about it, since I negotiated that any changes to the preexisting libraries would remain open-source (and other work would not, of course). Now, I'm realizing 2 things:
The contract does not fully reflect our verbal agreement and states that all new work belongs to the company.
As I have significantly improved my tools over the last few months, they are starting to worry that competitors would copy my code for free.
So, I've got 2 questions:
1. On the one hand, I understand their point of view, but I'd like my "baby" to remain free and open-source. Can you help me find a win-win situation?
2. If we can't figure it out, how can I start making a living wage out of it? (For unrelated reasons like issues in hiring someone overseas, I might have to leave the company anyway)
\-----
Might be relevant to know:
I'm bad at marketing, I hate anything related to money, and I'm very bad at defending myself, especially verbally; however, I've got a family so I need some income. I feel like research suits me much better than the industry, but opportunities are rare and slow to be created.
I am French, and the company is British.
Here are some tentative ideas:
1. Create a private fork, and merge it to the public one after a few months.The cons are that it might add a lot of friction to the merge process, considering that it will have to go both ways since other people will propose pull requests to the public branch. It might also alienate some contributors.The libraries may lose some of its impact and momentum, especially in such a fast-paced field (yes, there is some AI involved).
2. I could introduce dual licensing, commercial for proprietary use.I'd rather not do it since it would block some current small users such as physical therapists or independent developers.
3. We could take the opposite stance, and use this involvement in the open-source world as a marketing tool. Being the official sponsor of a recognized open-source project can be a competitive advantage: the company can brag that the creator is part of the core team! I'm pretty confident that the risks of being copied would be overcome by the good press it would provide. We could even highlight that competitors are building up on our tools (and thus playing catch-up with us). Or to push it even further, we could offer paid consulting for companies using the libraries (like the RedHat OS: open code, with paid support).
Other arguments in favor of keeping the current license:
1. This would it make us eligible for some grants, such as EU Horizon 2020, NumFOCUS, Mozilla Open Source Support, and probably others...
2. The software programs we build are much more than the libraries I created: competitors won't have access to our team’s expertise, support ecosystem, computing facilities, to our ability to create a relevant user experience that answers specific needs, etc. Competition is on service, not code.
3. We need the community, which is pretty much like free labor: Blender is successful *because* it is open-source and able to follow the latest research advances. On a very concrete level, some features would have never existed without them. My libraries would have never been that robust if I did not have
Hi all,
TL;DR: I created open-source libraries, joined a startup, and now they want to restrict the code. How can I keep them open-source?
I developed 2 open source libraries (BSD 3-clause) that are starting to get some traction and are recognized in the field (motion analysis for research, sports, medicine, animation, etc). They are not huge (500 and 170 stars, respectively), but they are cited, used, and growing. I've got a small Discord community (about 120 members), provide some active support, and spend time examining feature or pull requests. I'm thrilled that people are interested, but it is taking a lot of unpaid time.
At the end of a post-doc, one of my supervisors decided to create a start-up targeting professional sports teams and offered to hire me. I was pretty happy about it, since I negotiated that any changes to the preexisting libraries would remain open-source (and other work would not, of course). Now, I'm realizing 2 things:
The contract does not fully reflect our verbal agreement and states that all new work belongs to the company.
As I have significantly improved my tools over the last few months, they are starting to worry that competitors would copy my code for free.
So, I've got 2 questions:
1. On the one hand, I understand their point of view, but I'd like my "baby" to remain free and open-source. Can you help me find a win-win situation?
2. If we can't figure it out, how can I start making a living wage out of it? (For unrelated reasons like issues in hiring someone overseas, I might have to leave the company anyway)
\-----
Might be relevant to know:
I'm bad at marketing, I hate anything related to money, and I'm very bad at defending myself, especially verbally; however, I've got a family so I need some income. I feel like research suits me much better than the industry, but opportunities are rare and slow to be created.
I am French, and the company is British.
Here are some tentative ideas:
1. Create a private fork, and merge it to the public one after a few months.The cons are that it might add a lot of friction to the merge process, considering that it will have to go both ways since other people will propose pull requests to the public branch. It might also alienate some contributors.The libraries may lose some of its impact and momentum, especially in such a fast-paced field (yes, there is some AI involved).
2. I could introduce dual licensing, commercial for proprietary use.I'd rather not do it since it would block some current small users such as physical therapists or independent developers.
3. We could take the opposite stance, and use this involvement in the open-source world as a marketing tool. Being the official sponsor of a recognized open-source project can be a competitive advantage: the company can brag that the creator is part of the core team! I'm pretty confident that the risks of being copied would be overcome by the good press it would provide. We could even highlight that competitors are building up on our tools (and thus playing catch-up with us). Or to push it even further, we could offer paid consulting for companies using the libraries (like the RedHat OS: open code, with paid support).
Other arguments in favor of keeping the current license:
1. This would it make us eligible for some grants, such as EU Horizon 2020, NumFOCUS, Mozilla Open Source Support, and probably others...
2. The software programs we build are much more than the libraries I created: competitors won't have access to our team’s expertise, support ecosystem, computing facilities, to our ability to create a relevant user experience that answers specific needs, etc. Competition is on service, not code.
3. We need the community, which is pretty much like free labor: Blender is successful *because* it is open-source and able to follow the latest research advances. On a very concrete level, some features would have never existed without them. My libraries would have never been that robust if I did not have
to fit the needs of other people in challenging contexts. More subtely, motivating debates, eye opening discussions, constant feedback, and collective scientitfic monitoring also made me a much more skilled and relevant person for the company.
4. The developement is already steered towards the company's needs. There are some very interesting pull requests that have been waiting, sometimes for almost a year. They would be useful for the community, but since I priorize me professional work, I don't immediately review or merge them.
And I am still in need for ideas of how to make this work profitable, even indirectly.
https://redd.it/1pay9y4
@r_opensource
4. The developement is already steered towards the company's needs. There are some very interesting pull requests that have been waiting, sometimes for almost a year. They would be useful for the community, but since I priorize me professional work, I don't immediately review or merge them.
And I am still in need for ideas of how to make this work profitable, even indirectly.
https://redd.it/1pay9y4
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
elf – A fast, modern Advent of Code helper CLI for Python
Hey folks,
I built a small open-source tool to make Advent of Code workflows smoother, and I’d love feedback from the open-source community.
elf is a Python CLI that:
- Fetches and caches your puzzle inputs
- Submits answers safely (no accidental dupes or invalid retries)
- Shows your private leaderboard
- Opens puzzle pages, tracks guesses, and more
- Built with Typer, httpx, Pydantic, Rich, and follows modern Python packaging best practices
I’ve used earlier versions of this for a few years and finally polished it into something I think others might find useful for the AoC season.
GitHub: https://github.com/cak/elf
PyPI: https://pypi.org/project/elf/
If you try it out, I’d love any feedback on the CLI UX, packaging, docs, or anything that feels rough. PRs and issues welcome.
Thanks!
https://redd.it/1pazpnj
@r_opensource
Hey folks,
I built a small open-source tool to make Advent of Code workflows smoother, and I’d love feedback from the open-source community.
elf is a Python CLI that:
- Fetches and caches your puzzle inputs
- Submits answers safely (no accidental dupes or invalid retries)
- Shows your private leaderboard
- Opens puzzle pages, tracks guesses, and more
- Built with Typer, httpx, Pydantic, Rich, and follows modern Python packaging best practices
I’ve used earlier versions of this for a few years and finally polished it into something I think others might find useful for the AoC season.
GitHub: https://github.com/cak/elf
PyPI: https://pypi.org/project/elf/
If you try it out, I’d love any feedback on the CLI UX, packaging, docs, or anything that feels rough. PRs and issues welcome.
Thanks!
https://redd.it/1pazpnj
@r_opensource
GitHub
GitHub - cak/elf: A modern Advent of Code helper that fetches inputs, submits answers, and tracks your progress.
A modern Advent of Code helper that fetches inputs, submits answers, and tracks your progress. - cak/elf
user-scanner a CLI tool written on python that lets you choose unique username in all popular sites, by checking the username availability, actively looking for contributions⚡
https://github.com/kaifcodec/user-scanner
https://redd.it/1pb1988
@r_opensource
https://github.com/kaifcodec/user-scanner
https://redd.it/1pb1988
@r_opensource
GitHub
GitHub - kaifcodec/user-scanner: 🕵️ (2-in-1) Emaill and Username OSINT tool that analyzes username and email presence across…
🕵️ (2-in-1) Emaill and Username OSINT tool that analyzes username and email presence across multiple platforms, intended for security research, investigations, legitimate analysis - kaifcodec/use...
Unipac - Universal package manager for Linux - looking for feedback and ideas
Hey opensource subreddit!
I'm in the early design phase of a new open-source project called Unipac (Universal Package Manager) and would love to get feedback from the community before diving deep into implementation.
# The Problem I'm Trying to Solve
Linux package management is fragmented. We have distro-specific package managers (apt, pacman, dnf), language-specific ones (pip, npm, cargo, gem), and each creates its own silo. When you need Python packages, Node modules, and system libraries together, you're juggling multiple tools. Add to that the single-version constraint most package managers enforce, and you end up with version conflicts that force you into containers or language-specific virtual environments.
# What Unipac Aims to Do
Unipac is designed to provide unified package and environment management with these key features:
Universal interface \- Install from any package manager through one tool.
Multi-version support \- Multiple versions of the same package can coexist. Different applications can use different versions without conflicts through consumer-based routing.
Lightweight isolation \- Environment isolation without container overhead. Uses symlinks and filesystem redirection rather than duplicating entire OS images.
Reproducible environments \- Git-like snapshots of environments that can be shared and restored exactly.
Cross-distribution \- Use packages from any distro on any distro (within reason - binaries are fundamentally compatible, just paths differ). We use Kotlin DSL to provide new package managers, everything is customizable via plugins.
Environments (called "universes") are defined in a Kotlin DSL similar to Gradle, making them code that can be versioned and shared.
# Current Status
Unipac on GitHub : Very early - still in architecture and design phase. Not much code yet, just exploring whether this approach makes sense and what features would actually be useful. I'm just working on the DSL because that's where pacakge manager are being connected. later on I'll jump onto the core logics in C++.
# Questions for the Community
1. Does this problem resonate with you? Do you currently struggle with package management fragmentation or version conflicts?
2. What features would be most valuable? What would make this worth switching from your current workflow?
3. What am I missing? Are there edge cases or requirements I haven't thought about?
4. Similar projects? I know about Nix, Conda, Spack, containers, etc. What makes them insufficient for your use cases?
5. Would you actually use this? Being honest - if this existed and worked well, would you adopt it, or is your current solution good enough?
# Technical Approach
The core insight is that Linux binaries and libraries are fundamentally compatible across distros - differences are mostly in file paths and package metadata formats. Unipac acts as a translation layer, downloading packages from existing package managers, storing them in a unified repository, and using symlinks to create isolated environments. Consumer-based routing ensures the right versions reach the right applications.
Stack will be C++ (performance-critical parts) and Kotlin (DSL, higher-level logic). **MAYBE a GUI later on as well**
# Not Looking For
I'm not trying to advertise or promote this - there's nothing to use yet. Just want to validate the concept and gather ideas from people who deal with these problems daily.
Thoughts? Criticisms? Feature suggestions? Areas I should research more?
https://redd.it/1pb75cu
@r_opensource
Hey opensource subreddit!
I'm in the early design phase of a new open-source project called Unipac (Universal Package Manager) and would love to get feedback from the community before diving deep into implementation.
# The Problem I'm Trying to Solve
Linux package management is fragmented. We have distro-specific package managers (apt, pacman, dnf), language-specific ones (pip, npm, cargo, gem), and each creates its own silo. When you need Python packages, Node modules, and system libraries together, you're juggling multiple tools. Add to that the single-version constraint most package managers enforce, and you end up with version conflicts that force you into containers or language-specific virtual environments.
# What Unipac Aims to Do
Unipac is designed to provide unified package and environment management with these key features:
Universal interface \- Install from any package manager through one tool.
unipac get pip::numpy:1.24, unipac get apt::python:3.11, etc.Multi-version support \- Multiple versions of the same package can coexist. Different applications can use different versions without conflicts through consumer-based routing.
Lightweight isolation \- Environment isolation without container overhead. Uses symlinks and filesystem redirection rather than duplicating entire OS images.
Reproducible environments \- Git-like snapshots of environments that can be shared and restored exactly.
Cross-distribution \- Use packages from any distro on any distro (within reason - binaries are fundamentally compatible, just paths differ). We use Kotlin DSL to provide new package managers, everything is customizable via plugins.
Environments (called "universes") are defined in a Kotlin DSL similar to Gradle, making them code that can be versioned and shared.
# Current Status
Unipac on GitHub : Very early - still in architecture and design phase. Not much code yet, just exploring whether this approach makes sense and what features would actually be useful. I'm just working on the DSL because that's where pacakge manager are being connected. later on I'll jump onto the core logics in C++.
# Questions for the Community
1. Does this problem resonate with you? Do you currently struggle with package management fragmentation or version conflicts?
2. What features would be most valuable? What would make this worth switching from your current workflow?
3. What am I missing? Are there edge cases or requirements I haven't thought about?
4. Similar projects? I know about Nix, Conda, Spack, containers, etc. What makes them insufficient for your use cases?
5. Would you actually use this? Being honest - if this existed and worked well, would you adopt it, or is your current solution good enough?
# Technical Approach
The core insight is that Linux binaries and libraries are fundamentally compatible across distros - differences are mostly in file paths and package metadata formats. Unipac acts as a translation layer, downloading packages from existing package managers, storing them in a unified repository, and using symlinks to create isolated environments. Consumer-based routing ensures the right versions reach the right applications.
Stack will be C++ (performance-critical parts) and Kotlin (DSL, higher-level logic). **MAYBE a GUI later on as well**
# Not Looking For
I'm not trying to advertise or promote this - there's nothing to use yet. Just want to validate the concept and gather ideas from people who deal with these problems daily.
Thoughts? Criticisms? Feature suggestions? Areas I should research more?
https://redd.it/1pb75cu
@r_opensource
GitHub
GitHub - thisismeamir/unipac: lightweight multi-distro package and environment manager for linux ecosystem.
lightweight multi-distro package and environment manager for linux ecosystem. - thisismeamir/unipac
I made a feedback tool that boost conversion rate
https://www.npmjs.com/package/react-roast
https://redd.it/1pb9ma6
@r_opensource
https://www.npmjs.com/package/react-roast
https://redd.it/1pb9ma6
@r_opensource