I really hate that the options are limited and not that good even the paid ones I don't care if it's ai slop whatever i just want a good open source video editing software without ads if it exists

Brandon Thomas, developer of ArtCraft, a suite of open-source creative tools meant to replicate Adobe applications for free, has now announced apps to replace Microsoft Office tools such as Excel, PowerPoint, and Word, respectively, named GridCraft, DeckCraft, and WordCraft, that are created with Claude. Thomas has shared his new clones to ArtCraft GitHub, making them free for all to download.

The Document Foundation, the non-profit steering the development of LibreOffice, has unveiled a new logo.

The change means that, for the first time since its inception in 2010, TDF no longer shares the same logotype and wordmark as LibreOffice.

“The Document Foundation” is now the sole wordmark, written in a different font, Inter, and a refreshed set of brand colours complement it.

Unveiling the design, TDF’s Italo Vignoli made the case for a decoupling of the two brands, noting “the foundation speaks as an institution, not as a software project” whose work “extends well beyond the product” that it’s known for, i.e. LibreOffice.

Design breakout

URA Design, a Berlin-based design agency whose former clients include Mozilla and the Tor Project, handled the redesign. Its founder also worked on Ubuntu’s desktop installer in the past. Trivia: Canonical went the other way during its last brand revamp, incorporating the Ubuntu logo in to the Canonical wordmark, replacing its old, separate logo of two nested purple circles.

Carving out a visual identity of its own feels somewhat overdue.

Besides LibreOffice, TDF also contributes to the Open Document Format (ODF) standard and advocates for document interoperability and digital sovereignty with public organisations, educational institutions and governments.

The change only affects the branding of foundation. LibreOffice’s branding, logo, etc are unchanged.

The new brand assets are available to download if you fancy having a nosey. TDF says it will begin to use its new logo, fonts and colour scheme across its official websites, social media accounts, documents etc in the coming months.

Let’s Encrypt, the free and open certificate authority widely used to secure websites with HTTPS, announced it will shorten the default validity period of its TLS certificates from 90 days to 64 days, starting February 10, 2027.

All certificates issued or renewed from that date will have a 64-day lifespan unless users explicitly select one of the shorter options already available: 45 or six days.

Existing certificates will remain valid until their expiration dates. Let’s Encrypt expects the final 90-day certificate to expire on May 11, 2027. The organization also confirmed no valid certificates will be revoked during the transition.

To help administrators prepare, Let’s Encrypt will introduce 64-day certificates in its staging environment on October 14, 2026, allowing users to test their renewal setups before the change reaches production.

The move is part of a broader effort to improve web security by reducing how long compromised or incorrectly issued certificates remain usable. Simply put, shorter certificate lifetimes mean attackers have less time to exploit a stolen private key.

Of course, shorter validity periods also mean certificates must be renewed more frequently. For website administrators already using automated renewal tools, this should require little or no intervention.

In particular, Let’s Encrypt says users whose ACME clients support ACME Renewal Info should be ready for the transition. ARI allows the certificate authority to inform clients when certificates should be renewed, rather than relying on fixed schedules.

However, administrators using cron jobs or scripts with hardcoded renewal intervals should review their configurations. Instead of renewing a certificate a fixed number of days before expiration, Let’s Encrypt recommends scheduling renewals after approximately two-thirds of its validity period has passed.

The organization suggests checking scripts and configuration files for hardcoded values like 83, 80, or 60 days, which may no longer work reliably with shorter-lived certificates.

Another upcoming change concerns domain validation. Let’s Encrypt will reduce the period during which a previously completed domain authorization can be reused from 30 days to 10 days. In 2028, that period will shrink further to just seven hours.

The goal is to align with upcoming industry requirements and simplify how the certificate authority handles previously validated domains. Most users won’t need to make adjustments unless their ACME clients depend on reusing earlier authorizations.

Importantly, the transition won’t change Let’s Encrypt’s existing rate limits, ACME endpoints, or certificate issuance chains.

Looking further ahead, the organization plans to reduce the default certificate lifetime again, this time to 45 days in 2028. That makes the upcoming 64-day limit an intermediate step rather than the final destination.

For more information, see Let’s Encrypt’s official announcement.

Cloudflare has acquired Deno, the open-source JavaScript and TypeScript runtime created by Node.js founder Ryan Dahl. However, the acquisition comes with a major change: Deno’s core team will stop developing the runtime in 2027, after one final year of maintenance and security updates.

