slop - minimalistic display manager (replacement for login)
Hi everyone,
Recently, I decided to ditch the GUI display manager in favor of the TTY login. However, I was unable to configure the login program the way I wanted so I've decided to build my own.
Introducing [slop](https://github.com/spevnev/slop) \- Simple Login Program.
It is a replacement for getty and login designed to be minimalistic and simple.
Unlike login, which prints a bunch of extra info (date, issue, hostname, motd, etc.), it only displays what is needed for authentication (i.e. prompts from the PAM modules).
Also, it doesn't print an empty line before the prompt like [agetty does](https://github.com/util-linux/util-linux/blob/db0efab5c3e13794ae79fcb3db8371e3af510169/term-utils/agetty.c#L1831).
Features:
* Focus the TTY
* Set command to run on successful login, e.g. `startx`, or a wayland compositor.
* Clear screen after failed attempt
* Set noscript above the prompt
* Predefine a username
Hope this helps someone who wants a simple TTY login.
https://redd.it/1o3f9uw
@r_opensource
Hi everyone,
Recently, I decided to ditch the GUI display manager in favor of the TTY login. However, I was unable to configure the login program the way I wanted so I've decided to build my own.
Introducing [slop](https://github.com/spevnev/slop) \- Simple Login Program.
It is a replacement for getty and login designed to be minimalistic and simple.
Unlike login, which prints a bunch of extra info (date, issue, hostname, motd, etc.), it only displays what is needed for authentication (i.e. prompts from the PAM modules).
Also, it doesn't print an empty line before the prompt like [agetty does](https://github.com/util-linux/util-linux/blob/db0efab5c3e13794ae79fcb3db8371e3af510169/term-utils/agetty.c#L1831).
Features:
* Focus the TTY
* Set command to run on successful login, e.g. `startx`, or a wayland compositor.
* Clear screen after failed attempt
* Set noscript above the prompt
* Predefine a username
Hope this helps someone who wants a simple TTY login.
https://redd.it/1o3f9uw
@r_opensource
GitHub
GitHub - spevnev/slop: Simple replacement for getty and login with additional features.
Simple replacement for getty and login with additional features. - spevnev/slop
Treat files as individual repositories with qwe
Hi everyone!
I'm stoked to finally release Qwe, a side project that I've been hacking at for the past few weeks.
The Problem Qwe Solves
We all adore Git, but occasionally its project-level tracking can be overkill. Did you ever attempt to revert a single stand-alone config file or a single Python noscript without bothering the rest of the project? Sure, you can do this, but usually, it requires you to use convoluted commands such as git checkout $COMMITHASH -- $FILEPATH and can be needlessly cumbersome.
I created Qwe to make this easier by centering the file as the main unit of version control.
What is Qwe?
Qwe is a Version Control System (VCS) in which you can commit, monitor, and revert files separately with ease.
It's ideal for:
Software developers working with many standalone utility noscripts, configuration noscripts, or build noscripts.
Writers/Documentation Teams versioning Markdown or other text files where each file is a self-contained, independent whole.
Anyone who prefers a more straightforward, file-oriented method of saving history.
Key Features & How It Works
Individual Tracking: Each file is treated as an independent little repository. You don't commit the "project"; you commit the "file."
Simple Reversion: If you break one noscript, you can revert only that noscript to a former state without generating conflicts and touching any other files within your directory.
Built for Speed: Qwe is entirely Golang (GO) written, which keeps the underlying operations efficient and quick. It's compiled to one, static binary.
Try it Out!
I'm a programmer, not a designer, so it's presently a CLI tool, but it's fully working! I'd appreciate it if the community would give it a try and let me have some feedback on the workflow, command layout, and any bugs you discover.
Repo/Download Link: https://github.com/mainak55512/qwe
https://redd.it/1o3lgwv
@r_opensource
Hi everyone!
I'm stoked to finally release Qwe, a side project that I've been hacking at for the past few weeks.
The Problem Qwe Solves
We all adore Git, but occasionally its project-level tracking can be overkill. Did you ever attempt to revert a single stand-alone config file or a single Python noscript without bothering the rest of the project? Sure, you can do this, but usually, it requires you to use convoluted commands such as git checkout $COMMITHASH -- $FILEPATH and can be needlessly cumbersome.
I created Qwe to make this easier by centering the file as the main unit of version control.
What is Qwe?
Qwe is a Version Control System (VCS) in which you can commit, monitor, and revert files separately with ease.
It's ideal for:
Software developers working with many standalone utility noscripts, configuration noscripts, or build noscripts.
Writers/Documentation Teams versioning Markdown or other text files where each file is a self-contained, independent whole.
Anyone who prefers a more straightforward, file-oriented method of saving history.
Key Features & How It Works
Individual Tracking: Each file is treated as an independent little repository. You don't commit the "project"; you commit the "file."
Simple Reversion: If you break one noscript, you can revert only that noscript to a former state without generating conflicts and touching any other files within your directory.
Built for Speed: Qwe is entirely Golang (GO) written, which keeps the underlying operations efficient and quick. It's compiled to one, static binary.
Try it Out!
I'm a programmer, not a designer, so it's presently a CLI tool, but it's fully working! I'd appreciate it if the community would give it a try and let me have some feedback on the workflow, command layout, and any bugs you discover.
Repo/Download Link: https://github.com/mainak55512/qwe
https://redd.it/1o3lgwv
@r_opensource
GitHub
GitHub - mainak55512/qwe: A simple file-first atomic version control system
A simple file-first atomic version control system. Contribute to mainak55512/qwe development by creating an account on GitHub.
Exploring Vector Databases - Why opensource Cosdata OSS worked for me !
I’ve been exploring different vector databases lately for one of my projects - looking for something that’s fast, efficient, and cost-friendly to set up.
After digging into platforms like Cosdata, Qdrant, Weaviate, and Elasticsearch, I came across this performance comparison .
* Industry-leading 1758+ QPS on 1M record datasets with 1536-dimensional vectors
* 42% faster than Qdrant
* 54% faster than Weaviate
* 146% faster than Elastic Search
* Consistent 97% precision across challenging search tasks
Significantly faster indexing than Elastic Search while maintaining superior query performance.
Cosdata really caught my attention -especially because they offer an open-source edition (Cosdata OSS) that’s easy to experiment with for personal or production projects.
Recently, I joined their community, and it’s been great connecting with other developers who are building and experimenting with retrieval and AI-native systems.
If you’re working on projects involving semantic search, RAG, or retrieval systems, definitely worth checking it out. let me know if you want to join .
https://redd.it/1o3nkn8
@r_opensource
I’ve been exploring different vector databases lately for one of my projects - looking for something that’s fast, efficient, and cost-friendly to set up.
After digging into platforms like Cosdata, Qdrant, Weaviate, and Elasticsearch, I came across this performance comparison .
* Industry-leading 1758+ QPS on 1M record datasets with 1536-dimensional vectors
* 42% faster than Qdrant
* 54% faster than Weaviate
* 146% faster than Elastic Search
* Consistent 97% precision across challenging search tasks
Significantly faster indexing than Elastic Search while maintaining superior query performance.
Cosdata really caught my attention -especially because they offer an open-source edition (Cosdata OSS) that’s easy to experiment with for personal or production projects.
Recently, I joined their community, and it’s been great connecting with other developers who are building and experimenting with retrieval and AI-native systems.
If you’re working on projects involving semantic search, RAG, or retrieval systems, definitely worth checking it out. let me know if you want to join .
https://redd.it/1o3nkn8
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Markon • Minimal Distraction‑free Markdown editor
https://metaory.github.io/markon
https://redd.it/1o3thxj
@r_opensource
https://metaory.github.io/markon
https://redd.it/1o3thxj
@r_opensource
metaory.github.io
markon
Minimal distraction free local markdown live editor
I found a cool discord alternative
So I used to use revolt but they had to rebrand and their phone app got fucked because of it but I found a platform called nerimity that's pretty cool (nerimity.com)
Made a server too if anyone wanted to join it https://nerimity.com/i/XhwTD
https://redd.it/1o3un8g
@r_opensource
So I used to use revolt but they had to rebrand and their phone app got fucked because of it but I found a platform called nerimity that's pretty cool (nerimity.com)
Made a server too if anyone wanted to join it https://nerimity.com/i/XhwTD
https://redd.it/1o3un8g
@r_opensource
Nerimity
ℕ𝕖𝕨 𝔼𝕕𝕖𝕟 🌿 Server on Nerimity
You are invited to join the ℕ𝕖𝕨 𝔼𝕕𝕖𝕟 🌿 server on Nerimity.
Show & Tell GroundCrew — weekend build: a multi-agent fact-checker (LangGraph + GPT-4o) hitting 72% on a FEVER slice
TL;DR: I spent the weekend building GroundCrew, an automated fact-checking pipeline. It takes any text → extracts claims → searches the web/Wikipedia → verifies and reports with confidence + evidence. On a 100-sample FEVER slice it got 71–72% overall, with strong SUPPORTS/REFUTES but struggles on NOT ENOUGH INFO. Repo + evals below — would love feedback on NEI detection & contradiction handling.
# Why this might be interesting
It’s a clean, typed LangGraph pipeline (agents with Pydantic I/O) you can read in one sitting.
Includes a mini evaluation harness (FEVER subset) and a simple ablation (web vs. Wikipedia-only).
Shows where LLMs still over-claim and how guardrails + structure help (but don’t fully fix) NEI.
# What it does (end-to-end)
1. Claim Extraction → pulls out factual statements from input text
2. Evidence Search → Tavily (web) or Wikipedia mode
3. Verification → compares claim ↔ evidence, assigns SUPPORTS / REFUTES / NEI \+ confidence
4. Reporting → Markdown/JSON report with per-claim rationale and evidence snippets
>All agents use structured outputs (Pydantic), so you get consistent types throughout the graph.
# Architecture (LangGraph)
Sequential 4-stage graph (Extraction → Search → Verify → Report)
Type-safe nodes with explicit schemas (less prompt-glue, fewer “stringly-typed” bugs)
Quality presets (model/temp/tools) you can toggle per run
Batch mode with parallel workers for quick evals
# Results (FEVER, 100 samples; GPT-4o)
|Configuration|Overall|SUPPORTS|REFUTES|NEI|
|:-|:-|:-|:-|:-|
|Web Search|71%|88%|82%|42%|
|Wikipedia-only|72%|91%|88%|36%|
Context: specialized FEVER systems are \~85–90%+. For a weekend LLM-centric pipeline, \~72% feels like a decent baseline — but NEI is clearly the weak spot.
# Where it breaks (and why)
NEI (not enough info): The model infers from partial evidence instead of abstaining. Teaching it to say “I don’t know (yet)” is harder than SUPPORTS/REFUTES.
Evidence specificity: e.g., claim says “founded by two men,” evidence lists two names but never states “two.” The verifier counts names and declares SUPPORTS — technically wrong under FEVER guidelines.
Contradiction edges: Subtle temporal qualifiers (“as of 2019…”) or entity disambiguation (same name, different entity) still trip it up.
# Repo & docs
Code: [https://github.com/tsensei/GroundCrew](https://github.com/tsensei/GroundCrew)
Evals:
Wiki: Getting Started / Usage / Architecture / API Reference / Examples / Troubleshooting
License: MIT
# Specific feedback I’m looking for
1. NEI handling: best practices you’ve used to make abstention stick (prompting, routing, NLI filters, thresholding)?
2. Contradiction detection: lightweight ways to catch “close but not entailed” evidence without a huge reranker stack.
3. Eval design: additions you’d want to see to trust this style of system (more slices? harder subsets? human-in-the-loop checks?).
https://redd.it/1o3sqan
@r_opensource
TL;DR: I spent the weekend building GroundCrew, an automated fact-checking pipeline. It takes any text → extracts claims → searches the web/Wikipedia → verifies and reports with confidence + evidence. On a 100-sample FEVER slice it got 71–72% overall, with strong SUPPORTS/REFUTES but struggles on NOT ENOUGH INFO. Repo + evals below — would love feedback on NEI detection & contradiction handling.
# Why this might be interesting
It’s a clean, typed LangGraph pipeline (agents with Pydantic I/O) you can read in one sitting.
Includes a mini evaluation harness (FEVER subset) and a simple ablation (web vs. Wikipedia-only).
Shows where LLMs still over-claim and how guardrails + structure help (but don’t fully fix) NEI.
# What it does (end-to-end)
1. Claim Extraction → pulls out factual statements from input text
2. Evidence Search → Tavily (web) or Wikipedia mode
3. Verification → compares claim ↔ evidence, assigns SUPPORTS / REFUTES / NEI \+ confidence
4. Reporting → Markdown/JSON report with per-claim rationale and evidence snippets
>All agents use structured outputs (Pydantic), so you get consistent types throughout the graph.
# Architecture (LangGraph)
Sequential 4-stage graph (Extraction → Search → Verify → Report)
Type-safe nodes with explicit schemas (less prompt-glue, fewer “stringly-typed” bugs)
Quality presets (model/temp/tools) you can toggle per run
Batch mode with parallel workers for quick evals
# Results (FEVER, 100 samples; GPT-4o)
|Configuration|Overall|SUPPORTS|REFUTES|NEI|
|:-|:-|:-|:-|:-|
|Web Search|71%|88%|82%|42%|
|Wikipedia-only|72%|91%|88%|36%|
Context: specialized FEVER systems are \~85–90%+. For a weekend LLM-centric pipeline, \~72% feels like a decent baseline — but NEI is clearly the weak spot.
# Where it breaks (and why)
NEI (not enough info): The model infers from partial evidence instead of abstaining. Teaching it to say “I don’t know (yet)” is harder than SUPPORTS/REFUTES.
Evidence specificity: e.g., claim says “founded by two men,” evidence lists two names but never states “two.” The verifier counts names and declares SUPPORTS — technically wrong under FEVER guidelines.
Contradiction edges: Subtle temporal qualifiers (“as of 2019…”) or entity disambiguation (same name, different entity) still trip it up.
# Repo & docs
Code: [https://github.com/tsensei/GroundCrew](https://github.com/tsensei/GroundCrew)
Evals:
evals/ has noscripts + notes (FEVER slice + config toggles)Wiki: Getting Started / Usage / Architecture / API Reference / Examples / Troubleshooting
License: MIT
# Specific feedback I’m looking for
1. NEI handling: best practices you’ve used to make abstention stick (prompting, routing, NLI filters, thresholding)?
2. Contradiction detection: lightweight ways to catch “close but not entailed” evidence without a huge reranker stack.
3. Eval design: additions you’d want to see to trust this style of system (more slices? harder subsets? human-in-the-loop checks?).
https://redd.it/1o3sqan
@r_opensource
GitHub
GitHub - tsensei/GroundCrew: A team of agents that “ground” claims in sources
A team of agents that “ground” claims in sources. Contribute to tsensei/GroundCrew development by creating an account on GitHub.
GitHub - antoniorodr/Cronboard: A terminal-based dashboard for managing cron jobs.
https://github.com/antoniorodr/Cronboard
https://redd.it/1o3vkhd
@r_opensource
https://github.com/antoniorodr/Cronboard
https://redd.it/1o3vkhd
@r_opensource
GitHub
GitHub - antoniorodr/cronboard: A terminal-based dashboard for managing cron jobs locally and on servers.
A terminal-based dashboard for managing cron jobs locally and on servers. - antoniorodr/cronboard
Spend Less Time Searching, More Time Contributing — GitHub Issue Alerts for open source beginners
Hi everyone,
I recently built a small project aimed at solving one of the biggest problems beginners face when trying to get into open source: finding relevant issues before they are taken.
The problem: Beginners often spend hours searching for suitable issues on GitHub. By the time they find one, it is either too advanced, already assigned, or lacks the beginner friendly labels. This creates unnecessary friction and discourages many from contributing.
The solution I tried: I created a simple tool that monitors any public repositories you choose and notifies you via email or Telegram when a new issue appears that matches your chosen labels. For example, you can track labels like "good first issue" or "frontend" across multiple repositories. The setup is straightforward and can be done within minutes.
Why I think this matters: It saves beginners from wasting time on endless searching, lets them catch issues early, and makes the whole process of contributing less intimidating. It is designed to be minimal and intuitive, without requiring users to manage complex infrastructure or paid services.
Right now this is an MVP. It works, but I want to refine it further. I am looking for:
* Feedback on whether this solves a real pain point for you.
* Suggestions for improvements or additional features that would make it more valuable.
* Thoughts on how this can better serve both contributors and maintainers.
If you have a few minutes, I would really appreciate your insights. Thanks.
[Github Repo](https://github.com/Phoenix1531/IssuePing)
https://redd.it/1o3vhth
@r_opensource
Hi everyone,
I recently built a small project aimed at solving one of the biggest problems beginners face when trying to get into open source: finding relevant issues before they are taken.
The problem: Beginners often spend hours searching for suitable issues on GitHub. By the time they find one, it is either too advanced, already assigned, or lacks the beginner friendly labels. This creates unnecessary friction and discourages many from contributing.
The solution I tried: I created a simple tool that monitors any public repositories you choose and notifies you via email or Telegram when a new issue appears that matches your chosen labels. For example, you can track labels like "good first issue" or "frontend" across multiple repositories. The setup is straightforward and can be done within minutes.
Why I think this matters: It saves beginners from wasting time on endless searching, lets them catch issues early, and makes the whole process of contributing less intimidating. It is designed to be minimal and intuitive, without requiring users to manage complex infrastructure or paid services.
Right now this is an MVP. It works, but I want to refine it further. I am looking for:
* Feedback on whether this solves a real pain point for you.
* Suggestions for improvements or additional features that would make it more valuable.
* Thoughts on how this can better serve both contributors and maintainers.
If you have a few minutes, I would really appreciate your insights. Thanks.
[Github Repo](https://github.com/Phoenix1531/IssuePing)
https://redd.it/1o3vhth
@r_opensource
GitHub
GitHub - Phoenix1531/IssuePing: A simple & powerful tool to help beginner and experienced developers contribute to open source…
A simple & powerful tool to help beginner and experienced developers contribute to open source without wasting hours searching for issues. - Phoenix1531/IssuePing
My group is creating a website that lets you track your reading, chat with people, and unlock achievements based on your progress!
https://github.com/GRead-Development/GRead
https://redd.it/1o4a4l0
@r_opensource
https://github.com/GRead-Development/GRead
https://redd.it/1o4a4l0
@r_opensource
GitHub
GitHub - GRead-Development/GRead: Connect with other readers, discuss books, and earn points!
Connect with other readers, discuss books, and earn points! - GRead-Development/GRead
OSHPark like service for silicon coming soon. This was a cool talk from the guy starting it.
https://www.youtube.com/watch?v=0nqV9Eo17wA
https://redd.it/1o4bu8f
@r_opensource
https://www.youtube.com/watch?v=0nqV9Eo17wA
https://redd.it/1o4bu8f
@r_opensource
YouTube
Open source silicon and wafer.space - $7k for 1,000 custom ICs - Hackware Oct 2025
Speaker: Tim Ansel
Event Page: https://www.facebook.com/events/759331036899554
Produced by Engineers.SG
Event Page: https://www.facebook.com/events/759331036899554
Produced by Engineers.SG
We built open-source infrastructure for autonomous computer using llm agents at scale
https://github.com/LLmHub-dev/open-computer-use
https://redd.it/1o4fdax
@r_opensource
https://github.com/LLmHub-dev/open-computer-use
https://redd.it/1o4fdax
@r_opensource
GitHub
GitHub - LLmHub-dev/open-computer-use: The Open Framework for autonomous virtual computer agents at scale, fully open-source, safe…
The Open Framework for autonomous virtual computer agents at scale, fully open-source, safe, auditable, and production-ready. - LLmHub-dev/open-computer-use
I was tired of the "first 20 DMs" chaos, so I built and open-sourced a serverless giveaway tool on Cloudflare's free tier.
https://github.com/promocodequeue/promo-code-queue-hobby
https://redd.it/1o4gm7c
@r_opensource
https://github.com/promocodequeue/promo-code-queue-hobby
https://redd.it/1o4gm7c
@r_opensource
GitHub
GitHub - promocodequeue/promo-code-queue-hobby
Contribute to promocodequeue/promo-code-queue-hobby development by creating an account on GitHub.
Seeking Inspiration: What's a missing open-source tool you'd love to see built?
I'm a developer with some free time and a strong desire to give back to the open-source world. Rather than starting a project based solely on my own needs, I'd love to build something that addresses a genuine need for others.
So, I'm turning to you—the people who live and breathe open-source.
What is a piece of software that you feel is missing from the open-source ecosystem?
I'm casting a wide net. The idea can be related to any domain:
· Developer Tools: A better CLI, a VS Code extension, a testing utility, a new library for a common problem.
· Desktop Applications: A simple, cross-platform note-taking app, a personal finance manager, a dedicated media player.
· Web Apps & Utilities: A privacy-focused alternative to a popular SaaS tool, a self-hostable service dashboard, a specialized content management system.
· System/DevOps: A configuration management tool, a backup solution, a network utility.
The key is that it should be focused and actionable. I'm not building the next Linux kernel, but I am willing to build a robust, well-maintained tool that solves a specific problem well.
Please describe your idea with as much detail as you can. If your idea is the one I choose to build, I will open-source it from day one and gladly credit you for the inspiration.
I'm excited to see what problems you want solved. Thanks for your creativity!
https://redd.it/1o4gqcx
@r_opensource
I'm a developer with some free time and a strong desire to give back to the open-source world. Rather than starting a project based solely on my own needs, I'd love to build something that addresses a genuine need for others.
So, I'm turning to you—the people who live and breathe open-source.
What is a piece of software that you feel is missing from the open-source ecosystem?
I'm casting a wide net. The idea can be related to any domain:
· Developer Tools: A better CLI, a VS Code extension, a testing utility, a new library for a common problem.
· Desktop Applications: A simple, cross-platform note-taking app, a personal finance manager, a dedicated media player.
· Web Apps & Utilities: A privacy-focused alternative to a popular SaaS tool, a self-hostable service dashboard, a specialized content management system.
· System/DevOps: A configuration management tool, a backup solution, a network utility.
The key is that it should be focused and actionable. I'm not building the next Linux kernel, but I am willing to build a robust, well-maintained tool that solves a specific problem well.
Please describe your idea with as much detail as you can. If your idea is the one I choose to build, I will open-source it from day one and gladly credit you for the inspiration.
I'm excited to see what problems you want solved. Thanks for your creativity!
https://redd.it/1o4gqcx
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Muscle memory or my body as a user
I use a lot of hotkeys. And one of them — fast translate. I select any text in Dutch or Spanish, press the hotkeys on my keyboard, and then read the translation in English on the Google Translate webpage.
My brain and body are familiar with this pattern, so I don't think about it — my hands use this flow through muscle memory.
Yesterday, my hands automatically selected long text in English without paragraphs and pressed the hotkeys. Then I got stuck for a few seconds. The text is already in English, what happened?
Looks like the animal part of my brain uses these hotkeys differently. This is not a translation. This is a way to "make text easy to understand". Long text in English without paragraph breaks is too complicated, and my brain needs "translation" from this format.
Should we create a product based on this via AI/LLM? A tiny number of people use hotkeys at all. Even fewer people use them this way. Almost all people who use these patterns can code and will expect an open-source version, which is hard to earn on.
But it's interesting how my pattern "translate text" was actually "make text easy" all the time.
https://redd.it/1o4hmbt
@r_opensource
I use a lot of hotkeys. And one of them — fast translate. I select any text in Dutch or Spanish, press the hotkeys on my keyboard, and then read the translation in English on the Google Translate webpage.
My brain and body are familiar with this pattern, so I don't think about it — my hands use this flow through muscle memory.
Yesterday, my hands automatically selected long text in English without paragraphs and pressed the hotkeys. Then I got stuck for a few seconds. The text is already in English, what happened?
Looks like the animal part of my brain uses these hotkeys differently. This is not a translation. This is a way to "make text easy to understand". Long text in English without paragraph breaks is too complicated, and my brain needs "translation" from this format.
Should we create a product based on this via AI/LLM? A tiny number of people use hotkeys at all. Even fewer people use them this way. Almost all people who use these patterns can code and will expect an open-source version, which is hard to earn on.
But it's interesting how my pattern "translate text" was actually "make text easy" all the time.
https://redd.it/1o4hmbt
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Hey vibe engineers, A good Video Editor maybe?
Since Capcut isn't free and davinci needs 16gb ram what can i use for editing with capcut features.
can a vibe engineer opensource one?
https://redd.it/1o4kg91
@r_opensource
Since Capcut isn't free and davinci needs 16gb ram what can i use for editing with capcut features.
can a vibe engineer opensource one?
https://redd.it/1o4kg91
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Invio - Self-hosted invoicing without the bloat. | V1.0.0 Release
Hey r/opensource , today I’m excited to share the v1 of Invio 🎉
Invio is invoicing software that is designed to do one thing and one thing only - make invoices. I made Invio because I wanted to make some invoices but all the open source selfhosted solutions I could personnaly find where too heavy for my use case, so I made my own.
Why Invio might be for you:
You dislike the feature bloat of alternatives
You want to get your invoices out there quickly
You prefer a modern tech stack
And here is why Invio might NOT be for you:
You need more advanced features like CRM, project management
You have many employees
Here are the biggest chances since the last post I made:
Switched to puppeteer for PDF rendering instead of wkhtmltopdf
Proper tax handling
XML exports
XML embedding in PDF
Darkmode
Custom invoice numbering patterns
Improved custom templates
About the AI usage, I want to clarify this better then last time. AI was used during the development of this application, mostly to speed up the development proces, the app is however not vibe coded. Features are planned intentionally by me, code is sufficiently optimized (as far as I am concerned). I am open to have a discussion about ai usage in coding.
Repo: https://github.com/kittendevv/Invio
Site: https://invio.dev/
Docs: https://github.com/kittendevv/Invio/wiki
https://redd.it/1o4m6w9
@r_opensource
Hey r/opensource , today I’m excited to share the v1 of Invio 🎉
Invio is invoicing software that is designed to do one thing and one thing only - make invoices. I made Invio because I wanted to make some invoices but all the open source selfhosted solutions I could personnaly find where too heavy for my use case, so I made my own.
Why Invio might be for you:
You dislike the feature bloat of alternatives
You want to get your invoices out there quickly
You prefer a modern tech stack
And here is why Invio might NOT be for you:
You need more advanced features like CRM, project management
You have many employees
Here are the biggest chances since the last post I made:
Switched to puppeteer for PDF rendering instead of wkhtmltopdf
Proper tax handling
XML exports
XML embedding in PDF
Darkmode
Custom invoice numbering patterns
Improved custom templates
About the AI usage, I want to clarify this better then last time. AI was used during the development of this application, mostly to speed up the development proces, the app is however not vibe coded. Features are planned intentionally by me, code is sufficiently optimized (as far as I am concerned). I am open to have a discussion about ai usage in coding.
Repo: https://github.com/kittendevv/Invio
Site: https://invio.dev/
Docs: https://github.com/kittendevv/Invio/wiki
https://redd.it/1o4m6w9
@r_opensource
GitHub
GitHub - kittendevv/Invio: Self-hosted invoicing without the bloat.
Self-hosted invoicing without the bloat. Contribute to kittendevv/Invio development by creating an account on GitHub.
jws-server: 🧪 Mock websocket servers using json
https://github.com/AshnaWiar/jws-server
https://redd.it/1o4ps6m
@r_opensource
https://github.com/AshnaWiar/jws-server
https://redd.it/1o4ps6m
@r_opensource
GitHub
GitHub - AshnaWiar/jws-server: 🧪 Mock websocket servers using json
🧪 Mock websocket servers using json. Contribute to AshnaWiar/jws-server development by creating an account on GitHub.
What's an open-source tool you discovered and now can't live without?
Hey everyone, what’s one open-source tool you stumbled on that ended up being way more useful than you expected?
Could be for coding, AI/ML, writing, research, replacing Google, whatever helped you out big time but you don't hear people talk about much.
I use almost daily: Tuta Mail & Calendar, Signal, OpenSteetMap, Inkscape, but I feel like there are so many hidden gems that deserve more love.
Would be awesome to hear your picks, maybe even find some new favorites myself.
https://redd.it/1o4seqi
@r_opensource
Hey everyone, what’s one open-source tool you stumbled on that ended up being way more useful than you expected?
Could be for coding, AI/ML, writing, research, replacing Google, whatever helped you out big time but you don't hear people talk about much.
I use almost daily: Tuta Mail & Calendar, Signal, OpenSteetMap, Inkscape, but I feel like there are so many hidden gems that deserve more love.
Would be awesome to hear your picks, maybe even find some new favorites myself.
https://redd.it/1o4seqi
@r_opensource
Reddit
From the opensource community on Reddit
Explore this post and more from the opensource community
Project RogueGrid9 - Open-source P2P collaborative computing platform (Rust + React)
Hey r/opensource! 👋
I just launched the first public beta of RogueGrid9, a peer-to-peer collaborative computing platform I've been working on.
# What is it?
RogueGrid9 lets you share running processes (dev servers, apps, games) directly with your team using P2P connections - no cloud infrastructure needed.
Think of it like Discord meets VPS, but everything runs on your own hardware with peer-to-peer networking.
# Key Features
P2P Process Sharing \- Share terminals and running apps with teammates
Real-time Collaboration \- Text chat (voice coming in v0.2.0)
OAuth Authentication \- Google and GitHub login
Cross-platform \- Windows, Linux, macOS
100% Open Source \- MIT licensed
# Tech Stack
Backend: Rust + Tauri 2.0
Frontend: React 19 + TypeScript + Vite
Networking: Custom P2P protocol over WebRTC/WebSockets
Desktop: Native apps for all platforms
# Use Cases
Dev teams sharing local dev servers (no more ngrok bills!)
Pair programming with shared terminals
Gaming groups hosting game servers
Remote IT support
Collaborative debugging
Other cool stuff I havn't thought of
# Current Status (v0.1.5 Beta)
What works well: ✅ Windows and Linux fully supported ✅ P2P connections with NAT traversal ✅ OAuth authentication ✅ Text chat and grid management ✅ Process sharing and terminal emulation
What's experimental: 🚧 Voice chat (early stage) ⚠️ macOS process discovery (limited)
Not suported yet Turn relay servers for enterprise NAT has not been implemented yet due to bandwidth considerations but I plan to add this relitivly soon
# Links
GitHub: https://github.com/roguegrid9/roguegrid-desktop
Download: [https://github.com/roguegrid9/roguegrid-desktop/releases/latest](https://github.com/roguegrid9/roguegrid-desktop/releases/latest)
Website: https://roguegrid9.com
# Try It Out!
It's an early beta, so expect some rough edges. But it's fully functional and ready to use. I'd love to hear your feedback, bug reports, and feature ideas!
Windows and Linux work great. macOS users - you can use auth/chat but process sharing is limited (working on it for v0.2.0).
Found a bug? Open an issue on GitHub! Want to contribute? PRs welcome! Check out [CONTRIBUTING.md\]
Thanks for checking it out! Happy to answer any questions. 🚀
https://redd.it/1o4u499
@r_opensource
Hey r/opensource! 👋
I just launched the first public beta of RogueGrid9, a peer-to-peer collaborative computing platform I've been working on.
# What is it?
RogueGrid9 lets you share running processes (dev servers, apps, games) directly with your team using P2P connections - no cloud infrastructure needed.
Think of it like Discord meets VPS, but everything runs on your own hardware with peer-to-peer networking.
# Key Features
P2P Process Sharing \- Share terminals and running apps with teammates
Real-time Collaboration \- Text chat (voice coming in v0.2.0)
OAuth Authentication \- Google and GitHub login
Cross-platform \- Windows, Linux, macOS
100% Open Source \- MIT licensed
# Tech Stack
Backend: Rust + Tauri 2.0
Frontend: React 19 + TypeScript + Vite
Networking: Custom P2P protocol over WebRTC/WebSockets
Desktop: Native apps for all platforms
# Use Cases
Dev teams sharing local dev servers (no more ngrok bills!)
Pair programming with shared terminals
Gaming groups hosting game servers
Remote IT support
Collaborative debugging
Other cool stuff I havn't thought of
# Current Status (v0.1.5 Beta)
What works well: ✅ Windows and Linux fully supported ✅ P2P connections with NAT traversal ✅ OAuth authentication ✅ Text chat and grid management ✅ Process sharing and terminal emulation
What's experimental: 🚧 Voice chat (early stage) ⚠️ macOS process discovery (limited)
Not suported yet Turn relay servers for enterprise NAT has not been implemented yet due to bandwidth considerations but I plan to add this relitivly soon
# Links
GitHub: https://github.com/roguegrid9/roguegrid-desktop
Download: [https://github.com/roguegrid9/roguegrid-desktop/releases/latest](https://github.com/roguegrid9/roguegrid-desktop/releases/latest)
Website: https://roguegrid9.com
# Try It Out!
It's an early beta, so expect some rough edges. But it's fully functional and ready to use. I'd love to hear your feedback, bug reports, and feature ideas!
Windows and Linux work great. macOS users - you can use auth/chat but process sharing is limited (working on it for v0.2.0).
Found a bug? Open an issue on GitHub! Want to contribute? PRs welcome! Check out [CONTRIBUTING.md\]
Thanks for checking it out! Happy to answer any questions. 🚀
https://redd.it/1o4u499
@r_opensource
Reddit
Open Source on Reddit
A subreddit for everything open source related (for this context, we go off the definition of open source here http://en.wikipedia.org/wiki/Open_source)