The startup I work for is a Statsig customer. I reported an issue to the Statsig team and was directed to this forum thread as the reason Statsig is being blocked by content blockers. I would like to share two data points from my own personal experience:
(1) The app I am building uses Statsig for feature gating and dynamic configs. We relatively recently launched from beta and introduced the ability for users to self-serve sign up for the product; the entire sign-up flow was behind a dynamic config, whose default value disabled signup if the Statsig servers could not be reached. After launching out of beta, we decided to keep this config around in case we ever need to quickly disable signups without waiting for a code push (eg, if we see a spike in abuse that we want to quickly stop while we investigate). We've been hearing from an increasing number of users recently that signup has been broken for them. After digging in, we realized it's because browser extensions are blocking the network requests to Statsig, causing our app in these cases to fall back to the default value of signup being disabled.
(2) Our team uses Notion as a document library. Today, I was in the middle of collaborating on a Notion doc with a coworker when suddenly I found myself unable to edit tables (I could not add rows, remove rows, or view the table's options). Hard refreshing the page didn't help. I opened my JS console to investigate, and immediately saw that network requests to Statsig were being blocked by a browser extension. (I hadn't previously known Notion was using Statsig!) I disabled my content blocker, refreshed the page, and then I could edit Notion tables again. Without being a Notion employee or having access to the Notion source code, I'm not sure what the root cause was here (and I'm not currently able to consistently repro the problem), but as an end user, it's definitely highly surprising to me that major functionality on a tool that I rely on every day for work would break because a feature gating API is being blocked.
I use a content blocker in my browser because I want to minimize the ways in which companies can track me online, but I may have to uninstall or disable it if it's breaking application behaviors I depend on. I've read through the linked README listing what types of endpoints are blocked by EasyPrivacy, and while I understand that certain Statsig endpoints fall under categories in that list (like analytics), I agree with @jkw that there ought to be a specific feature flagging endpoint that is allowed.
