@sc oh dear. this seems to be awoo-specific too
@thingywott @sc @nolan might be fixed if I deploy to awoo? I've been meaning to do that
@vahnj more specifically, it's a domain block thing that only triggers when looking at another domain
so, if you are looking at pinafore.social and it tries to connect to any .space domain via websockets (like awoo.space), it gets blocked by the default adblocker rules of most blockers
@thingywott @vahnj I wonder if the adblocker in question supports the EFF's dnt-policy.txt file? If so then adding a /.well-known/dnt-policy.txt to awoo.space may fix it: https://www.eff.org/dnt-policy
@nolan @thingywott thanks Nolan! I'll check that out
@sc this rule seems to come from easyprivacy, where any websockets from .space third party domains are blocked (third party being why it doesn't affect awoo.space itself)
luckily, there is a forum where people can request things be unblocked: https://forums.lanik.us/viewforum.php?f=64&sid=e2265030160fa16b249be63ba30d87cf
maybe @vahnj or @nolan might be interested in this..?