Global objects are one of the core abstractions in Wayland. They are used to announce supported protocols or announce semi-transient objects, for example available outputs. The compositor can add and remove global objects on the fly. For example, an output global object can be created when a new monitor becomes available, and be removed when the corresponding monitor gets disconnected.

While there are no issues with announcing new global objects, the global removal is a racy process and if things go bad, your application will crash. Application crashes due to output removal were and still are fairly common, unfortunately.

The race

Let’s start from the start. If the compositor detects a new output, it may announce the corresponding wl_output global object. A client interested in outputs will then eventually bind it and receive the information about the output, e.g. the name, geometry, and so on:

Things get interesting when it is time to remove the wl_output global. Ideally, after telling clients that the given global has been removed, nobody should use or bind it. If a client has bound the wl_output global object, it should only perform cleanup.

However, it can happen that a wl_output global is removed shortly after it has been announced. If a client attempts to bind that wl_output at the same time, there is a big problem now. When the bind request finally arrives at the compositor side, the global won’t exist anymore and the only option left will be to post a protocol error and effectively crash the client.

Attempt #1

Unfortunately, there is not a lot that can be done about the in-flight bind requests, they have to be handled. If we could only tell the clients that a given global has been removed but not destroy it yet, that would help with the race, we would still be able to process bind requests. Once the compositor knows that nobody will bind the global anymore, only then it can destroy it for good. This is the idea behind the first attempt to fix the race.

The hardest part is figuring out when a global can be actually destroyed. The best option would be if the clients acknowledged the global removal. After the compositor receives acks from all clients, it can finally destroy the global. But here’s the problem, the wl_registry is frozen, no new requests or events can be added to it. So, as a way around, practically all compositors chose to destroy removed global objects on a timer.

That did help with the race, we saw a reduction in the number of crashes, but they didn’t go away completely… On Linux, the monotonic clock can advance while the computer sleeps. After the computer wakes up from sleep, the global destruction timer will likely time out and the global will be destroyed. This is a huge issue. There can still be clients that saw the global and want to bind it but they were not able to flush their requests on time because the computer went to sleep, etc. So we are kind of back to square one.

Attempt #2

The general idea behind the first attempt was sound, the compositor only needs to know the right time when it is okay to finally destroy the global. It’s absolutely crucial that the Wayland clients can acknowledge the global object removal. But what about the wl_registry interface being frozen? Well, it’s still true, however we’ve got a new way around — the wl_fixes interface. The wl_fixes interface was added to work around the fact that the wl_registry interface is frozen.

With the updated plan, the only slight change in the protocol is that the client needs to send an ack request to the compositor after receiving a wl_registry.global_remove event

After the compositor receives acks from all clients, it can finally safely destroy the global.

Note that according to this, a client must acknowledge all wl_registry.global_remove events even if it didn’t bind the corresponding global objects. Unfortunately, it also means that all clients must be well-behaving so the compositor can clean up the global data without accidentally getting any client disconnected. If a single client doesn’t ack global remove events, the compositor can start accumulating zombie globals.

Client changes

The client side changes should be fairly trivial. The only thing that a client must do is call the wl_fixes.ack_global_remove request when it receives a wl_registry.global_remove event, that’s it.

Here are some patches to add support for wl_fixes.ack_global_remove in various clients and toolkits:

• Qt: https://codereview.qt-project.org/c/qt/qtbase/+/721655
• GTK3: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/9649
• GTK4: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/9648
• SDL: https://github.com/libsdl-org/SDL/pull/15203
• Xwayland: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/2140
• Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40416
• Chromium: https://chromium-review.googlesource.com/c/chromium/src/+/7666143
• Firefox: https://phabricator.services.mozilla.com/D288357
• wayland-rs: https://github.com/Smithay/wayland-rs/pull/887

Compositor changes

libwayland-server gained a few helpers to assist with the removal of global objects. The compositor will need to implement the wl_fixes.ack_global_remove request by calling the wl_fixes_handle_ack_global_remove() function (it is provided by libwayland-server).

