LocaleFence is a userscript for hiding posts and automatically blocking X accounts based on the location shown in X's About this account data.
Automatic blocking creates real blocks on your X account and remains enabled across reloads until you turn it off. Review your selected locations before enabling it.
- Select individual countries, X regions, or whole continents.
- Hide matching posts without blocking their authors.
- Automatically block matching accounts as their posts appear in the feed.
- Show the account, flag, and triggering post in each block notification.
- Enable or disable notifications from the Settings tab. They are enabled by default.
- Exclude and immediately unblock an account from its notification or block-history entry.
- Keep a persistent queue when X temporarily cannot resolve an account location.
- Keep a local history of confirmed automatic blocks and their triggering posts.
- Cache successful location lookups for 28 days to reduce requests and rate limits.
- Install a userscript manager such as Tampermonkey or Violentmonkey.
- Open Install LocaleFence and confirm the installation.
- Open or reload x.com.
LocaleFence adds a LocaleFence item to X's navigation.
- Open LocaleFence and select the locations you want to match.
- Enable Hide matching posts, Automatically block accounts, or both.
- Use Lookup queue to inspect unresolved or failed location checks.
- Use Block history to review confirmed blocks and open their triggering posts.
- Use Settings to disable or re-enable notifications.
Automatic blocking remains enabled across X reloads until you turn it off. Changing selected locations changes which accounts match while it is enabled.
Selecting a continent includes all of its member countries. You can also select individual countries independently. Continent membership follows the UN M49 geographic classification.
When X rate-limits a location lookup, LocaleFence retains the account and post snapshot, retries with backoff, and exposes the pending item in the lookup queue. A non-matching account leaves the queue after resolution. A matching account remains until X confirms the block, then moves to block history.
LocaleFence runs entirely in the browser. It does not use an external server or send account data outside x.com.
It stores the following data locally:
- Selected locations, settings, exclusions, and the lifetime block count in
localStorage. - Resolved account IDs, names, locations, and cache timestamps in IndexedDB.
- Pending lookup records and up to 250 confirmed block-history entries in IndexedDB.
The Clear cache, Clear queue, and Clear history controls remove those respective datasets. Clearing history does not reset the lifetime block counter or undo X blocks.
- Locations come from X's account metadata and may be missing or inaccurate.
- X's private web APIs can change without notice and temporarily break lookups or blocking.
- Rate limits can delay decisions; unresolved accounts remain visible in the lookup queue.
- Excluding an account requires a successful unblock request to undo an existing block.
GNU General Public License v3.0 only. This software is provided without warranty.