Receiver improvements

[sean-regents]

Any ideas for improvements to Receiver.

Features at the crossroads of XMTP messaging (1:1, NFT groups, or public channels), Lens social graph and following, web3 profiles and identity (credential badges and zk-privacy of data).

Please include links to integrations or example sites.

[sean-regents]

Address saving: Your account is saved through a page reload or coming back to the site the next day. Metamask-level

Identity saving: Your XMTP identity is saved through a page reload or coming back to the site the next day. XMTP-level. Requires address saving.

Examples
xmtp.chat is open-source: https://github.com/xmtp/example-chat-react
This has both address and identity saving.

Address saving with SIWE: https://wagmi.sh/examples/sign-in-with-ethereum

Importance
no connect wallet step and no metamask signing for XMTP identity equals ==
the perceived loading times for receiver decrease because we can start loading the conversation list the instant the receiver component is loaded.

[sean-regents]

Lens Integrations

1. Following an address you're talking to or in a channel
2. Render a Publication(Post) within the chat
3. Allow Collect of a Post within the chat
4. Channels token-gated on owning the Follow NFT of an address (aka the set of addresses following another one)
5. Channels token-gated on owning 1 or more Collects

React examples:
https://github.com/daoleno/lenskit --> check out the linked vercel site