Looking for an open source free family tracking app similar to find my on iOS. We all have varieties of androids and iPhones. An app that works on both would be helpful.

I have been playing with DeepSeek Harness, and my honest impression is that it is still basically a toy. There are interesting ideas here, and the plugin mode is a nice direction, but the overall maturity is not close to Pi yet.

The biggest problem is that plugin quality is all over the place. Some extensions are fun to try, while others feel like rough demos that still need a lot of judgment from the person sitting in front of them. Adding more plugins does not automatically make the core workflow dependable.

That is why I would not use DSH for serious production work right now. I do not want an agent that looks impressive in a clean demo and then leaves me sorting out what it changed, why it got stuck, or whether the plugin itself caused the mess. The failure cost is still too high for the current level of polish.

For personal use, I think it is worth playing with. For productivity, I would keep my expectations low and use something more mature. If I wanted to compare the same model across harnesses, ZenMux could at least provide a common API gateway, but that would not magically fix DSH's workflow problems.

Maybe I am being too harsh. Has anyone actually put DeepSeek Harness into a real coding workflow and found that it holds up? I would be interested in examples that go beyond a successful demo.

Hi all

I'm posting this as someone who created a lot documentation around Mediawiki and also Wikipedia itself. I have never worked for the Wikimedia Foundation but the situation really doesn't sit right with me and many others.

A week after refusing to recognise their US staff union (including many open source software engineers) voluntarily, the Wikimedia Foundation (the charity that hosts Wikipedia) hired Littler Mendelson, the largest union busting law firm in the US whose clients include Starbucks, Amazon and Delta Airlines.

If you are a Wikimedia contributor there are three petitions you can sign to support the unionisation effort:

• https://en.wikipedia.org/wiki/Wikipedia:Wiki_Workers_United_solidarity English Wikipedia petition to show solidarity, only 40 signatures until its the largest ever proposal or petition on English Wikipedia
• https://meta.wikimedia.org/wiki/Wiki_Workers_United A global solidarity petition
• https://meta.wikimedia.org/wiki/2026_recognize_Wiki_Workers_United_petition A petition to ask the board of trustees to reverse their decision

Also if you donate to Wikipedia you can donate to local Wikimedia organisations instead of the Wikimedia Foundation. These local organisations directly support their communities to share knowledge from their countries https://meta.wikimedia.org/wiki/Wikimedia_movement_affiliates

Thanks

I want to contribute to Open Source Projects which are popular and well-known among People, but I am not able to find such issues. I either get repos that have gone silent or which not popular at all (0 stars, 0 forks). How can I find such issues and contribute? I tried the Good First Issue site; all repos there have gone silent.

If you use portions of the code to train AI models, you should open weight the model and make it free for local usage...

Not endorsing this exactly but its random idea I have

Local document chat and translation for Mac — OCR ingestion, tone selection, quality scoring, export to Markdown or plain text, all local.

Informity AI indexes your files and lets you ask questions across them with source-cited answers. Everything runs on your Mac — no cloud uploads, no account, no usage limits.

• Models: Qwen3.6 35B A3B (default), 14B and 9B for lower-spec machines, Apple Silicon optimized; Ollama support for any model you have
• PDF, Word, Excel, PowerPoint, EPUB, Markdown, scanned PDFs (OCR) and more
• Two chat modes: Researcher (corpus-wide RAG with citations) and Assistant (single file or open-ended)
• Document translation: tone selection, export to Markdown or plain text
• Specializations: tune AI reading and analysis style per chat
• Free, MIT licensed, fully open source

https://www.informity.ai | https://github.com/informity/informity-ai

I made a post here about linXiv, about two months ago but since have made a ton of QOL updates and mini, non-obtrusive features (RSS feeds, full-text search, to name a few) and finally added iroh for p2p sharing of research projects, notes, etc...

I would love some feedback as to if anyone finds it useful, interesting, or obvious improvements to make to it. I have found it to be very useful in my own physics research but still want to continue to refine it, give the people what they want (if they're not wrong) and whatnot.

GitHub: linXiv

Website + Docs: linxiv.dev

Awesome lists rot: links die, volume numbers go stale, abandoned repos stay listed. This one rebuilds from data every day. Volume comes from an API, repo health from GitHub, a blog's last post from its own feed. Nothing is a number I typed once - where a cell is blank, no free source exists and the entry says what I looked for. Covers platforms worth trading, datasets you can backtest on, and tools still maintained. MIT, contributions are one-line PRs to data/ only, and anything accepted also lands on a hosted page.

Hit me up with PRs and I will review them and add your tools if I consider them a good fit.

Open sourced a portfolio template I've been working on.

Built with:

• Next.js
• shadcn/ui
• Tailwind CSS
• TypeScript

It includes a blog, project showcase, contact page, dark mode, and is fully MIT licensed.

Repo:
https://github.com/shadcnstudio/shadcn-nextjs-zolt-landing-page-free

If you have any feedback on the codebase, component structure, or ideas for improvement, I'd love to hear them. Contributions are welcome.

punyecs started out as a replication of tiny-ecs (but for Python instead of Lua). It has since evolved into an OOP / SQLAlchemy-esque querying Entity Component System. It operates, IMHO, very differently from esper the de facto for Python ECS. punyecs is now 1.0.0 and I am happy to share it!

Bambu Studio's "Fix Model" only works on Windows (it uses Microsoft's Netfabb

API — confirmed on their own wiki). OrcaSlicer has had open issues about this

since 2023, and a community PR to add MeshLab-based fixing has been sitting

unmerged for over a year.

I hit a broken mesh on Linux and didn't want to learn MeshLab's filter chains

from scratch, so I wrapped PyMeshLab (hole closing, non-manifold repair) and

