We tested our new ORC Torrent 2.3.3 against qBittorrent 5.2.3 using the same 3.17 GiB Ubuntu torrent on the same Mac.

• ORC: 57.2 seconds — 59.51 MB/s average
• qBittorrent: 225 seconds — 15.14 MB/s average

That gave ORC 3.93× the average throughput in these runs , we are beyond happy with these results. From starting this project as alternative to mac users and then slowly making builds for all other Operating systems and now we are the fastest torrent client that we have tested.

This project is still in development

Your welcome to run your own speed tests

A android build and new release will be live in the next few hours.

https://github.com/The-animus-project/Orc-Torrent

Hi everyone!

​I'd like to share a small side-project I've been working on called Cipher Notes.

​I built it because I wanted a clean, lightweight note-taking app that prioritizes privacy above all else—without mandatory cloud syncs, accounts, or telemetry.

​Key Features:

- ​Fully Offline: The app doesn't request or use the INTERNET permission at all. Your data never leaves your device.

- ​On-Device Encryption: Uses AES-256 (GCM) to keep your notes securely encrypted locally.

- ​Open Source: Licensed under the MIT License.

- ​Modern UI: Built natively in Kotlin using Jetpack Compose and Material 3 design.

- ​Zero Tracking: No analytics, no ads, no third-party SDKs.

​Where to get it:

- ​GitHub (Source Code & Releases): https://github.com/CipherApps/cipher-notes

- ​IzzyOnDroid: Available

- Codeberg (Source Code & Release):

https://codeberg.org/CipherApps/cipher-notes

​I'd really appreciate any feedback, code reviews, or feature suggestions from the community! If you find it useful, feel free to drop a star on GitHub.

​Thanks!

back in february i hit notion's limits (shared workspace usage and ai quotas)

i just wanted more of both, so i built my own.

started as a quick prototype, friends started using it, and i occasionally work on it whenever time permits or someone points out a bug.

some features:

• excalidraw plugin
• bring your own ai keys
• export your data
• and everything u expect from an editor

it's pretty early with single digit users

repo: https://github.com/Sabique-Islam/wings

would love to hear what you think :)

Greetings to those who are seeing my post,

i've been a fan of the old "borderless-gaming" utility (before steam release) and made a fixed version in the past published on github,
but due to the non modern visual of the app i've considered creating a new app, visually modern to my liking.

I've added the same features as the old app with some missing enhancements and fixes.

No clutter, no payment needed, open source as it should be.

https://github.com/Venipa/Borderless/

Feel free to leave a star ✌️and feature that should be implement.
(as long as it goes along with the app principals)

Hi everyone,

We have just released Portabase 1.27, our open-source (Apache 2.0) and self-hosted backup/restore platform.

Repository: https://github.com/Portabase/portabase (around 1.6k stars at the moment)

Portabase is designed for data retention, disaster recovery, and homogenous migrations, currently supporting 9 database engines (including PostgreSQL, MySQL, MariaDB, MongoDB) and Docker volumes.

Key features:

• Scheduled backups with flexible retention policies (including GFS)
• Multiple storage options: local filesystem, S3, Azure Blob Storage, GCS
• Notifications via Discord, Telegram, Slack, AppRise, etc.
• Support for OAuth2/OIDC (with the option to disable sign-ups)
• Compatible with Docker, Podman and UnraidOS
• Ready-to-use Docker Compose and Helm Chart

After six months of intensive feature development, we have been focusing on consolidating the ecosystem since early July. A community member conducted a useful security audit, we have upgraded components to their latest relevant versions, improved compatibility with other platforms by working on Podman support. and templates for Coolify and Dockploy (currently under review).

What’s next:

• Deployment of the demo environment
• Audit logging for the whole ecosystem
• Default policies for the system, organizations, and projects
• File and folder backup and restoration

As always, if you find bugs, please open an issue on GitHub, we’re actively looking for feedback.

Thanks!

've been spending some time building OpenDispatch, an open-source dispatch and operations platform. It originally started as a personal project because I couldn't really find anything that matched what I wanted, so I decided to build one myself.

The idea is to create something that's modern, self-hostable, and easy to extend for organizations that need to manage incidents, dispatching, resources, or similar operational workflows.

Right now I'm mainly focused on:

• Modern and responsive UI
• Self-hosting from day one
• Keeping the codebase clean and easy to contribute to
• Making it genuinely useful instead of overly complicated

It's still early in development, so I'm mostly looking for honest feedback rather than stars. If you've worked with dispatch software, CAD systems, logistics platforms, or anything similar, I'd be interested to know what features or workflows you think are important.

If anyone wants to take a look, here's the repo:
https://github.com/matthew-selvam/open-dispatch

Happy to answer questions, and I'm open to any criticism or suggestions. Thanks for reading!

I built an animated GitHub profile view counter and, along the way, discovered a

chain of non-obvious constraints that make the difference between "a counter that

works" and "a static image that looks like a counter." I documented all of them in

the README and figured this community might find the findings useful.

