Good idea! I don’t know, but I’m watching this thread. :D

Because it clearly is, despite the missing question mark.

I agree with what we want, but I’m not gonna demand it from any profit driven company. We need to build it ourselves.

Not saying there aren’t any companies doing things properly, but in the end, they have to decide between more profits (cutting corners, selling data, etc) and making user friendly, durable products. The systems we live in are not designed for the latter - they have to go as well.

Looks great!

Pats on the back to whoever knows what these poles are for.

Giant Mikado, clearly

What exactly are you looking for? A replacement messenger or something that allows communication with those messengers?

Hehe manjaroty

Yeah I still do this. I have a cronjob on one of my servers that runs every five minutes, checks if the upstream DNS IP matches my public IP and, if not, sets it. Adding 60s TTL, this means an average downtime of 3 minutes per change, max 6 minutes.

It’s also possible to use different nameservers than the one the registrar provides, in case the registrar doesn’t have a proper API for DNS.

Big fan of how this goes. I wish I had something to blog about. :D

(I have, I just can’t get myself motivated to actually write about it)

There’s Ibis, a side project from one of the Lemmy devs (nutomic). https://ibis.wiki/

I’m not sure a fork makes sense given the dev merged way too much nonsense already. Maybe from a point in time before it started?

I’ve been looking to check out Booklore over some annoyances I have with CWA but IDK anymore.

I never tried ABS, but since I just read ebooks and don’t listen to audiobooks, it just never seemed fitting for me.

You can use reverse proxies for local only, usually by restricting the address to local IP ranges. You can even choose a non-existent fun tld!

It worked! Very cool

Looks like @fabio@manganiello.blog made a cool thing here!

Apparently it’s an iOS appstore

So, mentioning you like this shows up in the guestbook? @fabio@manganiello.blog

Looks pretty cool!

Opnsense is only between the servers and the pi, the pi is in the same subnet as our consumer devices and the opnsense (directly connected to the router). The issues are both on the consumer devices and on the server, so the opnsense should not be the direct issue.

Still waiting for my success. Pihole randomly doesn’t answer DNS requests in time, causing a lot of trouble between my services. It’s happening since I switched to dnsmasq in opnsense (which is upstream for my local domain for Pihole), but also for external domains. Can’t nail it down and am this short of reconsidering my whole network setup. It used to work fine for over a year though…

Opnsense dnsmasq is DHCP for my servers and also resolves them as local hosts. (e.g. server1.local.domain) and Pihole conditionally forwards there. Since the issue is also when resolving external domains, it shouldn’t be related, but the timing is suspicious. I also switched the general upstream DNS.

Pihole does have some logs indicating too many concurrent requests, but those are not always correlating with the timeouts.

I know it’s DNS, I just don’t know where yet.

Thanks for the example! The reasons you mentioned were why I wasn’t looking into it more (using it for my local docs as well).