We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure. What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, securely hashed passwords and authentication...
why stop there! let’s do the same for all the “self-host” projects that use CDNs or remotely hosted resources.
it’s not self-hosted unless it’s 100% hosted locally.
Right, he who does not rely on someone elses DNS-server shall throw the first stone!