X(twitter) on firefox problem #1005

Activity

1. therealaleph commented on May 10, 2026

   

   therealaleph

   on May 10, 2026

   Owner

   More actions

   Reviewed via Anthropic Claude.

   @amirvalipour-se — Firefox's tracking-protection warning on x.com is the cosmetic UI message; the actual login-loop / no-content issue with X via mhrv-rs has a separate root cause (#871 / #382 / #737). X.com fingerprints the JA3 of the connection and treats Apps Script's UrlFetchApp as a non-browser, so it serves the warning page or login-loops repeatedly.

   The architectural fix is to route x.com through an exit-node (Deno Deploy / Replit / fly.io / VPS), so the destination sees a normal browser-like JA3 instead of Apps Script's. Setup at assets/exit_node/README.md.

   "exit_node": {
     "enabled": true,
     "relay_url": "https://your-exit-node",
     "psk": "<secret>",
     "mode": "selective",
     "hosts": ["x.com", "twitter.com", "abs.twimg.com"]
   }

   Once x.com goes via exit-node, the JA3 mismatch resolves and the warning disappears.

   For the cookie/cache issue specifically: clearing site data is needed once after switching to exit-node, because Firefox cached the unsigned page state. Closing as duplicate of #871. PR #963 (utls Chrome ClientHello fingerprint) will also fix this without needing exit-node — currently in community testing.
2. therealaleph

   closed this as completedon May 10, 2026