In order to remove a global, the compositor will need to set a “withdrawn” callback and then call the wl_global_remove() function. libwayland-server will take care of all other heavy-lifting; it will call the withdrawn callback to notify the compositor when it is safe to call the wl_global_destroy() function.

Conclusion

In hindsight, perhaps available outputs could have been announced differently, not as global objects. That being said, the wl_output did expose some flaws in the core Wayland protocol, which unfortunately, were not trivial and led to various client crashes. With the work described in this post, I hope that the Wayland session will become even more reliable and fewer applications will unexpectedly crash.

Many thanks to Julian Orth and Pekka Paalanen for suggesting ideas and code review!

Today is the simultaneous release of Krita 5.3.0 and Krita 6.0.0!

Depending which version of Qt and KDE Frameworks you build, the same source will result in one of the other. Both versions are almost functionally identical, with 6.0.0 having more Wayland functionality.

But note that since Krita 6 is still considered rather experimental, since it's our first release based on Qt 6, and there were many complicated changes between 5 and 6.

For real work, please use 5.3.0! We expect 6.0 to become the main version of Krita before the end of the year, though.

What's New

Video courtesy of David Revoy.

Krita 5.3/6.0 is the result of many years of work by the Krita developers. Some features have been rewritten from the ground up, others make their first appearance.

Enjoy the completely new text feature: on canvas editing, full opentype support, text flowing into shapes. It is now easier than ever to create vector-based panels for comic pages. Tools got extended: for instance, the fill tool now can close gaps. The liquify mode of the transform tool is much faster. There are new filters: a propagate colors filter and a reset transparent filter. Support for HDR painting has been improved. The recorder docker can now work in real time. There is improved support for file formats, like support for text objects in PSD files. And much, much, much more!

For a complete overview of everything, check out our extensive release notes!

5.3.0 Download

Windows

If you're using the portable zip files, just open the zip file in Explorer and drag the folder somewhere convenient, then double-click on the Krita icon in the folder. This will not impact an installed version of Krita, though it will share your settings and custom resources with your regular installed version of Krita. For reporting crashes, also get the debug symbols folder.

[!NOTE] We are no longer making 32-bit Windows builds.

• 64 bits Windows Installer: krita-x64-5.3.0-setup.exe

• Portable 64 bits Windows: krita-x64-5.3.0.zip

• Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with recent releases, the minimum supported distro versions may change.

[!WARNING] Starting with recent AppImage runtime updates, some AppImageLauncher versions may be incompatible. See AppImage runtime docs for troubleshooting.

• 64 bits Linux: krita-5.3.0-x86_64.AppImage

MacOS

Note: minimum supported MacOS may change between releases.

• MacOS disk image: krita-5.3.0-signed.dmg

Android

Krita on Android is still beta; tablets only.

• 64 bits Intel CPU APK

• 64 bits Arm CPU APK

• 32 bits Arm CPU APK

Source code

For source archives, please download the 6.0.0 archives and build with Qt5.

md5sum

For all downloads, visit https://download.kde.org/stable/krita/5.3.0/ and click on "Details" to get the hashes.

Key

The Linux AppImage and is signed. You can retrieve the public key here. The signatures are here (filenames ending in .sig).

6.0.0 Download

Windows

If you're using the portable zip files, just open the zip file in Explorer and drag the folder somewhere convenient, then double-click on the Krita icon in the folder. This will not impact an installed version of Krita, though it will share your settings and custom resources with your regular installed version of Krita. For reporting crashes, also get the debug symbols folder.

[!NOTE] We are no longer making 32-bit Windows builds.

• 64 bits Windows Installer: krita-x64-6.0.0-setup.exe

• Portable 64 bits Windows: krita-x64-6.0.0.zip

• Debug symbols. (Unpack in the Krita installation folder)

Linux

Note: starting with recent releases, the minimum supported distro versions may change.

[!WARNING] Starting with recent AppImage runtime updates, some AppImageLauncher versions may be incompatible. See AppImage runtime docs for troubleshooting.

• 64 bits Linux: krita-6.0.0-x86_64.AppImage

MacOS

Note: minimum supported MacOS may change between releases.

• MacOS disk image: krita-6.0.0-signed.dmg

Android

