Neverending loading or broken physics with internal domain from recipe 2 caused by ad blockers #4282
Unanswered
wmurphyrd
asked this question in
Hubs Cloud Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When using domain recipe 2, which loads assets from the secondary/internal domain, these requests are considered "3rd party" requests by ad blockers and may be blocked.
Several coin mining protection lists have taken to blocking the less common TLDs, so the combination of a fun domain like
.space
and the internal/3rd party domain means your Hubs cloud will fail. Sometimes this manifests as a loading screen that never finishes, but it can also be weirder stuff like the scene loads but performance is poor and physics doesn't work (.wasm
blocked).The great folks at uBlock were kind enough to unblock
.space
for us (uBlockOrigin/uAssets#8389) and we've just made a similar request to the list used by AdBlock (hoshsadiq/adblock-nocoin-list#422). But if you're on a different TLD like .online, .party, or .xyz, you could still be getting blocked (full list)Beta Was this translation helpful? Give feedback.
All reactions