LAUTI Updates 2026

March 13, 20264 minutes

Welcome to our brand new blog! We want to start with what’s going on with LAUTI in 2026. The last release was a while ago, but we were busy nevertheless during the last months. We did a lot of networking with like-minded projects and people, e.g. at #39C3 and #FOSDEM26.

Whats new in 1.2.0

For the latest release 1.2.0 the focus was mainly on bugfixes like missing translated strings. A couple of smaller features were added as well that mainly serve new LAUTI instances and help in stabilizing the LAUTI code base.

Some highlights of the release:

2 new languages (Czech and Danish)
A new categorization: Areas
Improved admin experience around theming
Copy button to clone an event added
Release Binaries for x86 and arm available
Max zoom levels for maps now configurable

15 contributors made this release possible:

Joining the fediverse with nlnet

We’re delighted to announce that we started working on the #fediverse integration for LAUTI with support from nlnet NGI Zero Commons Fund. Thanks go out to @linos@graz.social for including us in his grant for interoperability of events in the Fediverse: https://nlnet.nl/project/Fediverse-event-interop/ The grant tackles the current plurality in event objects published by Fediverse servers. The goal is to streamline the event object and commit to a common baseline all applications understand and provide additional optional attributes.

In this scope we will implement publishing FEP-8a8e compatible event objects via a basic LAUTI instance actor. Furthermore, we will contribute to the refinement of FEP-8a8e.

Cooperation with Bonfire

Last year, Bonfire ran a successful crowdfunding campaign for project maintenance and a lot of cool features. One of them was the integration with LAUTI via the ActivityPub Client2Server interface. Sadly the crowdfunding did not reach the threshold for it, but we are still committed to make it happen.

We are currently in the beta testing phase and will hopefully bring this feature with version 1.3. So what is it about? And why Client2server? Well, Bonfire wants to enable communities to create and maintain their events and also bring them to the Fediverse. And instead of writing everything from scratch, they make use of the battleproven community events capabilities of LAUTI.

So with the upcoming releases instance admins can deploy Bonfire and LAUTI together, ideally via a tight integration in a co-op cloud recipe. For now, users will log in to the LAUTI backstage with their bonfire accounts to create events, which in return will then be transferred to Bonfire via Client2Server API. These events will then be published under a configurable single events actor on the Bonfire instance. For the future, publishing the events directly to group actors is planned.

LAUTI will act as a client and post events to an existing actor on the remote bonfire instance. This way people won’t have to follow two accounts but just one.

LAUTI documentation

Today, lauti.org also got an addition to improve usability of LAUTI. The brand new documentation is online. But beware that there are still gaps which need to be filled. We will tackle this in the upcoming weeks. The repository is also open for highly appreciated contributions.

New LAUTI Instances

Once there was only https://eintopf.info in Stuttgart, Germany, now the LAUTI ecosystem is growing. Since release of version 1.0 on May 1st 2025, new instances in our neighborhood stuck their head out: https://karlsunruh.org/ and https://ostalb.info/. Additionally a wider community adopted LAUTI: https://www.polyamory.events/. But these are not the only ones. More are in the making, also in other European countries. Stay tuned.

Do you know more LAUTI Instances in production or run one yourself? Please let us know, we are always interested in seeing LAUTI live in action and get in touch with operators.

What’s coming next…

In the next release we will finish up our SSO login feature. Then you can connect an OIDC provider with your instance. Another feature that needs finishing is the publisher. This will allow automatic publishing to other services like signal or telegram. Also the iCal importer is still in progress. With this festure you can use existing iCal feeds to list external events. Like mentioned above joining the fediverse is our next big step and will be a big focus of Klasse & Methode in the upcoming releases. Luckily we are not alone and others have their own focus. We are delighted, that @jeppe@uddannelse.social is looking forward to improve the new area feature.

Although new features are nice and shiny, we are aware, that maintaining the current software is quite a task already. Keeping up with dependency updates, onboarding new contributors and of course fixing bugs will still remain our top priority!

How to contribute

Contributions are always welcome :) There are all sorts of tasks, like adding or improving translations, writing documentation, fixing bugs or adding new features. Dropping into our chats on matrix is always a good start.