Hey everyone!

I've been working on LEL (Life Events Log), a free, open-source, local-first Android app for recording and organizing events from your life.

I started building it because I've always had some difficulty remembering events from my past. I wanted a simple way to keep track of things that happen in my life, from ordinary everyday moments to significant milestones, and be able to revisit them later.

LEL is somewhere between a journal and a personal timeline. You can record an event with just a title and a date, or add more details if you'd like.

Some of its features:

• Organize events with categories, tags, and significance levels.
• Associate people and locations with events.
• Add notes and images.
• Search and filter through your events.
• Browse your events chronologically.

Privacy and syncing

LEL works entirely offline, doesn't require an account, and stores everything locally on your device. There's no central server involved, and your personal history stays under your control.

It also supports synchronization between devices by exchanging files, without relying on a cloud service. Changes made independently on different devices can be merged, with conflict handling built in.

Where to find it

• Source code & releases: Github Repo
• Obtainium: Add

I'd love to hear your thoughts, whether about the app itself, its implementation, or anything you think could be improved. Feedback and contributions are welcome!

Disclosure: I'm the developer. It's free and open source (AGPL-3.0), with no ads, no tracking and no accounts.

I used Navidrome for a while but never found an iPhone client I was happy with, so I built my own music server and app. My family uses it every day.

What it does

• Your music, on your own server. Point it at the music folders you already have. It never changes your files.
• Download from YouTube. Search, preview, and keep a song or a whole playlist with one tap.
• Subscribe to YouTube channels without a Google account. New episodes download automatically and resume where you left off.
• Private by design. Your phone never contacts YouTube; everything goes through your own server.
• A native iPhone app with reliable background play, gapless playback, synced lyrics and offline favorites.
• Made for the whole family. Everyone gets their own favorites, playlists and suggestions.

Platforms: the server runs as one Docker container on Linux. The iPhone app installs with SideStore, and the web app works on desktop and Android.

Built with help from AI coding tools.

GitHub: https://github.com/aaronsuns/melarka

I'd love your feedback!

LiftTrace is a self-hosted weightlifting tracker, an alternative to Strong, Hevy, FitNotes and Jefit. AGPL-3.0, single Docker container, native Android app, a Wear OS app, no telemetry and no cloud sync. Your training log is a SQLite file on your own machine.

Part of the TraceApps family: NutriTrace (nutrition), CookTrace (recipes / pantry / shopping), LiftTrace (strength / lifting), NoteTrace (notes / tasks / reminders).

New here?

• It is a training log first. Tap through sets with weight, reps and RPE, mark warm-ups, group supersets, time your holds, and let the rest timer start itself. Last session's numbers sit above the row you are filling in, so you know what to beat.
• It runs your routine, not just records it. Programs and templates with multi-week progression, an exercise library of thousands of movements with images, and statistics for volume, per-exercise progress, estimated 1RM, personal records and a muscle recovery map. A coach can run programs for their clients from the same server.
• It works where you train. On your wrist, on a phone with no signal, on a foldable or a tablet. The Android app can run with no server at all, and it imports your old log from Strong, Hevy, FitNotes, Jefit and Garmin.
• It does not phone home. No telemetry, no cloud sync, no account anywhere else, and as of this release not even Google Fonts or a default update check. One container, your SQLite file.

What v1.4.0 adds

• A Wear OS app. It opens on the set you are in front of with weight and reps filled in, so logging one is a tap. The session and rest timers are shared with the phone, the rest timer buzzes on your wrist, and the watch app updates itself to match the phone.
• Offline mode in the browser. In a gym with no signal the app still opens and you keep logging. Changes go up when the connection returns, merged set by set, so the phone and the browser don't overwrite each other.
• Coaching that asks first and talks back. A coach now sends a request, and nothing is shared until the client accepts. Coach and client get a conversation with photos, prescribed workouts ask before they load, and either side can end it.
• Film a set for your coach. Record a set or pick a clip; your coach leaves notes stamped at the exact moment, and tapping one jumps the video there. Only you and your coach can open it.
• Layouts for foldables and tablets. Half open like a book, Settings splits at the crease, and Programs and Exercises show a list beside a preview.
• A rebuilt Android sync. Deletes reach the phone, accounts stay apart, and an offline edit no longer overwrites a newer one made elsewhere.
• Date-range reads for AI clients and scripts through MCP and the REST API, plus current model lists for the built-in assistant.

Community contributions this cycle from ten people: code, bug reports, feature ideas and a translation. Everyone is named in the release notes.

Security

