







we're planning v2 of our standard.site integration in the bsky app the goal is to make the "subscribe" button work. when you tap "subscribe" on a link card, what should happen? e.g. - get notifications on bsky when new articles are published - see new articles in a feed or separate tab - more?
Aug 11, 2026 at 5:24 PM
nicolo-ribaudo/bsky-to-mu
Browser extension that automatically redirects bsky.app to mu.social.
bsky to mu – Get this Extension for 🦊 Firefox (en-US)
Download bsky to mu for Firefox. Automatically redirects bsky.app to mu.social.


app.bsky.notification.getPreferences | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user's PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.*

So of course we followed suit with the @standard.site integration! The subscription buttons now appear in your activity stream, both when you publish an article, or when you post (or repost) it on @bsky.app Check out how this looks on the Profile-of-the-Day from @renderg.host:
Bluesky
v1.122 is rolling out today, featuring a better way to discover and share articles, blog posts and newsletters across the Atmosphere via new, dynamic Standard.site link cards. 🧵
Last week, the Bluesky app shipped a content visibility declaration setting to let people opt out of having their posts appear in feeds like Discover. How your app might use that setting is all about intent and reach. bsky.network/blog/content-visibility-decla…
Using the Content Visibility Declaration
bsky.networkwe're working on the v2 of our standard.site link cards. these cards currently link to both the article (top part) and publication (bottom part). they show a "Subscribe" button when possible, otherwise a "View Publication" button. what changes would you all like to see in the next version?
Guido X Jansen
It keeps confusing me that the main call to action in these cards (the button) does NOT go to the article but to the main website Is it just me that finds this weird...? The main visual CTA for a card about an article should go to that article no...?
I realise I'm probably pretty dense but the stansite subscription UX perplexes me. I hit the subscribe button. I'm not subscribed, but sent to blog landing page and asked to install an app. (But isn't the idea that I can subscribe to a stansite without installing multiple apps?).../1
Brittany Ellich
Hello! I've been at Bluesky for a bit over a month now and have a lot of thoughts, which are now going to be tucked away in this cute lil blog on @pckt.blog First up: Atmospheric Groups, an effort that we are working on in the Atmosphere community that I'm very excited about 👀👀
happy Monday, I wrote up my decision-making around our new endpoints.bsky.app HTTP reference! Thanks everyone for the push to do this 😊
About the new endpoints.bsky.app
alex-bsky.leaflet.pubAnyone know why Bluesky is so poorly integrated into @ifttt.bsky.social? A bookmark trigger seems pretty obvious. Something for @mu.social?
just added this to @linknotifier.bsky.social ! follow it to get a DM whenever someone posts a link to the website you use as your handle
Bluesky
v1.119 is live! Bot labels are here. If you run an automated account, you can now mark it as such in your account settings. The label will show up on your profile and posts so people know what's a bot and what's not.
we’re rolling out the first phase of the Bluesky + standard.site integration today! now, when you share an article from writing platforms that support standard.site (like @leaflet.pub, @pckt.blog, @offprint.app), you’ll notice the link card has more to it than a typical link card.
Bluesky
v1.122 is rolling out today, featuring a better way to discover and share articles, blog posts and newsletters across the Atmosphere via new, dynamic Standard.site link cards. 🧵
In 2026, @bsky.app is focused on what’s next for open social: bringing together users for conversations around live events, creator and platform monetization, and private state, giving users truly private data while preserving ownership and portability at the protocol level.