Post

what do yall think are the most impactful things we could do in the Bluesky app to support atproto builders?

26 reposts172 likes

People ask for mini-apps. Having all sorts of embellishment points in a given post, allowing a2ui or MCP apps to harbor in these places. Having some extension points for css per post, post as background styling, to let folks go wild with knowing who or what they're looking at.

I think mini apps could be a long-term goal (lots of technical aspects to work though) but richer atmospheric embeds in the social-app can be done now to highlight the wider ecosystem and let it be interacted within the social-app (no context-switching needed).

Gordon@gordon.bsky.social

mini apps + cross-atmosphere payments + wallet

Like we've seen with standard.site richer embeds visually signals a difference between atmospheric links and an ordinary OG embeds (curious if there are user metrics to back this up). They could be polls, event RSVPing, reviews, bookmark collections, games, etc.

The important part is social-app doesn't have to have chose a particular app to integrate with, just what lexicons do. I'd love to see more open governance emerge about proposing embeds and working with other parts of the atmosphere.

Eric Budd@ericmbudd.com

hoping this isn't off-topic, but I'm definitely wanting things like polls enabled in the protocol to answer the original question, I'm wondering if there are other third-party atproto tools that could be built-in / embedded inside posts as well

fix reporting. right now, you choose a reason, then who you're sending it to, even if that labeler doesn't handle those reports at all. each labeler should publish what kind of reports it handles, and the app should respect those.

distribution is the hard problem. every team needs every bit of help they can get on promotion. promoted posts is a dangerous feature, but a 'featured app' link on the left well would be a huge boon. with a weekly rotation, that's 52 apps a year.

if you want to go crazy, partner with security friends like @socket.dev to review apps and provide a directory with reviews. google chrome's initial benefit was incredible performance, the extensions however are what has locked in value and pulled developers from moz eco. the pattern holds here.

If polls were a native feature, you could make a list of the most suggested things and have people vote on their prioritization. Just saying 😉 In reality though, I really do think native features in parity to competitors is important for getting more people on board.

Everyone else's suggestions are wrong, only mine is correct: Allow users to place custom action icons in various places in the app. both appended to every post and to the main app chrome. for example, I'd like to replace my Bookmark button with a "Save to @semble.so " action.

Profile integration with other ATProto apps, ala Discord “Connections” Stuff you could do with this: - Rich Presence like Now Playing status from teal.fm or Rocksky - Stats from other apps like # of Photos posted to Pinksky or Grain - Links for other apps’ AppViews for your profile

Awareness that people have an Atmosphere account, not a Bluesky account. Explaining the concept of OAuth to them. Just so we don't get "This is trying to steal my password" as much

Progressive disclosure about pds choice, maybe using account completion, and a way for engaged users to see it’s worth the hassle so they can tell their friends

I was contemplating adding it, thanks for saying this! 100% agree.

As a developer (and also as a user), I wish the DM experience was richer. An API to serve user options and return context-aware responses would be amazing.

i'm sure this is industry practice or whatever, but i don't get why i need to re-approve the permissions of every atproto app so often... to me, that just means i don't even read what permissions it's requesting anymore, i get security fatigue. that's terrible for getting users used to oauth.

A way to display links to other apps' profiles in your profile, perhaps via a standard profile lexicon. A generic "status" area in user profiles that can be set by other apps in a similar way to the "live", to support e.g. "currently reading", "currently playing" like Discord.

build the atproto equivalent of Slack Block Kit into the app and give us primitives to integrate with the platform rather than y’al doing one-off integrations with successful projects

in all seriousness it is a good thing to point to for the concept since it’s very well encapsulated (from the outside)

Getting some high-level + privacy-friendly user analytics that could be used to target (willing) users who might be interested in other applications. Advertising but without being predatory?

Off-protocol analytics are so very unsolved in the ecosystem right now. Streamplace view counts are "eh just trust whatever Eli says". I bet we can do better

