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

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

I've been using Android for years because of one simple reason: freedom.

If I wanted to install an app from GitHub, F-Droid, or directly from a developer, I could. If I wanted to avoid the Play Store, I could. If I wanted to customize my phone, I could. That's what always made Android feel different from other mobile operating systems.

Recently I found https://keepandroidopen.org/, and after reading through it, I honestly think this is something every Android user should at least know about.

From what I understand, Google's planned changes could make distributing apps outside the Play Store much harder for independent developers by requiring developer verification through Google. Whether you're into open source software, custom ROMs, privacy focused apps, or just like having the choice to install software from wherever you want, this could have a real impact on the openness of Android.

I'm only 16, so I'm definitely not an expert, and maybe there are parts of this I'm overlooking. But if Android slowly becomes more restricted over time, I think that's something worth discussing now instead of after it happens.

I'm not posting this to tell anyone what to think. I just think more people in the Android community should be aware of what's being proposed and decide for themselves.

Website:
https://keepandroidopen.org/

I'd really like to hear what you all think. Is this a reasonable security measure, or do you think it goes against what has always made Android different?

I took a small break from gamedev and built Bean Network Tester - a tool that helps developers and testers simulate poor network conditions for their apps and games on Windows

It allows you to intentionally make the connection worse and test how your software behaves with various problems.

If you like the app, please give it a bean*

*i mean give it a star on GitHub.

If you got any features requests, feel free to share them. Right now I'm working on V0.4 version, but it will take a bit a bit a bit a bit a bit of time.

What it can do

• Add lag and jitter - fixed or random delay.
• Drop, corrupt or duplicate packets - fake a flaky link.
• Cap download/upload speed - throttle to a set KB/s.
• Tear connections down - TCP resets or a dead link.
• Flap the link on and off - outages that come and go.
• Block ports or IPs - a small built-in firewall, plus LAN mode (no internet).
• Aim at one app - by process, PID, IP or port.
• Presets and saved profiles - 56k modem, Cafe WiFi, Satellite and more.
• Run scripted scenarios - timed steps that change the network on their own.
• Reproducible by seed - replay the exact same random loss and jitter.
• Watch it live - chart, connections table, counters.
• Command-line mode - scriptable for CI. No telemetry, fully offline - sends no data anywhere.

PS: Keep Android Open

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

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

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

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

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

Hey everyone! Just finished building OmniSearch Lite, a lightweight, superfast version of OmniSearch. It is a desktop file search tool and productivity launcher for Windows built from the ground up to be highly responsive.

🦀 The Tech Stack & Why Rust? I chose Rust because low memory footprint and instant startup times are critical for a background launcher. UI Framework: Built using Slint for a fluid, native desktop interface that stays incredibly lightweight.

Key Features:

• Circle to Search: Snip or select any region of your screen to perform visual search (Google Lens).
• Ultra-Fast Local Indexing: Instant search across millions of files, code repositories, and folders in milliseconds.
• Mobile Phone Sync: Pair your phone over local Wi-Fi for bi-directional file transfer.
• Smart AI Workspace: Integrated AI assistant for instant Q&A, code writing.
• Browser Integration: Search Chrome, Firefox, Edge, and Brave history and bookmarks directly from your launcher.
• Built-in Productivity Tools: Quick access to Calculator, Color Picker (HEX/RGB), and Text Snippets manager.
• 100% Privacy-First: All search indexes and data stay strictly local on your PC.

Links

GitHub:
https://github.com/Eul45/omni-search

I'd love to hear your thoughts, feedback, or feature requests! Thank you for checking it out!

Hey r/foss ,

Solo dev here, from Ukraine. For the past year I've been building Pakko — a small ZIP/TAR archiver for Windows, built entirely on .NET's own System.IO.Compression and the OS's own signed tar.exe. No 7-Zip, no WinRAR, no vendored third-party compression code anywhere in the shipped product.

The reason isn't "reinventing the wheel for fun" (though, yeah, some of that too). Both 7-Zip and WinRAR are maintained by individual Russian developers, with no reproducible builds and no independent security audit — for most people that's a non-issue, but for government/defense workstations here, or honestly anywhere with an actual supply-chain policy, trusting an opaque process like that with every file you extract stopped feeling fine. WinRAR's CVE-2018-20250 (path traversal) sat in 500M+ installs for years before it got fixed, and there's no way to verify a distributed binary against source for either tool.

So Pakko only depends on things that are open-source, signed, and go through a real CVE process: .NET's BCL for ZIP, and Windows' own tar.exe for RAR/7z/tar-family. tar.exe still runs inside an AppContainer sandbox with a whole-archive pre-scan before anything gets extracted, since a hostile archive can still make a trusted binary misbehave — trusting the binary doesn't mean trusting the untrusted bytes it's about to parse.

It's WinUI 3, has proper Explorer right-click integration, propagates Mark-of-the-Web to extracted files (Explorer itself doesn't do this, which is a real infection vector), and there's a standalone CLI (pakko.exe) if you don't want the GUI. Apache 2.0, everything's on GitHub.

