I'm glad to announce v0.4.5 release!

Syncspirit is continuous peer-to-peer realtime syncrhonization tool. It implements BEP protocol and provides seamless interoperability with existing syncthing nodes and clients.

https://raw.githubusercontent.com/basiliscos/syncspirit/refs/heads/master/docs/fltk-overview.gif

You can download ready-to-use binaries for Linux x86_64 (AppImage), Windows 32 bit (WindowsXP is supported), Windows 64 bit and Mac OS X (Apple silicon).

Notable changes:

• [core] monitor local filesystem changes in realtime and propagate updates across the cluster (inotify/ReadDirectoryChangesW/kqueue)
• [core] allow arbitrary subfolder rescan
• [core] do not accept files with non-valid utf8 filenames
• [ci/cd] use https://sourcecraft.dev/ infrastructure for building
• [core] bugfixes

Syncspirt source code uses GPLv3 license.

Any feedback is welcome!

WBR, basiliscos.

Do any of you guys now a company that produces quality mice where their firmware is open source and can be flashed/programmed with opens source software?

I've been downloading legally purchased ebooks (ascm files) and using Calibre to trick it into thinking that it's Adobe Digital Editions and then removing the DRM. lcpi seems like a new format, and I don't know what to do with it. Any suggestions?

EDIT: Sorry, "lcpl" not "lcpi"

hey everyone, I wanted to share a project I’ve been developing for the past two weeks. I had tried to find a minimalist open-source bad-habit tracker, but I didn’t like the ones I found or ran into some issues. So I decided to build one using the stack I know best. I added some features like setting a target number of days with a progress bar toward that target, notes, and a feed to save articles, news, or video links that help you stay focused on your goal. there’s also an option to set a password to access the site, and both light and dark themes.

Severin Schols of MakerVan Labs has created the open-source hardware OSHW Coloring Zine, a booklet with pictures and descriptions of various open source hardware projects. It’s perfect to colored in.

Discarr is a self-hosted web UI that bridges disc rips (VIDEO_TS / BDMV / ISO) into Sonarr and Radarr. Scan a disc directory, map the titles to the right episodes or movies in the browser, and it handles the encode queue and arr notification.

Stack: Pure Node.js 18+, no npm packages, only built-in modules. Requires ffmpeg and ffprobe on the host; HandBrake optional. Docker image bundles both.

License: GPL-3.0.

Forgejo (primary): https://git.opensourcesolarpunk.com/Circuit-Forge/discarr GitHub (mirror): https://github.com/pyr0ball/discarr

Still early, issues and PRs welcome.

Meta has sold 7M+ Ray-Ban glasses that look identical to normal glasses but can record you silently.

NoPeek detects them using immutable BLE manufacturer company IDs - signals that cannot be randomized or hidden unlike MAC addresses.

Detects: Meta Ray-Ban, Snap Spectacles, Oakley Meta, TCL RayNeo, Meta Quest, Apple Vision Pro, Pico VR and more.

No ads. No tracking. No internet permission. Fully open source. MIT license.

github.com/getnopeek/nopeek-android

Are anyone up-to-date on the status of the syncthing-fork on Android, following the drama of catfriend1's sudden disappearance and the less-than-trust-building behavior of researchxxl? Did they rebuild that trust? Was it forked again by someone more trustworthy?

https://github.com/gary-host-laptop/ushiro https://addons.mozilla.org/en-US/firefox/addon/%E5%BE%8C%E3%82%8D-ushiro/

Every image a website doesn't want you to have is still there — just gated. Ushiro drops you behind the scenes to find it. Background images, clickable decoys, alternative resolutions, inline SVGs, base64 chunks, shadow DOM. If it rendered on your screen, you can take it.

I forked behind! extension and added a little extra touch, plus some improvements

• How can iodéOS (Lineage fork) be installed on phones with bootloaders locked?
• Why would phones like the Samsung Galaxy A7 (2017) and Note 9 appear on their list of phone that it can be installed on when it has "no" across the board on this list?
• On phones with the bootloader locked, does it just sit on top of the existing android OS?

Sorry for all of the questions, but I am looking at as many options as possible available with a decent phone and camera long term to move away from Android and Google completely. I have done in the past, but looking for semi long term for when Android becomes locked down.

I just don't understand how they can create an installer that works with bootloader locked phones, and then the OS remain completely secure.

TIA

Source code and details: https://github.com/umutcamliyurt/IrisChat_TUI

