This is my first blog post for Google Summer of Code 2023.
During the Google Summer of Code timeline, I will be working on implementing the admin APIs in Tokodon. These APIs will provide mastodon moderators with a suite of moderation tools within Tokodon. I would like to thank Carl Schwan ❤ for mentoring me during Season of KDE and once again for this project. I am really grateful to work under his guidance. By implementing this new feature, Mastodon moderators will be able to easily adopt Tokodon and utilize moderation tools within the application.
I haven’t come across any Mastodon client that implements the admin APIs so by implementing this feature in Tokodon, we can ensure wider adoption. I’ve already started working on implementing the feature and have been maintaining regular communication with my mentor.
I will be writing regular blog posts on my website. You can follow my progress here
If you’ve been following my previous blog posts, you may recall that I’ve been working on enhancing the user interface of the Bundle Creator in Krita. The new Bundle Creator is to be designed similar to an installation wizard. By compartmentalizing the functionality into four separate sections, users can effortlessly navigate through the various aspects of bundle creation process.
My Progess so far…
I spent the last two weeks working on the Resource Chooser section. The Resource Chooser page allows users to users to handpick the resource items they wish to include in their new bundle. The most notable enhancement is the transition from a traditional list view to a more intuitive grid view for the list of available resources, similar to the Resource Manager layout.
In the previous version, users were required to individually select each resource item and use the > key to add them to the list of selected resources. However, now users can simply click on resource items directly to add them to the selected list. This seamless integration of the grid view and the ability to click-to-select greatly streamlines the workflow, especially benefiting tablet users of Krita.
One can also filter resources by tag or name before choosing resource items to be added to the selected list. This allows users to swiftly select resource items that serve a similar purpose when creating a new bundle. Gone are the days of scrolling through the entire list of available items; now, users can easily narrow down their options through efficient filtering.
And finally, to remove a single resource item, users can now simply select it by clicking on it. Similarly, for removing multiple items, users can hold down the Ctrl key and select multiple items imultaneously.Once the desired resource items are selected, users can easily remove them by clicking on the Remove Resources button .
In the upcoming weeks, I would be working on the Choose Tags section. This requires some UI related feedback, and if you’re interested to help out, please feel free to drop a comment on this post I created on Krita Artists Forum!
And just to add a splash of colour to my blogpost, this is just a very quick artwork which I made using Ramon’s impressionism brush bundle. It’s super easy to use, do check it out! :D
MauiKit: A Toolkit for Multi Adaptable User Interfaces.
Today, we bring you a new report on the Maui Project’s progress.
We are excited to announce the latest release of MauiKit version 3.0.0, our comprehensive user interface toolkit specifically designed for convergent interfaces.
Built on the foundations of Qt Quick Controls and QML, MauiKit empowers developers to create adaptable and seamless user interfaces across a range of devices.
Community
To follow the Maui Project’s development or say hi, you can join us on Telegram: https://t.me/mauiproject.
Note: Please be aware that this is an ISO image from a third party.
What’s new?
In this update, we have focused on enhancing MauiKit’s capabilities to support convergent interfaces. With improved components, added features, and bug fixes, MauiKit enables developers to build interfaces that seamlessly adapt and respond to different screen sizes, resolutions, and device form factors.
In addition to the enhancements made to MauiKit, this release also includes updates to the Maui App stack. The Maui App stack consists of a suite of applications developed using MauiKit, designed to provide a consistent and cohesive user experience across different devices. These updates further strengthen the stack, ensuring a smooth and integrated workflow for developers and a delightful user experience for end-users.
With the convergence capabilities of MauiKit, applications built using the stack can seamlessly transition between desktop and mobile interfaces, providing a unified experience across different environments.
Check out the previous progress report blog for more details on what has been cooking for this new release:
Now, let’s delve into the details of the new release of MauiKit, exploring its enhanced features for building convergent interfaces. We will also showcase the updates to the Maui App stack, demonstrating how developers can leverage its capabilities to create compelling cross-platform applications.
Join us on this journey as we unveil the potential of MauiKit for building convergent interfaces and discover the possibilities offered by the enhanced Maui App stack.
A few custom CSD button styles added. I’ll probably move them to a new package maui-csd-styles. If you have a favorite window control button style- from back in the days of emerald and metacity – leave a comment with a link and I’ll add it. #mauikit@maui_projectpic.twitter.com/713rE9B1iI
A script element has been removed to ensure Planet works properly. Please find it in the original post.
MauiKit Frameworks
At the core of the Maui Project lies its foundational framework, MauiKit Controls, which provides a comprehensive set of template controls for creating user interfaces. In this latest release, we have made significant improvements to MauiKit Controls, focusing on enhancing its configurability and overall consistent user experience.
One of the notable advancements is the increased configurability of MauiKit Controls, allowing developers to adapt the interface to user preferences more effectively. For example, new color styles have been introduced specifically tailored for E-Ink and AMOLED displays, ensuring optimal readability and energy efficiency on these screen types. This level of customization empowers developers to create interfaces that cater to the unique needs of users and their device preferences.
Furthermore, we have worked to establish a more consistent look and feel across all graphical elements within MauiKit Controls. This coherence ensures a seamless user experience, where controls harmoniously blend together, providing a polished and professional interface. Users will appreciate the enhanced visual consistency and intuitiveness of the controls, resulting in a more satisfying and engaging interaction.
Controls & Style – [3.0.0]
Make the ToolActions have a uniform height for all the children.
Style fixes to the ComboBox and SpinBox.
In the Handy object check the clipboard for an image.
Allow opening ContextualMenu and the cursor position.
New control TextFieldPopup: a text field that expands to a popover for listing elements; a use case is for presenting inline searches and filtering.
Fixes to the minimum ApplicationWindow size constraints on mobile.
Tweaks to the TabView tabs, supporting now color and icon. Fixes the interactive property for touch-swiping gestures.
Fix padding of elements such as custom CSD buttons, FloatingButton, SelectionBar, and others.
Refactor the ToolActions control, no longer based on indexes, but rather relies on the Action children for setting the states.
Fixed the crashing issue on Wayland when performing a DND action.
The ListBrowserDelegate and GridBrowserDelegate now expose the autoExclusive property for such usage.
Start using the new MauiMan Accessibility module properties for the scrollBarPolicy and playSounds preferences.
Style the CheckBoxItem control for better contrast and consistency with the rest of the elements.
Fix binding loops on some controls, such as ToolBar.
Added a constrained width for the SideBarView sidebar to never exceed the width of the available screen width.
A script element has been removed to ensure Planet works properly. Please find it in the original post.
FileBrowser, TextEditor, ImageTools, and Accounts – [3.0.0]
MauiKit FileBrowsing, has also received refinements in this release. The dialogs within MauiKit FileBrowsing have been redesigned to be more compact and visually pleasing, providing a cleaner and more user-friendly interface for managing files. Drag and drop operations have been fine-tuned to ensure smoother file manipulation, simplifying the organization and transfer of files.
A script element has been removed to ensure Planet works properly. Please find it in the original post.
Additionally, the API of MauiKit FileBrowsing has been cleaned up, resulting in a more consistent and developer-friendly experience. These improvements streamline the integration of MauiKit FileBrowsing into applications, allowing developers to leverage its power more efficiently.
The frameworks received the necessary fixes for supporting translations via KI18n and the KDE’s infrastructure.
Check if the clipboard has any content that can be pasted into the FileBrowser.
Allow pasting images and text streams into a new file in the FileBrowser.
Added a readOnly property to the FileBrowser to avoid performing modifying actions, such as deleting, creating, or moving.
Allow selecting large amounts of files – still not good [TODO]
Do not count “.” and “..” entries in the directory count info.
Documents & Calendar – [1.1.0]
Updated to the latest MauiKit Controls changes. MauiKit Calendar has been updated to the latest changes in the Akonadi Frameworks.
Terminal – [1.1.0]
MauiKit Terminal serves as a terminal emulator control, powering the MauiKit Station app. In this new release, MauiKit Terminal has gained several exciting features to improve its functionality and usability. Users can now easily search through their command history, making it more convenient to reference past commands and outputs. Additionally, notifications for finished processes ensure users stay informed about completed tasks, enhancing multitasking capabilities.
To prevent accidental closures, MauiKit Terminal now includes alarms that warn users before closing any running processes. This helps avoid unintended disruptions and gives users the opportunity to save their work or take necessary actions. Furthermore, the adaptive color scheme of MauiKit Terminal has been refined for better readability and visual comfort, catering to various devices and screen types. The improved touchscreen support makes it even more intuitive for users to interact with the terminal using touch-based gestures.
Do not trigger a signal for the process name if it has not changed.
A script element has been removed to ensure Planet works properly. Please find it in the original post.
Maui Apps
The Maui Apps cover a wide range of essential functionalities, including a file browser, music player, text editor, image viewer, notes taker, video player, web browser, and calendar. In this latest release, our focus has been on expanding and refining the app stack, ensuring consistency, and bringing newer apps up to par with the established ones.
Among the recent additions, we have introduced an archive manager, providing efficient handling of compressed files. A GIT version control manager has also been included, streamlining collaborative software development. The new colors utility app helps users manage and explore color palettes effectively, while the camera app offers a convenient solution for capturing and managing photos.
It’s worth noting that some of these Maui Apps are also available on Android, making them accessible across multiple platforms. Furthermore, these apps are designed to work flawlessly on Linux phones, tablets, and desktop computers, ensuring a consistent and seamless user experience regardless of the device being used.
Index & Nota
Index PathBar delegates now mask the content item to the arrow shape for more precise clicks.
Index now allows pasting raw image and text buffers into a new file.
The main context menu now pops up on the cursor position if triggered with a right-click on the desktop.
Check if there are items in the clipboard that can be pasted.
Fiery & Vvave
Fiery now can download files and notify about them.
Fiery has a more compact look with merged tabs and toolbars.
Fiery has a more adaptive interface on mobile mode.
Vvave now has preference properties for toggling album titles.
Fiery web browser with a more compact & responsive layout + detaching tabs. now can also download files etc…#mauikitpic.twitter.com/MUZLvnwzK4
A script element has been removed to ensure Planet works properly. Please find it in the original post.
Buho & Pix
Bonsai & Clip
Bonsai refactored with a new backend for performing GIT actions.
Arca & Station
Arca can now create new compressed archives.
Correctly prevent closing active processes and correctly accept to stop them.
Station now has a new shortcut bar for signals.
Station now checks the current program being executed and sets the best-fitted shortcuts bar, for example for Nano the nano bar.
Station with fixes for text rendering with Zsh themes. added more configuration options in settings. and support for alerts on finished processes and prevent closing running processes too… also configurable.#mauikit@maui_projectpic.twitter.com/7ZoF8SlTUQ
Finally a sprint again! The 2019 the Plasma Sprint in Valencia was my first in person KDE event and I was hooked instantly.
However something mysterious happened in the next years that and in person meet ups stopped happening. While Akademy 2022
happened in person again, a sprint has different atmosphere and I was awesome to see people that couldn’t make Akademy
or for whom it was their first sprint. Other attendees have blogged about the sprint as well, check them out too. Either on
the planet or over on discuss Carl created a collection of a bunch of them.
So what did I do? Aside from the usual talking, discussion, planing which the others already blogged about. (And of
course the live bug investigations on fellow developers’ machines who always seem to attract the weirdest issues.)
I am afraid I spent the rest of the time on boring backend stuff.
For Plasma 6 we want to make use of the layer-shell wayland protocol
for positioning and stacking Plasma’s own panels, backgrounds and some other windows such as krunner. This protocol
was developed by the awesome wlroots people and is currently proposed
for standardization. In the past we used our own plasma-shell protocol and unfortunately not only Plasma is using it at the moment
but it also spread to applications with more advanced use cases than just having a normal window. As mixing windows from
both systems together will be harder to layout and in general a desire to move on from the plasma-shell protocol for a more
streamlined experienced I ported yakuake to use layer shell
via our own Layer Shell Qt library.
Still Wayland related but probably even less interesting, I started porting libtaskmanager away from KWayland. KWayland was/is a framework consisting of two libraries (client and server side) wrapping wayland code
for more straightforward consumption of Qt programs. As you can imagine this is quite some amount of boring code to maintain
and with other good solutions available we would like to stop doing so. The server part of the framework was already
moved to KWin in the past and we embraced qtwaylandscanner there for generating code wrapping wayland. For the client
side we are now moving in the same direction. KWayland included everything but most of it was not used because Qt handles
all the normal interactions with the compositor and almost all the remaining protocol interfaces were used only once
because there is only a single place in our stack that needs to communicate the additional information with KWin (for
example Klipper or the taskmanager). So it makes sense to move the code to the places where it is used instead of having
to maintain a framework with the usual stability guarantees.
But I did not only work towards eliminating a framework, I also created an entire new one. Sorry! Enter
KColorScheme. To be fair it’s not entirely new but KColorScheme
and friends moved to their own library. KColorScheme was a pain point in our dependency stack since it was
very central but its location in the KConfigWidgets library meant that you had to depend on a bunch of unwanted
stuff just to read some colors. So we decided at the sprint to split it out to a new library and I implemented that.
Afterwards I adjusted some consumers which do not need to longer depend on KConfigWidgets together with Nicolas.
As you can see it was quite the productive sprint which was possible because of the awesome people at Tuxedo Computers
who hosted us and the KDE e.V that enables people from all over the world to come together and build
awesome things. Consider donating so that we can continue doing so.
The last thing left to say, I will be at Akademy which happens soon. See you there!
As you probably have seen from other people’s blog posts there was the 2023 Plasma Sprint last week. It was generously hosted by TUXEDO Computers in their offices in Augsburg, Germany. Many thanks to TUXEDO for that!
Other people have already well summarized what happend there, so let’s have a look at what I have been doing:
Together with Kai Uwe, Volker, and Ismael I looked at notifications. This includes internal simplifications in KNotifications, API design questions, a proposed V2 for the notification portal API, and a new UI for per-event configuration in the notification settings module.
Together with Marco I looked into some API design topics around the Applet class in plasma-framework, and worked on a proposed new API for applet actions.
Given that Wayland was a huge topic at the sprint I continued the work of mine on enabling some accessibility options on Wayland. Sticky keys is not only what happens when you spill Spezi over your laptop, it is also an accessibility feature that allows people that cannot press multiple keys simultaneously to type key combinations like Control+C/Control+V. Basic support for this on Wayland is coming with Plasma 6. Not all of the options that are present on X11 work yet though. If you are a user of sticky keys please leave your feedback on https://bugs.kde.org/show_bug.cgi?id=444335 for which of these options should be prioritized.
Together with Natalie, KDE e.V.’s Hardware Integration Engineer, I discussed our touchpad configuration module and how to make it more robust and maintainable. We also discussed various topics around debugging and profiling KDE software.
Together with Xaver I looked into how Dolphin/KIO handles multi-GPU setups (so that apps preferring discrete GPUs will use them when launched via KIO). As it turns out there’s a few things to be improved there so we discussed approaches to do that.
With David I discussed some of my open changes to our global shortcuts infrastructure and continued working on improving that.
We also got a visit from two people from the city of Treuchtlingen, Germany. They have been using KDE software in their communal IT for over 20 years. We discussed their vision of using open source and open standards in government IT and some of their pain points with using KDE software for that.
Overall it was a very nice and productive week and it was great to meet so many fellow KDE hackers, some of them for the first time! Gatherings like this are only possible because of generous donations to KDE e.V. Please consider donating to make more such sprints possible.
I’m Srirupa Datta, about to finish my undergraduate Electrical Engineering degree at Jadavpur University, India, in June. This year, I got selected for Google Summer of Code and will be working on improving the Bundle Creator in Krita.
My Introduction to Krita…
It’s been more than a year since my last blogpost where I posted monthly updates on my progress on adding the Perspective Ellipse assistant tool in Krita during SoK’22. Being a painter who’s interested in software development, I’ve been interested in Krita ever since I started using it.
What it’s all about
The primary format to share resources in Krita is a Resource Bundle, which is a compressed file containing all the resources together. It also contains some other information like metadata and a manifest so Krita can check there’s no errors in the file.
Krita’s Bundle Creator allows one to create their own bundle from the resources of their choice. The project that I would be working on, aims to improve the user interface of the current Bundle Creator, and allow the ability to edit bundles (which is currently not supported in Krita).
The new Bundle Creator
The new Bundle Creator would look like an installation wizard with four pages which can be navigated using the Next and Back buttons, as well as buttons on the left side panel.
I think the primary objective behind designing the new Bundle Creator was to organize its workflow, that is, segregate sections devoted to a particular function or job. This is what led to the idea of using a wizard, instead of simple dialogs. Hence it would have four wizard pages:
Choose Resources
Choose Tags
Enter Bundle Details
Choose Save Location
Some of the cool features you can expect in the new Bundle Creator are a gridview like that of Resource Manager’s to view all the resources, filter resources by name or tag before selecting, and an option to change back to the default listview from gridview if one wishes to stick to the previous layout.
Adding custom tags to selected resources is a feature that we wish to integrate, but it would require a redesign of the Choose Tags wizard page that has been shown below. Just to clarify, these are all mockups!
Yet another important feature would be reloading last bundle data when opened/on startup - this is particularly useful when making a bundle for other people.
Apart from these, the new Bundle Creator would be resizable(Yaay!), and a separate Menu entry called Bundle Creator would be created. We plan to move Manage Resource Libraries , Manage Resources and Bundle Creator from Menu > Settings to Menu > Resources.
And lastly, I would be working on adding the feature of editing bundles - this however needs to be discussed more and would be dealt with post my mid term evaluations.
And of course, if you want to suggest some ideas or improvements, feel free to drop a comment on this post I created on Krita Artists Forum!
I’ve been happily using Woodpecker CI to get CI for my repositories on Codeberg.
Codeberg is a non-profit community-driven git repository hosting platform, so they can’t provide free CI to everyone.
Since I run lots of stuff on small arm boards (for example this website), I need my CI jobs to create arm executables.
The easiest way to get that done is to just compile on arm devices, so I was happy to see that Hetzner is now offering arm nodes in their cloud offering.
To make that as cheap as possible, the CI should ideally create a VM before running its job, and remove it again afterwards.
Unfortunately Woodpecker does not seem to support that out of the box at this point.
My solution to that was to build a docker proxy, that creates VMs using docker-machine, and then proxies the incoming requests to the remote VM. That works really well now, so maybe you will find it useful.
Setting that up is reasonably simple:
Install docker-machine. I recommend using the fork by GitLab
Install the backend for your cloud provider. For Hetzner I use this one
Create a systemd unit to start the service on boot in /etc/systemd/system/docker-proxy.service.
This particular one just runs it on the woodpecker-agent user that you may already have if you use Woodpecker CI.
Fill in /etc/docker-proxy/config.toml
This example works for Hetzner, but everything that has a docker-machine provider should work. You just need to supply the arguments for the correct backend.
IT feels like a billion years before the last plasma sprint, which was in 2019 in Valencia, before the pandemic, but finally this year we are back on track, and was great to see again many old friends as well as seeing many new faces for which it was the first sprint.
We were gracefully hosted by Tuxedo Computers in Augsburgh, makers of very nice laptops that come with Linux and KDE Plasma, as well as being KDE patrons.
First of all, everybody got up to speed with a full git build of a Plasma 6 session, so that everybody could participate in development and discussions from the same level.
There were many discussions about Plasma 6, about what we want to do in Plasma and in Kirigami, how we want to change the look and defaults for the new major release. Most of the user-facing changes have been wonderfully described by Nate.
On my part, I worked on mainly 2 things, that were fairly not “glamorous” but quite important never the less (and mildly painful to do) : a refactor of the plasmoid loading code and splitting all the Svg themes code to a new framework with far less dependencies, ideally usable by any application.
Plasma API
I spent most of my hacking time at the sprint on a refactor of the plasmoid loading code, which won’t be really “seen” by the user, but will make the infrastructure much more robust and the API cleaner.
The person which must pay attention to it is the plasmoid author, which will need to adapt the plasmoid code in a few places.
Most notable is that, just like when you are writing a QML application you have to use the ApplicationWindow root QML Item, for a plasmoid you now have to use a PlasmoidItem root object, so something like
Using the Plasma Svg code to support stylesheet recoloring, on disk image cache to speed up loading, and the 9-patches FrameSvg is something the several applications would be interested to, and some actually are already doing, but since plasma-framework has a lot of dependencies, for some applications that is a blocker. All the svg code has now been broken out into a new framework called KSvg, which is still work in progress, but in the end will support all existing plasma themes with no change, and if an application wishes to use it, the svg sets will be loaded from the app own data folder (or anywhere else the application configures it to) instead of the share/plasma/desktoptheme folder, where plasmashell looks for them (so they can also use a complete different theme structure and don’t have to provide the same elements)
While at the 2023 Plasma Sprint at the Tuxedo Computers office in Augsburg, Germany, I created a patch to add ButtonSegment, SegmentedControl and SegmentSeparator to Qt Quick Controls 6.6: https://codereview.qt-project.org/c/qt/qtdeclarative/+/476564
The patch has not been merged yet and may change significantly.
ButtonSegment is a Button subclass with an edges property that can be used to specify which edges are exposed to the outside of the group. The base flags available are NoEdges (0), TopEdge (Qt::TopEdge), LeftEdge (Qt::LeftEdge), RightEdge (Qt::RightEdge) and BottomEdge (Qt::BottomEdge). Why the outside and not the inside? It doesn’t matter a whole lot, it’s just what I decided to do. My thoughts were "These are the edges where extra visuals will be." There are also flag combination values like AllEdges, TopLeftEdges, TopRightEdges, BottomLeftEdges and BottomRightEdges to make your lines of code shorter.
SegmentedControl is a Control subclass with flat and down properties. This control doesn’t actually do much. Its main purpose is for providing a way to define unified graphics for a segmented button group (e.g., macOS Big Sur has a background underneath all of the button segments). flat can be used to define flat and raised appearances. down can be used to define a unified pressed/down appearance (e.g., a shadow used by a unified raised background could disappear when any segment is pressed). down does not change in response to ButtonSegment::down changes by default. You must set that up yourself. There are ways to make this behavior more automatic, but I have not used them yet. I might make the behavior more automatic because otherwise it will be difficult to support down when button segments are created from delegate components.
SegmentSeparator is a Control subclass that has orientation, vertical and horizontal properties. It has the same API as ToolSeparator. Its purpose is to provide styling for separators between button segments.
Automatic Behavior VS Boilerplate Code
Unlike similar controls provided by Flutter (SegmentedButton) and AppKit (NSSegmentedControl), there is no built-in API for getting/setting the current selected button(s), index(es) or other value(s) from segments. This isn’t a big problem in QML because it is easy to add the additional behaviors or properties you need. You can even choose the ones that suit your use cases the best. Don’t forget that you have ButtonGroup, ActionGroup, Repeater, ListView, GridView and various ways to define models.
Some, maybe even many of you may have felt a bit disappointed after reading the paragraph above. You may have been thinking something along the lines of "Why doesn’t it just do what I want without having to write extra code?" It’s a good question. When people (including myself) try to reduce the amount of code they need to write by making controls do things automatically, they often cause more harm than good. If the problems were obvious and the temptation wasn’t so strong, then people (including myself) wouldn’t make those kinds of mistakes over and over. What often happens is that controls that were intended to be generally useful become more specialized for certain use cases and the people implementing the automatic behavior don’t realize it until they discover that a valid use case they weren’t thinking about has become more difficult or even impossible to support. There are examples of great automatic behavior out there and specialized components where a lack of flexibility is completely acceptable. My point is that people should be careful when implementing automatic behavior. I chose greater flexibility at the cost of requiring users to write more code.
Example Code
This creates three independently checkable segments in a row.
Even if Kaidan is making good progress, please keep in mind that it is not yet a stable app.
Do not expect it to work well on all supported systems.
Moreover, we do currently not consider Kaidan’s security as good as the security of the dominating chat apps.
All messages sent by Kaidan can be encrypted now.
If a contact supports the same encryption, Kaidan enables it by default.
Therefore, you do not have to enable it by yourself.
And you will also never need to worry about enabling it for new contacts.
But it is possible to disable it for each contact at any time.
Additionally, all metadata that is encryptable, such as typing notifications, is encrypted too.
The new Automatic Trust Management (ATM) makes trust management easier than before.
The details are explained in a previous post.
We worked hard on covering as many corner cases as possible.
Encrypted sessions are initialized in the background to reduce the loading time.
Kaidan even tries to repair sessions broken by other chat apps.
But if you discover any strange behavior, please let us know!
We decided to focus on future technologies.
Thus, Kaidan does not support OMEMO versions older than 0.8.1.
Unfortunately, many other clients do not support the latest version yet.
They only encrypt the body (text content) of a message, which is not compatible with newer OMEMO versions and ATM.
But we hope that other client developers will follow our lead soon.
XMPP Providers
Kaidan introduced an easy registration in version 0.5.
It used an own list of XMPP providers since then.
The new project XMPP Providers arose from that approach.
That project is intended to be used by various applications and services.
Kaidan is now one of them.
It uses XMPP Providers for its registration process instead of maintaining an own list of providers.
Try it out and see how easy it can be to get an XMPP account with Kaidan!
Changelog
This release adds the following features:
End-to-end encryption with OMEMO 2 for messages, files and metadata including an easy trust management
XMPP Providers support for an easy onboarding
Message reactions for sending emojis upon a message
Read markers showing which messages a contact has read
Message drafts to send entered messages later after switching chats or restarting Kaidan
Message search for messages that are not yet loaded
New look of the chat background and message bubbles including grouped messages from the same author
Chat pinning for reordering chats
Public group chat search (without group chat support yet)
New contact and account details including the ability to change the own profile picture
@k3ys:matrix.org
GSoC
nicofee
noahdvs
