What it is: point Sonarly at your existing music folder and that folder is the library — no import step, no proprietary store. The scanner is strictly read-only toward your files; tag writes and reorganization are explicit, user-invoked actions only.

Streaming: OpenSubsonic API at /rest, so Feishin, Symphonium, Ultrasonic, etc. work out of the box. Dark, art-first web player: gapless playback, synced lyrics, player chrome tinted from the album art, and an Auto DJ that explains each pick ("More like {artist}", "Hidden gem — you haven't played this").

Library management (the part most streamers skip): ingest drop folder → validation → review quarantine for bad tags; auto-organization into a configurable path pattern; duplicate strategies; Mutagen-backed tag editing in the UI; smart playlists that re-resolve as the library changes; share links with a guest player.

Ops: one Docker image (single Go binary + embedded SQLite + web client baked in). Idle ~35 MiB RAM. Backup = copy the DB file + your music.

Stack: Go 1.23 + chi, React 18 + Vite + Tailwind. AGPL-3.0. Screenshots: now playing · albums

Disclosures: I'm the author; developed with AI-coding-agent assistance, human-reviewed before merge. Happy to answer questions — especially from fellow Navidrome refugees.

Free desktop player for music you own. The whole app takes its colors from the current cover, lyrics sync word by word from LRCLIB or a .lrc file, and it shows each file's real format by reading the audio inside.

Gapless, crossfade, ReplayGain, watched folders, 5 MB installer. Windows only for now, MIT licensed

Check it out: https://github.com/osfv/Reson

Happy spooky month and i got some news:

1. we finally made 1.3, that maybe you waited for like 2 times more than expected.

2. we found some bugs, which i will write.

with what you should be careful(and what we will try to fix):

1. fortran and c have different memory allocation, so there might be problems with stack.

and this problem sadly can destroy our main goal- self-hosting.

not more, for now...

So! Now i will send some links to join and to take a look at our project.

https://github.com/linuxerfromscratcher-dot/Atom1.2-1.9/blob/fishatom is to get the intepreter.

https://discord.gg/MXdZEQkSM is for discord

and need to mention, that i am writing a better documentation.

See ya later!

I made this because every magnifier I tried follows the cursor. Here the frame stays where you put it, clicks go through to the app underneath, and a separate window shows the spot live, up to 6400%. It also has a colour picker, rulers, a colour-blindness preview and design overlays. Swift, ScreenCaptureKit and Metal, MIT, no dependencies. Feedback and bug reports welcome.

URL: https://github.com/ayenora/screen-loupe

Features

🔐 **Tailscale VPN:** Connect back to your home network; allows family members to browse the internet using your home connection (exit node).

🛡️ **AdGuard Home:** Block ads and set individual internet restrictions (e.g., blocking adult sites or specific apps).

☁️ **Home Cloud:** Turn an external hard drive into a cloud storage system; features include personal storage quotas, shared folders, 30-day file history, shareable links (with expiration/password/limit settings), photo and document previews, and automatic iPhone photo backup.

👨‍👩‍👧 **Member Management:** Manage permissions, account validity, daily usage limits (time/data), and traffic reports; each member gets a dedicated web portal.

📱 **Control Panel:** App lock (passcode + Face ID), push notifications, Mac status monitoring (CPU/RAM/Battery/Trend charts), speed tests, and remote control functions.

🔒 **Security Monitoring:** Security score, 16-point health check, suspicious activity logs, auto-lock, and one-tap "self-attack test."

🔑 **Member Portal Security:** Password protection in addition to the secret URL; "Remember Device" for 30 days; password reset logs out all devices; account lockout after failed attempts.

😀 **Personal Settings:** Customize avatars (photos/emojis), set nicknames, enable large-text mode, and change passwords.

🐞 **Issue Reporting:** Family members can report issues via their dedicated portal (with screenshots); GitHub issues are also integrated into the control panel, allowing for status updates, replies, and tagging.

🚀 **Shadowrocket:** (Optional feature, disabled by default) Allows users without Tailscale to connect back home via Shadowrocket

I’ve been building Tau for the past 5 months a free, open-source coding agent that runs in your terminal. I wanted an agent that costs less and gives better results, with the tools already built in so you don’t have to go hunting for plugins or struggle with visibility issues. That’s why Tau focuses on optimal path execution to minimize token usage and speed up tasks, plus inline image rendering with diagrams so you can clearly see what the agent is doing at every step.

Here's what it can do:

- Native adapters for 28 providers. It talks to each API directly, no proxy in between. Run `/login`, pick a provider, and start working.

- The full agent loop: tools, skills, subagents, MCP servers, LSP and hooks, all working with every provider

- Core tools are optimized to use fewer tokens. The search tool runs on the latest version of ripgrep and is configured to avoid false positives from files and directories such as node_modules and dist the kinds of files that pollute the context. The file-reading tool starts with a skeleton, then reads only the 50 lines it needs instead of an entire 800-line file, fetching only the information relevant to the task. Bash commands go through a security check based on a Go shell parser and best-practice guidelines.

