← All posts

Security

Your Creator Account Is Still Signed In. Who Can Reach It?

Wayne, RedSky Security·

A separate app password is a good start. The browser, the shared laptop, and the old tools you forgot about deserve attention too.

The laptop you borrowed for a weekend is back on someone else's desk. Your creator account may still be on it.

That is an ordinary way to lose control of an account. No dramatic hack is required. A signed in browser is already a doorway, and keeping the main password private does not close it.

Here is a practical access review for creators who use RedSky alongside other tools.

Give each tool its own credential

RedSky currently uses Bluesky app passwords. Make a dedicated one for RedSky rather than reusing the credential you gave a scheduler or another client. A descriptive name helps: include the tool and the device if that is how you intend to manage access.

The AT Protocol authentication guide recommends an app password instead of the main account password when using password authentication. It also recommends OAuth for applications with a user login flow. RedSky's present app password flow and the protocol's preferred direction are different things; we should be clear about both.

An app password is still a credential. Do not put it in a support message, a shared notes document, or a screenshot of your setup.

Check the device, not just the password

RedSky keeps account sessions in the browser. When you add another account, it becomes available in that browser's account menu. Anyone who can use that unlocked browser may be able to switch accounts too.

Before lending a device, open RedSky and inspect the account menu. Sign out of every account you do not want accessible. Lock the device when you step away. Use a separate operating system account if someone regularly shares the computer.

A private browsing window can keep a temporary session separate from the normal browser profile. It does not protect you from a compromised computer, screen recording, or someone using the window while it remains open.

Retire access you cannot explain

Open the app password settings in Bluesky and review the names. For each entry, ask one concrete question: what device or service is this for?

If you cannot answer, remove the credential and reconnect the tool later if you discover a legitimate need. Expect to sign in again. Do this deliberately when you have time to recover access, not in the five minutes before a scheduled release.

If a device is lost, removing its saved session on a different device is not enough. Review the related credentials in Bluesky, secure the account itself, and use the account recovery options available there. Local sign out and remote credential management serve different purposes.

Treat an access request like a publishing request

A collaborator who needs a draft does not automatically need your login. Send the draft. Someone who needs the media folder does not automatically need the social account. Share the folder through the arrangement you already trust.

When a tool needs DM access, pause long enough to understand why. Give a tool only the access required for the work you actually want it to do. Do not assume a familiar brand name makes every permission necessary.

Make the review small enough to repeat

Keep a private list of the tools you use, the devices you sign in on, and the person responsible for each. Keep passwords in your password manager, not in that list.

Review access when you replace a phone, finish a collaboration, or stop using a service. Those moments are easier to remember than an abstract promise to become better at security.

Your audience sees one account. Behind it should be a short, understandable list of ways in.

RedSky is an independent client and is not affiliated with Bluesky PBC.

SharePost on XReddit

Related reading

Ready to see your feed, unfiltered?

RedSky is the Bluesky client for adults. Your account, your follows and your content, with the viewing controls you choose.

Open RedSky →