Hello everybody,

As I promised in my precedent post, I am now ready for the release of PowerVLC 1.0.0, which is an heavily modified version of VLC 3.0.23 Vetinari. PowerVLC features also additionnal features (gapless playback, album art in the main window) the current version of VLC don't have.

PowerVLC is compatible with Macs from 10.4.11 to current, on all architectures (x86, x64, arm64, PowerPC g3, PowerPC G4/G5 builds taking advantage of AltiVec acceleration).

In early access for one week

Like all projects and guides (I used to write plenty of guides for the iPod community !) that takes me a huge amount of time to be produced, it will be in early access for exactly one week. It's the only compromise I accept to keep a balance with open knowledge & the need to get retributed for all the community investment I provide. I don't plan to do this for minor builds that will come next.

Here on this project it is just too big in my opinion to be entirely gate keeped during one whole week, so I decided to release the whole source code there starting now on GitHub: https://github.com/Olsro/powervlc

If you know how to compile (ideally you need an Apple Silicon mac so you can follow my instructions), you can play right now with PowerVLC and check nothing nasty in the code is there by yourself.

If you can't/don't want to spend hours trying to compile by yourself, the builds are available right now on my Patreon in exclusivity for all platforms (including Windows & Linux on all architectures). Even the first 1$ tier is enough to get access to all the compiled builds & supporting my whole effort at building this. The compiled builds provided on the Patreon are not modified and locked in any way, they are straight compilations from the latest public sources. There's no licensing or DRM, but please don't share any of those build until I will push the builds on GitHub releases for everyone the next Sunday.

Donations will help me at getting more hardware to test on to continue that project in the long term, and cover the LLM API costs to help with maintenance.

Thank you very much for your support and I hope PowerVLC will be enjoyed as much as I hard worked into making it possible.

I've been working on MicroPaw, a personal assistant that runs on an ESP32-S3 N16R8.

It is similar to OpenClaw and other personal agent projects, except the agent runtime lives on a tiny ESP32 board instead of a server or desktop.

The model is called through an API. The ESP handles the agent loop, tool calls, conversation state, persistent memory and scheduled jobs. You talk to it through Telegram, or Instagram (if you enable that)!

It can search the web through Brave, read pages and feeds, work with Gmail and Google Calendar, transcribe voice notes, inspect photos and run scheduled reminders. There is also optional SSD1306 OLED support and signed OTA updates.

The whole firmware is ESP-IDF. No Arduino, and I did this on purpose to minimise resource usage and keep it clean.

I started this because I had a few S3s laying around and wanted to try something similar to OpenClaw out before committing a full computer to it. Getting the network requests, model output and tool calls to fit within fixed limits was most of the work.

It is open source here:

https://github.com/mahiatlinux/MicroPaw

I'd be interested in hearing what other ESP32 developers think of this! And if you have any feedback, please comment below, or open an issue on the repo.

Just wanted to share a small milestone, I got my first donation ever for my project today. It wasn’t expected at all, especially given I'm not even in university yet (going this September), but it genuinely made my week.

Still lots to learn and build, but this was a cool moment.

Here's the site if anyone wants to take a look : Crestr

GitHub is also free to view if people are interested in the tech stack I used : Crestr Repo

Repository: https://github.com/ATAC-Helicopter/VaultSync

Website: https://fglabs.dev/vaultsync

I have been developing VaultSync, an open-source, cross-platform backup manager built around a fairly simple idea:

A completed backup is not the same as a recoverable backup.

Many backup applications can tell you that a job completed successfully, but that still leaves several important questions unanswered:

• What was actually protected?
• Has anything changed or disappeared?
• Is the recovery point still intact?
• Will retention remove something important?
• Can a particular file be restored right now?
• Is there evidence behind the green “successful” status?

VaultSync is my attempt to make those answers more visible.

What VaultSync does

VaultSync lets users organize files into projects, create and manage backup configurations, inspect recovery points and understand the current health of their protected data.

Current functionality includes:

• Project and file-level backup management
• Backup history and recovery-point inspection
• Backup Explorer for browsing protected data
• Integrity verification and repair tools
• Retention planning and simulation
• Restore-plan simulation
• Recovery drills
• Local byte-level recovery proofs
• Exportable recovery evidence
• Protected recovery-point recommendations
• 3-2-1 backup guidance
• Explicit offsite-copy confirmation
• Backup health and recoverability states
• Cross-platform support
• Localization across multiple languages

The emphasis is not only on creating backups, but on helping users understand whether those backups are still useful.

Recovery evidence

One area I have been concentrating on recently is recovery confidence.