Features:

End-to-end encrypted DMs

• Signal Protocol (X3DH key agreement + Double Ratchet) over IRC private messages
• Post-quantum key encapsulation with Kyber-1024 in the initial handshake
• Compatible with the IrisChat Android client

Security & storage

• Password-protected local keystore (AES-256-GCM, PBKDF2-HMAC-SHA256 with 310 000 iterations)
• Encrypted SQLite message database (all message fields encrypted at rest with AES-256-GCM)
• Master key zeroed in memory on lock

There are different versions of the GPL license, ranging from the lightweight copyleft LGPL to the strong copyleft AGPL.

But if the LGPL is a lighter copyleft version of the GPL, why isn't there a lighter copyleft version of the AGPL?

I wonder if this has something to do with the EuroOffice drama. It's too bad, this was the only decent FOSS office app for Android.

Edit: Some commenters say this may not have been fully FOSS despite some of the code being published.

Hello!

As some of you might be aware, copyright law and precendence in the EU show a bit of a difference in the FOSS license landscape compared to for example the US. Particularly, I am talking about linking in the context of derivative work. I tried to do some research here, but I didn't manage to find any conclusive articles or discussions on the matter.

As both dynamic and static linking in the EU is generally considered as a question of interoperability rather than derivative work, linking-wise virality of licenses like GPL are basically void over here. The EUPL license (my license of choice) as per my understanding even explicitly claims that "derivative work" is a definition out of scope of the license text due to this. I today read about additional possible AGPL violations uncovered from BambuLab regarding not opensourcing a .so library that the software uses. This made me wonder: what stops someone from taking a copyleft project in the EU, and adding all their heavy modifications basically as callouts to a proprietary dynamic library? Do I only have to publish the modified source full of single line callouts, without the library source?

I built an orbital graph as an alternative navigation for my open-source messenger

Most messengers display conversations as a static list. I wanted to try something different.

In ONYX v1.5-beta I added Account Graph — an alternative navigation mode where your chats, groups and categories become nodes in a dynamic orbital system centered around your account.

The idea came from Obsidian's graph view. I adapted the concept for a messenger context.

Honestly, when I started building it I was pretty sure it would end up useless. Just a visual gimmick. But somewhere during development that changed. When you have a lot of chats across multiple categories, the graph gives you a better spatial sense of where everything is. You navigate by structure rather than scrolling through a flat list.

How it works:

• chats, groups and categories are displayed as connected orbiting nodes
• online users are highlighted via presence glow
• orbit speed is adjustable
• animations can be paused entirely
• graph position persists between sessions

The entire thing is optional and can be disabled at any time.

GitHub: https://github.com/wardcore-dev/onyx/releases/tag/v1.5-beta

Feedback is welcome!

When I first started working on open source projects, I really struggled with documentation. But after a lot of trial and error, I learned a lot about writing clear and helpful docs. Working on several open source projects has also taught me just how essential good documentation is to the success of a project. So, I'd like to share with you some of the tips that have helped me improve (hoping that they will save you the same headaches I've experienced ):

1️⃣ Guide first Start with simple guides that focus on common use cases to help users get started quickly.

2️⃣ Show, don’t tell Use screenshots & screencasts early & often to visually demonstrate features.

3️⃣ More code than text Prioritize clear, working code examples over lengthy text explanations.

4️⃣ Use plausible data Craft realistic data in examples to help users better relate & apply them to their projects. I use faker.js for this.

5️⃣ Examples as stories Write examples in Storybook to ensure accuracy & consistency between code & visuals.

6️⃣ The reference follows the guide If an advanced user is looking for all possible options of a component, they can find them in the same place as the guide.

7️⃣ Pages can be scanned quickly Break content into short, digestible sections for quick navigation and easy reading.

8️⃣ Features have several names Use multiple terms for the same feature to improve searchability.

9️⃣ Document features multiple times Cover features in different contexts (guides, HowTos, references) to enhance discovery.

🔟 Overview sections Provide high-level summaries of feature groups to help users grasp concepts before diving into details.

1️⃣1️⃣ Beginner mode Offer a simplified view of the doc to avoid overwhelming new users.

1️⃣2️⃣ Eat your own dog food Regularly use your own doc to spot usability issues & improve user experience.

Here's a doc example where I've tried to implement these best practices.

Feel free to share your tips for writing good documentation, so that we can collectively help other open source projects!--