About
What is FlockOff?
FlockOff is a mass-block tool for the Atmosphere. When a post goes sideways and you don't want to block 200 people one by one, FlockOff does it for you — in bulk, in the background, with full undo support. Your block records are written directly to your own Atmosphere repository. Your data stays yours — FlockOff never stores your personal records or history.
How it works
Paste a post URL
Drop in any Bluesky post URL. FlockOff fetches the post and shows you a live count of everyone who engaged with it.
Choose what to block
Pick which engagement types to include — the OP, likes, reposts, quotes, replies — and filter out mutuals or accounts you follow before you commit.
Block runs in the background
FlockOff queues a background job and blocks accounts one by one at the network's rate limit. You can close the page — the job keeps running on the server.
Everything is reversible
Every block event is saved to your own Atmosphere repository. You can undo all blocks from an event in one click, redo them later, or resume a job that was interrupted.
Import and manage block lists
The List Editor lets you import any public Atmosphere block list, preview its members, and block them in bulk — the same background job, the same undo support. You can also share your own block events as subscribable lists.
FAQ
Is my data stored on FlockOff's servers?
Your block history, event records, and block lists live entirely in your own Atmosphere repository — not on FlockOff's servers. FlockOff's server holds only an encrypted session cookie while you're signed in. We do track anonymous aggregate counts (total blocks run across all users, posts processed, lists created) for the Stats page, but never your specific records, history, or personal data.
What permissions does FlockOff need, and why?
FlockOff requests write access to block records (to create and delete them), your FlockOff event records (to track job progress and history), and list records (only if you choose to share a block event as a public list). It never requests access to your posts, follows, DMs, or any other data.
Can I undo a block event?
Yes. Every block event has an Undo button on its detail page. Undo deletes all the block records from your repository. You can also Redo — re-blocking the same set of accounts — or Resume if a job was interrupted mid-run.
What happens to my blocks if FlockOff shuts down?
Nothing changes. Your block records live in your own Atmosphere repository and are fully independent of FlockOff. The blocks stay in place, and you can manage them directly through Bluesky or any other Atmosphere client that supports block management.
What is the Nuclear option?
Nuclear selects all engagement types at once — OP, likes, reposts, quotes, and replies. It's a convenience shortcut for when you want to block everyone who touched a post, without cherry-picking.
How does sharing as a block list work?
After a block event completes, you can share it as a public Atmosphere block list. FlockOff creates the list in your repository and subscribes you to it. Anyone else on the network can subscribe — when you run a re-check and block new accounts, they're added to the list automatically.
Can I check for new engagement after blocking?
Yes. On any block event's detail page, the "Check for new engagement" drawer re-scans the original post and shows you accounts that engaged after the original block was run. You can select and block them individually.
Does FlockOff work with other Atmosphere apps?
Partly — and more is coming. FlockOff currently uses Bluesky's AppView API to fetch engagement data, so post blocking is only available for Bluesky posts for now. Support for other Atmosphere clients and appviews is planned. As for the blocks themselves: they use the standard Atmosphere block lexicon (app.bsky.graph.block), so they apply on any Atmosphere app that respects it — though not all apps do, so coverage may vary.
What happens if my session expires while a block job is running?
If your sign-in session expires mid-job, the job will stop processing silently — no error is shown since the job runs in the background. Your progress up to that point is saved to your PDS, so no completed blocks are lost. To recover, sign back in, go to your block history, and use the Resume button on the interrupted event to pick up where it left off.
How do I revoke FlockOff's access?
In Bluesky: Settings → Privacy and Security → Connected Apps → FlockOff → Remove access. This immediately invalidates FlockOff's session and it will no longer be able to act on your account.
More questions? Read the Terms & Privacy page, or get in touch.