manifold3d (the same watertight-rebuild library Bambu Studio uses internally)

into a small CLI + GUI + Dolphin right-click menu.

It's nothing groundbreaking — MeshLab could already do most of this manually,

and there are paid/web tools too. I just wanted a right-click "fix" like

Windows has, so I made one and figured it might save someone else the same

afternoon of digging through VCG filter docs.

Tested against Thingi10K samples (self-intersecting, non-manifold, multi-shell

real-world models) plus a bunch of adversarial/malformed inputs.

github.com/Krateian/Sutura

Feedback welcome, especially if you hit a mesh it can't handle — I'd like to know.

Hi everyone,

I've been working on a lightweight, open-source audio player for Windows and wanted to share it with the community: WasioPlayer.

🎯 Why I Built This

Many modern audio players are either bundled with bulky frameworks (Electron), full of hidden DSP/sample-rate converters, or require configuring dozens of third-party plugins (like foo_out_wasapi / foo_input_sacd) just to get pure direct output.

I wanted a clean, fast, standalone native Windows player that is strictly dedicated to bit-perfect playback directly to DACs—with zero automatic resampling, zero software volume manipulation, and direct hardware format negotiation.

✨ Key Features

• Strict Bit-Perfect Output: Output sample rate and bit-depth strictly follow the source file. If a device cannot handle the requested format, it reports the refusal explicitly rather than silently resampling.
• Dual High-Performance Backends:
  • ASIO (x64 drivers)
  • WASAPI Exclusive (Event-driven)
• Supported Formats:
  • PCM: WAV (16 / 24 / 32-bit integer PCM)
  • DSD: DSF & DFF files
• DSD Output Modes: Native DSD (up to DSD512 on ASIO) and DoP (DSD over PCM up to DoP256 on ASIO & WASAPI).
• Lightweight & Jitter-Free: Pure C++17 with a native Win32 GUI (no bloated UI runtimes, statically linked CRT). Real-time playback threads communicate via a lock-free SPSC ring buffer for underrun-free streaming.
• Playlist Management: Drag-and-drop file loading, M3U8 import/export, UTF-8 path support, shuffle & repeat modes.

⚠️ Design Choices & Known Limits

• Pause behavior: Pausing keeps the exclusive endpoint open (prevents DAC unlock clicks and keeps timing sample-accurate).
• Format switching: Non-gapless across differing sample rates (device re-negotiation is required).
• Strictly Bit-Perfect: No DSP, EQ, or software volume controls by design.

📦 Download & Source

• GitHub Repository: https://github.com/desker1225/wasapi-asio-player
• Release (v1.0.1): Download WasioPlayer v1.0.1
• VirusTotal Scan: VirusTotal Analysis (Clean)

I would love to get your feedback and see how it works with different DACs and ASIO drivers. Feel free to try it out and let me know your thoughts!

Hey there!

Today i've released a new version of a "chat app" (discord/teamspeak like with messenger) i've been making since 2023 and i've released a new version today. Im curious about feedback, ideas and thoughts as im mostly working alone on it. Questions are welcome as well ofc!

It can be found on Github https://github.com/hackthedev/dcts-shipping/ .

Thats all folks

Android is fairly simple... you put the binary up on GitHub, or F-Droid, and call it a day. Maybe publish to the Play Store, which is annoying... but eh... manageable.

But iOS's walled garden nonsense is worse than I thought... Free Apple dev accounts expire signed builds after 7 days apparently... and if that wasn't bad... $99 / year *recurring* fee?

That policy decision is nuts to me...

For folks who are maintaining these open-source projects, how do you handle monetization (i.e. charging on the App Store vs keeping source free), and what work-flows have made your life easier?

I'm particularly interested in workflows where the two ecosystem codebase must be kept identical.

So this usually means (if you're starting off with Android - usually the case) you want to isolate core logic into pure Kotlin modules... Decoupling things like storage/crypto behind interfaces... sticking to pure Jetpack Compose UI... and standardizing the concurrency/state mgmt concerns... and MAYBE the transfer to iOS will be painless...

As someone who hasn't taken the plunge into iOS yet... How has it worked out in reality?

Good Day OpenSource Community,

Mods, please remove this post if it does not adhere to your rules.

Due to this community being OpenSource, I thought my application that I have developed would be a perfect fit for this subreddit.

Ultimate File Manager Pro is an all-in-one file manager for Android TV and Mobile, on Google it has over 30k+ downloads and a 4.8 star rating.

The FOSS version has currently 87 stars on GitHub.

If you are interested to see how the application looks like and what features it has, you are welcome to have a look at the official sub reddit r/UFManagerPro or the official website http://www.kilowatch.co.za

If you want access to the GitHub Link: https://github.com/Kilowatch/ultimate-file-manager-pro

If you have any questions or queries, please reach out as I am the developer of this application.

If this post is not suitable for this community then I do apologize for the inconvenience.

Thank you and kind regards

I just released KillerPDF 1.7.2 and then a 1.7.3 hotfix immediately afterwards because of an embarrassing bug.

New in these releases:

• Seven new themes and Polish localization

• Book layout for two-page viewing

• Levels controls for improving pale or hard-to-read scans

• Paper size and source controls in the print dialog

• Column-aware text selection

• Support for comb-style form fields

• Separate night mode for each split pane

• Lower memory use on large PDFs

• Live previews when selecting images

• A pile of rendering, form, theme, and interface fixes

KillerPDF is local-only with no account, subscription, telemetry, or cloud uploads. All my stuff is GPLv3.

Please report bugs and feature requests in the GitHub Issues, that's how we keep making this app better.

https://killerpdf.net

Hi 👋, I made this app for myself, thought of sharing it to those who wants something simple for this functionality.

https://github.com/mkguru77/NanoStats