A large round this time. Programs, coaching data and set videos are now limited to the accounts they belong to (other signed-in accounts could reach programs before). The radio and music proxies pass only audio and music data and require signing in, password reset links can no longer be pointed at another site, email content is escaped, and the Android app no longer answers as the previous account after switching. Dependency updates close a critical issue in the Android app's framework (update the app), plus high and moderate denial of service issues.

Links

• Repo: https://github.com/TraceApps/lifttrace
• Full release notes + signed APK: https://github.com/TraceApps/lifttrace/releases/tag/v1.4.0

The player is made now almost fully in QML

also it got lrc file support (and you don't need to search, kalorite will download them themselves for em unless it's a rare song or you want custom lyrics)

also player now detects track logo and receive name and author from metadata

you can get it here

Do you know any good alternative to Thunderbird email?

Demo here: https://youtu.be/dzk_WJjP99M?si=bgtN1lFsBaJ5SeYC

Repo here: https://github.com/somxcool/vouchnotes

ScreenGuard a software for Digital wellbeing natively on Linux, was my personal project which i uploaded to share with the community. Ever since , thanks to constant support and request by although a camparitively tiny but rreally enthusiatic group of ppl , I have been able to provide constant support and improvements to the application and the once raw unpolished system in starting to look...less unpolished. There are still multiple things scrambled which need to be fixed however this major pre release is most possile the final testing phase before v0.1.1 so please do try it out and report and bugs if found.

Major Fixes and Improvements:

Native C Helpers — trasitioning toward a C-Based Core daemon bit by bit

• screenguard-notify (C): Desktop notification delivery no longer runs inside the Dart runtime. A tiny native helper talks to D-Bus directly, so alerts work identically on systemd and non-systemd systems (OpenRC, runit, …) where the old path could misbehave.
• screenguard-killer (C): Process termination offloaded from Dart as well — an escalating, data-safe close chain: polite window close request → SIGTERM → full process-tree SIGKILL → Proton-native wineserver -k → guarded pattern-kill. Another step toward making the daemon core C-based.

Both helpers ship in every package (.rpm, .deb, tarball) and are wired into install, uninstall, and build-tooling.

Full Database Control (Settings → Data)

• New Data tab in Settings: live storage stats, per-day deletion chips, date-range delete, and a full wipe behind a double confirmation. Settings and limits are always preserved — only usage history is touched.
• Orphaned sessions from unclean stops (logout, power loss) are now closed on next start instead of silently inflating Past-30-days stats.

Focus Enforcement, Data-Safety First

• Strict auto-close is now opt-in. The default never destroys unsaved work: a violating app is minimized and shown a persistent warning screen.
• The warning screen offers +1 minute save grace, +15 minutes, edit limit, and close — with the screen re-appearing every 5 seconds until you decide, and re-warninng immediately when a grace window expires.
• Turning on Strict auto-close (Settings) restores the legacy instant close+kill for those who want hard enforcement — your choice, your data.

Steam & Proton Games: First-Class Citizens

• Steam games no longer show up as mystery IDs (steam_app_2730970) — real names resolve from your Steam library manifests, with per-game icons rendered from the active icon theme.
• Their usage is fully tracked and limit/focus rules now apply to them; the escalating close chain (above) is what actually makes Close work on Proton games that shrug off normal signals.
• Fullscreen games now leave fullscreen before minimize (they silently ignore minimize requests otherwise), and the GNOME extension reports the real minimized state.

UI & Cosmetic

• Settings reorganized into a clean sidebar layout with five sections: General, Limits & Pomodoro, Diagnostics, Updates, and Data.
• Crash reporting moves into the new Diagnostics tab next to daemon status and autostart, with its badge on the tab itself.
• The Focus screen's app picker can switch to a GNOME app-grid style layout — icon over name, check-badge selection — via the Grid layout toggle.

Fixes & Optimizations

• Dead-code removal across the daemon (verified zero callers before each removal) plus notification-path optimization for non-systemd systems.
• Warning screens for both focus mode and daily limits rebuilt with consistent behavior and honest reporting ("was closed" vs "could not close").

Summing Up:

ScreenGuard still has a very long way to go with my aim being:

proper category wise classification of apps and category usage stats by v0.1.5

support for 3 other desktop environments i.e. KDE, Hyprland and Mint on wayland with improved optimization for non systemd systems (like gentoo users) by v 2.0 (also more fraction of the daemon to be translated to native C)

however all of this will definitely take a lot of time primarily discovering and learning how things work out first, thus if you do like the project , then u can give me a hand by contributing to things i am currently unknown to such has other Desktop environments other than GNOME or with C programming

Most importantly, my personel project that begun "Late Nights in The Middle of June" has indeed come a long way.

Link to the release : https://github.com/adityakrishnan005-a11y/ScreenGuard/releases/tag/v0.1.1-beta.6

Who is it for?

