Following, followers and unfollower history are different

The Following workspace works on accounts that you currently follow. Unfollowing removes that outgoing relationship from your account; it does not remove someone from the list of people who follow you. A current “not following back” result means the relationship is non-reciprocal now. It does not prove that the account followed you previously or record a historical unfollow event.

BskyDelete loads the current following list through paginated Bluesky requests and retrieves public profile and relationship fields for review. It does not keep earlier follower snapshots, send unfollower alerts, bulk-follow accounts or automatically decide that a relationship should end. You remain responsible for reviewing every selected profile and confirming the change.

Current relationship and profile filters

Basic filters describe current returned data. Paid-plan signals can prioritize a review queue, but none of them is a factual judgment about a person or an instruction to unfollow.

Search current following by handle, display name or visible profile description.
Filter by current mutual-follow status to review accounts that do or do not follow you back now.
On a paid plan, set ranges for public post, follower and following counts.
On a paid plan, use the inactivity signal based on reported post count relative to account age, not a private last-login time.
On a paid plan, review suspicious-bot or very-active heuristics derived from public profile patterns; these signals are not definitive labels.
On a paid plan, add handles or names to a whitelist so matching selected accounts are skipped during the unfollow batch.

A non-mutual, quiet or unusual-looking account may still be useful to you. Treat every filter as a way to narrow candidates, then open and assess profiles before changing the relationship.

A safer bulk unfollow workflow

1
Connect the intended Bluesky account through OAuth, open Following and wait for the paginated list and profile batches to finish. A paused or incomplete load cannot represent the complete set of accounts you follow.
2
Choose one explainable review rule, such as a current relationship state or profile characteristic, and apply the matching filters. Inspect visible profile context and do not treat inactivity or bot heuristics as proof.
3
Select only accounts you are prepared to stop following. Filter changes clear the selection, and whitelist matches are skipped during processing. Paid plans can export selected rows with display name, handle, DID, bio, avatar URL and current mutual status; the CSV does not re-follow accounts automatically.
4
Confirm a small initial batch, monitor successes and failures, reload Following and verify the current relationships. Retry only accounts that remain and reassess the filter before starting the next group.

OAuth and public-profile data boundaries

BskyDelete does not request a Bluesky password or App Password. The authorized browser session asks Bluesky for the current following list, public profile fields and relationship state, then submits unfollow requests for selected follow records. Bluesky can rate-limit or reject those requests, and BskyDelete cannot bypass the provider.

Following and selection data are processed for the review you request; BskyDelete application servers are not designed to keep historical follower snapshots or a persistent copy of your following list. Separate account, analytics and subscription providers operate under the current Privacy Policy. Disconnect shared devices and never send credentials or OAuth tokens to support.

What bulk unfollow changes—and what it cannot prove

A successful request stops the connected account from following the selected profile. It does not block that profile, remove it as your follower, delete either account's content, or explain why the relationship was non-mutual. Feed composition may change after an unfollow, but BskyDelete does not promise more reach, engagement or follower growth.

BskyDelete has no automatic undo. You can choose to follow an available account again manually, which creates a current relationship rather than restoring an earlier state. Keep a paid-plan CSV reference when useful, preserve important handles or DIDs, and verify each completed group before continuing.

Daily quotas and large following lists

The Free plan permits up to 30 successful deletion or unfollow actions per local calendar day across supported workspaces. Paid plans remove BskyDelete's daily action quota and enable advanced filters and selected-data export, but Bluesky API limits and temporary service or network failures still apply.

A large following list needs cursor pagination plus profile requests in smaller batches, so loading can take time. Deletions are also processed in controlled batches. If loading is paused or a batch partly fails, refresh the current list, identify confirmed successes and continue only with records that remain.

Why the following list or result may look wrong

Loading was paused or pagination is incomplete, so the visible list does not represent every current follow.
Current mutual status changed or public profile data is delayed; refresh before drawing a conclusion about the relationship.
A heuristic matched a harmless profile pattern. Review the account instead of treating the signal as proof of inactivity or automation.
Only part of the unfollow batch succeeded, or OAuth and provider limits interrupted it; retry only relationships that still remain.

Review relationship guidance before unfollowing

These guides explain the current Following workflow, non-reciprocal relationships and the limits of the inactivity signal.

Ready to review Following? Load the complete list, protect important accounts, and test one small selection before expanding the batch.

Review following in the workspace

Other BskyDelete features

Continue your account review with another focused BskyDelete workflow.

Filter and Bulk Unfollow Bluesky Accounts You Follow