Da die Löhne der meisten Menschen erst nach Jahren, wenn überhaupt, zu den aktuellen Preisen aufgeschlossen haben, wird sich mMn. nicht viel verändern.

Es ist gut, dass die Inflation nicht mehr stark steigt, aber Aussagen wie "der Mindestlohn wurde 'erst vor kurzem' angehoben, dementsprechend reicht das für die nächste Zeit", obwohl die Erhöhung nur die Verteuerung der Jahre zuvor kompensiert, wird viele Arbeitnehmer nicht zufriedenstellen.

Letztendlich hat die AfD ihr neues (altes) Thema bereits gefunden.

Most people using these sites prefer the lossless codec flac anyway, which can be transcoded to anything.

MP3 320kbps and MP3 V0 is transparent to most (all?) people, so there's not much of a reason to go with a newer codec, except for space savings.

There's not even much of a reason to go with 320kbps, as V0 achieves the same quality with smaller files. That's why almost nobody actually downloads MP3 320.

I personally think MP3 is there for historical reasons, as I don't see a reason for using lossy codecs for archiving purposes. Just download flac and transcode it once or on demand on a media server for streaming.

Not natively, as far as I know. NTFS works well on Linux for the most part (unless you need permissions), but macOS natively only supports reading.

FAT32 is universally well supported, but the partition size limit and 4GB file size limit make it unusable for me.

Linux filesystems as well as macOS filesystems aren't supported natively anywhere else, so ExFAT it is.

ExFAT does make sense, since it's the only filesystem which supports read and write on all major OS. Sadly it's also pretty basic, and thus not the first choice on any OS - except for USB sticks.

I generally recommend formatting any new storage media before using it. Just to make sure it's properly formatted to work with my machine, and the manufacturer didn't mess up their implementation for some reason.

What format did the drive use? HFS+?

Navigation within a single workspace is pretty much the same as in Sway/i3.

I don't remember how it's done in Sway/i3. If you have two monitors side by side, moving the focus from the left most window on the right monitor to the left, moves the focus to the left monitor.

A major difference is the workspace design. In Cosmic, there's currently a single set of workspaces for each monitor. In Sway there's one set shared between all monitors.

The workspaces can be either horizontal or vertical, which is useful depending on how you configure a multi monitor setup. This is because with vertical workspaces, moving down from the bottom window moves the focus to the next workspace (and vice versa).

In my case with two monitors side by side, this is awesome, because moving the focus feels like moving naturally on a single giant plane. E.g. moving down moves to the next workspace, then moving to the left moves to the left monitor, where I could move up to the workspace above etc.

It's difficult to explain for me, so I recommend giving it a try (or maybe wait a while, depending on your needs, e.g. there's no VRR, no window rules etc. Also, currently monitors have to be aligned at the top edge to be recognised as side by side. If they aren't, moving between monitors and workspaces doesn't behave right.).

I like the Cosmic tiling better than Sway, because it tiles through the long edge by default.

I.e. If I just two windows after each other, Sway will tile them as two equal columns. If I open another window, it'll add another column, while making each column the same size.

Cosmic also creates two equal columns with two windows, but the next window tiles the focused column horizontally.
With three windows this means half the screen is a single window, the other half is two windows taking up a quarter of the screen. Obviously if you instead focus another window, it'll be tiled instead.

This is basically the same behaviour as the autotiling script for Sway/i3, but it works reliably (I've always had issues with those scripts).

Blocking incoming traffic and accepting outgoing traffic is usually the default for distributions anyway.

Make sure to not refresh the page, else it seems like all progress is lost.
I found out simultaneously that I enabled pull down to refresh the page in Firefox Android.

Edit: The survey wasn't created by me, I just shared it.

fclones is fast and supports hardlinking/softlinking of duplicates instead of removing them.

I've used it successfully to deduplicate my documents folder (and "archive").

As its quite the amount of data, I recommend using the --cache option to make subsequent runs way faster, if you want to dial in the options. This directory can be deleted at any point and isn't necessary.

https://github.com/pkolaczk/fclones

Wenn wir von einer Geschwindigkeit von 150km/h ausgehen, wäre das ein Bremsweg von ungefähr (150 / 10) * (150 /10) = 225m.

Wenn jedes Kind ungefähr 30cm Platz braucht, wären das 218m an Kindern.

In dem Fall sind es sehr kleine Kinder, da sie durch den Aufprall das Auto nicht ausbremsen.

Mit der Dreifachen Geschwindigkeit an einem "Achtung Schulkinder"-Schild vorbeizufahren, ist doch noch im Rahmen.

It'd be great of this meant SR-IOV for all GPUs, but this seems like it only allows for sharing of a GPU to multiple guests. And even then, with most of the driver being on the GPU this might not help regular consumer GPUs at all (features being disabled in firmware). But I really don't know anything about what this actually means.