Post

fig (aka:[phil])
@bad-example.com

FOLKS WE DID IT ✅ I'm typing this on @aviva.gay's deer.social ✅ which posted to @alnkq.bsky.social's AppViewLite ✅ which is listening to the @blacksky.app atproto.africa relay

fig (aka:[phil])@bad-example.com

pretty damn close to a 100% top-to-bottom bluesky-free bluesky ✅ indie pds (lots) ✅ indie relay (mine + others now!) ✅ indie jetstream (mine + many more (optional)) 🌀 indie appview (AppViewLite has some issues, @futur.blue's should work, more in progress) ✅ indie client (@aviva.gay's deer.social !)

fig (aka:[phil])
@bad-example.com
fig (aka:[phil])@bad-example.com

if you're on a bluesky app and reading it, i think the short version is: it means bluesky is an open/interoperable social network every piece of infrastructure i used to make that post was running independently from bluesky!

fego
@fegodev.bsky.social

Thank you. So what you did demonstrates that anyone can build a client using the at protocol, meaning that if bluesky gets killed or someone buys the company, other social apps using the at protocol wouldn’t be affected? Is this turning Bluesky more like Mastodon?

Eric
@edavis.dev

previously* to access bluesky (the microblogging platform) you were reliant on Bluesky (the company) for the client, appview, and relay with this, you get access to the *same* bluesky microblogging platform as everyone else but through an independent client, appview, and relay

0 reposts3 likes