The announcement confirms the entire Deno team is joining Cloudflare to work on its Workers platform and related technologies. Instead of developing Deno as a separate runtime, the developers will focus on making Cloudflare’s application platform easier to run, including on privately operated infrastructure.

Built using Rust, the V8 JavaScript engine, and Tokio, Deno offers built-in TypeScript support, a security model that restricts access to system resources by default, and integrated tools for testing, formatting, and managing dependencies. Now, however, its original developers are taking a different direction.

According to Dahl, the team will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that period, ending in October 2027, the team will cease development work on the runtime.

Importantly, this doesn’t mean Deno itself will disappear. The project will remain open source, and other developers are welcome to continue maintaining and improving it. Whether the community will take over its development remains to be seen.

The acquisition also affects Deno’s commercial services. Deno Deploy, the company’s serverless application hosting platform, will operate for another six months before shutting down around April 2027. Paying customers will receive assistance migrating their applications to Cloudflare Workers.

Moreover, JSR, the JavaScript and TypeScript package registry developed by the Deno team, will continue operating, with its infrastructure moving to Cloudflare. The team has also committed to maintaining rusty_v8, the Rust bindings for Google’s V8 JavaScript engine, with plans to integrate the project into Cloudflare’s workerd runtime.

So, why is Cloudflare interested in Deno if the runtime itself is being phased out of active development by its creators?

The answer lies primarily in celld, a project developed by Dahl to simplify running distributed applications across multiple servers. It builds on the Cloudflare Workers programming model and Durable Objects, which combine application logic with persistent data storage.

Cloudflare provides an open-source runtime called workerd, which powers its Workers platform. Running the same infrastructure independently has limitations, especially when applications need to distribute data and workloads across multiple machines.

This is where celld comes in. The project was designed to make that kind of distributed infrastructure easier to deploy and operate without relying on Cloudflare’s own network.

Cloudflare now plans to combine the work behind celld and workerd, with Ryan Dahl and Deno co-founder Bert Belder leading the effort. The goal is to make self-hosting Workers and Durable Objects an officially supported option, allowing developers to run applications using the same programming model on Cloudflare’s network or their own servers.

For Cloudflare, this could make its development platform more attractive to organizations that prefer to control their infrastructure rather than depend entirely on a cloud provider. The company says more announcements about the combined work are planned in the coming months.

For existing Deno users, the immediate concern is the runtime’s future. The departure of the original development team raises questions about long-term support, compatibility, and future releases. Unless new maintainers step forward, Deno could remain functional without substantial improvements.

For additional details, visit Deno’s official announcement and Cloudflare’s announcement.

Kovid Goyal released Calibre 9.16 today as a new stable update to this open-source, free, and cross-platform e-book management software for GNU/Linux, macOS, and Windows systems.

Coming three weeks after Calibre 9.15, the Calibre 9.16 release is a hefty one, bringing support for high-quality Kokoro voices to the Read Aloud feature, which sound much more natural than the Piper voices, especially for English, and support for downloading news from websites that block automated access by using the Camoufox headless browser.

Calibre 9.16 also adds support for right-to-left text and better handling of multi-column pages to the PDF Input feature, adds support for reading images in the AVIF format, and adds a new option to the tag browser to let you sort hierarchical tags that have only children but no actual books as folders before all other tags at their level.

The Edit Book feature was improved in this release to allow skipping of problems of a particular type, indicate what ToC (Table of Contents) entries, if any, are in the file being currently edited, and update CSS selectors when automatically fixing invalid IDs.

On the other hand, the E-book viewer received a new option to display the immediate parent ToC section in headers or footers, and support for specifying margins in metric units when printing to PDF. Moreover, the E-book viewer now lets e-books store up to 1MB of data persistently, updates the “Pages from paper edition” value faster, and correctly handles dark mode theme color overrides.

EPUB 3 to EPUB 3 conversions were also improved to preserve IDs on navigation elements so links to them continue to work, while the Book list now respects horizontal alignment settings for all icon-only column types, and the Cover grid is no longer being rendered too small in some specific cases.

Calibre 9.16 also improves the PDF Output feature by fixing an issue with trailing content at the end of individual HTML files being lost when the files use multi-column layout and a regression in the Calibre 9.x series that caused conversion of some e-books with vertical writing to fail.

On top of that, Calibre 9.16 adds the ability to search rules across the Tag mapper and HTML/CSS transform rules, support for removing individual entries from the search history dropdown, support for resetting the main window layout, and support for exporting and importing saved games in the “Create your own Adventure” feature.

