Call for Developer Projects · bluesky-social atproto · Discussion #3049
The last few weeks have seen a swell of developer interest in atproto. Welcome! The protocol is maturing, and now is a great time for early adopters to jump in and start building. This post lists s...
Lexicon Embeds Overview
ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...
HappyView (@happyview.dev)
Lexicon-driven AppView for ATProto. Open source. Maintained by @trezy.codes. https://github.com/gamesgamesgamesgamesgames/happyview
This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
I'm thinking about how non-developers will feel about atproto. For example, will it take people by surprise that data entered into one app can show up somewhere else? More thoughts in this post.
How do we talk about atproto to non-developers? | Rachel Andrew
rachelandrew.co.ukrelated: for a number of use cases on atproto, the challenge has shifted from 'how do i get people to use my app' to 'how do i get people to use my lexicon' this also shifts what prototype apps even are
dame
in my experience there is now room to “vibecode” a prototype, evolve it into a more serious app, and then down the road refactor it into something that is more professional, organized, and sustainable previous AI models couldn’t handle large refactors like this, but they now can with human aide
some thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgsome thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgSome initial atproto-related learnings from #Rebuild Helsinki 🇫🇮 * most people building apps here have no idea what atproto is, which is a shame since especially when building social apps, atproto is a great starting point for many reasons
Plea to #ATproto developers & companies: Pleasepleaseplease make it easier for the rest of us to help boost your apps & tools by creating good, clear documentation geared toward non-techie users? (not just fellow developers or internal team).🤞🏽 See my post on @leaflet.pub.
Why good non-techie user documentation is vital for a wider embrace of the ATmosphere
debbieohi.leaflet.pubNew Build Notes article discussing ATProto and how we as developers can go about forming standard lexicons for common datatypes without being overly prescriptive on implementation details that would limit creativity and competition blog.stygiantech.dev/a/3msmoumcr4d23-atproto-stand…
ATProto Standards Bodies—Guiding the Future of the Network
blog.stygiantech.dev
