Subscribe to one of my feeds:
This is the homepage of Karl Voit.
On this page you can see the latest blog updates. For further articles, please use the search bar or navigate through the blue tags. My recommendations are pim, privacy, security and of course populararticles.
I recommend any decent RSS/Atom aggregator to get notified on blog updates.
Most recent articles or updates:
Das ist ein Artikel aus meiner Serie zu Songs und Liedertexten:
Das ist ein Artikel aus meiner Serie zu Songs und Liedertexten:
This is an extended comment from this original reddit thread where Deep-Fox6860 wrote:
Hi all, wanted to raise a discussion about a thought I had.
As a moderately experienced Emacs user (8 years), I've invested a LOT of time into learning and configuring Emacs (including email, RSS, browsing, calculator, etc). I can say that it does what I want and how I want it. I won't go into the fact that it's a never ending process because tastes and interests (+ jobs) change.
I would reckon that we all stick to Emacs, at least in some small part due to the sunk cost fallcy. Basically it means a price already paid in the past on our actions keep influencing our decisions in the future even though it shouldn't. From the link:
»People demonstrate "a greater tendency to continue an endeavor once an investment in money, effort, or time has been made."«
The question of whether the time invested in Emacs is worth the productivity gained is discussed here all the time. My view is to justify it by a combination of the following: believing in FOSS, (related to that) text centricity, and it could be viewed as a mental hobby, a creative outlet.
However I might admit that I exhibit some sunk cost fallacy thinking. It becomes clear when I realize that I WON'T recommend Emacs to new users - unless they are going to invest large amounts of time learning it, like I did.
What are your thoughts on this? would you admit that there's some irrational thinking in choosing Emacs over some other tools, e.g. the longer you use it the more you're convinced it's the best even though new tools are keep being developed.
I think I understand what you're writing here and to some extend, I do agree.
However, I would like to challenge the point of view to this good philosophical question on tool choice with this article.
DEL key doesn't work in email list"This is my report on my migration process from Thunderbird Mail 78.8.1 (64-bit) to Evolution 3.40.1 (by Flathub.org). Except my use-case with linking to emails (via message-ID) and opening those emails, my story should reflect a general business email/calendar management point-of-view.
My own blog generator lazyblorg is mostly a works-for-me project. However, there are people out there who do find its feature set intriguing so that they're using it for their blog.
If you took a look at lazyblorg before 2026-02, you might want to re-check as there are many cool features I added with the help of Claude recently. Yes, AI/LLM. Through unit- and E2E-tests, I'm fairly certain that the LLM-work was not introducing unwanted side-effects. After all, it's static HTML that is generated which (at least) should not cause any security concerns.
Not just for this shameless self-plug but also to inspire other blog generators, I'd like to mention a few features I personally do love and which I did not find in many other solutions yet.
For a long time, I've had the feeling that nowadays chart hits are quickly popular and also quickly forgotten.
I was never sure if this is just a subjective feeling of me getting older or me having more connection to songs from my youth in comparison to the music nowadays which I hardly listen to.
Today, I came up with a prompt for Claude LLM and let it work on my assumption.
Here is the resulting data. Please be aware that LLM is involved. So anything in the output might be wrong.
The result did not answer my assumption to my fullest satisfication. There are too many open questions left. For now, this is enough to me since I don't want to spent too much energy on that topic.
However, if there is somebody with the same impression, this might serve as a brainstorming and provide ideas for any further analysis with hard numbers which I - unfortunately - were not able to do without investing much more coding effort and data gathering.
If you do have further data, insight or links that contribute to the topic, please do comment below.
Hallo liebes Team vom Podcast "methodisch inkorrekt" (minkorrekt),
Ihr habt die letzten Episoden überlegt, wie es mit dem verstorbenen Podcast-Forum weitergeht, da die alte Wordpress-Instanz sowieso einen Neustart gebraucht hätte. Ihr sucht nach Hilfe, da ihr die technischen und organisatorischen Herausforderungen nicht mehr alleine stemmen wollt.
Verständlich.
Ich hätte da einen vielleicht etwas unkonventionellen Vorschlag.
Allerdings hat mein unkonventioneller Vorschlag aus meiner Perspektive sehr viele Vorteile für euch:
Mein Vorschlag wäre, das Forum nicht durch ein anderes Forum zu ersetzen.
Mein Vorschlag wäre ähnlich zum Di.Day-Rezept wie man zu Mastodon wechselt.
Das mag jetzt seltsam klingen aber ich denke, das ist absolut praxistauglich. Let me explain anhand eines Serviervorschlages für die beiden Perspektiven: das minkorrekt Team als auch die der Hörer:innen.
Klarerweise bleibt hierbei noch offen, wie man die Webseite an sich mit Artikeln befüllt. Allerdings zu diesem Teil des Problems gibt es sehr viele andere Möglichkeiten, wie beispielsweise die Klasse von statischer Webseitengeneratoren. Das aus meiner Sicht spannendere Problem ist daher, wie man die Interaktion mit den Hörer:innen gestaltet.
On this page, I collect my public/media appearances of any kind.
I do have a separate press information page with my bio in German and English, summary of my academic work and photographs to download. Drop me a line via email in order to get the URL.
Some of them are available in German language only.
Here are the shownotes of my GLT 2026 workshops to Emacs and Org-mode:
There is no recording of this four hour session. There were at least 42 participants (official count of the Linuxtage team at one point in time). However, there were many participants streaming in all the time.
Update 2026-04-10: Feedback suggests that the LLM did not get the issues right. So I probably would need to compile the list of MD issues with Obsidian manually but I don't know when I'll have enough time for that tedious process. I don't want to unpublish this for now. Maybe it serves as a starting point for people who would like to contribute.
Scott Jenson wrote a Mastodon message that brought me to his 43min talk about the issue that we've got hardly any innvation going on on our computer desktops. I've already mentioned that in articles like that one where I think that hardware is the only remaining innocation factor. Or that one where I would like to see the world abandonning the rest of the desktop metaphor because of its negative impact on our user interfaes.
Scott is well known in the field of user experience (UX) and interface design. He contributed ideas to Apple, Symbian, Google, Mastodon and Home Assistant.
Please do watch his talk where he promotes the idea of loops, gives recommendation to KDE, explains the issues with Microsoft Recall and mentions awesome projects like Ink & Switch, Dynamicland and other resources that are worth your time.
Once again, this talk confirms my presumption when I was doing research for my PhD that the desktop UI is stuck in a local optimum where we can't escape.
Ich war bislang immer recht skeptisch, was Rasenmäherroboter betraf. Die Dinger fand ich dekadent, da sie ziemlich teuer sind und ineffizient viel Strom verbrauchen für deren Grasschneideleistung. Die Routing-Algorithmen sind chaotisch, was die Hersteller als Vorteil anprangern (keine Streifenbildung).
Zufällig wurde ich beim Bauhaus (sehr gut) beraten, als ich mir die Dinger rein aus technischer Neugierde mal genauer angeschaut habe.
This is an article from a series of blog postings. Please do read my "Using Org Mode Features" (UOMF) series page for explanations on articles of this series.
In my "How to choose a tool" article, I describe the general approach how I do think that you should make tool choices.
Well, it's not just tool choices - the process can be generalized to any choice making process, if you think about it.
In order to support this process for a few steps, I generated an Org-mode yankpad template which minimizes the manual effort to create the boilerplate.
One single tool can not be a perfect fit for all sets of requirements. You need to differ between different situations, frequency of use, preconditions related to the user's knowledge, user interface requirements, and so forth.
On the other hand, for each given tool, there exists at least one set of requirements where this particular tool is a perfect fit. This way, each tool is a legitimate choice for at least one situation.
Since the requirements are defined by our situation alone, the only free variable here is the tool of choice. Therefore, we need to find a match between our current set of requrements at hand and a tool.
Unfortunately, I have to watch people making sub-optimal choices for their software tools too often. Most of the time, the root cause for a bad tool choice is that there was no deliberate process on how to select the tool. Maslow once said:
I suppose it is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.
For me, the proper way of choosing a tool is following this pattern:
In that order.
Let's take a look at each step.
It got complicated. In my opinion, we do need an overview, what information is visible/exposed/known to/by whom when using the Signal messenger software.
Until a few years ago, the situation was somewhat simple: there was your phone number, E2E encrypted content and some meta-data on the conversation and list of contacts. There were some analysis by Signal and external parties. All fine.
However, in the meantime, we've got additional features that complicated the situation in a way that even security savvy people don't know the details.
If you're, for example, contributing to a reddit thread about something which is irrelevant or anything with only a short-term relevance, this article does not apply to you right now.
However, as soon as you're helping somebody solving an interesting issue, summarize your experiences with something or write anything that might be cool to be around in a couple of years as well, you do provide potential high-value content. My message to all those authors is: don't use web-based forums.
In 2022, I talked about this topic at the Grazer Linuxtage and there is a video on the pages of the CCC as well as on YT:
In late 2023, I got the opportunity to give a talk at the 37C3 by the CCC in Hamburg. This talk was not recorded but overlaps in most parts with the recorded talk above.
TL;DR: all of the content of closed, centralized services will be lost in the long run. Choose the platform you contribute to wisely now instead of learning through more large data loss events later-on.
The longer version is worth your time:
(I do have a similar article on password management in english language as well.)
Ich war beim Podcast Methodisch inkorrekt! in Episode 239 mit einen Audiokommentar on air, wo ich etwas zu den Themen "Wie man eine Authentifizierungs-App auswählt" und Passwortsicherheit im Allgemeinen sagen durfte. Der bezog sich auf die Diskussion zum Thema "Google" der Podcast-Episode 238 "Mö Mö", wo Reini einen etwas saloppen Kommentar zu der Thematik geäußert hat.
In diesem Artikel möchte ich den Teil mit den Tipps zum Umgang mit Passwörtern und Zweifaktorauthentifizierung (2FA) beschreiben.
Natürlich gibt es hier im Detail noch interessante Dinge zu betrachten. Deshalb gehe ich in den folgenden Kapiteln auf die wesentlichen Fallstricke und Hintergründe etwas näher ein. Falls es phasenweise etwas trocken wird empfehle ich trotzdem, da zumindest einmal durchzusteigen, da die Sicherheit all deiner Daten und auch deines Geldes davon abhängt.
The Fediverse is an umbrella term for a federated set of social networking services that are able to exchange messages among each other.
You already know another federated Internet service: email. With your business email account, you can exchange mails with people using other email providers such as GMail, yahoo, hotmail, and so forth. It does not matter if your email partner is hosted on the very same email server as you. This is because both email services are able to talk to each other via an open standard.
Same as with email, you can decide to run your own server for a Fediverse service. Those servers are also called "instances". For instance, the instance graz.social (disclaimer: I'm affiliated) is running a few Fediverse services for our local community.
The most prominent Fediverse service is called Mastodon which is similar to X/Twitter. There are other Fediverse services you can imagine as free alternatives to some commercial networks:
| Fediverse Service | Similar to … |
|---|---|
| PeerTube | YouTube, Vimeo, … |
| Pixelfed | Instagramm, … |
| Lemmy | reddit, … |
... and many more!
I think that you definitely should start using free Social Network services from the Fediverse. Maybe as an additional network for starters. But then you really should think of stopping to use the commercial ones for multiple reasons.
And this is the story why this would be a very wise decision by you in the long run:
It's a long article. But you are free to skip sections that are not of interest to you right now. This article is not - and will never be - a complete guide for beginners. The main goal of this article is to express my arguments why it is a good idea to use Mastodon as your main social network and probably stop using all the others as they are unhealthy and manipulative.
Update 2026-02-11: Mein Beitrag erschien minimal gekürzt in der Ausgabe 7/2026.
Subject: Falter 6/26, S.11ff:
Eva Konzett Lina Paulitsch Tessa Szyszkowitz Barbara Tóth:
Droge Smartphone: Wie uns das Handy kaputtmacht. Und was dagegen zu tun ist
To: Leserbriefe@Falter.at
Cc: Szyszkowitz@Falter.at, Toth@Falter.at
Sehr geehrte Redaktion,
mit Interesse habe ich Ihren Artikel zu sozialen Medien in Ausgabe 6/26 gelesen. Die kritische Auseinandersetzung mit Endless Scrolling und süchtigmachenden Algorithmen war wichtig und überfällig – gerade weil diese Mechanismen nicht nur Kinder und Jugendliche betreffen, sondern uns alle. Während über Social-Media-Verbote für Minderjährige diskutiert wird, bleiben Erwachsene denselben manipulativen Designs ausgesetzt.
Was mir jedoch fehlte, war eine Recherche zu Alternativen, die bereits existieren und ohne diese problematischen Mechanismen auskommen. Das Fediverse – ein dezentrales Netzwerk mit Mastodon als bekanntestem Vertreter – zählt mittlerweile etliche Dutzend Millionen Nutzer:innen besonders im deutschsprachigen Raum. Hier gibt es keine Algorithmen, die uns in Filterblasen drängen, keinen endlosen Feed, der uns die Zeit stiehlt, und keine Konzerne, die unsere Daten monetarisieren.
Gerade jetzt erlebt das Fediverse durch Initiativen wie di.day einen bemerkenswerten Aufschwung. Diese Entwicklung verdient journalistische Aufmerksamkeit – nicht nur als technische Randnotiz, sondern als gesellschaftlich relevante Alternative. Es geht um digitale Souveränität Europas, um die Unabhängigkeit und Privatsphäre unserer Daten, um die psychische Gesundheit unserer Kinder und um unsere eigene.
Ich würde mich freuen, wenn der Falter in Zukunft auch diese konstruktiven Ansätze beleuchten würde. Kritik ist wichtig, aber das Aufzeigen von Auswegen macht sie erst wirklich wirksam.
Mit freundlichen Grüßen
Karl Voit
Vorstand "graz.social – Verein zur Förderung ethischer Digitalkultur"
Here's another real world comparison, although they are often problematic when you take those comparisons too seriously or you did not think it through properly. They always do have their problems when it comes to details, of course.
As I've stated already in Emacs is Not Just An Editor, I don't think that those editor wars do serve any useful purpose. I'm using both, vim and Emacs, for decades on a daily basis.
(Please note that I'm using "vim" as a term for the whole family of editors: vi, vim, neovim, ...)
I got the impression that most users of vim do not have the full picture when they complain about alleged downsides of the Emacs platform. And not every argument is meant in a jokingly fashion.
The earliest point in time where I myself was able to grasp the fundamental difference of Emacs to basically any other software, not just vim as a text editor, was only a couple years(!) before I started to embrace it. Some people will be faster in understanding all the impact, I'm sure. Unfortunately, from my experience most users of vim never got near that point in time.
Therefore, I think that comparisons from real world scenarios may be able to help to bridge this gap a bit. Let's try this one using a bicycle metaphor.
Mir wurde eine Podcast-Episode empfohlen, wo der selbsternannte "Finanzphilosoph" Maximilian Runge-Segelhorst als Interviewgast beim Podcast "beyond kpi" über seine Erkenntnisse zum Geldsystem spricht.
Disclaimer: ich bin kein Experte in dem Gebiet, kann auch die Theorien dahinter nicht so genau einordnen und fand die erwähnten Inhalte prinzipiell mal interessant, da sie eine mir logisch erscheindende Alternative zum gängigen Erklärmodell liefert, das auch für mich noch nie so richtig Sinn ergeben hat.
Wenn Herr Runge-Segelhorst deiner Meinung nach Blödsinn erzählt hat, dann freue ich mich über einen Kommentar, wo auch Quellen zitiert werden, wo man nachlesen kann, weswegen das Erwähnte nicht korrekt sein sollte.
To: drahtesel@argus.or.at Cc: argus.steiermark@radlobby.at, hannes.friedrich@radlobby.at Subject: Bitte keine Unterstützung für Geldmacherei mit wirkungslosem Schwurbel
Guten Tag,
Leider musste ich in der Drahtesel-Ausgabe 4/2025 auf Seite 11 feststellen, dass sie eine meiner Meinung nach unzureichend als Anzeige zu erkennende Seite platziert haben, wo Sie Werbung für überteuerte Produkte machen lassen, die nachweislich wirkungslos sind und mehrfach als Schwurbelei aufdeckt wurden.
On this page, I summarize my IT set-up according to the last update time-stamp in the changelog.
Here is a list of tasks I do on my computers and the software I am using for accomplishing these tasks. The first column also links corresponding workflow descriptions with further information on how I am doing things which should be our focus, not the tool. At the very bottom, there are links to more workflow descriptions.
For all the Emacs people visiting this page: here, I just list a few Emacs packages. For more details on which packages I'm using for my workflows, please do visit my online Emacs config and check out the first chapters explaining my setup.
It is important to emphasize that you can not derive anything for your situation without knowing my requirements and how they lead to my choice for a tool. For some workflows, I've added a link to further information which might also contain a description of my requirements (first column).
I love to watch someone doing stuff on computers. Partly this is because I am able to learn new things. Partly this is because I love to help people getting more efficient. Not because I want to show them how great I am. I do this because of my general aversion to spending time on things that can be done faster or avoiding things that are not worth the time at all. Additionally, I have so much fun when I am able to help people making their (IT) world a bit more enjoyable.
When I do give advice, I sometimes suggest a different tool which I do think might be better for the job. Sometimes I suggest a slightly different method to achieve the same or even a better result.
However, Many times I hear the phrase "it's OK, it's good enough for me" when I try to give advice on personal information management in general. I do think that in many cases, this is just an excuse.