Skip to content

Saturday, 8 August 2026

Natural Language Search in digiKam – GSoC 2026 Project by Srirupa Datta

We are excited to announce the successful integration of Natural Language Search in digiKam, developed by Srirupa Datta as part of the Google Summer of Code 2026 program. This new feature allows users to search their photo collections using plain English queries, making it easier than ever to find specific images without manually configuring filters.

What’s New?

With Natural Language Search, you can now type queries like:

Friday, 7 August 2026

Last Call

Last chance to submit your KDE Goals proposal

The call for submissions for the next KDE Goals cycle closes tomorrow, August 8.

As of the time of writing we've received nineteen proposals, covering a variety of topics like enterprise, gaming, personal well-being, documentation, accessibility, semantic desktops, color management, design, user experience, mobile and more.

Current proposals (by order of submission):

Join in

If any of the proposals above spark your interest, then by all means join the effort as a co-champion or contributor. And if you don't feel inspired by any, then there is still time to submit your own and champion a new KDE Goal.

Remember that you do not have to be a developer to participate. Read the selection process carefully before you send your proposal. If you have any doubts, join our Matrix room or create a topic at the KDE forum.

What's Next?

Once the submission period is over, we'll move into the refinement phase, where champions and the community work together to polish their proposals and finalize them so they're elligible for voting.

Timeline:

  • Call for submissions - June 19 to August 8
  • Refinement of proposals - August 9 to August 27
  • Voting period - August 28 to September 11
  • Tallying & preparation - September 12 to September 18
  • Announcement at Akademy - September 19

Alright, this will be the last review of the Summer. I’ll take a break until September as I really need to unplug for a bit. The next edition will be at the end of the first week of September. See you then!

But first… let’s go for my web review for the week 2026-32.


Tags: tech, gdpr, web, europe, law

This campaign is definitely worth a try. Hammering people with cookie banners exhibiting dark patterns isn’t exactly a good way to seek people consent.

https://killthecookiebanner.eu/


Stop Sending Me Your Errors

Tags: tech, email

Yes please! The amount of email system which get it wrong nowaday is really kind of sad.

https://kramkow.ski/article/2026/08/05/stop_sending_me_your_errors.html


Offensive Internet Posture

Tags: tech, internet, security, self-hosting

Indeed, so many things to do to deter bottom feeders. Lots of good funny ideas in there.

https://bruceediger.com/posts/offensive-machine/


Atom is better than RSS, in ways that matter

Tags: tech, atom, rss, blog

Indeed Atom is a better standard than RSS for feeds.

https://chrismorgan.info/atom%3Erss


The DISTINCT in your COUNT

Tags: tech, databases, postgresql, performance, optimisation

Careful how you use DISTINCT or ORDER BY on very large tables. You might want to reevaluate (after checking if there’s a problem of course).

https://boringsql.com/posts/distinct-in-your-count/


C++26: #embed

Tags: tech, c++

Another nice addition to the standard for dealing with embedded assets.

https://www.sandordargo.com/blog/2026/08/05/cpp26-embed


Crubit: C++/Rust Bidirectional Interop Tool

Tags: tech, c++, rust, interoperability, bindings

Interesting tool. Maybe more chances for C++ and Rust hybrids?

https://crubit.rs/


rust-lang/rust is adopting an LLM policy

Tags: tech, ai, machine-learning, copilot, foss, codereview, rust

Interesting policy. I think it strikes a good balance.

https://blog.rust-lang.org/inside-rust/2026/08/05/rust-langrust-is-adopting-an-llm-policy/


A Guide to Watchdog Timers for Embedded Systems

Tags: tech, embedded, reliability

Long and nice guide about watchdogs in an embedded context.

https://interrupt.memfault.com/blog/firmware-watchdog-best-practices


Elevators

Tags: tech, algorithm, simulation, complexity

Nice little post with simulations about the algorithms behind elevators. It’s quickly more complex than it sounds.

https://john.fun/elevators


The Wheels We Keep Reinventing

Tags: tech, architecture, complexity, supply-chain, vendor-lockin

There is truth here that our profession reinvents the wheel way to often. Some problem are solved, they don’t need reinventing. Be careful on your dependencies though, this is where lies the tradeoff.