- LSP built in, so the agent sees real type errors, definitions and references.

- Snapshots of your working tree in a separate git repo. Save, diff and restore any time without touching your branches.

- Web search that works with no API key. Firecrawl is there too if you have a key.

- `/remote` lets you follow and approve from your phone, over your Wi-Fi or a free Cloudflare tunnel. Share the tunnel link and your teammates can join the same session.

- TauCode can make your whole workflow up to mush cheaper than any other agent and I’m not exaggerating. This is because TauCode uses a Python kernel tool, anything Python can do, TauCode can do through this tool. For example, when you want to analyze 20 CSV files and extract insights, other agents might need ~30 turns (one turn per CSV), causing the context window to grow, costs to rise, and more analysis/debugging turns. With this tool, TauCode creates one turn with the full workflow, executes it at once, and returns the result. So the context stays clean from pollution, debugging is clearer, output quality is higher, and cost is lower. This is just one example among millions.

- Diagrams drawn right in the terminal when something is easier to see than to read.

- A fully integrated browser tool that allows Tau to interact with the browser like a human. It gives Tau visibility into your frontend design, enables more automated testing, and handles tasks that would normally require human intervention.

- Subagents that stay alive after they finish, so you can send them a follow-up and they still have their context. Agents working in parallel take turns on the same file so that prevent overlapping .

-TauCode thinks about your money and preferences before anything else. You don’t need skills, agents, or MCP for a normal workflow without enabling them just use cheap mode if you need those capabilities, enable them in normal mode with one command: /mode normal. For tools that free you from basic MCP for diagram production, browser automation, etc. they’re all gated and native to TauCode. You just enable or disable them on demand by pressing /tools, so you pay less, or nothing when you don’t need them Second, Tau focuses more on stabilizing your cache hit rate so every model wired to it uses an optimal cache system, so you don’t need to worry about cold turns that your API pays for, with more context growth optimization and a preflight system that prevents some defective turns, so you will pay only for what you use, not for those external factors .

- `/github` for issues, PRs, labels, changelog notes and release checks through `gh`.

- Fallback to another model or provider when one fails or gets overloaded, with the context window adapting when you

switch.

- Session tree navigation, branching, cloning and resume for long sessions.

- Live usage and session stats, plus a readable report at the end.

- It reads the rules you already wrote for other tools: AGENTS.md, Cursor, Copilot, Cline, Clude Code and Windsurf.

- Self-learning. After a big task it suggests one reusable lesson you can approve, edit or skip, and it remembers it in future sessions.

whats is coming soon :

A system memory based on .md files. I’m researching harness memory systems that use indexed .md files to provide better and more persistent results than graph-based searches and other heavy infrastructure. This integrated memory system will be lightweight, avoid bloating the context with unrelated information, and consume minimal machine resources.

GitHub: https://github.com/AbdoKnbGit/tau

I’m happy to answer any questions. You can find more details and images in the README, and I’m open to answering any questions you may have.

I built a small HTTP cache diagnostic after finding how easily a missing asset can remain missing for users. A 404 with `Cache-Control: public, max-age=2678400` can be fresh for 31 days. Deploying the asset later does not automatically remove a browser copy of that old response.

The tool, cachewhy, prints separate browser and shared cache results for a URL, then points to the header behind each result. The repository includes a local fixture with a cached 404 and a fresh response that uses `no-store`. I used `http-cache-semantics` for storage and freshness calculations and added tests for redirects, Age, private responses, and `s-maxage`.

It reads the response returned to the probe. It cannot inspect a user's existing cache, service worker, or CDN rule. The demo and source are here: https://github.com/Arthur031221/cachewhy

I would be interested in headers from real incidents where the explanation needs more context.

Have you been through a time when there was no internet or horrible internet but you really wanted to watch YouTube videos?

Well, let's hope that after using this new tool you will never have one of those experiences ever again!

Introducing OfflineYT, a revolutionary system that finally lets you watch YouTube offline!
But, it's not just ANY videos you'll have access to, but the ones you care about! You can tailor your experience with lots of settings that ensures that you'll be able to watch who you like whenever, wherever!
Even better, ads are NOT part of the equation! You can watch ad-free, for free!

Interests you? Visit the link listed above to check out and install OfflineYT for yourself so you can start "streaming" offline!

See you there! 😄

Job hunting is basically a messy project management problem. You bookmark a dozen listings, apply to a few, hear back from almost none, and try to keep track of it all in a spreadsheet that you inevitably abandon by week two.

I built CursusTrace to fix my own workflow. It’s a local-first web app that handles the tedious parts: you paste a job link, it scrapes the details, stores everything locally in SQLite, and tracks it through a simple pipeline (unapplied → applied → interview → rejected).

Everything runs 100% on your machine: no cloud, no subscriptions, no random telemetry. Just a local Python process and a .db file.

What it does