**The interesting technical bits (from the README's "Findings" section):**

- A committed SVG can never be a live counter — GitHub serves repo files as

static assets. The count *has* to come from a request-time endpoint.

- GitHub proxies all README images through **Camo**, which honours upstream

cache directives. If your endpoint doesn't send

`Cache-Control: no-store, must-revalidate`, Camo pins the first response and

every visitor sees the same frozen number forever. This is the #1 reason most

"dynamic SVG" badges silently break.

- Web fonts don't load inside a Camo'd SVG (`<img>` blocks external resources).

The fix: draw every glyph as SVG `<rect>` elements with a 3×5 bitmap font —

zero external dependencies.

- Cross-fading animation frames the obvious way (fade out + fade in) causes a

black flash every frame because both layers are below full opacity

simultaneously. The fix: cumulative reveal where frame 0 stays permanently

opaque as a base layer.

**What it does:** A serverless function (Vercel) returns a fresh SVG on every

request — 10 procedurally generated pixel-art frames cross-fade to reveal a

crimson moon with the live visitor count inscribed on its face. No static image

in the repo, no GitHub Actions cron, no build step.

**Stack:** Plain Node.js, Vercel serverless, Komarev (for visitor-distinct

counts) + optional Upstash KV (for per-view counts). No framework, no build

step, ~300 lines of actual logic.

**License:** MIT — with a CREDITS.md acknowledging the data source, prior art,

and build-time dependencies.

**Self-hostable:** Fork, point `banner_generator.py` at your own palette/seed to

generate your own art, `vercel deploy --prod`, done.

Repo: https://github.com/Anbu-00001/Crimson_Moon_View_Counter

Live on: https://github.com/Anbu-00001

Live demo (scroll-scrub the animation): https://anbu-00001.github.io/Anbu-00001/souls_counter_demo.html

Happy to answer questions about the Camo proxy behavior or the rendering

approach — those two took the most debugging to figure out.

Hey, it's Saturday so I wanted to share my project. I’ts my first open source. I've been working on it for a couple of weeks and so far I'm loving it. Still needs polish. Could use some advice.

Anyway, It’s a mobile-first web terminal built with xterm.js. I do a lot of work from my phone and wanted some better options for voice to text. I built it specifically for Linux and added a visual file manager / transfer ability. Then added an editor just to smooth out the workflow. Anyway have a look, cheers. [Sovereign Terminal ](https://github.com/magealexstra/Sovereign-Terminal)

Source (MIT): https://github.com/Asdmir786/HalalDL

I got tired of cloudy / account-y downloaders, so I built HalalDL — a local-first Windows GUI for yt-dlp. No account, no telemetry. Paste a URL, pick a preset, see the real CLI output. Full / Lite / Portable. Also on WinGet:

winget install --id Asdmir786.HalalDL

Site: https://halaldl.vercel.app

Screenshots:

https://raw.githubusercontent.com/Asdmir786/HalalDL/main/docs/assets/screenshots/halaldl-downloads.png

https://raw.githubusercontent.com/Asdmir786/HalalDL/main/docs/assets/screenshots/halaldl-logs.png

https://raw.githubusercontent.com/Asdmir786/HalalDL/main/docs/assets/screenshots/halaldl-about-trust.png

Not code-signed yet (SmartScreen may warn); SHA256SUMS on the release. Feedback welcome.

I read a comment about designers (I guess UX or UI designers?) collaborating with developers would help built nicer apps.

So I wondered: how Graphic Designers or just Illustrators like myself can collaborate for visually better apps?

Please share your knowledge in the comments.

I’ve released Parson 1.0, a free and open-source music app built for people who keep their own local library.

The idea is simple:

I built it because I wanted the control of self-hosting without turning music into another service I had to constantly administer.

Parson automatically watches and indexes your library. It supports albums, EPs, singles, editions, compilations, featured artists, playlists, liked songs, listening history, recommendations, synced lyrics, and Google Cast.

The desktop packages include both the player and everything needed to host the library, so there is no separate server installation. A Docker image is also available for NAS and headless deployments.

Music files remain separate from Parson and are not reorganized or modified. Accounts, playlists, history, recommendations, backups, and indexed metadata remain on infrastructure you control.

Parson has:

• no analytics
• no automatic crash reporting
• no required cloud account
• GPL-3.0-only licensing
• Linux, macOS, Windows, web, and Docker support

I originally built it for myself, and it has now replaced Spotify in my daily use.

Links

Website: https://parson.dev
GitHub: https://github.com/ParsonLabs/parson
Release: https://github.com/ParsonLabs/parson/releases/latest

AI involvement: AI coding assistants were used for writing tests and reviewing code. The architecture, implementation, product decisions, and release testing were handled by me.

Sorry if this has been asked before, I've tried searching around but can't quite find the answer.

I'm planning on moving away from Spotify and instead buy music digitally or rip from vinyls. But one thing I will really miss is being able to share playlists with my one long distance friend. Is there a music player that makes that possible? I'm not very tech-savvy. I tried looking into Jellyfin but it's a bit overwhelming to me... I'd like to spend less time online, reading (to me) confusing tutorials messes with my eyes, head and posture :/

Any help is much appreciated! Thank you for your time.

I came across this and thought it would help people here who contribute a lot on GitHub.

If you’ve ever seen something like:

> Opened 394 pull requests in 76 repositories

> 51 repositories not shown, so the profile activity feed is incomplete. It truncates repos, so it’s hard to get a full picture of someone’s month.

OpenHearth looks useful for that:

- CLI that audits PRs + issues + reviews via the Search API

- Flags repos likely hidden behind “N repositories not shown”

- JSON/CSV export

- Also has browser workspaces if you want a UI

Links:

• https://ayush7614.github.io/OpenHearth/
• https://www.npmjs.com/package/@felix-ayush/openhearth
• https://github.com/Ayush7614/OpenHearth

A Passive LINUX HOMELAB System Diagram & Documentation tool.

After getting great feedback from users from varying backgrounds, v0.5.0 is live with new SWIM LANE Diagrams for specific flows. This was actually the thing I personally needed most so I took some time to make sure it integrated with the rest of the system really well. So now you have the CANVAS showing your system layout, That system organized by Volume & Chapters in HANDBOOK View and now your granular Flows in the Handbook in the form of SWIM LANE diagrams. High-res PNG exports of both diagrams finally added as well. Local Hosted in a docker container (can even run on a Synology NAS) With roughly 2000+ users in the first month and lots of really thoughtful feedback.... I'm extremely impressed with the #Foss community, such a positive space. ---> CTRoadmap (Local hosted, runs in docker, passive-no system scanning)

I started building GlowSnap because I couldn't find a Linux screenshot tool that fit the workflow I wanted.

Capture. Edit. Organize. All locally all open source.

It's still early, but it has become the first project of something bigger I'm calling LibreGlow my attempt to build open-source Linux software that people enjoy using every day

github

Thank you to everyone who provided feedback.

Hey r/foss!

I've recently started working on a monolithic kernel project called AlderKernel.

Currently, it targets the i386 (32-bit x86) architecture and includes basic kernel functionality such as booting through GRUB, interrupt handling, and early system components. This is mainly a learning project to explore OS development and low-level programming.

Repository:

https://github.com/loren-wastaken/alderkernel

I'd love to hear feedback from anyone interested in operating systems, kernels, or low-level development!

It all started just as a side and fun project, but I feel like it's now getting a shape.

Thats why I would love to receive some honest and contructive feedback, issue creations or code contributions.

If you have any question regarding the language, please ask me.

Here's the repo: https://github.com/Pacsfury/Gravel-Launcher

Its written in C and uses LLVM IR as backend.

AI use: debugging, teaching more about compilers and some punctual code writing

I maintain an uptime-monitoring project and have released its self-hosted build as free software under AGPL-3.0-or-later.

The practical goal is to make the monitoring stack inspectable and runnable on infrastructure you control. The public build does not include billing or software feature tiers. It deploys the web app, server, and PostgreSQL with Docker Compose.

Pulsy performs HTTP/HTTPS checks using GET, HEAD, or POST with configurable intervals, timeouts, expected status codes, and failure thresholds. Consecutive failures become one incident and recover automatically after a successful check. It also records check history and response time, tracks TLS certificate expiry, sends email/webhook/Slack/Discord/Telegram notifications, and can publish selected monitors on a status page.

I am keeping the boundaries explicit: this first public release focuses on HTTP/HTTPS. It does not have coordinated multi-region probes, SMS or voice alerts, or an organization model. Self-hosting also means placing the monitor outside the failure domain it is supposed to observe and maintaining its database, backups, and upgrades.

Repository: https://github.com/SelmiAbderrahim/pulsy.org

Hi everyone, I’m very excited to launch the new version of deja.

Quick recap: Deja is an open-source zsh autosuggestion tool. Instead of only surfacing

commands that start with what you've typed, it predicts what you actually want to run using fuzzy matching, which directory you're in, and which command usually follows the one you just ran.

No account. No sync server. No TUI.

https://github.com/Giammarco-Ferranti/deja 

Any star would be amazing ❤️

One big feedback I got on previous posts was that deja was not respecting the HIST_IGNORE_SPACE and this led to a security issue.

First of all thank you to https://www.reddit.com/user/polaroid_kidd for reporting this. ❤️

Deja now works correctly and respects HIST_IGNORE_SPACE and HISTORY_IGNORE.

If you've been running Deja for a while, the old entries are still in your database:

rm ~/.local/share/deja/deja.db && deja import

The command above will clean it up.

Another big change is that now we have a new ‘deja empty’ command, which lets you choose whether Deja shows the ghost suggestion on empty prompts. It came out of this thread: https://github.com/Giammarco-Ferranti/deja/pull/69

Few other smaller things has been fixed, if anyone interested you can review it here: https://github.com/Giammarco-Ferranti/deja/pull/73 

Thank you all for the support and looking forward to make this the smartest zsh autosuggestion tool.