Krita 6.0.0 is not yet functional on Android, so we are not making APK's available for sideloading.

Source code

• krita-6.0.0.tar.gz

• krita-6.0.0.tar.xz

md5sum

For all downloads, visit https://download.kde.org/stable/krita/6.0.0/ and click on "Details" to get the hashes.

Key

The Linux AppImage and the source tarballs are signed. You can retrieve the public key here. The signatures are here (filenames ending in .sig).

Hello again! Welcome to another bugfix release. This update is highly recommended, as it tackles a few critical issues to keep the app running smoothly.

• Resolved a crash that occurred when creating your first notebook.
• Fixed an issue that prevented notebooks from being removed.
• Corrected a glitch allowing notes to be drag-and-dropped through quick sketches.
• Note sorting is functioning as intended now.
• Restored the undo and redo buttons when a single note is open.
• Added the "Clear" button to allow removing content from the quick sketches.
• Added several minor background improvements for better overall stability.

Get Marknote

We encourage everyone to update as soon as possible. You can grab the latest version via Flatpak, or your favorite package manager.

Packager Section

You can find the package on download.kde.org and it has been signed with Carl Schwan's GPG key.

Heading into the final weeks of SoK, things got a bit chaotic. Week 7 was right in the middle of my university exams, so i had to take a planned break from coding. I survived the exams and was geared up for a solid Week 8 sprint to wrap things up, but then my laptop chose violence again. A few weeks back it had already died on me once (the screen went completely dark). I replaced the panel, it came back to life, and i thought we were good. This time it was worse: no screen flicker, no fan spin, nothing. The repair shop confirmed a motherboard failure and told me, “We can look at it… eventually… no promises on timeline.”

Me, staring at the SoK deadline and GSoC proposal date sliding toward me in glorious slow-motion...

Waiting around simply wasn't an option. So i did the only logical thing in full panic mode: I went straight to a store and bought a new laptop. RAM prices hit me hard too 💀, but I think it'll be worth it at this time. Huge thanks to my mentor, Finley, for being super understanding and providing an extension so i could set up my new dev environment and finish strong!

Once the new setup was ready, i jumped right back into Lokalize. Both of my final MRs ended up being fixes for edge cases in the major features i built earlier in the program.

1. Fixing an Oversight from Week 3: Menu Availability

Back in Week 3, i wrote the updateMenuAvailability() logic to dynamically disable top-level menus whenever a user switched tabs. However, i missed a crucial edge case: what happens when you close the very last tab? Because there were no tabs left to trigger my update function, the menu state would stay stale when the application fell back to the "Welcome" screen.

To fix my own bug, i patched the showWelcome() function to directly call updateMenuAvailability() and made sure that the application startup sequence initialized through showWelcome(). This way, the refresh path runs consistently every time the Welcome screen appears, ensuring the menus are greyed out correctly when no tab is active.

Merge Request: Lokalize: Refresh top-level menu availability on Welcome screen

2. Fixing a DRY Failure from Weeks 4 & 5: Tab Focus