lead the way with rebranding the logon experiance to "ATmosphere account" so it lays the groundwork for all other apps to do the same, then post from bsky account about how you are rebranding so you know that the atmospher account can be used other places

Related to @wesleyfinck.org 's post here , even showing the different apps people use on their profile without needing users to subscribe to a labeler (which hardly anyone does) could be great

Wesley Finck@wesleyfinck.org

Visibility of other atproto apps. We need wayyy more users to approach sustainable levels. Bsky can help greatly with exposing Semble to new users. One idea: recommend other apps after following someone, similar to how substack recommends pubs and accounts. Eg "this user is also active on Semble"

+1 to this! If I could add my other atmosphere profiles and get icons for each directly on my bsky profile page that would be pretty cool (basically like the germ icon but for other vetted apps). Even a little Semble icon on some peoples profiles pages would be awesome for us!

I'm not sure if it's the most impactful, but I think probably moving the social-app to use OAuth. OAuth is the chosen/recommended path for auth, and it's really solid as is. But I think for atproto apps building in the style of the social-app (XRPC proxying, client holds auth)...

there's still some pain points with the 2 week max auth. I think if Bluesky was dogfooding it, it could help improve that experience, whether it's TMB or client assertion backend since that would probably have to be the path for the social app to use OAuth. Will give better experience to devs who...

Want to build atproto applications in this manner as well. Added bonus is I think it would help in the long run show a bit more that Bluesky is an application on the Atmosphere, and you are logging into a service provider instead of the Bluesky app, which in turn might help...

people feeling comfortable logging in to an account they already have on other atproto apps if they see a familiar login that they experience when logging into an atproto app they already trust with their password (Bluesky).

Not actually be afraid of the Atmosphere branding. Use it, mention it in the logon flow. It doesnt have to be the first thing people see, but it should create a visual identity that can be recognizable elsewhere. Noone not techy understands what the atmosphere impliesand we should change that

Late answer and probably other stuff on here deserves to be addressed first but one thing is, allowing people to move back to a bluesky pds. I’m curious about self-hosting but I really don’t want to permanently lock myself out of the experience I get now if things go badly

Custom applets as a post type. An applet includes input fields of predefined types like radio buttons, dropdown, text input, etc. When a user enters input, it is recorded in their PDS, and indexed in the AppView according to input type. This index is exposed both in the UI and as an API.

This is coupled with support for rapid editing of the post, so the applet can serve as an interface for a 3rd party app. The idea is to implement polls without implementing polls, so other types of creative applets are also made possible.

I think giving feedback whenever possible and just generally interacting in the community is a must! even if you don't have the best techy skills it's important to just be a community member! that's how we get tracktion build awareness

Give us blue badges when we help fix stuff, and build great products on atproto that add value to the community?

SVPN@svpn.com

Sometimes we help fix Cloudflare and Bluesky atproto things 🫡

Get regular users used to the oauth PDS screen by making the app go through it. 99% of users don't realize they have an atmosphere account on bluesky, not vice versa.

To invest in marketing, specially outside atproto communities. Creating tools is nothing without users, and each new user drag in the atproto benefit the whole ecosystem. Many campaign are made without money (inde, artists, small NGO...) BUT somebody as to focus on that, not just more dev.

