Initially, I planned to present the current state of K4/Clarissa Chemnitzer Linux Tage 2024 but it has been rejected, unfortunately. Please, feel free to read abstract and a short paper originally submitted there. Additionally, I added a short article in German instead, that describes what was intended to be shown.

In the meanwhile K4/Clarissa contains about a decade of work of two. We developed a lot of concepts and tested database engines (see our DSBENCH project). While the software is growing it becomes more and more clear that we need supporters who can contribute at many construction sites we still have, for instance: GUI conception and design: More eyecandy widgets, matching color palettes, GUI concept and workflow optimization. Although Clarissa is already able to “speak” English and German, it would be fine to give all dialogs a revision.

Maybe, some of you will ask why our software (although its intended as Open-Source) isn’t available for download so far. The reason is quite simple: We have high demands on quality of a piece of software before we publish. Most of the software is written in Python3. We already made some tests with cx_Freeze to create a “compiled” release, but there is still a lot to do to get reliable results.

The GUI of the K4 project Clarissa contains an included help and description. I compiled the introduction and the index of the current state (in German) of that documentation.

Clarissa Net is simply a network consisting of K4/Clarissa users which are able to communicate to each other. Be noted, that the communication is not limited to K4/Clarissa users only, but the scope of communication is vastly extended if both are using K4/Clarissa. K4/Clarissa includes several systems to communicate to others. We call such systems transports and they are based on known methods like Telegram (https://telegram.org), Matrix (https://matrix.org), XMPP (https://xmpp.org), E-mail.

After a long time of silence on this site its time to give at least a short update about progress on our K4 project. Contrary to the picture that our web presence gave to you the project is still active and experienced some fundamental changes. The following notes only give a short and incomplete overview about what happened (between 2019 and end of 2023): Our original intention to implement the GUI of K4 (which is also called Clarissa) in Object Pascal turned out to be too limited - so we decided to completely redesign it in Python3 + QT5.

Presentation at Chemnitzer Linux Tage 2019 event is done now. Please, feel free to download the presentation or to read a detailed treatment (both in German).

We plan to present the current state of K4 for the first time at Chemnitzer Linux Tage 2019. Our presentation will be in German. Please, feel free to read abstract and a short paper.

In order to test our e-mail import module and the word indexer we picked up the ENRON e-mail corpus and loaded it into our database. ENRON was one of the biggest US energy companies with headquarter in Houston, Texas. In 2001 ENRON caused a big scandal due to continued balance forgery. During crime investigations all e-mails of the company were confiscated. In the meantime these e-mails are released for computer and programming science purposes.

Over the last years communication between people has changed substantially by the use of smart phones and messengers like WhatsApp and Telegram. Nevertheless, communication by e-mail is still one of the most important ways of exchanging digital data and information. This is even more true for companies and authorities. Hence, e-mail is a key element in the management of personal and private data. From a technical perspective a single e-mail contains communication content and besides of that also a lot of useful information in the header, for instance receive time, addresses and names of communication partners.

Applications that collect searchable data (basically every messenger) usually use a SQLite database. SQLite is a very simple relational SQL database without any procedural programming capabilities. Datacentric applications, even those which use far more advanced database products, often view a database as a simple data storage container from which data can be retrieved very fast. If no attempt is made to use relational features, a database often is reduced to a centralized data store, used by some orthogonal persistence layer which is fed data by some middleware.

Tiny Data - What is that supposed to be? Imagine the following situations. A few months ago, you had a great idea and wrote it down in an electronic file. Suddenly you need your notes, but how do you find them? Because somehow they are not in the place you remember them to be. And your operating system doesn’t know about a thing called “note”. But you could still search your entire drive…