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

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.

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).

Oh makes sense! ENS lets you add in an email field but I don't think a lot of people use that. Seems like there is a lot of opportunity to build a core infra layer here.

To me that's a feature. I wouldn't want someone to mention me on Web3 Quora and be notified about it. I want a world with fewer notifications.