Scott
@scott.nstar.social
Co-founder @ nstar.social – A decentralized, local-first social network on the @ATProtocol keeping users in control of their data. Private beta soon!
A decentralized social internet restores user agency over billionaire self-serving walled gardens.
A decentralized social internet restores user agency over billionaire self-serving walled gardens.
“and not in a way benefits the masses.”
November 8, 2025 at 9:30 PM
“and not in a way benefits the masses.”
There’s a reason these platforms remain “free.” These actors are concentrating extreme wealth to reshape society…and not in a way that does not benefit the masses.
November 8, 2025 at 9:29 PM
There’s a reason these platforms remain “free.” These actors are concentrating extreme wealth to reshape society…and not in a way that does not benefit the masses.
The monetization & political exploit of our social interactions is a major cause for the erosion of democracies around the world. People need to be more concerned how these platforms continue to manipulate society & generate extreme wealth to our collective detriment…
November 8, 2025 at 9:26 PM
The monetization & political exploit of our social interactions is a major cause for the erosion of democracies around the world. People need to be more concerned how these platforms continue to manipulate society & generate extreme wealth to our collective detriment…
My experience is the PLC requires an “atproto_pds” service. And things get wonky when the “alsoKnownAs” doesn’t have an “at:” handle.
October 13, 2025 at 7:28 PM
My experience is the PLC requires an “atproto_pds” service. And things get wonky when the “alsoKnownAs” doesn’t have an “at:” handle.
It’s unrealistic to believe a single PDS would store the entire data for a user (aka DID). Limits are one reason; there are many others. We can’t predict all the future innovative solutions on the ATProtocol that may require a newer PDS or a specialized PDS.
October 13, 2025 at 7:22 PM
It’s unrealistic to believe a single PDS would store the entire data for a user (aka DID). Limits are one reason; there are many others. We can’t predict all the future innovative solutions on the ATProtocol that may require a newer PDS or a specialized PDS.
Very good question. Rejecting non-Bluesky schemas would contradict the current ATProtocol architecture which limits a single user DID to one PDS. I’ve raised this artificial and unnecessary limitation as a concern. One DID to one PDS is contradictory to achieving full decentralization. It’s silly.
October 13, 2025 at 7:10 PM
Very good question. Rejecting non-Bluesky schemas would contradict the current ATProtocol architecture which limits a single user DID to one PDS. I’ve raised this artificial and unnecessary limitation as a concern. One DID to one PDS is contradictory to achieving full decentralization. It’s silly.
Do you know why a configurable client is an issue for Apple and Google? I’ll dig into their guidelines but by chance do you know the general vicinity to look?
October 10, 2025 at 1:55 AM
Do you know why a configurable client is an issue for Apple and Google? I’ll dig into their guidelines but by chance do you know the general vicinity to look?
Correct. You set the atproto-proxy to an Bsky-compliant AppView Api / Lexicon did:web. I performed this POC a few weeks ago successfully when Zeppelin was still available. Demonstrates the power of the decentralized architecture.
October 10, 2025 at 1:50 AM
Correct. You set the atproto-proxy to an Bsky-compliant AppView Api / Lexicon did:web. I performed this POC a few weeks ago successfully when Zeppelin was still available. Demonstrates the power of the decentralized architecture.
Btw…our upcoming NorthStar Social app under development has an option to configure the AppView of choice. We tested it with Zeppelin when it was still functioning. Works great!
October 9, 2025 at 5:50 PM
Btw…our upcoming NorthStar Social app under development has an option to configure the AppView of choice. We tested it with Zeppelin when it was still functioning. Works great!
There needs to be a registry for these various ATProtocol host-able components (pds, relay, appview, etc) that providers can opt-in and client applications can subscribe for programmatic discovery to offer options for end-users.
October 9, 2025 at 5:47 PM
There needs to be a registry for these various ATProtocol host-able components (pds, relay, appview, etc) that providers can opt-in and client applications can subscribe for programmatic discovery to offer options for end-users.
This comes down to branding.
Sign up & Sign across all apps, including Bluesky, should be an AT Protocol brand.
Blebbit.app is a decent example of branding ATProtocol. However, it’s the Blebbit.app a user is signing into not Bluesky. End users don’t understand the difference.
Sign up & Sign across all apps, including Bluesky, should be an AT Protocol brand.
Blebbit.app is a decent example of branding ATProtocol. However, it’s the Blebbit.app a user is signing into not Bluesky. End users don’t understand the difference.
October 2, 2025 at 1:46 AM
It’s not too different from any web browser’s ability to go to any web server. Nor any user’s choice to choose their search engine - DuckDuckGo, Google, Bing, etc. For the decentralized social network to succeed, the architecture needs the same versatility the web brought us.
September 21, 2025 at 9:10 PM
It’s not too different from any web browser’s ability to go to any web server. Nor any user’s choice to choose their search engine - DuckDuckGo, Google, Bing, etc. For the decentralized social network to succeed, the architecture needs the same versatility the web brought us.
Recent events have shown alt Bsky-like AppViews can provide user choice to continue using Apps free of Bsky. We’ve learned App’s can offer users an AppView configuration choice. App sets the “atproto-proxy” header to the alt AppView’s did:web. Great for users & App devs. That’s decentralization!
September 21, 2025 at 8:59 PM
Recent events have shown alt Bsky-like AppViews can provide user choice to continue using Apps free of Bsky. We’ve learned App’s can offer users an AppView configuration choice. App sets the “atproto-proxy” header to the alt AppView’s did:web. Great for users & App devs. That’s decentralization!
Thank you for your contribution demonstrating the versatility of an architecture supporting decentralization. Showed Apps could be portable to alt “Bsky”-like AppViews. This is instrumental in users having choice to continue using favorite Apps when an AppView operator’s policies are incompatible.
September 21, 2025 at 8:48 PM
Thank you for your contribution demonstrating the versatility of an architecture supporting decentralization. Showed Apps could be portable to alt “Bsky”-like AppViews. This is instrumental in users having choice to continue using favorite Apps when an AppView operator’s policies are incompatible.
I just canceled my Hulu/Disney+ bundle. These companies need to go bankrupt for failing to defend our democracy.
September 19, 2025 at 2:06 AM
I just canceled my Hulu/Disney+ bundle. These companies need to go bankrupt for failing to defend our democracy.
If Bsky believes in their decentralized architecture, it’s time the components separate from Bsky & rebrand to @ATProtocol. Starting with rebranding signup/in:
“Sign in/up with @ATProtocol”
Until then, architecture & design decisions will be Bsky-centric to the detriment of decentralization.
“Sign in/up with @ATProtocol”
Until then, architecture & design decisions will be Bsky-centric to the detriment of decentralization.
September 17, 2025 at 2:15 PM
If Bsky believes in their decentralized architecture, it’s time the components separate from Bsky & rebrand to @ATProtocol. Starting with rebranding signup/in:
“Sign in/up with @ATProtocol”
Until then, architecture & design decisions will be Bsky-centric to the detriment of decentralization.
“Sign in/up with @ATProtocol”
Until then, architecture & design decisions will be Bsky-centric to the detriment of decentralization.