←back to thread

333 points indigodaddy | 1 comments | | HN request time: 0.239s | source
Show context
hatware ◴[] No.33579350[source]
Plex lost their best users by missing the point of self hosting entirely. Nobody wants to deal with third party downtime, even if it is rare and intermittent.

I think most products go through phases like this. Plex has some diehards that have stuck around (I think it's just buyers remorse for the Plex pass) but I think they are at a 5th or 6th tier of "customer" at this point, seeing the continuous churn spiral they are fighting.

replies(6): >>33579432 #>>33579433 #>>33579922 #>>33580045 #>>33581087 #>>33582678 #
imran-iq ◴[] No.33579432[source]
> Nobody wants to deal with third party downtime

Not only that, I don't want my adblocker to have to block services running on my local network (they have some analytics + sentry).

replies(1): >>33579527 #
srcreigh ◴[] No.33579527[source]
Does this require any special set up?

I’m asking out of laziness.. my local server has pi hole set up, and the other devices use that for DNS thru Tailscale, but I’m not sure what gets blocked for stuff running on the server. I recall some Tailscale setup involved a flag to disable some DNS thing. Hmmm

replies(1): >>33579910 #
imran-iq ◴[] No.33579910[source]
In my case not really. There is server side scanning in which plex shares data about your media with their backend. Not sure if there is any setting to disable that.

As far as the web client goes ublock origin handles it for me.

replies(1): >>33580404 #
1. srcreigh ◴[] No.33580404[source]
Ok. As per my above comment, it should be possible to filter out the analytics/sentry via DNS using pi hole. In theory, you'd just have to set up your Plex machine to use pi hole DNS ad blocking, and ensure that the pi hole domain list includes analytics domains. And Tailscale MagicDNS with the primary DNS server being your Plex/pi hole server, with your other devices configured with Tailscale, should block everything.

The only potential blocker I can see is whether the HDMI streaming device makes HTTP requests, in which case it would need to use the Tailscale proxy, and I'm not sure if that's supported.