Mordikan

At it's heart, this is what @selfhosted is meant for:

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

I would say that members talking about paid/closed products they use (ex. "I connect to this via Tailscale" or "I use company ABC for hosted VPS") to accomplish something is fine, but marketing or job boarding (ex. "Looking for QA on my commercial product") is not.

Readarr was orphaned, so most people switched to using LazyLibrarian. LL is kind of difficult to work with and you'll typically see a lot of failures in the logs for various things. Instead, you could use Shelfmark which fulfills the same general purpose but is more straightforward.

For browsing/reading, most people using Calibre-Web. You can write a simple bash script to random periodic imports via calibredb. Just point the output directory of Shelfmark to the input directory for that command.

Windows?

edit2: thanks again everyone, you don't need to check if it's working. apparently I'm blocked from accessing the site, can't see any other explanation. DNS resolves fine, flushed caches, tried private mode, clear cookies, tried everything on my end to rule stuff out, nothing

You might run traceroutes/mtr to see where exactly this is failing. Here's the IP I show in case yours differs:

➜  ~ dig freedns.afraid.org @10.10.0.1 A

; <<>> DiG 9.20.23 <<>> freedns.afraid.org @10.10.0.1 A
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51734
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;freedns.afraid.org.		IN	A

;; ANSWER SECTION:
freedns.afraid.org.	60	IN	A	69.42.215.252

;; Query time: 206 msec
;; SERVER: 10.10.0.1#53(10.10.0.1) (UDP)
;; WHEN: Wed Jun 03 14:48:58 CDT 2026
;; MSG SIZE  rcvd: 63

I remember getting into security about 15 years ago. This was around the time of Android really kicking off and it was crazy all the stupid things you could get away with (and that's just a static permission set). Now you have AI pentesting tools and AI slopcode to use it on. Depending on perspective, this is either a great time to be working in security and/or an awful time to be working in security.

Damn kids with your twitternets and me mes.