What is FlockOff?

Is my data stored on FlockOff's servers?

Your block history, event records, and block lists live entirely in your own Atmosphere repository — not in a FlockOff database. While you're signed in, FlockOff uses an encrypted browser session and temporary in-memory OAuth and job state so it can perform the actions you request. That state is not written to a persistent application database and is lost when the server restarts.

What permissions does FlockOff need, and why?

At sign-in, FlockOff requests write access to block records (to create and delete them) and your FlockOff event records (to track job progress and history). If you use a list feature — sharing a block event as a public list, or importing and managing lists — FlockOff asks for list permissions at that moment and brings you right back. 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?

FlockOff accepts post and list links from supported Atmosphere clients as well as raw at:// URIs. Engagement reads still come from one configured AppView — Bluesky's public AppView by default — so FlockOff can only see content indexed by that AppView. The blocks themselves use the standard AT Protocol block lexicon (app.bsky.graph.block), so they apply in apps that respect it, though coverage can vary by client.

Can I sign in from a custom PDS?

Yes, if the PDS supports the current AT Protocol granular OAuth permissions. FlockOff deliberately does not fall back to the legacy transition:generic scope because that would grant write access to every record type in your repository. If sign-in reports unsupported permissions, your PDS operator will need to update the server.

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.