As of this past week in the FreeBSD source tree for FreeBSD 16, the last of the GNU GPL licensed code from the base system has been retired.

The dialog implementation was the last piece of GNU GPL licensed software in FreeBSD's base system. The FreeBSD installer previously transitioned to using bsddialog in place of dialog and then dpv was the last user of dialog but itself since turned off and now retired.

This ticket to retire dialog was opened back in February while is now merged to the FreeBSD source tree for what will become FreeBSD 16.0.

With dialog removed, the latest FreeBSD code now retires the GNU sub-tree of the FreeBSD base system now that no more GNU code remains.

FreeBSD 16.0 is working its way toward release that is expected to happen in December 2027.

A year of strong growth in income

Total income for 2025 reached € 2,175,997, a substantial increase on the € 1,387,589 recorded in 2024. The growth came from three distinct sources, and it is worth being precise about each.

🔴 Donations The largest share, € 1,976,825, came from donations — overwhelmingly from individual users and small businesses, mostly in Europe. Part of this increase was organic, reflecting the continued strength of LibreOffice downloads.

A further part can be attributed to a concrete change: in mid-2025 we introduced a new update notification on Windows, which periodically — after every major release and selected minor ones — informs users that an update is available, presents the new features, and invites them to support the project with a donation. The effect was immediately visible as a step-up in donations from the moment it was deployed, and it is keeping donations at a higher level into 2026.

🔴 Online stores The second source was income from the sale of LibreOffice through online stores, sponsoring and related commercial activity, which together generated € 168,975. The Apple App Store (€ 118,942) and the Microsoft Store (€ 35,393) accounted for most of this.

🔴 Securities The third source was € 30,197 in income from securities held under the foundation’s asset management.

How the money was spent

Total expenditure for 2025 was € 1,457,343.

The breakdown by category shows where donor money goes.

🟢 Staff and operations remained by far the largest commitment, at € 1,091,032. This covers salaries (€ 406,736), statutory social security contributions (€ 93,244) and freelancers (€ 591,052) — the people who keep infrastructure, communication, administration and project coordination running, in order to share knowledge, support the community in its activities, and enable contributors to do their work.

🟢 Tenders. As in 2024, no development tenders were funded in 2025. Tenders related to LibreOffice development remain on hold, and will be resumed based on the development strategy currently under discussion according to the new Procurement Policy.

🟢 Events and community support amounted to roughly € 87,000, including the LibreOffice Conference (developer conference, € 51,184), community projects (€ 15,014) and student scholarships (€ 17,368), together with marketing initiatives.

🟢 Infrastructure and hosting came to € 51,420, covering the hosting, virtual machines, services and domains that underpin the project’s technical independence — a foundational asset we continue to prioritise.

🟢 Legal and administrative expenses totalled roughly € 92,000, including accounting and the preparation of financial statements (€ 34,164), legal advice and counselling (€ 36,597 across project and general legal work), and insurances (€ 4,626).

🟢 Cost of fundraising Receiving donations is not free. In 2025, payment-processing and banking fees came to roughly € 98,000 — Stripe fees of € 46,446 and bank transfer and money-transfer fees of € 51,190. These are simply the cost of doing business: they scale with the volume of donations we receive. It is worth adding that these figures do not capture the full picture, because PayPal’s currency-conversion costs are embedded in the transactions and not separately visible — though they are comparable in scale to the Stripe fees. We report this plainly so that no reader underestimates what it costs to collect the donations that fund our work.

Results and transparence

After expenses, we closed the year with a result of € 554,476, asset management contributed €21,263, and the commercial business operations returned a profit of € 142,916.

Our accounting is handled by a professional accountant, and our complete ledgers, listing all income and spending broken down by project, are published on our public wiki at https://wiki.documentfoundation.org/TDF/Ledgers

To everyone who contributed time, skills, resources and money in 2025: thank you. The foundation’s strength is your achievement.

https://blog.documentfoundation.org/blog/2026/07/13/financials-and-budget-tdf-annual-report-2025/

Does anyone here actually support Google's Developer Verification?

I don’t. I’ve put a warning about it in my repo because I’m against policies like sideloading restrictions, forced ID verification.

