devin ivy 🐋

devin ivy 🐋's avatar
devin ivy 🐋
🛡️ divy.zone_at_bsky.brid.gy@momostr.pink
npub1jasz...326x
🌀 bluesky team 🌉 [bridged](https://fed.brid.gy/bsky/divy.zone ) from 🦋 [divy.zone](https://bsky.app/profile/divy.zone ), follow nostr:npub1pqr3g2gk3vsnrqk9kwfqqcxc6d5cwjr0hyc0nlzz9py5nf92vd9sn02sck to interact Web site: https://bsky.app/profile/divy.zone Link: https://divy.zone
fresh atproto proposal! this one is for the oauth, app architecture, and security folks: [github.com/bluesky-soci...](
GitHub
proposals/0010-client-assertion-backend at main · bluesky-social/proposals
Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.
 ) here we're defying the labels of traditionally "public" vs "confidential" oauth clients, and challenging assumptions about what it means to be a browser-based app. 1/8 [proposals/0010-client-assertio...](
GitHub
proposals/0010-client-assertion-backend at main · bluesky-social/proposals
Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.
 )
#atmosphereconf was unreal. this community is soo damn cool and knowledgeable. also a great reminder this work has roots, is just part of what will be a very long tradition. slides for my talk can be found somewhere in here! [pdsls.dev/at://did:plc...](
PDSls
Browse the public data on atproto
 ) RE:
Bluesky Social
AT Protocol Community (@atprotocol.dev)
Devin Ivy, @bsky.app team @divy.zone, The Shape of Apps to Come A lot of people see "Twitter Clone" in Bluesky. Yes! Except atproto devs see ... r...
 View quoted note →
at a glance this is just a small, backwards-compatible protocol tweak. that's true, but the implications are pretty big. to date the amount of data you need to store to fully verify the next write to someone's repo grows with their repo's size. we're able to make it constant instead. but how? 1/10 RE:
Bluesky Social
bryan newbold (✈️ vacation/travel through mid-Jan) (@bnewbold.net)
🛠️ atproto devs! 🛠️ got a new proposal out about Sync 1.1, aka inductive firehose, aka cheap validating relays. it is a long, low-leve...
 View quoted note →
private content is one of the top asks of atproto, we have some ideas. leading designs involve each user having multiple private repos. they differ from your public repo as they are access-controlled and not signed/redistributable. but they are still key->value, addressable, and of course they sync! https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:l3rouwludahu3ui3bt66mfvj&cid=bafkreifcwiycvynitqipppql6cjeturhmftpyrrcdkqpk2ffbnacmqmuje
one thing i dig about how atproto architecture (middle) has played out is that the different layers have checks and balances against each other, but developing an app still feels super similar to how you'd build a traditional platform app (left). atproto app dev is gonna get so good!! https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:l3rouwludahu3ui3bt66mfvj&cid=bafkreicakirm5oe463hhxweoarwtrejgua3oa54a4hnake22oikujl4gqa
pretty sick to think, every 1M users who join bluesky are also 1M users joining the atmosphere. 1M users who essentially already have an account and social graph on all apps—present and future—built on atproto. i have a feeling the next year of building within the atmosphere is going to be wiiild.
we just deployed a fix to a long-standing issue with our image cdn: images within posts are no longer unnecessarily scaled-up. that means many images will load faster and use less data. we also took this as an opportunity to improve the quality of full-size images, as many have requested! 🌅 https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:l3rouwludahu3ui3bt66mfvj&cid=bafkreibvscbxm6esj5lp5ngtcu5g6hridpyxowtxkzkqekrw4n6y5r2y6e