Comment by AnthonyMouse

The question is, what's going on here? Is this Firefox blocking some path/subdomain/cookie on x.com because it's used by their tracking widget, but the same is also used by some important part of the site itself, so it's essentially a false positive and Mozilla need to adjust the filter to be more specific? Or is the site detecting the ad blocker and purposely refusing to load?