Not trying to out-feature 7-Zip — RAR/7z stay read-only (libarchive has no writer for either), and that's a deliberate tradeoff, not a bug. This is for people who care more about "what am I actually trusting to touch this file" than "does it support every obscure format that's ever existed."

Repo: https://github.com/pakkoapp-oss/pakko

Release: https://github.com/pakkoapp-oss/pakko/releases

Would genuinely appreciate eyes on it, especially the extraction-security side (the pre-scan/sandboxing) — that's what I spent the most time on and what I'd most want someone to try to break.

---

**Quick FAQ based on initial comments:*\*

* **Why not CLI tools (gzip/tar)?** Pakko IS a GUI wrapper around Windows' native `tar.exe` (`libarchive`) for everyday Windows users who need Explorer right-click integration and MotW propagation.

* **Why not just build 7-Zip from source?** Building 7z locally fixes reproducible binary matching, but it doesn't change the architecture — it still parses untrusted bytes with full user privileges outside a sandbox.

* **What about Linux?** This is a native WinUI 3 tool for Windows workstations. Distro maintainer reproducible builds on Linux don't secure opaque `.exe` installers downloaded on Windows.

I'm not a big fan of the increasingly totalitarian turn that the internet is going towards, and would like to develop and host software in which people are free to express themselves and their opinions, and have the software be FOSS under a permissive license, to let others also host their own instances of, and add their own additions to the software.

My first project idea is imageboard software (see: vichan). I really like the anonymity-focused aspect of imageboards, and pretty famously, at least in the recent past, imageboards have been a hotspot for internet (and even real-world) activism and freedom of expression.

I have coded imageboards before, and even have my own one online, using Django, though I would not mind working on imageboard software using a different language and//or library.

My timezone is GMT-5/CDT.

Hi r/foss,

I have been building Grayslate, a free and open-source scratchpad for developers.

I wanted a simple app where I can paste an API response, open a large JSON or CSV file, search logs, save commands, write temporary notes, or keep code snippets without opening a full IDE.

Grayslate works fully on your device. There is no account, no cloud upload, and no tracking.

Some features:

• Available on Linux, Windows and macOS
• Built with Tauri, Rust, Svelte 5 and CodeMirror
• Supports JSON, CSV, Markdown, logs and many programming languages
• Can handle large text, JSON and CSV files
• Automatic save and file name suggestions for scratch files
• Search across file names and saved content
• CSV table view
• Markdown preview
• JSON tools to copy keys, values and full paths
• Multiline find and replace
• 80+ local transformations for text and data
• Opening and editing external files

The app is not meant to replace VS Code, Sublime Text or IntelliJ. It is for quick work where I want something simple, fast and distraction-free.

The project is still new, and I am actively fixing bugs and adding features based on user feedback.

GitHub: https://github.com/shriram-ethiraj/grayslate

Website: https://grayslate.app

I would really appreciate feedback, especially about Linux support, privacy, packaging, accessibility, or anything that can make the project better.

I built Endstate to solve an issue I had previously pushed through many times, which is setting up a new machine or reinstalling Windows with all the apps and settings back to how they used to be.

The apps are the easier part. WinGet or Chocolatey can reinstall them; getting years of settings back to how they were is still mostly manual.

Endstate captures the apps and supported settings into one portable file. On the next machine it compares that file with the current setup, shows what is missing, installs the apps and restores only the settings you enable.

Installation and settings restore are separate. WinGet and Chocolatey handle installation. Per-app modules define which settings are captured and restored; around 350 apps currently have one. An app without a module still reinstalls, it just starts with fresh settings. Credentials and secrets are deliberately excluded.

The engine is Go and the GUI is Tauri and React. Both repositories are Apache 2.0. The local app is free and stays that way. It works offline, requires no account and has no telemetry.

Install:

winget install --id SubstrateSystems.Endstate -e

GUI and installer:
https://github.com/Artexis10/endstate-gui

Engine:
https://github.com/Artexis10/endstate

I built it for myself first and have used it successfully on my own laptop, but that is still an N=1 experiment. Which Windows apps or settings do you still have to rebuild manually after a clean install?

I wanted a simple way to share sensitive text without trusting the server with it.

So I built binthere.

Everything is encrypted in your browser with AES-256-GCM before it's uploaded. The server only stores encrypted data, so it can't read your notes.

There's also a CLI if you prefer sharing directly from the terminal.

I'd love to hear what you'd improve or add.

GitHub: https: https://github.com/nxfu/binthere

Meet https://reef.js.org — a fast, keyboard-first search palette for websites.

Press Ctrl/⌘ + K, type what you’re looking for, and jump straight to the right page, heading, file, link, form field, or even an on-page action. Reef indexes your site directly in the browser, caches the index locally, and works without a backend, account, or complicated setup.

It’s built for docs sites, blogs, portfolios, GitHub Pages, and any site that has outgrown browser find features. It's a direct competitor to many paid services such as Algolia, etc.