Curious what other devs here think. Is Play Store still worth the hassle?

Hello everyone.

I'm developing an open-source visual novel engine. And I'm struggling to choose between the two licenses: MIT and BSD 3-Clause. I wasn't much about licenses until this moment, so I have to ask someone else. Which one should I pick and why, if someone knows?

Thank you in advance.

URL for the crowdfunding: https://www.crowdsupply.com/oddly-specific-objects/open-book-touch

Specs:

• Display: 4.26" e-paper touchscreen, 480 × 800 px, warm + cool frontlight
• Processor: ESP32-S3 dual-core, Wi-Fi + Bluetooth LE
• Memory: 16 MB flash, 8 MB PSRAM
• Formats: EPUB and plain text, no DRM
• Storage: microSD card slot
• Interface: USB-C with integrated LiPo charging
• Dimension: 78 × 120 × 10 mm, about 85 g
• Open source: MIT-licensed firmware, open hardware (to be released at shipping)

It also has a replaceable 800 mAh battery, I found it cool :)

Hi everyone,

I’m happy to share that Portabase now supports backup and restore for Docker volume!

Portabase is an open-source, self-hosted backup and restore platform, currently supporting 9 databases including PostgreSQL, MariaDB, MongoDB, Redis, and more.

We’re now expanding it to cover Docker volumes too, because many self-hosted apps do not store critical data only in databases.

Typical use cases include WordPress uploads, Nextcloud user files, media libraries, app configuration data, and more generally any self-hosted service where critical data lives in Docker volumes.

The goal is still the same: make backup and restore simple, reliable, and easy to operate. Portabase uses a central server with lightweight agents running close to your workloads.

If you find bugs, please open an issue on GitHub, we’re actively looking for feedback.

Thanks!

I'm trying to help out one of many collectives stuck on Crabgrass (https://we.riseup.net/), but most tools I can see don't really seem like a much better option. If not that the software is really ageing and is very much not adjusted to mobiles - it would still serve pretty well.

In this case it's some 40 users, with mostly very little computer skill and old hardware and many years of notes and documentation to be moved. Some of it could be public or semi public (think volunteers), some is for the collective eyes only or an even smaller internal group.

Nextcloud with the Collectives plugin would be the most obvious choice... But from what I understand/tested there's no way to stop anyone with access to the notes from ie. downloading or deleting them all. I'd expect that to at least be impossible by mistake, and preferably somewhat more complicated to do for anyone.

Most other tools I've seen are either crypto-, esoteric language based maintenance nightmares which will be a overkill, or a pure wiki, which tends to be confusing for non-tech's or a niche French software for associations.

I'm interested in what would be a actually 'battle tested' software for internal use and how if fares against an old drunk punkrocker or in another extreme a deliberate sabotage attempt.

#Forgejo keeps impressing. Migrating a larger repo with lots of issues etc, only took the creation of an access token. Once again, i'm super happy with my decision to selfhost my #git.

#selfhosted #opensource #devops

https://docs.codeberg.org/advanced/migrating-repos/#migrating-from-services

We are currently in Beta, but the core features are built and ready for testing!

Here is what you can do in this release:

• Connections: Add contacts with their notes, social links, and relationship context.
• Custom Reminders: Set your own check-in frequencies and get daily notifications so you never accidentally let a relationship drift.
• Important Dates: Track birthdays and anniversaries with annual reminders.
• Home Dashboard: See exactly who is due for a check-in at a single glance.
• QR Sharing: Share and import connection profiles completely offline via QR code.
• Data Backup: Full JSON export and import backups. Your data is yours.
• Organization: Search by name and archive connections you don't need in your main view.

Beta Notice: This is an early release, so please use the Data Management -> Export Backup feature regularly to keep your data safe between updates!

If you want to give it a try, report a bug, or help shape the roadmap, I'd love to hear your thoughts.

Community & Feedback: Telegram

Download: Github Releases Codeberg Releases

I've been building a project to preserve family voices, stories, photos, and history, and one question has influenced almost every design decision:

Should something this personal ever require people to trust someone else's servers?

