NaN
Cyber DJ
According to Mozilla setting both to the value 1 is the better idea. The fallback then won’t be “Accept all”.
I always wondered why Google took this choice. With the help of this article I understand now.
RSS ist still not dead but many commercial websites and platforms are not interested in this because it is harder to monetize.
Although the advantages are obvious. An RSS feed is much more accessible in many ways. It is most times better readable, sortable, offline savable and more efficient to get. What is even better for the environment because a with scripts and external content overloaded web page has a much higher carbon fingerprint.
Google Reader died and so ATOM/RSS will because the lack of commercial success.
This works for me perfectly as well.
A funny result is the accumulation around server centers, here Hetzner.
Occasionally I get feedback that some listen to DJ sets I put together to work. So I took a look at what I actually listen to for deep work and recorded a mix specifically for that.
To open a thread sounds like a gooid choice.
I guess this is the actually best way to use Lemmy on a phone. Either Chromium or Firefox based browsers work.
This is how I run my daily driver since a time. Coming from Redhat -> Suse -> Debian -> Gentoo -> Arch (-> Fedora) I feel very stable with NixOS.
The main system is NixOS with Flakes enabled, the user apps are installed with home-manager and on top a couple of desktop Flatpaks.
In between I did try to switch back to other distros taking less compilation time but there are so many features in Nix keeping me.
There is a huge difference in the result. With NixOS you run a stateless system where ths main configuration is built during the startup and not editable during the run.
With Ansible you can generate the configuration as well for every run though. But in most cases you will write hard config files.
Foot is the fastest and I use it as default. Second is Kitty because it uses GPU acceleration.