Have found myself thinking more and more about new web3 social apps. But almost all of them seem worthless to pursue without notifications infrastructure, particularly:

- the ability to send notifications to users not yet on the app.
- an inbox that users pay attention to.

hearts are sometimes bookmarks. peterzakin.com | pzakin.twitter

possibly controversial opinion: i would like that inbox to be inside farcaster. FC is my only DAU app for pzakin.eth. 

Seems like the only candidate that can dependably deliver messages that will be *read* by other users...

Building mobile games @ volley // Building https://anything.is/possible

It's not for the use cases I'm talking about. E.g. if I built web3 quora and i wanted to @mention you but you weren't on the service yet, i would have no way of reaching you unless I knew your email address (which I don't).

For Badge, we've added an optional email field for the recipient when sending someone a Badge. Seems like email is the most obvious solution here.

I'm excited by the idea of followers and following being tied to wallet, and any social app can request permission to access social graph or part of social graph. No network effect lock in. A lot of innovation is possible with this design.