Since you seem to be in good faith: no, you’re wrong. Using a language cannot force you into adopting a licence, because automatically everything you produce will be all rights reserved unless otherwise specified. It’s then up to the developer to choose a license.

Rust doesn’t even populate the license metadata in your manifest, it’s up to you.

I think MIT dominance came about thanks to GitHub’s choose a license.

Very ingenious approach too!

deleted by creator

Yes, exactly. But at least you can have an e2e encrypted relay as syncthing does.

This problem is similar to the one faced by Matrix on iOS, and they provide the notification service. All of your conclusions apply though.

This could be worked around, in theory

When you begin hosting you have to wait a bit before your email doesn’t go to spam, at least that was my experience in 2018.

Edit: I just checked and I can now deliver to Hotmail/MS365 too!

deleted by creator

This should be at the top

Nice

What are you using for Heating? Is it house heating or physical warm up?

eBlocker does indeed seem German. It’s also much more than PiHole (it MITMs your packets, it seems) https://eblocker.org/en/how-eblocker-works/

eBlocker uses SSL bumping with a unique root certificate to decrypt possibly encrypted TCP/IP packets. After this deep packet inspection a pattern matching to the target URI is performed. In case of a match, the request is answered by the eBlocker (instead of being sent to the target URI).

As a slightly less accurate alternative, eBlocker uses DNS blocking for fallback, where the domains of known data collectors are blocked. This way, even devices that do not allow to install root certificates are also protected.

Beware! Now there’s a hardware revision for a TP-Link router (I think the C7) that is not supported by OpenWrt and never will

Wow! How do you do that? Do you accept that something could be down sometime?

Yours looks power hungry though…

I would post mine but it’s too messy for now

Cool project, but Rust is a cool language too :)

Interesting. I’m using Argo, there may be something similar for it

It’s because of this:

$ dig +short insights.navidrome.org
209.141.42.198
$ dig -x 209.141.42.198

; <<>> DiG 9.20.11-4-Debian <<>> -x 209.141.42.198
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12665
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;198.42.141.209.in-addr.arpa.   IN      PTR

;; ANSWER SECTION:
198.42.141.209.in-addr.arpa. 30 IN      PTR     demo.navidrome.org.

;; Query time: 208 msec
;; SERVER: 192.168.1.1#53(192.168.1.1) (UDP)
;; WHEN: Sun Mar 08 17:13:34 CET 2026
;; MSG SIZE  rcvd: 77

In practice, demo and insights are on the same IP, whose reverse points to demo

Just don’t go below 4 cores of x86 and you’ll be fine

My greatest problem is that the CPU load is too high and I ran into an issue with iSCSI that would occasionally peg one core to 100%. It would also make nodes NotReady when too many PVs were scheduled