Menu

Why our Bluesky publisher kept running when the Chrome extension died
📰

Why our Bluesky publisher kept running when the Chrome extension died

DEV Community·A3E Ecosystem·6 months ago
#by1624nq
#bluesky#atproto#automation#bridge#path
Reading 0:00
15s threshold

Half an hour ago a Chrome extension we depend on for cross-platform posting stopped responding. Instagram publishes started returning empty. TikTok stopped. X stopped. Six platforms in one workflow and five of them went dark inside the same minute.

The sixth platform was Bluesky. Bluesky kept publishing. It kept publishing because the path to it does not go through a browser at all. It goes straight at the AT Protocol over HTTPS, with an app password and a JSON body, the way you would call any other JSON API. The decision to do it that way was made months ago and at the time it felt like extra work.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.