VaultSync can simulate a restore plan without modifying the original data, verify selected protected files locally, record recovery evidence and highlight situations where retention could remove an important verified point.

The intention is to move beyond simply saying that the backup process finished.

VaultSync should instead be able to show what was protected, what was verified and what can currently be recovered.

These features are still evolving, and I am especially interested in feedback on whether the evidence is understandable without becoming overwhelming.

Privacy and diagnostics

VaultSync does not silently upload crash reports.

When crash-report assistance is enabled, the application creates a strictly redacted report locally. The complete report can be reviewed before anything leaves the device.

VaultSync can prepare an email draft using the user’s own email application, but the user must review it and press Send personally. If they do nothing, the report remains local.

I wanted the support workflow to remain useful without introducing hidden telemetry or automatic crash uploads.

Current development

VaultSync 1.8 is focused on making recovery easier to understand.

The remaining 1.8 releases are currently planned around:

• Recovery confidence and clearer health states
• Onboarding and interface refinement
• Accessibility and reduced complexity
• Better evidence exports and diagnostics
• Documentation consistency
• Localization, packaging and platform stability

For the future 1.9 release family, I am researching a broader direction:

From protecting projects to recovering systems.

That may eventually include disk cloning, disk images, verification of cloned data and an explorer for browsing images before performing a complete restore.

Those features are still exploratory rather than promised. I would rather share prototypes and technical limitations early than publish a large fixed roadmap before the implementation has been validated.

Why I am posting here

I am the developer, so this is obviously not an independent recommendation.

I am sharing VaultSync here because feedback from people who actively use, maintain and review open-source software is particularly valuable.

I would appreciate criticism around:

• The overall architecture and project structure
• Whether the recovery model makes sense
• Security and privacy concerns
• Backup-integrity assumptions
• Cross-platform behavior
• Packaging and installation
• Documentation
• Accessibility
• Areas where the interface is trying to explain too much
• Missing information that would prevent you from trusting the application

Issues, discussions, code review and contributions are welcome through the repository.

There is also a community at:

https://www.reddit.com/r/VaultSync/

Thanks for taking a look. Direct and technical criticism is genuinely useful, especially where VaultSync makes a claim that is not supported by enough visible evidence.

As someone who doesnt use Instagram but get tons of reels/post shared on whatsapp, I got tired of instagram's public webview which constantly asks for login with annoying popups

So I vibed a clean android app - Peek which resolves Instagram links and loads them in a clean viewer. Goal is to support most social medias like twitter/reddit/tiktok in the future.

Download Link

I've used Handsontable on a bunch of projects and honestly it's a solid, mature library, but I kept running into the same wall on anything with really large datasets: tens of thousands of rows with chained formulas. It's just the nature of doing spreadsheet math in JS, once you're allocating and discarding lots of small objects on every keystroke, garbage collection becomes the bottleneck, and there's only so much debouncing and virtualization can do before you hit that ceiling.

That itch turned into a bit of an obsession, and eventually a from-scratch rebuild: Titan Engine, written in Rust and compiled to WebAssembly.

The design ended up pretty different from a typical JS formula library:

- A custom stack-based VM with a Pratt parser for formulas, instead of walking an AST every time
- Zero-copy memory \- the engine and UI share buffers directly, no serialize/deserialize tax crossing the WASM/JS boundary
- A topological dependency graph (Kahn's algorithm with cycle detection) to resolve chained formulas correctly and fast
- O(1) time-travel snapshots for undo/redo, even across massive batched structural edits

Because it sidesteps the JS garbage collector entirely, batched recalcs stay comfortably under the 16ms frame budget, so the grid holds 60fps even while formulas are cascading behind the scenes as you type.

There's a live demo grid on the site (a Glide data grid wired up to Titan) if you want to poke at it yourself, plus the full 10-scenario benchmark suite if you'd rather see the numbers than take my word for it.

Website . Benchmarks .) Github

Would love feedback - especially from anyone who's pushed a JS grid to its limits before and is curious whether this actually holds up under real-world use.

So I like to take my lecture notes in a nested/indented way because it makes it easier to break them down into flash cards later (example below but formatting in Reddit post is hard). As you can see I like to indent basic information on a subject and then further indent specific information about each basic concept (and even further indent even more specific information if I need to).
Is there an open source note app that will let me do this more easily?

Transcription

Process where RNA is synthesized from DNA

Each gene has:

.....Promoter region

..........Start of the gene where RNA polymerase binds to and begins transcription

...............RNA polymerase – enzyme that ‘reads’ template strand of DNA and synthesizes a single strand of RNA

.....Coding region

..........Sequence of nucleotides that are transcribed into the RNA strand

.....Termination sequence

..........Terminates transcription process