https://blainsmith.com/articles/reinventing-the-wheel/


The development pipeline is a production system

Tags: tech, developer-experience, production

And indeed that makes it as important as the final product.

https://sundry.jerryorr.com/2026/07/31/development-pipeline-is-a-production-system


Committing to creativity

Tags: creativity, motivation

Interesting take. It’s indeed mostly about committing to something on the long term and doing the grunt work which begets creativity. It’s not just motivation between grit teeth or waiting to be blessed by a muse. Those won’t get you as far in your craft.

https://herman.bearblog.dev/creativity/



Bye for now!

Several months ago, as part of my internal move to the “IdP” team at Nextcloud, I started to co-maintain the user_saml application. This application allows Nextcloud users to implement single sign on with the SAML and Kerberos protocol. This protocol is based on XML and is mostly used in combination with Active Directory Federation Services (AD FS), Microsoft Entra ID, Authentik, Okta, Google Workspace and more.

New Admin Settings

The most visible change for administrators is the new admin interface to configure SAML. I completely rewrote it from a mix of PHP templates and jQuery to Vue3. This allows the interface to make use of all the @nextcloud/vue UI components and improve the user experience for admins who want to set up SAML on their instance. The user interface is now also more similar to the OIDC integration.

 

 

Nextcloud Login Form

The SAML app provides its own login page and previously didn’t integrate at all with the default one from Nextcloud. We had an interface IAlternativeLogin to expose one alternative login provider but it had to be static, this allowed, for example, the registration application to expose one Registration button, but wasn’t enough for applications exposing a variable number of login providers like the user_saml and user_oidc do.

Since Nextcloud 34, I added a new interface IAlternativeLoginProvider which applications can implement to expose zero or more IAlternativeLogin objects. The SAML and OIDC applications were both ported to use this interface.

For the SAML application, switching to the default login form is still behind a config flag which can be turned on in the admin settings, but this might change in the future.

Login form with ‘Authentik’ button
Login form with ‘Authentik’ button

Flexible User Matching between LDAP and SAML

SAML is often used in combination with LDAP. This is because SAML is a pure authentication protocol, whose main feature is to log a user in, but it doesn’t provide something very essential: user provisioning. This is where LDAP takes over and from the LDAP server we are able to get a list of users with their attributes as well as their group membership.

The only requirement is that the unique identifier used by the LDAP backend and the SAML backend are the same. This can be a UUID, a username, an email address, or any other field that the admin configured, but we recommend it to be the UUID as this value doesn’t change over time. With this identifier, Nextcloud is then able to identify that a specific user from LDAP is the same as one from SAML.

With Nextcloud 34, we now have a flexible user matching, meaning the SAML backend is able to try to query another field from the LDAP backend when matching the SAML user with an LDAP user (for example an old email address) making migration easier.

PHP Code Modernization and Cleanup

Since SAML is a security critical application, we have to ensure the code quality of it stays high. For this we use various tools.

  • The static analyser psalm. This tool has various strictness levels and we are now using level 2. Additionally now the unit tests are also scanned and type hinting was added in various places both in the app itself but also in the public interface from OCP/server that the app uses.

  • The refactoring tool rector. This tool is used for refactoring PHP codebase to newer PHP constructs allowing us to make use of new syntax sugar and functions available in newer versions of PHP.

Finally, annotations in phpdoc comments were converted to proper PHP attributes and most deprecated usages of the Nextcloud internals were replaced with modern alternatives.

Integration Testing

Integration tests are an important part of making sure that the application works correctly. Previously, we only tested the usage of this application with the SAML protocol, and after ending up with a regression with the usage of the Kerberos protocol, I added tests to also check the combination of Kerberos authentication with an SMB/Samba.

Performance Improvements

Aside from cleanups, the user backend and group backend now implement several optional interfaces that allow Nextcloud to query the user and group data more efficiently by using batch processing of users or limiting the size of the SQL queries.

The new interfaces we implement are IBatchMethodsBackend, ILimitAwareCountUsersBackend and ISearchableGroupBackend.

Additionally, display names of groups are cached when querying groups (which avoids doing n+1 queries in many places).

In total and with some other changes in the Team folder (groupfolders) app to make use of these new APIs, this managed to reduce the amount of queries done by 70% for some API requests.