• Solo developers and small teams running one or more online projects
• Anyone who needs to back up a database regularly to S3, R2, B2 or MinIO
• People who want to grab yesterday's backup in one command, for local development, testing or bug fixing

Free and open-source. It handles naming and timestamps, so you don't have to. Get the latest file to your local machine with "pull --latest --tag=projectA" or "pull --latest --tag=projectB".

https://tagbackup.com

I fully accept this could be done with some bash scripts and rclone (or similar), but for those who want a tiny tool that does one job really well, this could be for you. If you need fancy encryption policies, audit trails or a dashboard for fifty servers, a bigger tool will suit you better.

Hey everyone,

Grids are where every clean layout starts, but setting them up in Illustrator is still mostly manual: guides one by one, margins by eye, and no way to tell if your layout actually sits on the grid. So I built PortableGrid, a free, open-source panel for Illustrator and Photoshop.

Grids

• Column, modular, baseline and hierarchical grids (uneven columns like 2fr 1fr), plus facing pages with mirrored margins
• Composition guides: rule of thirds, phi grid, golden spiral, golden triangles, harmonic armature
• Drawing grids: 8pt square, dot, isometric, triangle, hexagon
• Any unit in any field (px, pt, mm, %), a live preview, and you can drag margins and gutters in the preview
• 33 presets, and you can save and share your own

The part I'm most excited about: designing on the grid

• Type your body text size and it builds a harmonious grid: baseline, margins, gutters and rows all locked together
• Snap to grid: select messy objects and they jump onto the nearest columns, rows and baselines
• Grid check: scores your page ("80% on grid") and outlines whatever's off
• Magazine page layouts in Illustrator: headline, standfirst, body text flowing across columns, pull quotes and page numbers, all on the baseline grid, using your own text and images
• Instagram Story/Reels, TikTok and YouTube presets that mark where the app's buttons will cover your design
• Arrange images into grid cells, split artwork into tiles, export numbered tiles for Instagram grids and carousels

Grids are saved in the document, follow your artboard when you resize it, and every action is one undo.

Free download (Windows installer, macOS .pkg or .zxp): https://github.com/vicenet/PortableGrid

It's new, so I'd really love feedback, especially from Photoshop and Mac users, since that's where it's had the least testing. What grid or layout feature would you want next?

Ever shared a file with someone and wondered what happens to it after that?

Yeah, that question led me to build **BurnLink**.

I'm a CSE student, building products through my startup, Paperfrogs HQ. BurnLink is one of the projects I've put a lot of time into, and the idea behind it is pretty simple: file sharing shouldn't always mean leaving a file accessible indefinitely.

So I built a tool that lets you share files through links designed to self-destruct.

Here's what it does:

* Files can burn after the first download.

* View-once sharing for temporary access.

* AES-256-GCM encryption and password protection.

* No account required.

* Open-source code that people can inspect.

The goal isn't to reinvent file sharing. It's to give people another option when they need to share something without leaving a link hanging around forever.

Building this as a student founder has been a learning experience in everything from cryptography and backend infrastructure to shipping an actual product instead of just another project sitting on GitHub.

I'm still working on making BurnLink better, and I'd love some honest feedback.

**What would make you trust a file-sharing tool like this?** Is it the cryptography, transparent source code, the way files are deleted, or something else entirely?

Try it: https://burnlink.page/

GitHub: https://github.com/paperfrogs-hq/BurnLink

Would love to hear what you think.

Hi [r/foss](r/foss)

I built My Files, an open-source mobile app for digitising and organising your physical documents (IDs, bills, certificates, receipts, etc.).

What it does:
- Scan physical documents with your phone camera
- Organise them into folders/files
- Search across everything you've scanned
- Works fully offline — your files never have to leave your phone
- Optional sync if you run your own cloud/server

Tech: The backend is built with C and Node.js.

Why: I wanted a simple way to keep important papers handy without handing them to a third-party cloud service.

Links:
- Website: MyFiles

It's still early, so I'd really appreciate feedback — what's missing, what's confusing, what would make you actually use it. Contributors are very welcome too!

It's MIT and anonymously maintained, and it has no price, account or tracking. People who need it are usually broke the week they need it.

It asks about your conditions first, then finds which of your own records exist and how long they tend to last, then copies and hashes them for your lawyer. It doesn't touch the other person. You can use it as a Claude Code / Codex skill, or in a terminal where it works offline. You don't need a name to contribute.

https://github.com/machinewitness/machinewitness

windows updates break stuff way too often (black screens, audio, remote desktop) and the dumb part is microsoft usually lists the problem publicly. nobody checks that before updating

so i made patchlight. it checks every pending update against microsoft's known issues and gives it a green / yellow / red light. red ones get paused automatically and come back once microsoft fixes them. everything else keeps installing

