Post to Bluesky via API — Schedule, Publish, Analyze

Bluesky uses the AT Protocol, a decentralized authentication model that doesn't rely on OAuth. Instead, you connect your account using your Bluesky handle (e.g., yourname.bsky.social) and an app password. App passwords are separate from your main login — they grant limited access to third-party services without exposing your primary credentials.

To generate an app password, open the Bluesky app or web client, go to Settings > App Passwords > Add App Password. Give it a descriptive name like "CodivUpload" and copy the generated password. Then navigate to the Integrations page in your CodivUpload dashboard, click Connect Bluesky, enter your handle and the app password, and save.

CodivUpload authenticates against your Bluesky PDS (Personal Data Server) using the AT Protocol's com.atproto.server.createSession endpoint and maintains the session automatically. If the session expires, CodivUpload re-authenticates transparently before publishing your next scheduled post. Your app password is stored encrypted at rest (AES-256-GCM) and is never exposed in API responses.

This approach means you can revoke CodivUpload's access at any time by deleting the app password from your Bluesky settings — without affecting your main account login or other connected services.

Bluesky's 300-character limit is the tightest among major text platforms (Twitter/X allows 280 for free users but up to 25,000 for premium; Threads allows 500). Every word counts. Write your post, then cut it by 20%. The constraint forces clarity — posts that land a single point well outperform those that try to cover multiple ideas.

Decentralized protocol, different dynamics: Bluesky runs on the AT Protocol, which means the network is fundamentally different from corporate-owned platforms. There's no central algorithm deciding what goes viral based on engagement bait. Custom feeds curated by the community replace the algorithmic timeline. This means gaming the algorithm with rage-bait or clickbait doesn't work — content surfaces based on genuine user interest and feed curation choices.

No algorithm gaming: On Bluesky, the most effective strategy is also the simplest — post things that are genuinely useful or interesting to your audience. Share behind-the-scenes progress, technical insights, specific opinions, or useful resources. The community skews toward tech, design, journalism, and academia, so domain expertise carries more weight than polish. A concrete tip about your craft performs better than a vague motivational post.

Authentic engagement matters most: Reply to others' posts with substantive comments. Quote-post to add your perspective rather than just amplifying. Follow the custom feeds relevant to your niche (there are feeds for design, programming, startups, science, and hundreds more) and contribute to those conversations. Bluesky users can tell when someone is broadcasting versus participating — participation builds a following, broadcasting gets ignored.

Images and alt text: The Bluesky community has strong norms around accessibility. Posts with images should always include alt text. CodivUpload's bluesky_alt_text parameter lets you set this programmatically — skipping it is technically possible but culturally frowned upon. Describe the image concretely: what's shown, any text visible, the relevant context.

Posting cadence: Consistency over volume. Two to three posts per week at times when your target audience is active produces better results than daily posting that feels like a content treadmill. CodivUpload's scheduling queue lets you batch-create posts and spread them across the week with precise timestamps.