That's what pushed me toward making it open source and fully self-hostable. If someone wants to keep their family's memories on hardware they own, they should be able to.

That said, I know not everyone wants to run a server, so I'm also offering a managed hosted version. The idea isn't to lock anyone into a platform or build another big cloud service—it simply helps fund the project for people who'd rather not manage the infrastructure themselves.

For those of you who self-host, I'm curious:

Would you actually self-host something this personal?

What would make you trust (or distrust) a project like this?

What are some mistakes you've seen developers make when they say they support self-hosting?

I'm genuinely interested in hearing how this community thinks about it before I finish everything up.

https://notepad-plus-plus.org/downloads/v8.9.6.4/

https://web.archive.org/web/20260708160424/https://notepad-plus-plus.org/downloads/v8.9.6.4/

Since fable 5 went down just some time ago(although this is no longer the case), a lot of fable or Mythos related content including models and datasets were completely killed from HF, it seemed like such a blow to the local development community to lose such important files, this is what inspired me to work on my project, it's a p2p decentralized distribution network (aka a torrent site) that pulls files from HF and verifies them through sha256, I've been making slow and steady progress but so far I haven't made a single public post about it. I'm genuinely scared of a number of things happening, that the project won't gain traction, ridicule from more experienced developers, I'm also worried about security vulnerabilities which I'm sure I haven't fully patched yet...

How do I get over this fear of talking about my project? How do I gain stars on GitHub, and community engagement? After all, a decentralized distribution network is nothing without its peers...

Say I'm writing a small GPLv3 licensed Python script that I want to release publicly. It would use a few MIT licensed libraries and maybe also some chunks of code from some MIT licensed projects.

As per the MIT license conditions I would have to include the MIT license text in my project. So how would that be done properly? And how about other licenses that require the license text to be included?

Sorry if this has already been answered a million times. I'm relatively new to this stuff and I find the licenses really hard to understand despite my attempts. I tried to also use some other open source projects as examples, but most of them don't seem to include the license texts anywhere but the readme files at least seem to state which libraries they use.

Hi everyone,

I wanted to share a project I recently started working on called Tend (an Android app built to help you automate the scheduling of your social life).

The idea originally came from a discussion on r/fossdroid about how hard it is to keep in touch with friends and extended family without relying on algorithm-driven social media or bloated, cloud-based business CRMs.

Most "Personal CRM" apps require you to upload your contacts to a random server. I wanted something that was 100% offline, private, and simple.

What it does: You can think of it as setting up cron jobs for your relationships.

• Contact Cards: Create dedicated profiles for people you want to keep up with (Name, notes, phone, socials, etc.).

• Custom Frequency: Set a "check-in" schedule (e.g., every 14 days, monthly, quarterly).

• Smart Reminders: The app will notify you when it's time to reach out.

• 100% Offline: Everything is stored locally on your device via SQLite/Room. No accounts, no telemetry, no cloud sync.

I’d love your feedback! Since this is in the initial development phase, I’m looking for feedback on the features and the UI.

Repository: Github: Github Repo Codeberg: Codeberg repo

Disguising itself as the innocuously-titled “Android Developer Verifier” (ADV) process, this trojan horse runs surreptitiously in the background as a system service with full root privileges, quietly awaiting an activation signal. The service cannot be blocked, disabled, or removed. Unlike a commonplace bit of malware, this extraordinary strain won’t be detected and neutralized by Play Protect (the malware scanning and remediation service that is installed on all Android Certified devices). In fact, Play Protect is itself the vector through which this virus is transmitted and installed.

[...]

As we discussed in “What We Talk About When We Talk About Sideloading”, beware the dangers of allowing the terminology of debate to be defined by those who don’t have your best interests at heart. Malware being synonymous with “software we don’t like” means that they can unilaterally dictate — driven either by business incentives or by being compelled by a sufficiently powerful government — what the malware-du-jour definition is to be.

For precedent, personal content filtering in the form of “ad blockers” has long since been banned from the Play Store, and they have even classified some instances as malware. How long before they designate all ad-blocking software as malware, block installation on all Android certified devices worldwide, and permanently designate all developers of this class of software as malware creators?

