feat: direct messages

[dozyio]

• Adds direct messaging
• Adds toast for errors
• local dev server over ssl
• Autodialer for gossipsub peers
• Pinger to drop dead connections
• Opinionated eslint & prettier
• Replaced download/blockies with react-18-blockies
• Fixed chat height to match viewport
• Moved some functionality to libs
• Unread message count
• Timestamps
• Spinner while message sends
• disable file uploads button when direct message - ideally move file uploads to Helia in a separate PR
• DM page for mobile
• back to public chat link on DMs page when on mobile

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
universal-connectivity	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2024 2:34pm

[2color]

What's the reason for enabling the DHT in the browser again?

I added delegated routing to avoid running a DHT client in the browser, but if there's a good reason, we can enable.

Also see #113 for more background on why this app relies on the IPFS DHT.

[2color]

Have you tried this out and can you tell whether this works for two browsers behind NAT?

[2color]

Thanks for submitting this PR. I skimmed through the PR and looked at the preview and it looks like you've cleaned up and refactored a lot which is great.

Before giving this a more thorough review, some initial feedback:

• I'm reluctant to add custom protocols to this app, due to the complexity and maintenance overhead it adds. However, I see the value in direct and signed messaging.
• I'm currently working on getting browser-to-browser connections to work properly out-of-the-box and well documented (with some ambient peer discovery mechanism). This is something that I'd like to get working and documented ideally before merging this. I saw that you attempt this in the AutoDialer component, but I am pretty sure that for browser-to-browser to work, the browser needs a circuit relay reservation and a multiaddr dialable from the browser that ends with p2p-circuit/webrtc/p2p/peer_id, e.g. /ip4/147.28.186.157/udp/9090/webrtc-direct/certhash/CERT_HASH/p2p/12D3KooWGahRw3ZnM4gAyd9FK75v4Bp5keFYTvkcAwhpEm28wbV3/p2p-circuit/webrtc/p2p/OTHER_BROWSER_PEER_ID.

[2color]

Any thoughts @dozyio. Really appreciate this PR!

[dhuseby]

• I'm reluctant to add custom protocols to this app, due to the complexity and maintenance overhead it adds. However, I see the value in direct and signed messaging.

I agree with this however what if you instead just implemented something that has some level of adoption such as the LIME Protocol. I'm all for this PR landing. Let's make it happen.

[dozyio]

See #175