Windsock

Windsock Support

These steps resolve the most common account, content, notification, and local-storage problems without exposing private account data.

Before troubleshooting

  1. Choose Windsock > About Windsock and note the app version.
  2. Confirm that Bluesky works for the same account in another client.
  3. Quit and reopen Windsock, then try the action again.

Account or sign-in problems

Open Windsock > Settings… > Accounts. You can switch accounts, remove an account, or add it again. Removing an account deletes its saved credentials and purges its disposable post/feed caches and reading positions from Windsock. Durable drafts, mute rules, and local notification state remain in the shared app database. This action does not clear the shared, session-independent image cache or delete the account at its social provider. Use Clear Cache to remove the shared image cache.

Stale or missing content

Refresh the current timeline first. If cached content remains incorrect, open Windsock > Settings… > Advanced and choose Clear Cache. This clears post/feed caches and the shared memory/disk image cache. Drafts, mute rules, and reading positions are not disposable cache entries.

Notifications

Open Windsock > Settings… > Notifications and choose Open Notification Settings…. Confirm that macOS allows Windsock notifications. Windsock must be able to reach your social provider to discover new notifications.

Local data

Open Windsock > Settings… > Advanced and choose Reveal Data Folder to locate the app database. Do not publish that database or diagnostic material containing account identifiers, posts, drafts, or messages.

Privacy and account data requests

Read the Windsock Privacy Policy. Requests about content or account data stored on Bluesky or another AT Protocol service must be directed to that service, because Windsock does not operate the server that stores it.

Contact support

If these steps do not resolve the problem, email hello@pixelfoxstudio.com. Include the Windsock version, your macOS version, what you expected, and what happened. Do not send passwords, OAuth tokens, private messages, or the app database.