Kobo support has been improved as well with the addition of newer firmware, the DOCX Output now supports clickable images inside links and preserves non-breaking spaces, and various operations are now faster when dealing with large libraries, such as startup, deleting many books, sorting by series, searching and refreshing the Tag browser.

Last but not least, Calibre 9.16 fixes saving and restoring of layouts when the alternate book list visualisations is currently active, adds support for clearing FB2 metadata, such as series, comments, etc., when they are cleared in the app, and hardens the Content server, while improving support for older web browsers when using the book details page in the Mobile view.

New news sources have been added in Calibre 9.16, including World Socialist, Poetry Magazine, The Believer, and Respekt, while the Reuters, Heise, The New York Times, The Economist, The Atlantic, La Jornada, Naked Capitalism, and The Saturday Paper news sources have been improved.

Check out the release notes for more details about the changes included in Calibre 9.16, which you can download right now from the official website as binaries for 64-bit and ARM64 Linux systems, as well as binaries for macOS and Windows systems. You can also install Calibre as a Flatpak app from Flathub.

I built Airvia because I wanted my Android phone to play on my HomePod, and nothing free actually spoke real AirPlay 2.

Airvia captures your phone's audio output — Spotify, YouTube Music, podcasts, radio, almost any app — and streams it to your speakers:

• Real AirPlay 2 (transient HAP pairing, encrypted channels, buffered ALAC), confirmed playing on a real HomePod — plus AirPlay 1/RAOP fallback, DLNA/Sonos, and Chromecast
• Multi-speaker casting with a separate volume slider per speaker, and your phone's hardware volume buttons control the speaker while casting
• Per-app capture if you only want certain apps cast
• 5-band EQ + preamp, now-playing metadata with artwork, sleep timer
• Android 10+, no root, no account, no ads, no trial limits

Honest limits: apps can opt out of audio capture and DRM output is never captured, and AirPlay's buffer means a second or two of delay — great for music and podcasts, not for lip-syncing video.

It's free and open source (MIT). APK and source are on GitHub — feedback and bug reports welcome, especially from anyone with receivers I don't own.

Built by me, an independent developer — I designed it, decided every feature, and tested everything on my own devices. It’s built on top of open-source projects.

The emulator behind amberfolio.org is AGPL-3.0. It emulates only what SSI's Gold Box games need (an 8086, EGA, the timer, the PC speaker and the Tandy sound chip) and runs the original Pool of Radiance unchanged: natively on Windows, macOS and Linux, built from source, or as WebAssembly in a browser.

Where the lines are:

• The emulator is open source; the website is not. Every page on the site that runs the emulator links to the exact source commit it was built from.
• No game is included. The repository holds only facts about the program (addresses, offsets, SHA-256s), with a content guard in CI. Players bring their own GOG or Steam copy, which never leaves their browser.
• Every enhancement switches off. The automap, the game's printed journal on its own screen and the rest are optional; with them all off, CI checks that a run ends in exactly the same machine state as a build without them. The site also reads the game's text to a screen reader, though not its pictures, so the game can't be played without sight through it.

It was built with heavy use of AI coding tools, and the whole history is public. Desktop browsers, iPhone, iPad and Android; a controller with the usual layout works, without remapping yet. Questions about the licensing split, or the code, are welcome.

Not affiliated with the rights holders of Pool of Radiance or the Gold Box games.

Today I'm using Alltrails and also Trailforks to find hiking and mtb trails. However, I'm also trying to replace as many proprietary apps and services with open source alternatives. So, what is the best open source alternatives to Alltrails and Trailforks?

I have seen Wanderer which looks like what I'm looking for, but perhaps there are other alternatives with more users/trails or something else that makes it better?
Endurain is, as I understand it, for self-hosting which is nice but I also want to see trails that other people have uploaded in order to be inspired and find good trails when I visit a new place.

Are there any other sites I should consider?

Microsoft has released LiteBox 0.1, the first version of its open-source, Rust-based Library OS designed to isolate applications from the underlying operating system, reducing access to host resources and limiting security risks.

Unlike a traditional operating system such as Linux or Windows, Library OS does not run independently or provide a complete environment for users. Instead, it implements operating system functionality as a library that applications use within a controlled execution environment.

In LiteBox’s case, the goal is to provide applications only the interfaces they need while minimizing interaction with the host operating system. This reduces the attack surface, meaning fewer ways for malicious or compromised software to interact with the underlying system.

