talkingpumpkin

you will have to spend a lot of time learning the Nix language

I'd say you shouldn't use any system (be it nixos, ansible or even bash scripts) if you are not willing to learn it.

That said, I too find pre-made modules less useful that I initially thought when I got into nixos: unless you want to do very basic stuff, a lot of times it's easier to just generate whatever scripts/configuration files you need directly (using one of the trivial builders in lib or writing a custom derivation) rather than learning how the corresponding nixos module works.

One could say nixos modules make easy things slightly easier, and hard things much harder (this is adapted - possibly imprecisely - from a quote on ORMs, I think by Joel Spolsky).

In your shoes (and, in fact, in mine) I'd try to move away from interactive tools and into file-driven ones.

Personally I use nixos, run WUD (what's up docker) to be notified of available updates, and manually test/update the containers once in a while (every couple weeks or so?)

There are a bazillion other solutions (from stuff like ansible/chef/puppet, to docker-compose, to kubernetes, to... a hand-written bash script) - the idea is to setup stuff via files that you can version, reference and write comments in rather than using some gui for interactive steps that you'll forget to document in some wiki.

Monitoring is a whole different beast than configuring: you'll be probably better off using something that does just that instead of some all-in-one solution. Try looking into something like beszel before going for the full prometheus/graphana stack.

domain-driven design (or development?)

I'm not 100% what it is (I'm really not into nomenclature), but I think it's the practice of modeling your software after the domain you are working in... IDK if/how it differs from what everyone has always been doing since forever.

It would seem my point is not getting through (ie. I must not have expressed it well enough).

You having freedom doesn't mean other people have a duty to support what you do - it just means they don't have legal ground to stop you.

For example, freedom of speech doesn't mean that newspaper must publish whatever you write - it just means the police won't come knocking on your door at 5am because you of something you wrote.

The "idea of linux" (by which I take you mean the idea of FOSS in general, not of the kernel specifically) isn't to support anything and everything.

Does dropping 32 bit go against the "idea of linux"? Does software being developed/tested only on specific distros go against it? Do devs that only supporting glibc because they don't care about musl go against the idea of linux?

I’m just expressing a concern where over relying on one init system will limit options

Nope, nothing actually limits the options of people who don't like systemd: if they want to run some FOSS piece of software whose upstream devs don't care about openrc (or whatever init of choice), they'll just have to fork the projects, put the work in, and the upstream devs won't be able to stop them in any way.

This is what the "freedom" in FOSS means. Twisting it to mean that upstream goes against "the idea of linux" if they don't support whatever thing you care about and they don't is entitled.

this doesn’t go with the idea of Linux, which is having “freedom” with your os

Err... it's "freedom" as in "you are free to run your own system using whatever software you wish" not "freedom" as in "distros and devs have a duty to support your freedom to run any specific software you happen to like".

Let's turn down the entitlement dial a bit.

TLDR:

Current status for 26.04 LTS

We shipped rust-coreutils as the default in Ubuntu 25.10 to maximise real-world testing ahead of the LTS. Based on the audit findings and remediation progress, here is where we stand for Ubuntu 26.04 LTS.

We have included the latest upstream release 0.8.0 in Ubuntu 26.04, which incorporates the bulk of the security fixes.

cp, mv, and rm continue to be provided by GNU coreutils in 26.04. These utilities have remaining open TOCTOU (time-of-check to time-of-use) issues (8 as of Apr 22, 2026) that need to be resolved before we are confident shipping them.

Our plan is to address the remaining issues as soon as possible and target Ubuntu 26.10 with 100% rust-coreutils.

Does https://www.olivetin.app/ look like what you have in mind?

(OT) what did you use to annotate the picture?

Still, some neckbeards only wanna use software from orgs who are in it “for the love of the game”.

Nope, that's just you fighting strawmen and labelling people who don't hold your same opinion "neckbeards".

I would be excited for a new FOSS browser regardless of specific features, and I could be excited for a non-FOSS one if it had particularly promising features that are not provided by any FOSS browser. As far as I can see, Orion does not fall in either category.

BTW marketing a product for its privacy (or security) without it being open source amounts to having "trust me bro" as a slogan... of course one is free to trust whoever they want to.

It's not FOSS, so I couldn't possibly care less. That said, best of luck to you!

I've not looked into it much yet, but https://radicle.xyz/ seems interesting.

It's kinda a bittorrent-powerd codeberg and it looks like it's worth playing around with (even though it might not get you rid of much bandwidth... IDK how popular it is, but source usually doesn't weigh that much).

Getting the router to actually assign an IP address to the server

You would typically want to use static ip addresses for servers (because if you use DHCP the IP is gonna change sooner or later, and it's gonna be a pain in the butt).

IIRC dnsmasq is configured to assign IPs from .100 upwards (unless you changed that), so you can use any of the IPs up to .99 without issue (you can also assign a DNS name to the IP, of course).

all requests’ IP addresses are set to the router’s IP address (192.168.3.1), so I am unable to use proper rate limiting and especially fail2ban.

Sounds like you are using masquerade and need DNAT instead. No idea how to configure that in openwrt - sorry.