That seems to be the current design pattern but has serious side-effects that can lock user out of all AT Protocol if PDS is unavailable.
Provider bans. DDoS. Data center outage. Etc.
PLC w/ replicas is the equivalent to DNS.
Also, authorization should be separated. It needs high availability.
Posts by Scott Handley
PLC being independent with replicas would prevent a PDS down situation from impacting all the Apps & PDSes used by a user.
PLC is the DNS of AT Protocol.
You can update the PLC directory by requesting “identity:*” OAuth scope.
Agree, the extra email adds too much friction.
Agree, there needs to be “safe” PLC endpoints to add services & update rotation keys to prevent malicious actors.
Sad, these aren’t priorities as PDS can be a failure point.
Great idea! Another use-case to the growing list demonstrating why multiple PDSes are the reality. We can’t expect service providers will adopt newer PDS capabilities. Nor can we expect all PDS software implementations to update either. We’ll need a way for discovery…perhaps at PLC directory level.
Next meetup is Tuesday, 5/5!!!
Our very own @brittanyellich.com will kick the meeting off with a preview of her CascadiaJS talk on ATProto - AND we're raffling off a free ticket!
We'll also do another open breakout session, so if you've got a topic you'd like to discuss, we'd love to hear from you
Private social networking with friends & family...your data, your device, always available. That's decentralization you can count on!
We're inviting users who value their privacy to kick the tires, work out the kinks & make NorthStar Social the best it can be. Join our waitlist:
beta.nstar.social
That's why handle resolution should NOT be with Bluesky but with the PLC Directory and replicas!
Open to new opportunities! If you know of any senior eng / fullstack roles (remote or PNW based), especially in the open source / decentralized tech space, shoot me a DM!
10+ years fullstack, currently building on #atproto, check out @grain.social
Something like:
community.lexicon.app.declaration
community.lexicon.provider.declaration
I’m in the process of drafting something very similar for PDS and Bsky AppView discovery. Initially, due to time constraints I plan to
host them. Ideally, it would be something owned by each provider through a community lexicon.
Are you using the Bluesky permission-sets?
Several people have been unable to get them to work. It looks like the restriction in the permission-set on inheriting the audience has issues with some "atproto-proxy" requests erroneously failing.
Permission-sets with "aud: *" work as expected.
What about a lexicon that provides details for each app/provider hosted in their own repository?
- Name
- Description
- Website
- Image
- Color
- ToS
- Privacy
An image of a portion of the NorthStar Social sign-in screen. In the top-left corner, a button that returns the user back to the Welcome screen. The screen continues with the NorthStar Social icon followed by the words "NorthStar Social on the ATmosphere" and the NorthStar Social moto "People. Privacy. Period." Under the moto, the heading: "Select an account" followed by button(s) for available accounts to select.
Join us in the Atmosphere where it’s all about people not mega-corporations.
Our contribution to the Atmosphere this spring will be E2EE private social posts, photos, and videos with family and friends alongside your public interactions.
Beta waitlist now open: beta.nstar.com
Sign-in sneak peek:
2 separate issues:
Permission-sets w/ inherited audience don't work with atproto-proxy.
Permission-sets with "aud: *" works seamlessly with atproto-proxy. In a decentralized ecosystem, where anyone can standup an AppView that supports #appview_bsky (eg. Blacksky), this is a necessary setting.
This is the way. There are a few issues w/ permission-sets that need to be addressed. Inherited auth doesn't work for the Bluesky permission-sets via atproto-proxy. They should also be set to "aud: *" to facilitate an app's ability to support any #appview_bsky service (eg. Blacksky, Bluesky, etc).
A capital “Atmosphere” is a word. And looks wrong capitalized like a proper noun in sentences.
All lower case “atproto” doesn’t work at the beginning of a sentence. Nor standalone.
These speak brand:
ATproto, ATProtocol, ATmosphere
What’s your AT id?
Image with the NorthStar Social logo (a north star with a purple backdrop) and text alonside the words "@ATProtocol"
Yeah. It's so hard to let go of @ATProtocol with the blue. It just resonates a "brand." But, @ATproto would work too (and it's shorter).
Once our data was all local. Now, it is all in the cloud.
But why, when we can have both?
Local + Cloud = Better Together = NorthStar Social
Wait...we want this cool place to grow, right? You just disincentivized the masses from joining! 😉
An image of the NorthStar Social Sign In screen. At the top, the NorthStar Social brand and motto "People. Privacy. Period". In the center, @ Sign In and a text field labeled "Sign in to your Atmosphere account" with a Handle or DID. At the bottom, an explanation of "What is an Atmosphere account?" The explanation is cutoff but reads " Your social identity for accessing your data and apps on the open social internet, such as Blacksky, Bluesky, Eurosky, Northsky, Stream.place, Smoke Signal, and many others."
It must be Friday 😀!
Lots of healthy branding discussion about this amazing decentralized ecosystem powered by the AT Protocol.
My $0.02:
- Be unique.
- Be consistent.
- Be identifiable.
- Be fun.
- Be memorable.
🤔 Do I say $0.00 now that US pennies are decommissioned? Or $0.05?
😂
👆THIS!
bsky.app/profile/scot...
bsky.app/profile/scot...
bsky.app/profile/scot...
It would be really bad for users to enter their social security numbers! And bad for apps/providers to accept them!!
I'd suspect it'd be shortened at least o: Atmosphere ID
-2 syllables... still not as simple as:
"What's your email (address)?"
"What's your Atmosphere (ID)?"
Doesn't work so well without the qualification of "ID" or "Identity"
Agree. I'm not adverse to your suggestion. It's kinda clever.
Btw "social" in the US, could be confused with your social security number.
🤔 A little bit of both camps...so inclusive! 😀