Developer Experience Improvements

And finally to make it more convenient to work on this app, Maxence and I worked on improving the Nextcloud developer docker setup, to automatically configure a SAML provider and Nextcloud by only typing one command:

docker compose up nextcloud authentik

This saves a lot of time as I use a lot of ephemeral instances of Nextcloud and tear them down when switching between stable versions.

And this also works with a Global Scale Setup:

docker compose up portal proxy lookup authentik gs1 gs2 gs3 database-mysql

Thursday, 6 August 2026

Welcome to the inaugural edition of This Quarter in KDE Digital Sovereignty!

This blog series will cover the work done throughout KDE’s software stack that’s funded by the investment KDE received earlier this year from Germany’s Sovereign Tech Agency.

Commissioned work on a variety of projects has been done by KDE contributors working for KDE e.V. itself, as well as the Techpaladin Software and enioka Haute Couture companies.

This post will cover the work done in the second quarter of 2026. Let’s get into it!

Quality assurance and testing

The bulk of the work consisted of getting KDE’s house in order when it comes to automated testing — ensuring things that are working stay working, and providing early warnings about incompatibilities from updated dependencies.

The Sovereign Tech Agency’s investment in KDE included substantial funding for this work across KDE Plasma, KDE Linux, and KDE PIM, providing a strong technical foundation for all of the future funded work.

On the PIM side, we set up a dedicated test suite and an extensive set of newly-created tests for both IMAP and CalDAV/CardDAV resources. You can read more about it on Kevin Ottens’ blog. In any case, it helped uncover some issues which were promptly fixed (most notably recurrence exceptions are properly handled now), and identify dead code which has been cleaned up.

A similar process unfolded on the KDE Linux side, with a dedicated testing server managing a new openQA-based system that runs integration tests for many high-level cases relevant to Plasma in general and KDE Linux specifically. You can read more about it in this blog post by Thomas Duckworth. And it has also already borne fruit, including detecting an accidental regression in KWallet and protecting users from a KWin crash caused by a brief regression in Arch Linux’s gcc tooling.

IMAP4 revision 2

Beyond the QA, work also proceeded on the PIM side for the topic of improving support through the KDE PIM suite for IMAP4 revision 2. This led us to add support for more IMAP4 extensions in our stack like BINARY, LIST-EXTENDED, or LIST-STATUS. We also completed support for CONDSTORE and QRESYNC. Altogether, it allowed us to speed up IMAP resource syncing while using less network bandwidth — sometimes in a fairly drastic way, lowering the sync of a given mailbox to a single server round trip in the best cases!

We had more good news on this front too. It turned out to be less work than expected, as our IMAP implementation is in a fairly good shape! It will free some time to go further on the QA and testing side.

Automatic account configuration

Additional PIM topics included initial work to build a system for automatically discovering and setting up resources based on nothing more than an email address and password. We already have partial support for this kind of magic in KMail, but it doesn’t go beyond configuring email; that will change soon!

For this work, we’re preparing a new library which will implement the relevant draft RFC. The API is mostly in place, although we keep improving it. We’re now at the stage where we can plug this new implementation into KMail, and later on integrate the whole feature set via System Settings’ Online Accounts page. It will be nice when you just give an email and password there, to automatically see all your PIM apps automatically configured: mail, calendar, and identity.

WebDAV push notifications

The latest work started on the PIM side is about supporting push notifications for DAV calendars. This is based on a draft specification proposed by the DAVx⁵ folks. We’re currently mostly in the design phase, even though some adjustments to KDAV are already being made.

Ultimately this should lead to more targeted syncing when something changes on the server, reducing the network bandwidth requirements. It will also make your calendars sync with the server almost immediately instead of waiting for the next poll interval.

Network share handling

On the Plasma side, work also began to overhaul the way network shares are handled throughout KDE. So far the work has concentrated on beefing up KDE’s FUSE-based network share mounting in a variety of ways.

Perhaps the most notable way being explored is to create the FUSE mount in response to a request to access a file on a network location even if the user has not already accessed it from Dolphin. This work is in progress.

Work is also in progress to mount these FUSE mounts at a standardized and predictable path, and to surface them in the standard Places panel for ease of access.

Data integrity