LiteBox uses a modular architecture built around two interfaces: North and South. The North interface provides operating system functionality to applications through a Rust API inspired by the nix and rustix libraries. The South interface connects LiteBox to the underlying execution platform.

By separating these components, developers can combine different application interfaces with different platforms without redesigning the entire system.

Microsoft says LiteBox is intended to work in both kernel-mode and user-mode environments, allowing it to support several application isolation scenarios.

For Linux users, a relevant use case is sandboxing Linux applications directly on Linux. Another is running unmodified Linux programs on Windows, although LiteBox is not intended to replace WSL as a general-purpose Linux environment.

Beyond these scenarios, the project also targets more specialized security environments, including AMD SEV-SNP, which provides hardware-backed memory protection for virtual machines, and OP-TEE, an open-source trusted execution environment.

Microsoft additionally lists Linux Virtualization-Based Security among the supported use cases.

The project is still under active development. According to its maintainers, APIs and interfaces may change as the architecture matures. Developers requiring long-term stability are advised to wait for a stable release or be prepared to adapt their implementations.

LiteBox is available under the MIT license, with its source code, development information, and contribution guidelines hosted on GitHub.

For more information, visit the official LiteBox GitHub repository.

Since 2022, Google's Open Source Software Vulnerability Reward Program (OSS VRP) has been the path for outside researchers to get paid for reporting security flaws in the company's open source code, including projects like Flutter, Angular, Go, and Fuchsia.

With an announcement on X, they have now decided to discontinue the product-facing side of it.

They are calling the change temporary, while supply chain reports remain open and anything submitted before October 1 stays unaffected. What's closed, what's not?

Product vulnerabilities are bugs in the projects themselves, like a failing HTML sanitizer, memory corruption issues in file format parsers, or insecure code examples in documentation.

The updated rules do not limit the change to a specific project tier, as they just won't be accepting any reports related to this.

Supply chain reports, on the other hand, cover vulnerabilities in how the software is built and shipped. Exposed package manager credentials used to publish build artifacts is one case the rules page lists. It remains unaffected by this change.

There's also an exception for some Google Cloud repositories. If a bug there affects a Cloud product, Google may still accept the report, but through its Cloud VRP.

Why did it come to this?

Back in March, a post on the Bug Hunters blog from Google engineers said AI-generated reports were flooding the program. Some were serving up hallucinated information, while others were flagging legit coding errors that had little to no impact on the security posture of the targeted project.

Google's first response was to raise the bar on memory corruption reports for its two top project tiers. Researchers had to either reproduce the bug through an existing OSS-Fuzz fuzz target or point to a patch that maintainers had already merged.

An update to the same post the following month went further. The standard and low-priority tiers, OT2 and OT3, stopped offering rewards or credit for product vulnerabilities and other security issues. The top supply chain reward for OT2 projects also fell to $3,133.70.

Supply chain reports still pay, from $500 on OT2 projects up to $31,337 on flagship ones.

As an alternative, Google points to the Patch Rewards Program, which pays between $100 and $15,000, though only for patches that have stayed in a project for a month without being reverted.

An open question

Google has not said when or in what form product vulnerability reports will return. Their announcement only promises an update in the first quarter of 2027 while they continue reworking that part of the program.

There's also a loose end. At the time of writing, the OSS VRP page still lists reward ranges for product vulnerabilities, up to $7,500. Though, as you saw earlier, the rules page for it has already been updated, so it shouldn't be long before this is addressed.

EU - Germany

Even if it works despite being AI slop that's been developed in a mere 4 days (?) and somehow has all these contributors, I'm not sure I agree with the idea.

It's cool that they went with Rust for it, but I would have much preferred if all that effort went towards improving GIMP and existing open formats.

If it works then I guess it's the same end result at the end of the day, but it would suck if GIMP doesn't end up being the one to put a nail on Photoshop's coffin after all these years of serious development by humans.

Edit: I already see the kneejerk dislikes coming, I'm just interested in starting a conversation about the idea of it, I also dislike the fact that it's AI slop as I already implied. I'd appreciate joining the conversation instead of dislike bombing with no argument.

I remember that comaps was forked from organic maps due to some drama around organic maps, but I am out of the loop on what exactly happened. Can someone get me up to date?

on the web, I came across the ReveriePaint app, it's kind of like krita, only for mobile devices🤩 https://github.com/LanRhyme/ReveriePaint