OnlyOffice appears to have removed their Android app from their repos: https://github.com/ONLYOFFICE/documents-app-android

It can still be found on an archive: https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https%3A%2F%2Fgithub.com%2FONLYOFFICE%2Fdocuments-app-android

This means if you are de-Googled like me, they are no longer an option.

Perhaps coincidentally, they have also started making legal claims against the EuroOffice fork: https://github.com/ONLYOFFICE#%EF%B8%8F-legal-note

cross-posted from: https://feddit.uk/post/51641374

The other day I was looking for lyrics to a song. I went to a lyrics website and was hit with a wall of ads, despite my pi-hole! I then went to another site that put me into a redirect loop. It got me thinking about privately self hosting a lyrics site. I started thinking that lyrics are just a type of simple static content, and what would be ideal is an application in which you can upload multiple directories of markdown files. Perhaps the directory should be in a standardised .mds (markdown share) format for instance. It would essentially be a zip file with directories of markdown files and a yml file for indicating how it would ideally be displayed. Perhaps with an a-z, or perhaps text-searchable, or both. The styling would be configurable in the app and independent of the mds files completely. Does this kind of standard for sharing simple text or markdown in bulk exist in any capacity that encourages a known file format? I'm aware that static site generators exist, but they seem to be aimed at the creation of documentation, not at sharing it in bulk. I'm imagining easily downloadable recipe books, wikis, lyrics databases. Does this sound like something anyone would be interested in or am I over/under thinking it?

I'm not convinced that the concept was understood so I've decided to add some more context and perhaps the open source community is the correct place to ask.

To be clear, I'm not thinking about a lyrics solution in particular, nor am I unaware of static site generators. I'm wondering if a standard (and FOSS software built around that standard) for a compressed file format that will contain directories of markdown files that could be dropped into a repository without technical understanding would be sought after and useful.

Hello Lemmy,

This release contains some major bugfixes, which include:

• Correctly resolving adapter-device relationships (👀)
• Fixing OBEX transfers
• Properly syncing media player with the connected device during playback

And much more.

For Windows/MacOS users, libhbluetooth needs to be installed. Follow the download instructions and place the libhbluetooth dynamic library file next to the bluetuith binary, and then launch bluetuith.

Bluetuith is a TUI based bluetooth manager, that aims to be an alternative to most bluetooth managers, and can perform bluetooth based operations like:

• Connection to and general management of bluetooth devices, with device information like battery percentage, RSSI etc. displayed, if the information is available. More detailed information about a device can be viewed by selecting the 'Info' option in the menu or by clicking the 'i' key.

• Bluetooth adapter management, with toggleable power, discoverability, pairablilty and scanning modes.

• Transfer and receive files via the OBEX protocol, with an interactive file picker to choose and select multiple files.

• Handle both PANU and DUN based networking for each bluetooth device (Linux only)

• Control media playback on the currently connected device, with a media player popup that displays playback information and controls. (Linux only)

I hope you enjoy this release, and any feedback is appreciated.

I’m building Agentic Control Freak (ACF): a local control plane for Codex CLI, Claude Code, Antigravity CLI, and Ollama. With ACF, you can build local projects ranging from Next.js apps to training ML models all via your browser on your local machine.

The agents still do the coding. ACF owns the outer loop:

"task -> plan -> approve -> execute -> verify -> preview -> handoff"

It keeps durable state outside any one agent session: plans, tasks, filesystem diffs, checkpoints, undos, forks, verification runs, previews, memory, skills, and handoff briefs. That means you can switch providers mid-project without starting from zero.

It also does not trust the agent’s final message. The filesystem diff is truth; verification and live preview are owned by the control plane.

The orchestration, workspaces, previews, and state are local: localhost-only, workspace-confined under .workspace/<project>, and not meant for hosting. Provider CLIs may still call their model services. Optional Telegram control lets you approve or steer runs from your phone through a token-gated local worker.

Repo: https://github.com/Antibody/Agentic-Control-Freak

Video intro: https://youtu.be/1fRH-XQrgkY

ML model design and training video: https://youtu.be/KdiiU4RIfFU

P.S. I’d love feedback, especially on whether the app works on Mac or Linux (I tested only on Win11).