To help atproto builders, we need new people to come on the ecosystem, and feature alone will not do that. I hope a market/com team will be created to support one of the atproto project (or all), and will be as active as dev around here. (I'm volunteer if a team like that should be created🙆‍♂️)

Improve discovery for users finding good 3rd party feeds. Make embedding vectors available for ppl building 3rd party feeds maybe just for popular posts. Make it clear you’re not going to kill off shit ppl are building by competing from you position of central advantage

Encourage expansion into other micro-publishing formats with centralized hosting providers. Right now, webcomics are reeling.

Midgart@midgart.bsky.social

tapas closing will affect me personally and but my biggest annoyance is the consolidation of web/toons being the only viable comic hosting site for reaching a larger audience now

Asking is great! Highlighting what other apps/lexicons people are using on their profile would help discoverability a lot. Use the same PDS auth path as every other app. Showing content from other lexicons (music streams, X is live on Y, etc) in feeds/profiles of bsky app.

Images I can understand being a child safety concern but typing indicators I’d also get behind

Also a replies API that allows users to program when a message is a reply to another message

My top features: - Read/sent/sending statuses for messages -GIF Browser -Typing indicators I have a 3rd party app I’ve been developing called Not Twitter that would greatly benefit from it

Your feed builders are the most numerous type of builders in the entire Bluesky ecosystem. Making positive changes to feed building in any way massively impacts the largest number of people doing free labor to make Bluesky a more engaging and personalized place. Nothing else is even close!

<3 and give users more control: - if they want to sort by most popular let them! - if they want to sort by chronological let them! - if they want no links, let them! - if they want no pics, let them! i should not have to run multiple of the same feed just to let users make these simple choices.

and if this seems like "but that's not atproto, it's bsky" - wrong. feeds can easily provide a surface into other atproto apps either simply by e.g., just showing links to standard.site articles. or feeds could get more love and more natively support multiple lexicons.

seconding this & also actually kinda *begging* for the team to do more to educate non-techie users abt custom feeds 🙏🏼

i'm not a technical person, so i'm not sure if this makes sense... but it'd be neat if an app like Sill could open links in Mu.Social rather than the official Bluesky app. ie: pick a preferred client app.

Spreading as much awareness about the entire network as possible to non-techies, maybe some would get interested in learning how to develop something for the whole Atmosphere! There's no future for ATproto if people aren't aware of its existence, Bluesky is not promoting it nearly enough!

Add some funky little Hollywood animations to logins and page refreshes that highlight how Bluesky is part of a greater decentralised network. Like "reticulating splines" but showing a very quick diagrams of a PDS with multiple apps listed, then Bluesky gets selected.

maybe dumb/impossible idea: optional semantic search (as a toggle-able option or a totally separate thing, not a replacement for regular search) that prioritizes results related to advertisers better results than normal search, tradeoff being that the top results are... a bit less-than-organic

like if someone uses the (again, optional) semantic search thingy to look for posts about dealing with ingrown hairs, maybe the top results are perfectly normal posts that happen to mention how pleased someone is with their safety razor (semantic search brought to you by Leaf Shave)

farcaster frames was an influencing thought over here for a beat. worth revisiting. not meaning that we should build exactly farcaster frames, but it serves as a bit of art on the wall to reference.

Wallet and *bundled* micropayments to external sites would be great. individual micropayments for clicking an article don't work because of transaction fees. but a wallet that's charged monthly avoids this elegantly.

like even if a single user only clicks 3 articles to media sites A/B/C you just move credits internally to group site-wide payments to one payment for each of the 3 end of month.

This would be fantastic. I'm often willing to pay $0.25 - $2.00 to read an interesting article on some site that has been linked by a person I follow, but I'm NOT willing to create a bespoke profile and sign up for a subscription when I'll likely never go there again.

something along the lines of the official @standard.site integration, but open for the community to build & play around with would be awesome!

Ahmed Soliman@solimaniac.com

bluesky needs some sort of atproto-powered plugin system, registered implementations & views of different PDS records made by devs in the community the @standard.site integration was the first step towards this, but anyone should be able to build these integrations

Farcaster and WeChat are interesting prior art. Web-based. Key thing is when you launch mini app, you’re already logged in and have some kind of IAP. Low friction distribution + user acquisition.

and atproto mini apps would be much more compelling then Farcaster, 'cause Farcaster handled automatic authentication but had no coherent shared data plane after that, no PDS repo Data in mini apps generally lived in random Postgres databases from the developers, we can do much better!

That is a very complicated question, because I don't want them to have to be JS or HTML, but they also need to work everywhere. I want to say Wasm, but that leaves a big UI question open. I'm working on some of these issues. I'd be happy to talk!

standard.site is a very cool approach to lexicons and I really think it could be adopted for more types of content. a standard for microblog posts could pave the way for other microblog apps to actually feel like interconnected apps in the wider atmosphere, vs just Bluesky clients.

I'm imagining a scenario where I login to Bluesky and see posts with tags for Blacksky, Northsky, mu, etc. because they were posted to their own lexicons, but are visible from my Bluesky client since I follow them via the microblog standard lexicon.

Ooooo I 𝘳𝘦𝘢𝘭𝘭𝘺 like this & for multiple reasons; catering to user convenience is probably the biggest one. I love surf since it does this, but it being it's own app view is enough friction against habituated muscle memory that, for my mileage, the app just collects dust unfortunately

would be a soft introduction of the concept of atproto for many people, and would also open up the ability for atproto microblog builders to really create their own spaces that are distinct from Bluesky

Collaborate with apps like @sprk.so to support records for short form video posting on Bluesky Genuinely think this is one of the biggest things you could do to support the current ecosystem of ATproto apps We NEED to improve/encourage short form video posting on the Atmosphere

Inside the app: two things. An app directory, and a "via" label on every post that links to the client's site and its support page. Users find the apps. The apps get a path to getting paid.

Choose some cool non-Bsky lexicons that have momentum and find a way to integrate them in a way that feels native (even if it’s read-only). It’s one thing to say that the atmosphere is interoperable, but it would be whole ‘nother thing to interoperate.

Brainstorm: Standard: Blog reader with a “recommend” button Teal: Music player with a “like” button Tangled: Code preview with a “fork” button Community: Calendar event with “rsvp”

Support embedding more 3P lexicon in responses. Would love embedded events in ui in app

Still waiting on a lot of feed related requests that have already been shared with the team tbh 🤷🏻‍♀️ promoted feeds list being kinda static, in two places different, and no real means of surfacing new / relevant feeds to users makes it feel like the effort I put isn’t worth it for the usage it gets

But I also think the feeds I’m building are valuable and would be well-received if they weren’t dependent on word of mouth or seeing it randomly in explore or search

yeah pretty much, like more of a worry about governments requesting demanding that info,,,, which would already be public anyways but i think they just don’t want to be the ones that may be pressured to hand over the info by a government.

People are saying mini apps which I feel is a bit extreme trying to be wechat but something similar to discord interactions where apps can put buttons/widgets that can open links, call xrpc endpoints, etc. would go a long way

Hmm

Andrew F@aftd.dev

Slack has (had?) this feature where if someone sent you a link to Miro or Lucidchart or something like that, clicking the link would auto-provision an account using the data Slack sent. No sign up needed. It wasn't super well-adopted there but it maybe makes more sense in the Atmosphere context?

Honestly a lot of replies in this thread including my own seem be things that wouldn’t be specific to bluesky and should probably be built as community or protocol standards instead of the product team.

Do A LOT MORE communication about AT Proto and why bluesky is cool because of it. Stop doing stupid comm on Twitter dunking other apps, just explain and promote your stuff. So bad com won't penalize AT Proto projects. pay me to develop @lichen.wiki also hehe

facilitate opt-in push notifications through the bluesky app, redirecting through other apps streamplace app has push notifications but most people don’t have that downloaded

Someone would use this to push malicious notifications and I think the App Store would be very unhappy

+1 this, IMO a standardised cross-app notifications channel is probably the biggest way Bluesky could support other apps on the ecosystem

yes and ideally through an approach that other clients like blacksky or mu can easily support too a one stop shop for atmospheric notifications, all through whichever app you use

Well. ..... As you've proved from your post. It would be nice to have an app where we could put up our "impactful things"and vote on "our" priorities. Until then. Let's have another discussion. 🫢