Fun fact: I use NixOS since six years now and at least in the first two years the Arch Wiki helped me a lot to understand the NixOS configuration options.

A funny result is the accumulation around server centers, here Hetzner.

Was miss reading "we are a Spirituality community now" and thought that this is very unexpected.

But to have c/spirituality as a community here is very welcome.

The process to ask simple questions like these is not a barrier for users looking for honest conversation.

That is one of the facts I did choose Beehaw, because it shows the will for maintain a non-toxic community.

Honestly the best way would be to start coding by yourself. While trying to find solutions you might find the right people too.

Almost every dev has its own ideas and ideals. There is no lack of ideas but everytime a big lack of time and men power. Software developers have more too much on the plate then too less.

So sharing ideas is nice but contributing is gold.

I would call it the FOSS Dev Paradox.

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.

• the immutable system
• reproducible builds
• switchable generations
• easiness to maintain in a Git repo
• very fresh

Because nobody mentioned it already I want to bring Notesnook in.

It is very privacy friendly, OpenSource and cross platform. Just if you want to sync there is no self hosted solution yet.

Great idea and project!

I am afraid you already have a bot problem.

Another NixOS user.

Foot is the fastest and I use it as default. Second is Kitty because it uses GPU acceleration.

There is a huge difference in the result. With NixOS you run a immutable 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.

I have a Bangle.js 2 and there are two things I don't like. One is the display which has too low contrast and the second is that the hardware itself feels not very valuable because it is very light and plastic.

For audio files sox and beets are my live saver.

c/mobility

c/cargobikes

Startet using Linux in 1999. Then I did a lot of distro hopping:

• Redhat
• Suse Linux
• Gentoo
• Sabayon Linux
• Debian
• Kdenlive
• Arch
• Ubuntu Studio
• Fedora
• Fedora Silverblue
• since 2017 NixOS

NixOS feels very contemporary and will stay a while. It is very advanced and usable in many diverse environments. In the past I did learn a lot installing and maintaining Debian and Arch – which has a great community.

Historically the GPL seems to be not cermercial in the sense of taking care for developers rights. The GPL is also connected to the term Open Source. Because it was too restricted for some cases a derivation was made witj the LGPL with which it is posdible to use GPL licenced libraries easier in combination with other more restricted or more opened licenses.

For some looking for Free Software all this was too restricted and the libre BSD license and all its derivations were made.

There are several licenses which forbid commercial use. But where does this work? When I want to use a piece of software while working on a profitable project it is commercial use. It may be on purpose to restrict this but sometimes it is not meant to be not free.

@Sintamo@beehaw.org Very nice!
I made a fork and put in a one file solution with @media queries.

https://github.com/tasmo/Beehaw-Hive-Theme/commit/c30cd19ad383e2e7fd9166405d0bb11a9c7ceb98

If you want to I can open a pull request. If not, never mind. :)

Edit: Line breaks added.

According to Mozilla setting both to the value 1 is the better idea. The fallback then won't be "Accept all".

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.

https://hearthis.at/tasmo/dj-tasmo-deep-work/

I guess this is the actually best way to use Lemmy on a phone. Either Chromium or Firefox based browsers work.

This works for me perfectly as well.

Tried it quickly and was not well surprised. I appreciate thr approach a lot! The app is nice looking but feels too chewy. Prefer the mobile browser.

To open a thread sounds like a gooid choice.

If you are open for something very goid but a little different take a look at the fabulous Niagara Launcher.

Or the even faster successor gojq.

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.