The ReactOS open-source operating system has seen its NTFS file-system driver mature to the point that it can be finally used for installing and using ReactOS with it. NTFS formatting support is also finally now possible with this driver too.

Hitting this major milestone of its NTFS driver maturing to the point of installing and using the ReactOS operating system itself with it also puts the project one step closer to its elusive beta release.

ReactOS posted to X today this big goal being realized of the NTFS driver being much more mature for handling ReactOS installations.

It is important to note though that the ReactOS NTFS driver still lacks caching leading to slower performance than other NTFS drivers/platforms, journaling, and security support are also not yet implemented. There is also the possibility of other undiscovered bugs they note.

A nice milestone for ReactOS and the latest in a variety of nice achievements they have made so far in 2026.

I wrote this, so disclosure first.

It measures per-app mobile data against your billing cycle rather than the calendar month, splits what you spent using an app from what the app spent on its own while the screen was off, and blocks apps per network, so something can be dead on mobile data and completely normal on Wi-Fi.

The part I think actually belongs in this community is the permission. There is no INTERNET permission in the manifest. Not a privacy policy promise, it is simply absent, so Android will not let the process open a socket at all.

What interests me is that you do not have to read the source to verify that. One command on the APK prints six lines and INTERNET is not among them:

aapt dump permissions DataSaver-v0.8.apk

The source being public is good for plenty of reasons, but it is not what makes this particular claim checkable, and I think those two things get conflated a lot. Most people who install a FOSS app never read a line of it. A claim you can check from the artifact itself is worth more than one you can only check by trusting that somebody else read the repo.

Under the hood it reads NetworkStatsManager for the figures and uses VpnService in package-list mode with no packet forwarding for the blocking. Both plain AOSP, no Play Services dependency. The only library it pulls is androidx.core-ktx.

GPL-3.0, free, no ads, nothing to buy, no accounts, no analytics, no servers. Android 7 and up.

The honest gap: right now it is only distributed through Play. The F-Droid request has been open at fdroid/rfp#4520 since 8 October, which as far as I can tell is normal queue time rather than anything wrong. Until then it builds from a clean clone.

https://github.com/anubisproductions/data-saver-usage-blocker

Hi, I'm the developer of OpenTV, a TV and film tracker for iPhone and Android.

I built it around one idea: your watch history should belong to you. So the library lives on your device in SQLite and works fully offline. The server is optional. It only handles community comments and, if you choose, backup and sync. There is no watch history table on the server at all.

If you'd rather not depend on my server, the backend is in the repo with self-hosting docs, and the app can point at your own server for backup and sync.

• License: MPL-2.0
• Stack: React Native / Expo, SQLite on device, Cloudflare Workers + D1 for the optional server
• Imports: TV Time, Trakt, Simkl, Letterboxd, IMDb
• Free, no ads

Feedback on the code, the architecture or the license choice is very welcome.

I'm building a catalog for the Internet, with an XXX.XXX.XXX (INF.REF.ENC) categorization system. And would like to make submitting a site as straightforward as possible. For legal reasons (writing bad descriptions could cost views), we're completely opt-in.

The entire database will be licensed under CC-BY-SA, and hosted over IPFS.

Are these instructions clear, or do they need to be redrafted?

I've been running OpenAltFinder for almost 16 months now, and received quite a bit of positive feedback. The directory has also grown substantially. Over the last few months I've been receiving more and more submissions that were AI-assisted/vibe-coded.

Personally I'm a bit skeptical (both quality wise, and longevity wise), but I also want to give everyone a chance to showcase what they've build. I had already added an "AI-assisted" label, but right now the majority of submissions include that label.

To counter this, I decided to build an AI-free version of it over at: https://noai.openaltfinder.com/, inspired by duckduckgo.

Gpslogger uses the most battery. Even if I din't use the phone. It'll consume too much. What are your settings to improve battery life? I started logging every 5 seconds and now every minute but that doesn't actually imorove battery life. Is there a solution?

I’m the founder of Prerender Buddy, and this is our Apache-2.0 CLI for inspecting what a public URL returns over HTTP. The CLI runs locally without an account, telemetry or calls to the hosted PB API. The commercial hosted service is separate.

