This post takes a look at ATProto from a different angle, and explores the value of some possibly less-noticed pieces of it.

The "Login with Google" button has been so useful and yet so horrible for the freedom of the web. Why does google get to be the gatekeeper to all of our web logins?

We need an alternative, but it also needs to be easy, and by making handles domains, and making it so that normal people can use and understand it, they have made it possible for an actually decentralized social login button.

Linking Identity to your Personal Data Store and using Domains as Handles is a crucialcombination that is really starting to unlock web freedom.

A lot of what I'm trying to get at with this post is that there is more than one way to leverage ATProto, and that there are some pretty major things it has started to do right that we really need right now.

We're used to the idea that there's more than one way to make a web app, and the same is true even if you are building it on ATProto. It hasn't set a lot in stone, it's just given us some bricks that we can all share.

The "AppView" is a component of the ATProto architecture that you are given nearly free rein on. It can be any kind of thing you want, and I think there's all kinds of unexplored possibilities there.

You might even be able to make an AppView with a meaningful ActivityPub integration, or possibly borrow ideas about inboxes and outboxes as an alternative to relays.