Given that Pixelfed is designed as an Instagram alternative, it seems like it'd make more sense to just put the short-form videos on there.

cross-posted from: https://leminal.space/post/40562232

From Fluxer's updated roadmap on their website

See the polyproto website they linked here

I hadn't heard of this protocol before, but the possibility of transferring accounts between homeservers sounds exciting!

Here's the text from the screenshot:

Federation lets people on different instances talk to each other as if they were on the same service, the way email works across providers. Fluxer's federation will be based on polyproto-core, a specification from the polyproto project, with our own extensions on top. polyproto is still young, and we hope that building a real implementation of it, and sharing what we learn, helps the specification mature and benefits everyone else who builds on it.

polyproto-core describes an identity that works across servers. Your identity is anchored on your home server and looks like name@domain. Behind it is a certificate that your home server signs over a key created on your device. To prove who you are to another server, your device signs a challenge from that server, so one identity works across servers and you don't need a separate account on each. Messages are signed by the sender, so a server you visit can't forge messages from you without being detected, as long as your home server and your device haven't been compromised. The specification also defines how to move to a new home server.

polyproto-core is an early beta specification maintained by the Polyphony project. As of October 2026 it is at v1.0-beta.13. It focuses on identity and leaves message formats and chat features to extensions. We'll write our own extensions for Fluxer's features and propose changes to the protocol where they would help others too.

We'll publish an experimental draft pull request in 2026 that you can try and give feedback on. The stable release follows in 2027. Until the draft is up, the discussion happens in Fluxer Labs, and you're welcome to join in.

You can already sign in to several instances from one app. You sign in to each instance separately and switch between them. The mobile apps already support several instances and accounts, and the desktop app gets the same in early October 2026 with the update described in #2.

cross-posted from: https://slrpnk.net/post/43551913

After reading the article about 31 New species discovered in 2 weeks of exploration, it was mentioned that they used a microscope, known as Squid,which is an open-source, confocal microscope

From their site:

What is Squid?

Squid is a quantitative imaging platform with a full suite of hardware and software components and configurations for deploying facility-grade widefield microscopes at a fraction of the cost of commercial solutions. Developed with the goal of helping translate the rapid advances in the field of microscopy and microscopy-enabled methods, including those powered by deep learning, we envision Squid will simplify roll-out of microscopy-based applications - including at point of care and in low resource settings, make adoption of new or otherwise advanced techniques easier, and significantly increase the available microscope-hours to labs.

Significance

Manual microscopy has served as a bedrock for the diagnostics of various infectious diseases, although at a cost of tedious labor and human errors. Imagine looking for 1 to 5 parasites amongst 5 million red blood cells. Currently, microscopists can take up to 10-15 minutes to review a single slide. Automated robotic microscopes are poised to enable a new era of smart field microscopy but current platforms remain cost prohibitive and largely inflexible, especially for resource-poor and field settings.

github repos
CAD models linked available here (a lot of google links there (docs, drive, etc))

tags frugal science microscopy tracking fluorescence excitation patterned illumination instrumentation frugal science malaria

I've been working on reverse-engineering Grindr and creating an open source client implementation for it since March.

When GrindrPlus closed, my project turned out to be its de-facto successor and immediatelly several thousands of people started following it. Now it has 70k+ downloads on Forgejo and the authorship is dedicated to public domain :)

• MIT licensed, no ads, no analytics, no trackers, no diagnostics, no statistics, no telemetry, only opt-in updates checking
• Signed releases, reproducible builds on all four platforms, full transparency
• And it's now in Google Play (for the time being) and being reviewed for F-Droid!

Already applied for Apple developer enrollment and going to publish this to EU alt stores as well as in the TestFlight. Then a classic unsigned ipa and also going to attempt Apple AppStore just for completeness.

You need an existing Grindr account. Downloads: https://opengrind.org/download

Questions and criticism welcome.

LibreSSL 4.3.3 has been released as a maintenance update to the OpenBSD-developed TLS and cryptography library, bringing several security and reliability fixes alongside portability improvements for macOS and Windows.

The most notable fix in LibreSSL 4.3.3 addresses an Online Certificate Status Protocol responder authorization bypass affecting both libtls and the ocspcheck utility.

OCSP is used to determine whether a TLS certificate has been revoked. LibreSSL’s fix tightens validation around which responders are authorized to provide that information.