Source: https://github.com/kopachlager/prerenderbuddy-cli

One part I’d like feedback on is the application-shell heuristic. It looks at readable text, empty mount points, loading text and script markers. That can flag a page worth investigating, but a deliberately minimal static page or a canvas app can need a different interpretation.

There’s a loading-placeholder fixture in the repo. From a local checkout, npm run demo:fixture passes that static fixture through the normal check and formatting functions. It lets you inspect the warning without relying on a live site that might change tomorrow.

For a public site you control, with Node.js 20 or newer:

npx @prerenderbuddy/cli check https://example.com/ --user-agent googlebot
npx @prerenderbuddy/cli compare https://example.com/ --user-agent gptbot
npx @prerenderbuddy/cli files https://example.com/

Both sides of the comparison are HTTP fetches. Neither runs JavaScript, and a user-agent string does not reproduce a crawler’s verified network origin. The output is diagnostic evidence, not proof of a crawler failure or a prediction of rankings or AI recommendations.

What fixtures would you add to keep this kind of heuristic honest? Small static sites, cookie banners and canvas apps are already covered, but reproducible false positives would be useful.

A self-hostable offline audio transcription app. State-of-the-art AI models, running entirely on your machine.

17 Contibutors including Mr. Gipity Claud

https://github.com/rishikanthc/scriberr

NOTES FROM DEVELOPER

Apologies for the radio silence.. I did find a new job, but had to move across the country for it. So between multiple moves, settling down into the new job and just recuperating from all the stress and anxiety I went through during the process made me want to take some time off.. So I was taking it easy, spending time with my family and didn't really have a lot of free time nor the mindset to work on my personal projects.. That said, things are good now and boredom has been creeping up and I have been itching to get back into my personal projects.. I still need to setup my self-hosting server which I have been procrastinating for a while now xD

TLDR the project isn't abandoned. I'll be starting development again this week :) Look like a lot of advancements and developments have happened in this domain in the past few months and I could actually use your input and thoughts on something. Please check #485 and please do drop your thoughts and comments. I would like to get the communities input on this one to decide next steps. Also, thanks for all the love and support ! Y'all are awesome.

Why I built this

The inspiration for Scriberr was born out of privacy paranoia and not wanting to pay for subscription. About a year ago, I purchased a Plaud Note for recording voice memos. I loved the device itself; the form factor, microphone quality, and workflow were excellent.

However, transcription was done on their cloud servers. As someone who is paranoid about privacy I wasn't comfortable with uploading my recordings to a third party provider. Moreover I was hit with subscription costs: $100 a year for 20 hours of transcription per month, or $240 a year for unlimited access. As an avid self-hoster with a background in ML and AI, it felt wrong to pay such a premium for a service I knew I could engineer myself.

I decided to build Scriberr to bridge that gap, creating a powerful, private, and free alternative for everyone.

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.

Hey, total noob here. I've been free of Windows and using Mint for a whooping 2 days. It's been great. I work on text docs 7 hours a day. Libre Office didn't mesh with Mint, and I'm using OnlyOffice. It's perfect for my needs. BUT.

Back on Word, I had Autocorrect customized with shortcuts for phrases I use a lot. It's a feature I absolutely need. I can't find it in OnlyOffice. For maths, yes. For text, nothing.
There must be a plugin, a script (not sure what scripts are, tbh), something.

I'm not talking about autocomplete (I don't want it to list words I might be typing, I want it to insert "Hello world" as soon as I type "hh" or whatever.)

Please?

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.

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.

Not everything mentioned is actually open source, but a decent amount is.

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

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 an open-source directory of 3,300+ AI agent tools across 32 categories (frameworks, coding agents, MCP servers, memory systems, RAG, evals...), all ranked by GitHub stars. A bot rescans trending sources every 5 hours, checks new repos against a quality bar (1,000+ stars, actively maintained), and prunes dead links automatically. Site: https://tayyabimam1.github.io/awesome-ai-agent-stack/ Repo: https://github.com/tayyabimam1/awesome-ai-agent-stack Free forever, open source. Feedback welcome!

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.

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.