Post

Ok gotta nitpick, PDS is still Bluesky in this case!

if you resolved my plc doc to confirm that then you know enough to one-up me and close that gap 🫡

haha fair, let me pull up my company account, that is currently self hosted

Wow I was just kidding before turns out it’s real

internection 📈📈📈

What is all of this? I'm so confused yet so interested

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!

Oh my goodness So I can literally make an instance out of Bluesky independently from Bluesky servers? Just like Mastodon? If so that's neat, I really liked Fediverse related stuff but didn't knew where to start

@todepond.com it finally happened!

great how do i sign up to this third party appview

But you didn’t post to an indie PDS! Doesn’t count! Mastodon remains undefeated!! ActivityPub W3C ARGLE BARGLE.

oh noooooo (you know how sometimes you intentionally leave one inconsequential flaw in something so that the haters have something to fixate on?)

On it 🫡

Am I being an idiot here? Trying to get my AppViewLite working with @tokimeki.blue, but its just... not. Doing the proxy as "did:web:bsky.zio.blue#bsky_appview", and then nothing is loading after that. Not sure if I missed something, or AVL has issues with Tokimeki?

the xrpc endpoints on appviewlite are ruff for service proxying right now, see github.com/alnkesq/AppV...

spent a couple days trying to figure out whats wrong with appviewlite with non-appviewlite clients but last night i saw that fix of yours and it finally got my appviewlite deployment working with klearsky, thank you!

oh wait, i don’t see your did:web at that url

CC @004822.xyz

you can repro! custom-appview.deer-social.pages.dev/profile/did:... under settings -> deer -> custom appview did, enter: did:web:appview.bad-example.com lots still broken (just need to repair the xrpc endpoints), but you should be able to open that direct link after setting the appview ^^

also you can use AppViewLite directly without deer until some more of the xrpc paths are fixed. it works smoothly and is very full-featured! my same instance that the service DID references: appviewlite.bsky.bad-example.com

Out of curiosity: Where do user identity information live? PDS? Or do they require any central infrastructure?

separate from pds, somewhat centralized. keyword is “DID”, with two supported DID methods in atproto: did:plc has a centralized log (with aspirations of operating independent from bluesky) and did:web, which has no service dependency (well, DNS and domain registrars)

Honestly don’t understand what’s up with this? Why is this good? Please someone explain.

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?

If a billionaire buys Bluesky the company they aren't buying bluesky the network and can't just turn it into a Nazi site.

god i hope you're right

Hey @bad-example.com, I would love to achieve something similar. Would it be possible for you to share a GH project?

hi! it’s early and not in a state that’s easy to plug and play, but my ansible playbooks might help you get started: github.com/at-microcosm... some of it’s a little broken or behind. also if you haven’t set up your own PDS, that would be a great place to start, much more established path

hello youtube / i was here