The next task came out of the code review for the batch file actions (Save All, Close All, etc.) I built back in Weeks 4 and 5. While reviewing my MR that implemented the "Revert All" feature, Finley pointed out an existing DRY (Don't Repeat Yourself) failure in the codebase.

When "Revert All" is triggered, it checks if any open files have unsaved changes. If they do, it activates a warning prompt via the existing fileOpen() function. The problem was that fileOpen() was triggering a warningTwoActionsCancel dialog ("The document contains unsaved changes...") without focusing on the related tab first. If a translator had many files open, they wouldn't know which specific document the warning was actually about. Because this UX issue affected any call to fileOpen(), he asked me to tackle it in a separate, dedicated MR.

I fixed this by adding a new signal signalActivateThisTabRequested(QWidget *tabWidget) to the EditorTab class. Right before the prompt is called in editortab.cpp, I emit this signal passing this as the argument. I then wired this up in lokalizemainwindow.cpp to connect to activateTabByPageWidget. Now, the second the warning appears, the UI automatically flips to the correct document, making the action much safer and more intuitive.

Merge Request: editor: focus relevant tab before unsaved changes prompt in fileOpen()

While testing this new tab focus MR, i actually found another bug in my old "Revert All" code, it doesn't revert all the open files every time. I suspect this might be due to some interference from autosave, so I'll be looking into fixing that in the future.

This officially wraps up my Season of KDE! It’s been an incredible experience diving into C++, Qt, and KDE's XMLGUI architecture. Huge thanks to Finley and the KDE community for the mentorship and support throughout the journey 🙏.

Animations… Everybody loves animations. They make your desktop look more eye candy, and they also help with guiding or drawing the user’s attention towards certain elements on the screen, for example a new window or a popup or a button, etc.

An animation is a just quick series of images to simulate the movement of an object on the screen. For example, consider a basic animation that only lists digits

As you can see, it’s just a sequence of individual digit images that are presented quick enough.

The animation frames have to presented at a steady pace to maintain the smooth feeling. If one or two frames are late, a frame drop can occur, which the user will likely notice. There are various reasons why a frame may not be presented on time. One reason might be that the app has been busy doing something else, for example loading a big file from the disk. However, there can also be reasons that are not exactly under the direct influence of the app, for example the operating system scheduler may prioritize scheduling other tasks or perhaps the memory scheduler has decided that it needs to do some of its things, etc. An animation with a frame drop may look as follows

If a frame cannot be painted on time, we are in a sticky situation no matter how you look at it. The animation won’t look as smooth as it could.

That being said, it is also worth mentioning how some apps (and compositors) drive animations. A lot of them advance animations simply by the amount of time that has passed since the last frame. In pseudo-code, it looks as follows:

const milliseconds target = next_presentation_timestamp();
const milliseconds delta = target - previous_repaint_time;
previous_repaint_time = target;

advance_animations_by(delta); 

The biggest drawback of this approach is that it can introduce discontinuities to the motion of an object. For example

If the app becomes busy for about 48 milliseconds after painting the frame 3, the delta interval will be 48 the next time a frame will be painted, which will effectively advance the animation to frame 7. Technically, this is not the wrong behavior. It does make sense if you look purely at the math. From the human eyes point of view though, the fact that there is a discontinuity in the animation now is far from ideal.

Luckily, there is a simple workaround. If we know the refresh rate of the monitor, we could estimate the maximum allowed delta interval for a single frame (for example, for a 60Hz monitor, it will be 16.6ms) and limit the animation delta time by it. It won’t make animations butter smooth but it will reduce discontinuous jumps in the animation.

In comparison to the aforementioned described method to advance animations, with the proposed method, animations will advance as follows

As you can see, even though there was a frame jitter, the frames 4, 5, and 6 have not been dropped. Obviously, this is not a silver bullet solution. The final motion may still look “wonky” depending on the duration of the frame jitter but even with that being said, the advantages are still worth it. In pseudo-code, it will look as follows

const milliseconds target = next_presentation_timestamp();
const milliseconds max_delta = 1000 / output->refresh_rate;
const milliseconds delta = min(max_delta, target - previous_repaint_time);
previous_repaint_time = target;

advance_animations_by(delta);

Plasma 6.7

The animation delta interval throttling will be implemented in the next release of Plasma. Note that this will only affect compositor-side animations, for example the ones that are played when a window is opened or closed. It will not affect animations that are played inside applications, the compositor has little actual influence on those.

In my testing, both on my desktop and a less powerful laptop, I noticed slight improvements when opening new windows, animations feel a little bit more smoother especially on the laptop. That being said, please don’t take it as me saying that animations will be perfectly smooth. No, if a frame jitter occurs, we’re in a pretty ugly situation and these changes are mostly about hardening kwin so the animations look less choppy.

During FOSDEM this year, I met a group of very cool people that put together events about Open Source Design. They invited me to participate this year.

The topic was similar to my talk during FOSDEM, but with a twist on the soft skills needed to complete the creation of a new design system for Plasma.

The conference is only one day. Something really cool they did was to have something like BoF (Birds of a Feather) sessions during the afternoon slot before my talk. We had the opportunity to discuss important aspects proposed by the attendees around design and making your way into the field.

Since I was representing KDE in this project, I brought my newly-acquired tshirt from FOSDEM!

The experience was great. Everyone was awesome and even met up with new contributors to the VDG. Comments from after my talk were very positive and I look forward to participating in even more events of this nature.

Design System Update

At this time, the design system keeps evolving. I have gone back to rework some application icons. After reviewing the current designs and consulting with team members, the consensus is that they should be simpler, more approachable. I have made some concepts that I will keep exploring going forward.

Additional to that, new tokens have been created. We now have shadow tokens, and I have applied them to all the components that I can think of. They have replaced manually-created shadows from the previous time.

Radius and spacing tokens now need to also make their way into the components. Unfortunately, Penpot is struggling today on creating new tokens. I will wait for an update. However, the work involves going through out component buttons and applying foundational spacing tokens to the sides and inner spaces for the components.

While this might be long, it is easy. The spacing numbers are already in the component. My part is to create all the spacing components, locate the margin or padding number I see today in buttons, find the base component, and apply the spacing tokens.

I am also closely following up on Penpot’s new beta, hopefully coming out soon, with their new rendering engine.

I have also connected the Penpot team with our LAS (Linux App Summit) event and hopefully they can attend.

More to come!

If you’re interested in participating in this effort and have some awesome design and integration skills, join us!

https://matrix.to/#/#visualdesigngroup:kde.org

Welcome to a new issue of This Week in Plasma!

This week several new features landed, in addition to a number of user interface improvements and some nice performance improvements and bug fixes. Check ‘em out:

Notable new features

Plasma 6.7

For each additional time zone you add to the Digital Clock widget, it now also shows how far forward or behind that time zone is compared to yours. (Nate Graham, plasma-workspace MR #6417)

After

Before

If you disable the feature to invoke KRunner by typing on the desktop, instead typing on the desktop invokes “type-ahead”, which allows selecting files by typing the first letter or two of their names. (Guillermo Steren, KDE Bugzilla #427961)

You can now reverse the ordering of items in the System Tray widget. (Nathaniel Krebs, KDE Bugzilla #517016)

Notable UI improvements

Plasma 6.7

Discover now sorts app lists by number of reviews by default, resulting in vastly more relevant results while browsing rather than searching. The old rating-based sorting method is still available, of course. (Nate Graham, discover MR #1274)

After

Before

Discover now filters out non-apps from its home page, preventing death spirals of negativity where people would leave 1-star reviews saying they were broken (not being launchable apps, the “Launch” button wouldn’t work), causing them to move up higher in the list. (Nate Graham, discover MR #1287)

System Settings and KWin now consistently use the word “pointer” to refer to the mouse/touchpad pointer. (Philipp Kiemle, plasma-workspace MR #6425 and kwin MR #8982)

Screen un-dimming is now faster than dimming, since un-dimming would mean you’re ready to use the system again. (Kai Uwe Broulik, kwin MR #8963)

The currently-active task in a grouped task tooltip now has bold text, to help you pick it out. (Christoph Wolk, KDE Bugzilla #516278)

Labels for Bluetooth devices in the System Tray widget have been re-arranged so that you can always see the battery level no matter how long the device name is. (Kai Uwe Broulik, KDE Bugzilla #515090)

The Global Menu widget’s menu highlights are now rounded consistently with the highlights for other menus. (Akseli Lahtinen, libplasma MR #1459)

You can now set a modifier key all on its own to focus a Plasma panel. (Christoph Wolk, plasma-desktop MR #3547)

Plasma’s panel configuration window now only offers opacity settings if the active Plasma style supports it. (Filip Fila, KDE Bugzilla #516042)

Notable bug fixes

Plasma 6.5.6

Fixed a bug that distorted the image on certain vertically-oriented monitors while displaying the Plasma Login Manager. (Anton Gobulev, KDE Bugzilla #517409)

Plasma 6.6.3

Fixed a case where KWin could crash after changing the Zoom effect’s settings in certain specific ways. (Ritchie Frodomar, KDE Bugzilla #517073)

Fixed two cases where KWin could crash when misconfigured or given broken content. (Nicolas Fella, KDE Bugzilla #517137 and KDE Bugzilla #517711)

Fixed a few cases where KDE’s printing management system could crash due to faulty information from printers about their ink levels. (Mike Noe, print-manager MR #311)

The tooltip for the Refresh button in Discover’s Updates section no longer says “F5 (QQuickShortcut(gobbledygook))”, fixing an unexpected side-effect of a recent KDE Frameworks update. (Akseli Lahtinen, KDE Bugzilla #516392)

Plasma 6.6.4

Fixed an issue that made the “bounce keys” accessibility feature break key repeat in the Brave browser. (Ritchie Frodomar, KDE Bugzilla #513268)

In the shortcut conflict dialog opened by System Settings’ Shortcuts page, the “Re-assign” action now works. (Dávid Bácskay-Nagy, KDE Bugzilla #471370)

Made the update count in Discover’s notifications more accurate. (Akseli Lahtinen, discover MR #1284)

Frameworks 6.25

Reverted an innocent-looking change that broke icons for some apps like OBS and Ungoogled Chromium due to an underlying deficiency in the Qt toolkit’s SVG renderer. (Nate Graham, KDE Bugzilla #516007)

Notable in performance & technical

Plasma 6.6.4

Reduced CPU and GPU load for full-screen windows (also known as “direct scan-out”) on screens without the pointer on them. (Xaver Hugl, KDE Bugzilla #516808)

Plasma 6.7

Added support for “3D LUTs” in KWin, which reduces resource usage on GPUs that support color pipelines in hardware. (Xaver Hugl, kwin MR #8475)

The Networks widget now only fetches network speed information while that information is visible. (Ser Freedman, plasma-nm MR #544)

Stopped creating unnecessary OpenGL contexts for apps that don’t use OpenGL, which reduces their memory usage by 10-15 MB or more per app and also speeds up launch times. (Vlad Zahorodnii, plasma-integration MR #209)

Qt 6.10.3

Fixed an issue that broke HDR support while using the Vulkan renderer on certain hardware. (Joshua Goins, Qt patch #711621)

How you can help

KDE has become important in the world, and your time and contributions have helped us get there. As we grow, we need your support to keep KDE sustainable.

Would you like to help put together this weekly report? Introduce yourself in the Matrix room and join the team!

Beyond that, you can help KDE by directly getting involved in any other projects. Donating time is actually more impactful than donating money. Each contributor makes a huge difference in KDE — you are not a number or a cog in a machine! You don’t have to be a programmer, either; many other opportunities exist.

You can also help out by making a donation! This helps cover operational costs, salaries, travel expenses for contributors, and in general just keeps KDE bringing Free Software to the world.

To get a new Plasma feature or a bug fix mentioned here

Push a commit to the relevant merge request on invent.kde.org.

Let’s go for my web review for the week 2026-12.

The “small web” is bigger than you might think

Tags: tech, web, self-hosting, blog

Also, it’s likely a pessimistic estimate… Indeed, it’s mostly based on a list from Kagi, which likely doesn’t list many sites which would qualify.

https://kevinboone.me/small_web_is_big.html

Have a Fucking Website

Tags: tech, web, social-media, self-hosting

So much this… I’m sick of all those little businesses having only an Instagram or Facebook account or whatever. I wish we’d have proper websites for all of those instead.

https://www.otherstrangeness.com/2026/03/14/have-a-fucking-website/

RIP Metaverse, an $80 Billion Dumpster Fire Nobody Wanted

Tags: tech, facebook, vr, hype

This was stupid hype… Why do we have regularly this kind of fever in our industry?

https://www.404media.co/rip-metaverse-an-80-billion-dumpster-fire-nobody-wanted/

Bluesky announces $100M Series B after CEO transition

Tags: tech, social-media, bluesky, business

The writing is on the wall I think… the real question is not if but when will the enshittification begins? It’s been data harvesting for a while now.

https://techcrunch.com/2026/03/19/bluesky-announces-100m-series-b-after-ceo-transition/

Open Source Gave Me Everything Until I Had Nothing Left to Give

Tags: tech, foss, psychology, productivity, life

This is an account of how dark things can become when you align your identity with your contributions. Stay healthy, stay safe!

https://kennethreitz.org/essays/2026-03-18-open_source_gave_me_everything_until_i_had_nothing_left_to_give

How Can Governments Pay Open Source Maintainers?

Tags: tech, foss, business, fundraising

Let’s help them help us. There are a few things to have in place for governments to be able to pay maintainers.

https://shkspr.mobi/blog/2026/03/how-can-governments-pay-open-source-maintainers/

The price of accountability: corruption erodes social trust more in democracies than in autocracies

Tags: politics, democracy

This is definitely a disturbing result. It indeed makes democracies more fragile, all the more reason to build more democratic resilience.

https://www.frontiersin.org/journals/political-science/articles/10.3389/fpos.2026.1779810/full

Age Verification Lobbying: Dark Money, Model Legislation & Institutional Capture

Tags: tech, gafam, facebook, law, lobbying, surveillance

It looks more and more likely that the current age verification fever has dark origins…

https://tboteproject.com/

Rep. Finke Was Right: Age-Gating Isn’t About Kids, It’s About Control

Tags: tech, politics, law, surveillance

The commentaries and analysis of those unjust laws continues. The motives behind the people pushing for them are getting clearer and it isn’t pretty.

https://www.eff.org/deeplinks/2026/03/rep-finke-was-right-age-gating-isnt-about-kids-its-about-control

Ageless Linux — Software for Humans of Indeterminate Age

Tags: tech, law, surveillance

Good initiative to push these unjust laws to their limits. Hopefully it’ll show how absurd they are.

https://agelesslinux.org/

Lotus Notes

Tags: tech, history, email

On the little known history of Lotus Notes. Crossed its path as a teenager during an internship at a bank. Can’t say I remember it fondly though.

https://computer.rip/2026-03-14-lotusnotes.html

The Most Important Software Innovations

Tags: tech, innovation, history

Interesting list and way to frame the problem. It’s important to maintain this resource, an update is likely needed.

https://dwheeler.com/innovation/innovation.html

Wayland has good reasons to put the window manager in the display server

Tags: tech, wayland, x11, history, complexity, input

Let’s not forget where we’re coming from and why window managers tend to be merged with display server. It removes some complexity and some latency.

https://utcc.utoronto.ca/~cks/space/blog/unix/WaylandAndBuiltinWindowManagers

Containers Are Not Automatically Secure

Tags: tech, containers, security

Kind of obvious I think, but this likely bears repeating. Containers are not a magical recipe for security. There are many attack vectors to keep in mind and evaluate.

https://www.lucavall.in/blog/containers-are-not-a-security-boundary

Why WebAssembly components

Tags: tech, webassembly, rust

Good explanation of where WebAssembly is going and why the current initiatives are important to its success.

https://blog.yoshuawuyts.com/why-webassembly-components/

How many branches can your CPU predict?

Tags: tech, cpu, hardware, performance

Not all CPUs are born equal in term of branch prediction. Interesting little benchmark.

https://lemire.me/blog/2026/03/18/how-many-branches-can-your-cpu-predict/

C++26: Span improvements

Tags: tech, c++, standard

Nice little quality of life improvements coming to std::span in C++26.

https://www.sandordargo.com/blog/2026/03/18/cpp26-span-improvements

More Speed & Simplicity: Practical Data-Oriented Design in C++

Tags: tech, data-oriented, object-oriented, design, architecture, c++, performance

A very good talk which walks you through how to move from object-oriented design to data-oriented design. Shows quite well how you must shift your thinking and the difficulties you might encounter with data-oriented designs. I appreciate a lot that it’s not just throwing object-oriented design out of the window, indeed you have to pick and choose depending on the problem space. Also it’s interesting to see how C++26 reflection might make some of this easier.

https://www.youtube.com/watch?v=SzjJfKHygaQ

Minecraft Source Code is Interesting!

Tags: tech, 3d, graphics, game, portability, refactoring

Lots of interesting tricks in this code base. Gives also a good idea of the shape and tradeoffs of such ports.

https://www.karanjanthe.me/posts/minecraft-source/

Oxyde ORM

Tags: tech, python, rust, orm

Looks like an interesting ORM which brings advantages of the Django one without all the bagage. It’s still young, let’s see how it evolves.

https://oxyde.fatalyst.dev/latest/

Python 3.15’s JIT is now back on track

Tags: tech, python, performance, jit

Interesting read on how the CPython JIT effort has been saved.

https://fidget-spinner.github.io/posts/jit-on-track.html

The Optimization Ladder

Tags: tech, python, performance, optimisation

Here are the main levers to make Python code faster. Tries also to distinguish the effort level of each approach.

https://cemrehancavdar.com/2026/03/10/optimization-ladder/

XML is a Cheap DSL

Tags: tech, data, declarative, xml, portability

Interesting lesson here. It looks like XML still has its place in our modern tool belts. We should stop dismissing it too quickly.

https://unplannedobsolescence.com/blog/xml-cheap-dsl/

JPEG compression

Tags: tech, graphics, compression

Wondering how JPEG works? Here is a primer.

https://www.sophielwang.com/blog/jpeg

A Decade of Slug

Tags: tech, graphics, fonts, shader, patents

Nice algorithm for rendering fonts. Turns out it’s not patent encumbered anymore, this is good news.

https://terathon.com/blog/decade-slug.html

Video Encoding and Decoding with Vulkan Compute Shaders in FFmpeg

Tags: tech, video, codec, vulkan, computation

Vulkan compute shaders are very much capable nowadays. Exemplified by its use in FFmpeg.

https://www.khronos.org/blog/video-encoding-and-decoding-with-vulkan-compute-shaders-in-ffmpeg

The Best Darn Grid Shader (Yet)

Tags: tech, 3d, graphics, shader, mathematics

Good exploration on how to make grid shaders. It’s definitely not a simple problem.

https://bgolus.medium.com/the-best-darn-grid-shader-yet-727f9278b9d8

A sufficiently detailed spec is code

Tags: tech, ai, machine-learning, copilot

Or why this latest trend in genAI hype is a fool’s errand.

https://haskellforall.com/2026/03/a-sufficiently-detailed-spec-is-code

Rob Pike’s 5 Rules of Programming

Tags: tech, programming, optimisation, performance, complexity

These are good rules. Take inspiration from them.

https://www.cs.unc.edu/~stotts/COMP590-059-f24/robsrules.html

Invest Your Political Capital

Tags: tech, architecture, organisation, politics

Interesting model for bringing architectural and organisational changes. This is indeed at least in part political games… so you need some political capital to spend.

https://architectelevator.com/transformation/political-capital/

Bye for now!

Last week we released version 1.5 of Marknote, a fast and free alternative to existing slow and pay-walled note-taking apps. Today we announce a release that fixes some issues and improves a few things across the app.

So here is a list of the most notable changes and improvements:

• Pasting text in Source mode no longer clears document content.
• Pasting images from clipboard works really well too.
• Find and replace text shortcuts are brought back.
• Note names are now properly elided.
• Markdown syntax highlighter is added to the Source mode.
• Code blocks now have their own background.
• Items in the Table of Contents will follow active paragraphs.
• Edit button is shown in compact mode (for when the format bar is hidden).
• Fullscreen mode is brought back for those who need full immersion (Ctrl+Shift+F on Linux or Alt+Enter on Windows).
• The KRunner plugin now works pretty well inside Flatpak.
• Single note loading is much faster now.
• We optimized image loading and reduced video memory usage by almost 50%.

The future is bright

To address some of the questions since the last release:

• Yes, code blocks will have proper highlighting in upcoming versions (please keep in mind that we don't have the staff of a large enterprise company, and we probably don't need one either ;)).
• Yes again, quotes and some embedded content types are planned to be added too.
• Yes once more, cross-platform support is set to be improved. We will release stable versions for all the major platforms once they get through proper testing.
• And one more thing: the all-new and shiny block editor is a work in progress, and it will be done when it's done™.

Thank you all

Thanks to everyone for making Marknote your software of choice. We will make sure to keep Marknote up and running at lightning speed for everyone. As always, you can get the latest version of the app via Flatpak, Snapcraft or your favorite package manager. Stay tuned!