DTLS, which provides TLS-style encryption for datagram-based protocols such as UDP, also receives several corrections. The developers fixed an incorrect size check in dtls1_preprocess_fragment(). They introduced a limit on buffered DTLS handshake data and addressed a potential overread that could occur when retransmission was interrupted.

Certificate verification receives attention as well. LibreSSL 4.3.3 ensures that verification callbacks configured to always return success can still detect a hostname mismatch. In addition, support for RelativeDistinguishedName in CRL distribution points has been removed.

On the portability side, the release adds support for building LibreSSL on macOS Golden Gate 27.0.

Windows users also get a couple of fixes. The developers worked around incorrect code generation produced by the MSVC ARM64 optimizer in constant-time big-number code, while LibreSSL’s Windows socketpair() emulation now correctly sets close-on-exec on the appropriate handle.

Lastly, projects building LibreSSL through CMake can now override TLS_DEFAULT_CA_FILE, providing more flexibility over the default location used for trusted certificate authorities.

For additional detail, see the release notes.

LibreSSL is a fork of OpenSSL created by the OpenBSD project in 2014, focusing on simplifying the codebase, removing legacy components, and improving security and maintainability. Besides being used by OpenBSD, a portable version is available for Linux, macOS, Windows, and other Unix-like systems.

Darktable 5.6.2 has been released today as the second point release to the latest Darktable 5.6 series of this open-source, free, and cross-platform raw image editor for GNU/Linux, macOS, and Windows.

Coming a little over a month after Darktable 5.6.1, the Darktable 5.6.2 release adds white balance presets for the Leica SL3-P (DNG) and Sony Alpha 7R VI (Sony ILCE-7RM6) cameras, improves highlights modes for 4BAYER (CYGM/RGBE) raws, and improves OpenCL support for recent Intel graphics drivers.

Darktable 5.6.2 also fixes OpenCL input gamma-corrected scaling for some devices, an OpenCL error in filmicrgb leading to wrong masks, a crash that occurred when importing a style whose module order is empty, and small memory leaks when expanding variables, which grew with the number of images imported or exported with each instance.

On top of that, this release fixes a small memory leak that occurred each time a history stack was pasted onto the image open in darkroom, corrupted output or a crash when an AI model returns more data than darktable reserved for it, which affected object masks and Lua models, and an issue with transparent dialog title bars on macOS 27.

Also fixed is a crash that occurred at the end of neural restore’s raw denoise on certain sensor sizes, where blending the tile seams wrote past the edge of the image, an OpenCL error in filmicrgb leading to wrong masks, and highlights Laplacian OpenCL code.

For Windows users, this release addresses a crash or hang when checking a faulty custom ONNX Runtime library, a bug causing Alt+Tab to fail to switch away from darktable when the mouse pointer was over a lighttable thumbnail, and an issue with the console windows that appeared repeatedly when darktable or a Lua script ran an external command.

Lastly, Darktable 5.6.2 fixes a stealing focus issue from other apps on Windows, which could happen when hovering over lighttable thumbnails, during import and export, or when log messages appeared or expired. According to the devs, while Darktable was minimized, it took the keyboard without becoming visible.

Some documentation updates are present as well, so check out the release notes for more details. Meanwhile, you can download Darktable 5.6.2 as a universal AppImage binary from the official website, which you can run on virtually any GNU/Linux distribution without installing anything on your personal computer.

Hi! I’m a table tennis player, club captain and referee who apparently decided that what the world desperately needed was another tournament manager.

So I made LibreTT. 🏓

It’s a desktop app for running table tennis tournaments: players, registrations, fees, groups, draws, matches, knockout brackets, results, backups and exports. It runs on Linux, Windows and macOS, works offline and requires no account.

So why another one?

Because I don’t think competition data should belong to the software that records it.

A result is created by players, clubs, referees and organizers. The software is just a tool. If LibreTT disappears tomorrow, your tournament history shouldn’t disappear with it.

That’s why LibreTT is licensed under AGPL-3.0-or-later. No subscriptions, activation servers, paid feature tiers or vendor lock-in. The source is public, the data stays local, and the community should always be able to preserve, move and continue its own infrastructure.

This is the first public beta (0.1.0-beta.1), so the next milestone is testing it against its natural predator: an actual tournament organizer who is 15 minutes behind schedule.

Development is AI-assisted and I disclose that in the README. I review and test what goes into the project and take responsibility for it.

Feedback, criticism and contributions are very welcome.

Source code · Website

Disclaimer: LibreTT website is still in development, expect bugs