the first building block of an atproto-based social browser

this is awesome!

This! There is a clear conflict of interest running an app view and a PDS. In the future, I expect PDS hosts to run independent of major app views

This feels pretty good for @tangled.sh www.theverge.com/news/757461/...

As atproto apps increasingly choose to verticalize PDS hosting, we need to be weary of user identity/data fragmentation across apps (ironically one of the key problems that atproto/bluesky was designed to solve)

Interesting to see another atproto app vertically integrate PDS

bsky should really emphasize the best part of atproto: the PDS. investors should fund startups selling PDSs, both as a cloud service and a physical self host device. make it clear to users that the biggest benefit of atproto isn’t “one account for all platforms”, it’s “choice in sharing data online”

Idea: build a PDS hosting service that enables creators and publishers to monetize their data

Testing backlinks for blahg blog.smokesignal.events/posts/3ltgan...

What would be the incentive for an existing web2 service to adopt atproto and become an appview?

We need to create a human-readable namespace for atproto DIDs and records

Does anyone know who built atpage?

In a world where AI/machines reduce execution risk, having the right idea is what matters most

One step closer to building a general-purpose atproto client

One of the most powerful features of crypto/blockchain systems is the separation of user data from application presentation. I can take my identity and token balances with me across apps. Atproto will do the same for the web, taking us from enshittification --> cryptification.

at:// links will be critical in making it easier to traverse the open social web. Well done @ngerakines.me for demonstrating this to the world

With atproto, we can go from monetizing the screen real estate users see (i.e. clients) to monetizing data itself. I believe this subtle difference will lead to a more open and innovative web where data exists and is useful independent of the client it was created in.