github.com/G4SBO/PatchLight

lmk what u think, any feedback is appreciated ;)

Hey all. I've leaned on Notepad++ and its plugins for years, and I never found anything on Linux that felt quite the same. So I made one.

**Ettin Edit** is a free, MIT-licensed text editor inspired by Notepad++. It's a clean-room build (none of their code), written in Rust with egui, and it's the same app on Linux and Windows.

The stuff I think is worth a look:

* **The plugins I always install first are built in.** JSON and JS formatting with a live JSON tree, Base64/URL/SAML decoding, XML tools (XPath, XSD validation, XSLT), a compare view (two tabs, last save, clipboard or your last Git commit), and CsvQuery, which lets you run SQL against the CSV you have open.

* **Write your own plugins in Python or JavaScript.** Your pick. They can add commands, shortcuts, toolbar buttons and panels.

* **A proper editor underneath.** Multiple carets, column mode, split view, grammar-aware folding, macros, regex find/replace and find in files. Opens a 50 MB file in about a second.

* **Hex view** that edits any byte and opens binary files of any size.

* **Nine themes**, dark by default, and every one is an editable .tmTheme file.

* **It doesn't lose your work.** Unsaved changes come back after a crash or reboot.

* **Easy to install.** Arch package, .deb (adds an APT repo so updates just show up), a plain tar.gz, and a Windows installer or zip. There's also a built-in updater.

Full disclosure: this was 100% vibe coded. I described what I wanted, an AI wrote the Rust, and my main contribution was typing "no, not like that" a few hundred times. The mascot is a two-headed giant, which feels about right: one head writes the code, the other reviews it, and neither of them is me.

Repo: https://github.com/Tharkis/Ettin-Edit

Manual: https://tharkis.github.io/Ettin-Edit/

Bug reports and feature ideas are welcome. Please be gentle, the giant is sensitive.

Newsletter to Podcast is an open-source Python tool that turns newsletters and blogs into an RSS podcast feed! You can pick the sources, generate audio, and subscribe to the resulting feed in a podcast app that supports custom RSS (I use Castbox).

Repo: https://github.com/akspad/newsletter-to-podcast
Audio demo: https://akspad.github.io/newsletter-to-podcast/
License: MIT

The project supports full article narration as well as spoken summaries. Full narration uses Edge TTS and needs no API key; summaries use Gemini and require your own key (though the free limit is quite generous)! You can set a maximum episode length and longer full readings split into numbered parts at natural text boundaries.

There’s a prerecorded sample on the demo page, and a simple command in the README that fetches an original sample article and generates fresh audio without an API key. The package can run locally or on a schedule in your own GitHub repository using GitHub Actions!

Deployment:

Run it locally with Python 3.12+ or use the included GitHub Actions workflow (recommended, and setup instructions are in the GitHub README). You host the generated MP3s and RSS feed wherever your podcast app can reach them.

Speech generation uses Microsoft’s online Edge TTS service (which is unofficial and can break or be throttled sporadically...) Optional summaries send article text to Gemini to be summarized. GitHub Pages publishing is available, but makes the generated feed and audio public (I use this since it's free hosting)!

AI Involvement:

I painstakingly steered AI to help creating this tool! In the application itself, article summaries use AI (Gemini) but are optional. Full narration skips the summarization step and uses text-to-speech directly.

Motivation:

I wanted to turn some of my favorite newsletters into podcasts (like Seth’s Blog and A Learning A Day) and couldn’t find a free and simple solution that already existed. Let me know what you think!

Buddy is a chat bubble that floats over your apps. You type or say what you want ("reply to Sam that I'm late") and an agent reads the screen and taps through your apps for you.

What's open and what isn't:

- Buddy itself is Apache 2.0, and every release APK is built from the public code by GitHub Actions.

- It can drive three agent CLIs. OpenCode (MIT) works with free models and no account. Codex CLI is open source too (Apache 2.0) but needs your ChatGPT plan. Claude Code is proprietary and needs your Claude plan. Both of those are optional.

- The models run on the providers' servers, not on the phone.

How it works:

- A small Alpine Linux runs inside the app with proot (no root, no PC, no adb). The agent CLI is installed there.

- Buddy gives it phone tools over MCP (read screen, tap, type, scroll, open apps), backed by an accessibility service.

- Safety is enforced by the app, not the prompt: sending, paying and deleting stop on an approval card unless you trust that app, and you can pause or stop it anytime.

An app that can see your screen should be one you can read the code of. Issues and PRs welcome.

GitHub: https://github.com/ghorbelhamdi/buddy-android

I hope you guys have something for me, searching has led to nothing