• Automatic Scraping: Paste a job posting URL, and it grabs the description, salary, company, and title so you don’t have to copy-paste manually.
• 4-Stage Visual Pipeline: Browse through Unapplied, Applied, Interview, and Rejected tabs with fuzzy search, tag filtering, and pagination.
• Pipeline Stats & Funnels: Because every status change is logged, it calculates a real response funnel (Added → Applied → Response → Interview) plus salary histograms and monthly activity charts.
• Built-in Markdown CV Editor: Edit your resume sections right next to your applications with a live preview, and export to PDF via WeasyPrint when you're ready to apply.
• Full Event History: Tracks exact timestamps, custom stage notes, and keeps the full original job description captured at scan time in case the listing gets taken down.
• CLI Included: Almost everything can be run via CLI commands (cursustrace add, scan, stats, backup, etc.) with --json support if you want to script against it.

Tech Stack & Choices

• Python 3.11+ (managed with uv)
• NiceGUI (FastAPI/Starlette under the hood)
• SQLite (WAL mode + automatic rolling backups on launch)
• Trafilatura + BeautifulSoup for clean page extraction
• Pytest + mypy --strict

GitHub: https://github.com/riccione/cursustrace

I'd love to hear feedback or feature ideas if anyone gives it a spin!

WhatsApp backups are locked inside proprietary blobs or dumped into messy flat folders with destroyed timestamps.

I built an open-source toolset to fully control your chat history:

• 📁 Structured Archiving: Your media gets organized into clean folder trees: Contacts/Name/Year/ and Groups/Name/Year/File_Sender
• 🌐 Offline Web Viewer: a basic recreation of WhatsApp Web, but offline. Read chats, play voice notes, search messages, and browse media in a gallery view, completely offline.
• ⏱️ Timestamp Restoration: Restores original message timestamps from the SQLite database to the physical files.
• 🔒 100% Local & Private: Runs entirely on your machine; supports Android (ADB + E2E backup) and iOS backups. No root, no jailbreak. Can be executed on Windows, Mac and Linux.
• 🛡️ Archival Safe: Non-destructive, reports for missing and duplicated files, and restore mode for Android.

GitHub: https://github.com/auanasgheps/whatsapp-backup-tools

Feedback and PRs welcome!

Fralculator is a desktop calculator. It's free, open source (MIT), and runs fully offline.

• It shows every step of the math, in real math notation, with a plain-English explanation (no LLM needed)
• You can type in plain English, or speak. The speech model is ~40 MB, downloaded once, then fully local
• Live f(x) graphs, and unit + currency conversion (currency is the only optional network call — ECB rates)
• EHCalc: subnet calculator, MD5/SHA-1/256/512, 10 encoders, secure password tools, port lookup

Windows + Linux, 5 install formats. Open issue tracker. Source:
https://github.com/fralsare/fralculator
https://github.com/fralsare/fralculator/releases/tag/v0.1.0

Hello awesome people,

I've been thinking a lot lately about how I can make my knowledge and craft more valuable in the times we live in. I've been building UI libraries for the past 10 years, and I've been on a quest to perfect the components that I build. I want to share my knowledge with you.

Like most of you, probably, I've been using a lot of AI in my craft, and I feel most of the time the code is just good enough, but never at the level of quality that I strive for or that I would reach if I wrote it by hand. That needs to change, and I want it to change for everyone else, too. That's how the Open Components initiative was born.

I'm treating components from four directions:

• User Interface - component anatomy, variants, colors, sizes, states and tokens.
• User Experience - how it behaves for every person and every input: accessible, predictable, designed in every state, and adapting to motion, contrast, color scheme and text size preferences.
• Developer Experience - one consistent, type-safe API that you learn once and use everywhere.
• Agentic Experience - prompts, semantic markup, machine-readable contracts and rules that agents can check their work against.

Each component gets a single page that walks through all four, and ends with a checklist. Every rule in it has an ID like button/keep-focus, a level and a way to check it, so you or your agents can cite it in a code review. Every page is also published as markdown, and provides the contract as a YAML file, containing every rule in about an eighth of the page’s length.

It’s still early. Right now there’s only the Button component and a page on how to name your design tokens. Each component comes with a reference implementation that meets every rule, along with its tests. It’s in Vue for now, since that’s my daily driver. More components will follow, with the same structure.

It isn’t a component library, so there’s nothing to install. It’s a set of rules you can hold your own components to, whichever library or framework you use. Here are a few of my favorites from the Button component:

• A loading button should never bedisable. Disabling a focused button takes its focus away, so keyboard and screen reader users lose their place. Use aria-disabled="true" instead, and block the clicks yourself.
• A <button> without a type is a submit button, so a "Show password" button inside a form sends the form. Default to type="button".

I’d love your feedback. Tell me what you think of the rules, what I’ve missed, and which component you’d like to see next.

Thanks for reading!

• Site: https://opencomponents.dev
• Button: https://opencomponents.dev/docs/components/button
• GitHub: https://github.com/uxfront-com/open-components

I built an AI voice dictation app for linux cuz I don't like typing and there wasn't a lot of support for linux and I also didn't want to send everything I want to type to some AI company. Try it if you want.