To improve data integrity throughout KDE, we created a new service for interfacing with Btrfs snapshots. This will form the backbone of various user interfaces integrated throughout KDE software (starting with Dolphin) to offer users the possibility to restore earlier versions of their files from snapshots, and use those snapshots for traditional backup systems.

In addition, we put some work into improving KDE’s Kup backup system, in the form of UI improvements for determining what gets included in backups, and modernizing the user interface of its Plasma widget.

Configuration management

Work began on an overhaul of KDE’s configuration management infrastructure in the form of porting software to use the more modern KConfigXT system. This system uses a declarative syntax with defined schemas, allowing KDE software’s available configuration options and default settings to be knowable without having to read the source code.

This effort will eventually open up the possibility of writing a management app similar to GNOME’s DConf Editor tool that can offer administrators the ability to graphically visualize and change configuration options.


Looking forward

So it was a busy quarter of shoring up some of the foundations in KDE to lay the groundwork for future efforts. We’re very grateful for the Sovereign Tech Agency’s investment in KDE that made this possible! Once the QA efforts wind down, we’ll be in a great position to start working on the more user-facing elements of the investment.

Hi!

Past 2 weeks of my GSoC work about font subsetting in Poppler involved a lot of:

  • Acting on code reviews on my MR https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/2220
  • Solving a lot of bugs. A lot of bugs took me 4-5 hours to troubleshoot and solve. I conquered my fear of GDB a little bit by doing this. I feel slightly better at the art of debugging now.
  • Working on subsetting for form fields. I have it working for single font texts but not multi-font text because our support for multi-font text in form fields is complicated and it's proving difficult to test right now.

I also made the discovery that I need to also do the following (maybe in the GSoC period or maybe outside):

  • Rewriting the CID-to-GID map in a font so that we don't have to retain glyphs anymore while subsetting. Retaining glyphs can prove to be slightly expensive for some fonts, such as Droid Sans. One can only unlock font subsetting's full potential when they don't have to retain the glyph IDs anymore.
  • Subsetting the width array in the font.

Deciding to keep the blog short this time :)

Thanks, Bye!

Wednesday, 5 August 2026

Union: Summer 2026 Update

A lot has been happening with Union recently, so it is time for another update. As a reminder, Union is a project to build a new style engine for applications that tries to unify all the different ways Qt and KDE applications can be styled.

Union in Plasma 6.7

Image
A screenshot of Plasma System Settings' Application Style page showing the Union application style selected.
Union in System Settings

As mentioned in the [spring update], Union had its first release as part of the Plasma 6.7 release. Before release we had some back and forth as the intent was to use it as default for QtQuick applications, but that turned out to not be feasible. Instead, we came up with a solution where we use a proxy style as the widget style, which allows Union to be selected from System Settings. For widgets, we forward the styling to the Breeze style still, but when you select the Union style, QtQuick applications will (after restarting the application) use Union for their styling.1

This allows anyone with Plasma 6.7 to opt-in and test how well Union works with their favorite applications, with an easy way to go back should things not work correctly. We already received several bug reports of things not working quite correctly, most of which have been resolved. If you have not yet checked how well Union works for you, give it a try!

Styles and Style Selection

The above solution for selecting Union is mostly intended as an easy way to test Union with Plasma 6.7. It is not meant to be a long-term solution. Instead, we want applications to use Union by default, with a page in System Settings that allows selecting which Union style to use. Initially, that page and the current Application Style will live side-by-side in some form. Once there are a lot more Union styles, we can look at dropping the current Application Style page or moving it somewhere less prominent.

Creating a style selection page required some extra work to make sure that we are able to correctly identify styles and associate metadata with those styles. This work has recently completed, resulting in a fairly big overhaul of the core style loading of Union. Unfortunately, this does mean any styles that have been created so far will need conversion to the new format. The advantage is that now the style determines what input format is needed for the style, which leads to reduced code, increased robustness and easier backward compatibility in the future.

Image
A screenshot of Plasma System Settings showing the in-development Union style selection page.
A screenshot of the in-development style selection page for Union.

With Union now having a proper definition of what constitutes a "style", it became fairly straightforward to build a System Settings page to allow selecting the active style. The first version is mostly a copy of the current "Application Style" page, but this will evolve over time as that design is not ideal for what Union is capable of. In addition to the System Settings page, there is also a command-line tool to make it easier to work with Union's styles.