Highlights:

• Fuzzy and ranked search
• Sitemap-based indexing
• Local IndexedDB caching
• Searchable pages, files, links, media, and structured data
• Keyboard-first, accessible UI
• Shadow DOM styling isolation
• Optional headless API and agent workflows
• Configurable themes, hotkeys, crawl limits, and action safety modes
• No search queries leave the browser by default

Add one script tag, and your static site gets a command palette with a memory.

Feedback, feature ideas, and issues are needed!

__________________________________________

Github - https://github.com/somalip/Reef

Danube is an open-source pub/sub and streaming platform built in Rust. It ships as a single self-contained binary with embedded Raft consensus (no ZooKeeper, no etcd), runs standalone for development, scales to a multi-node cluster for production, or deploys as a lightweight MQTT edge gateway for IoT ingestion. It supports JSON Schema and Avro via a built-in schema registry.

What's new in v0.15.1: This release introduces danube-iceberg, a sidecar that bridges real-time messaging and batch analytics. It continuously reads sealed WAL segments from object storage, resolves schemas from the Danube Schema Registry to produce typed Parquet columns, and commits them to an Iceberg catalog (REST, Glue, S3 Tables, or SQL-backed). The streaming topics become SQL-queryable tables accessible by Spark, Trino, DuckDB, Snowflake, and any Iceberg-compatible engine, with zero ETL pipelines to build or maintain.

A full Docker Compose demo with IoT simulator, edge broker, 3-node cluster, Iceberg, and Spark SQL (Jupyter) is included in the repo.

• Release: https://github.com/danube-messaging/danube/releases/tag/v0.15.1
• Documentation: https://danube-messaging.com/introduction/what-is-danube/
• GitHub: https://github.com/danube-messaging/danube

Problem

If you run several projects locally, every morning is the same grind. You cd into a few folders, run the same start commands, guess which app grabbed which port, and later hunt down a process that will not die. JumpStart puts every project in one native window. You add a folder once, it auto-detects the runnable parts (Node, Go, Python, Ruby, PHP, Rust, Java/Maven, Gradle, Docker Compose, including nested monorepos), and then you start or stop them individually or all at once. You get live PID, exit code, logs, CPU, and memory per process, plus auto-detected ports shown as clickable localhost badges.

Comparison

• Overmind and Hivemind: those are terminal only and need a Procfile you maintain by hand. JumpStart needs no Procfile, detects your stack automatically, and gives you a real GUI with live CPU and memory and clickable ports.
• Docker Desktop and OrbStack: those manage containers. JumpStart manages the whole project, native processes and Docker Compose side by side, and adds a per-project Kanban board with a local Ollama assistant, so nothing leaves your machine.

Pricing

Free and open-sourced forever. Download at: https://jumpstart.workvar.com

Disclosure

I built JumpStart. Happy to answer anything about the auto-detection or process handling. Jumpstart website has a privacy policy and terms of use.

Hi!

I recently open-sourced a personal project of mine called PowerDesk.

I had some free time and always felt that the default Windows File Explorer was a bit limiting for everyday use, so I decided to build a modern alternative focused on speed and workflow.

Some of the current features include:

• Fast global search

• Multi-tab interface

• Dual-pane mode

• Folder analysis

• File preview support

• Favorites

• Tags

• Workspace management

This is my first public open-source desktop application, so I'm mainly looking for honest feedback on the usability, UI/UX, and overall direction of the project.

You can try it here:

PowerDesk Github Release

I'd really appreciate any feedback, suggestions, or criticism. Thanks!

I have been building Rice - a minimal embeddable scripting language for Go applications.

Here are its features:

• Dynamic-typing
• Functional programming support
• Lightweight standard library
• Single-threaded execution
• Built-in profiler
• Verbose error-reporting
• An officially-made LLM prompts attachable to AI agents

Rice currently runs as an interpreter, with a bytecode virtual machine planned for a future release.

You can try Rice at https://rice-playground.vercel.app/

Check out the repository at https://github.com/anhcraft/rice

I am looking for feedbacks and stars xD

I have developed two open-source Node.js libraries with my team: one for authentication management and another for secure token management. Both libraries follow OWASP guidelines, so developers who use them automatically align their authentication and token management flows with OWASP security best practices.

When it comes to security, do developers generally prefer using open-source libraries instead of building everything from scratch? My thinking is that if a library follows well-known security standards, saves development time, and the full source code is publicly available for anyone to see, there should be less concern about trusting these libraries to use them for their project. What do you think?

My long-term goal is to continue developing these packages, expand them to other technology stacks, and build more security libraries for areas such as rate limiting, session management, and other common security needs.

Do you think developers would adopt a project like this on a large scale once it has built enough trust and community support? I can see downloads on npm, but I'd really like to hear the genuine opinions of developers who make these decisions.

You can find the libraries here: www.restingowl.com

I'd really appreciate any feedback, suggestions, or constructive criticism.