

I fully agree.


I fully agree.


The whole reason everyone moved to Discord was because it was a centralized place and since Discord needed to pay for it’s servers, it had to find a way to finance that, and enshittification naturally happened.
No! Stop perpetuating this “they have bills to pay” nonsense. Discord has more than enough money to run itself and be profitable.
The enshitification happens in services like Discord when shareholders gain control of the product.
Edit: toned down a word.
That’s actually easier than on android, we need a caldav sync provider app.


I don’t have any specific recommendations for a discrete tool for this, but radarr and sonarr can do this automatically if you enable it.


I’ve always found the Discord ui on desktop and mobile to be really bad, just very busy and unintuitive.


WG Tunnel. It does exactly this.
When I leave my WiFi, tunnel turns on. When I rejoin my WiFi, tunnel turns off.


deleted by creator


Delays? Jitter? What are you talking about?
Didn’t you say you have whitelist of allowed ips? Why don’t you just drop any other inbound traffic?


This is a waste of time and your router’s CPU. You already have a whitelist and know your safe TCP sources, just drop all wan traffic and only allow new input from whitelist. Your chain input rule is just creating a pretty list of bots you’re dropping anyway.


Ah, good catch, thanks.
It’s moot point for me because I’m sick of unifi so I’m not going back to worse performance and locked-away features.


This is an opinion on the WiFi access points.
I took the unifi pill in 2018 on the advice of my devops coworkers that ubiquiti is set-and-forget. I also was sold on the unifi network controller I deployed and used until last month being easy to use and local only.
The single pane of glass to control and update the access points is nice. Wifi works OK. There are, however, several downsides:
After the unifi Debian repo stopped updating properly, I decided to install openwrt on my APs.
Not only did it work well, but performance is now much better with openwrt.
I’m personally stepping away from brands that have their own ecosystems from now on, if I can help it. The enshitification is just too tempting for them, it seems, and it it’s always at our expense.


Fair enough.
I see your posts and comments regularly in self-hosted, keep it up. Staying engaged is learning.


As a fellow tinhat wearer, I applaud your reluctance to trust what they tell you.
However, there isn’t much you can do about your VPN provider setting up multiple exit routes, or maybe they’re doing something really fancy like NAT filtering DNS requests so big players like Netflix have a harder time catching on to ppl geo-hopping.
But the outcome is the same: you have no control over this behaviour.


DNS leak tests only understand your exit IP. If your VPN provider allows round Robin load balancing, this may happen. This is a drawback of VPN exits out of your control, that you can’t know how their exits are handled.
Why you are so concerned about DNS leaks beyond one test is another matter only you can solve. Unless you are changing your dnssec config daily, this should be checked once.


- Have the router to block portscanners
What do you mean by this? Closing unused ports?


It doesn’t really matter, the current limitations are not so much data density at rest, but getting the data in and out at a useful speed. We breached the capacity barrier long ago with disk arrays.
SATA will no longer be improved, we now need u.2 designs for data transport that are designed for storage. This exists, but needs to filter down through industrial application to get to us plebs.


I use a filesharing platform called nicotine+and then curate my music manually.
Nicotine isn’t just for music, but it is really good for finding weird and non-mainstream music, which is what blocks me from.using lidarr.


I have lots of single songs rather than albums
Lidarr is not for you, then. Lidarr has a very particular workflow, and playlists like yours aren’t it.
But you got through it, and ZFS isn’t a walk in the park for most. I think you’re selling yourself short.
As someone else mentioned, leaving truenas on the asustor and using a container orchestrator or a hypervisor on the Xeon machine sounds like a good plan to me.