I also really hate that since AI slop has turned search engines useless, you virtually cannot find anything, even if you remember the exact words of the title.

Yeah, extremely cheesy way of putting it: The best work position is the next one.

I.e. don’t stay in one position for a long time, but rather switch it up regularly.

I’m guessing, they mean JavaScript and WebAssembly in general…

Oh man, this is one of the songs that lots of amateur bands have in their repertoire now, because of the clown association, even though it’s actually quite a difficult piece.
So, I thought, maybe a recording on YouTube with *checks notes* 18 million views would be better. And let’s just say this: Hahaha no.

🫠

alot

I mean, yeah, this shouldn’t be seen as an announcement or whatever, but rather as a thing to discuss and potentially get involved in. KDE is a community project after all.

I mean, I do like the idea, but syncing such a database file is by far the smallest challenge about this (and could be easily achieved today with e.g. Syncthing or Rsync).

The far harder part is getting RSS readers to support the same file format. There is actually a small project (by basically a singular guy), which tries to accomplish this: https://github.com/39aldo39/DecSync
The desktop RSS reader it supports is GTK, though.

Somewhat of a technologically simpler solution might be to self-host FreshRSS.
Unfortunately, it is of course less simple to actually use, unless you have a home server and some sysadmin skills…

Well, I have it bound to Super+X, but you could do any of those. I just create a .desktop file for it and then it can be used like a normal application. And well, it is intentionally built so you don’t have to pass command-line flags or see the command output for creating the file.

So, this is the program I use: https://codeberg.org/trem/jot
It has basically three larger features, which is adding a file, removing empty files (because you sometimes might end up creating a file, but not using it) and then searching through empty files.
Honestly, none of these are particularly difficult to throw together in a Bash script yourself, if you don’t feel like using a random program off the internet.

Basically, for adding a file, this is a crappy version of it:

data_dir="$HOME/.local/share/notes"
mkdir -p $data_dir
date=$(date +%s)
file_name="$data_dir/${date}.md"
touch $file_name
xdg-open $file_name

And for searching through the created files, grep -iR -C2 $data_dir is virtually just as good, too. 🫠

Well, I assume they had other concerns, too. For example, it adds a bunch of complexity for reformatting a JSON from single-line to pretty-print, if comments can appear in there. I’m certainly not saying that I’m always best friends with the decision to remove comments, just that I can somewhat understand it.

Hmm, if I understand you correctly, this is about Windows blocking access to files while they’re being accessed by other processes. Kate is primarily built for Linux where this would not be a problem to begin with, so it is well-possible that it does not handle this gracefully.

But it does actually keep its own buffer for files. By default, you have to actively click in the UI before it will load the changes from the file. It does watch the file for file changes, but I don’t think, it has to keep the file open for that, since there’s kernel APIs to be notified for file changes on all mainstream operating systems these days.

So, uh, TL;DR: I don’t actually know, but I’m somewhat optimistic. 🫠

I have a tiny program/script that creates a file in a folder underneath ~/.local/share with basically just a timestamp in the file name and then it opens it in Kate. Certainly somewhat of a workaround, but it works quite well for me.

I can understand the sentiment and would 100% agree for programming languages.
But personally I actually like that it encourages a flat structure, because you do not want to be yakshaving the structure of your config file. Too much nesting means you will sooner or later run into configuration keys being nested under the wrong category, because your project context changed over time.

And well, as I’ve argued in a few other comments already, I think non-techie users have a disproportionally simpler time when no nesting is used. They understand the concept of a heading and then just adding a line underneath the appropriate heading is really intuitive.
You can just tell them to add the line certificate="/tmp/cert.crt" under [network.tls] and they will find a line in their config file which actually reads [network.tls] and they can just paste that line as-is.

With nesting, they’d need to add it under here:

network: {
    tls: {
        certificate: "/tmp/cert.crt"
    }
}

Which means:

• You need some awkward explanation where they should nest it, or an explanation that e.g. “network.tls” translates to nesting.
• They will ask whether they should indent the line you sent them.
• Well, and it’s also surprisingly difficult to explain between which braces they should put the text, and that’s at the end of the braces, but not after the braces etc., if you’re talking to them on a call.

It’s not even that I’m completely enamored with TOML, but this aspect is certainly growing on me…

Hab erst heute zufällig in F-Droid ein Update gesehen, falls du die App meinst: https://f-droid.org/packages/app.passwordstore.agrahn

I’m always surprised to hear people believe in ghosts, not because I consider it particularly ridiculous, but rather because ghosts have no relevance in my life. I don’t need them to exist to explain what’s happening around me.

Every few years or so, I might hear a noise where I don’t have an explanation, but that always feels adequately explained by me not knowing things. I’m constantly surrounded by living beings as well as materials that are subject to gravity, temperature, humidity etc.. Occasionally, they’ll make noises quite naturally.

Their point is that one could come up with a billion hypotheticals for what might theoretically exist, because we cannot disprove it. If we spent as much time humming and hawing whether each one actually does exist as we do for ghosts, souls, gods, Big Foot etc., then you won’t be doing anything else in life.
That’s why it’s a typical position to just say that they don’t exist until proven otherwise.

Or in the more general sense, this is Occam’s Razor: If there’s multiple possible explanations for something, then one should assume the simplest explanation until proven otherwise.
And if you hear a door slamming shut in your house, then wind is a much simpler explanation than ghosts.

Will mich da mal nochmal damit ausprobieren, weil ich mir erhoffe, dass es konfliktfreier über Systeme ge-synced werden kann, weil eben nicht mehr die gesamte Datenbank-Datei als geändert markiert wird, sobald man auch nur ein Passwort ändert.

Aber ja, hatte das vor einer Weile schonmal probiert und war mir damals doch zu minimalistisch…

Habe pass nur mal kurz vor 1-2 Jahren ausprobiert, aber wenn ich mich richtig erinnere, gab es da durchaus teilweise die Anforderung die Dateipfade direkt auf der CLI anzugeben. Also vielleicht willst du’s doch nicht zu tief im Dateisystem vergraben, oder zumindest dann einen Symlink im Home-Verzeichnis haben…

98 Tatverdächtige

In Deutschland leben knapp 200 Franziskaner

Ähm, puh. Keine Ahnung, wie vergleichbar die Zahlen sind, weil wohl mindestens auch die Niederlande teil der Untersuchung waren, und weil evtl. die Mitgliederzahl seither zurückgegangen ist. Aber so sehr kann man das gar nicht schön rechnen, dass das auch nur annähernd normal aussieht.

Selbst wenn man die aktuelle globale Mitgliederzahl von 13.600 dagegen hält, reden wir immer noch von 0.7% Sexualstraftäter, was immer noch absurd hoch ist.

You could always have a proper alarm a few minutes later as a fallback…

VSCode is Electron, i.e. a webpage, so it’s not hugely surprising that they opted for the natively supported JavaScript Object Notation. And also shows that they don’t care for using the right tool for the job to begin with.

Personally, I much prefer TOML over YAML, because it does not have significant whitespace, and because you can read the spec in a reasonable amount of time. It just has so much less complexity, while still covering the vast majority of use-cases perfectly well.