This is kind what Bluesky is doing now. Makes sense now with atproto in growth mode…let’s see how the story evolves

Another issue is that if you’re an app view running a PDS, your users might use that same PDS to interact with a competitor’s app view. Thus, you would effectively be subsidizing storage for your competitor’s app view

Resolving at:// URIs to HTTP URIs is one piece. The second (and harder) piece is building a UI / application flow uniquely suited for social browsing.

Web browsing is facilitated by a search bar and links. What should the format for social browsing look like?

People might get confuse it with Ethereum, the “world computer”

At the same time, it would be cool to build an atproto-native social browser that traverses across at:// uris

Who’s building white-label, B2B2C PDS infra??

Well said, I agree

What would it take for a browser to natively support AT-URIs?

I suppose handles are effectively the namespace for atproto identities