Widgets

Image
A screenshot of the Oxygen Demo application showcasing progress on the Qt Widgets style.
The Oxygen Demo application running using the in-progress Qt Widgets support of Union.

Over in Qt Widgets land, Akseli Lahtinen has been chipping away at building a proper Qt Widgets style for Union. This is slow going, as there is little documentation on how to actually work with the QStyle API and it is also showing its age.

Still, progress is being made. At this point, the Union widgets style is no longer a proxy style, with everything being rendered by Union itself. Things are starting to look similar to both the Qt Quick side and to the Breeze QStyle. We are unsure if the work will be finished by the time Plasma 6.8 is released, but we are certainly trying to get it there.

Image
A screenshot of Dolphin runnin with the in-development Union widgets style.
A very much work in progress screenshot of Dolphin running with the Union Qt Widgets style.

Other

There have been several discussions with regards to what capabilities Union needs to have to make it possible to support other styles. This includes discussions around porting Oxygen over to Union to increase the compatibility of Oxygen with Qt Quick applications. There is also ongoing work to build the new Ocean style using Union.

Hopefully with Plasma 6.8 we can move things from being in a tech preview state to become a core part of KDE's experience. But there is still a lot of work ahead of us. If you would like to help get things done, take a look at the Union repository or come talk to us over on Matrix.

Discuss this post at KDE Discuss.


  1. Assuming the application does not hardcode the style to use as several KDE applications did. ↩

ahiemstra

Want to make a meaningful contribution to KDE beyond coding? Help us organise Akademy 2027!

Every year, Akademy brings together KDE contributors, users, partners, and the wider Free Software community to collaborate, learn, and innovate. Now it's your chance to help shape the next Akademy by hosting it in your city.

We are looking for proposals to host Akademy 2027 during June, July, August, September, or October. Download the Call for Hosts guide and submit a proposal to host Akademy in your city to akademy-proposals@kde.org by October 1, 2026.

Have questions? We'd love to help! Whether you need advice, guidance, or support while preparing your proposal or organising the event, the Akademy team is here for you every step of the way.

Let's work together to make Akademy 2027 an unforgettable event!

Monday, 3 August 2026

In the feedback about dropping X11 support, one very surprisingly common comment is from users saying they "need" kgamma, a simple tool that allows the user to adjust the gamma, red, blue and green that gets drawn to the screen operating directly on the X server.

On our Wayland session we have colour management that blows simple gamma adjustment out of the water, so on the face of it it seems weird that this would come up. However at the same time, I get it. ICC profiles are very confusing and it's not the same as a few basic sliders that anyone can understand.

We want people to have the best transition to Wayland we can offer and this is a relatively easy fix.

The new tool

I have made a simple tool that edits the relevant part of an ICC profile - VCGTs.

"VCGT (Video Card Gamma Table): An optional, private tag inside an ICC file that stores 1D grayscale/gamma curves loaded directly into your graphics card's hardware Look-Up Table (LUT)."

That's a lot of fancy terms, but the key point is it's a tiny subset of the thing Kwin already supports. We can add a UI around those few values and not need to add a second code path in kwin or kscreen.

The UX is deliberately similar to the old UI.
Obviously it needs a round of polish (volunteers welcome!), but it's functional.

Why this is even better than on X11

Unlike KGamma on X11, this new tool:

  • Supports multiple monitors with independent values

  • Works with night colour rather than fighting over the same settings, Kwin will blend the two sets on top of each other

  • Gets applied by Kwin on startup so the first frame is perfect, rather than glitching during loading

What next

Whilst changing your red/green settings wtih sliders might be something a few users do, and we got a few comments it remains a niche case.
My intention is to post it as a standalone application on Flathub and not as part of Plasma. I think that strikes the right balance of providing support without holding ourselves back longterm.

Getting it

The new tool is available at:

https://invent.kde.org/davidedmundson/kgamma2

Usual CMake + build instructions apply.

Feel free to make pull requests and let me know if it helps solve your issue!

… is now hosted on KDE infrastructure, instead of this blog! Check out the July 2026 post, or the entire series here.