Needs integration with pear runtime to solve the hosting issues in a p2p fashion. Relays should serve as a means to cache content/info when things are initially posted or when peers are limited or unavailable.
Discussion
Nostr relays and syncthing relays need more in common.
Don't know much about syncthing, but it never seemed to work the way I thought it should & was just a massive let down after bittorrent sync suicided itself. Keet & pear work the way I have always imagined things should work.
It shouldn’t be synching, it should have more in common with syncthing. Meaning, it should have more in common with Secure Scuttlebutt. Meaning, relays don’t store data. Clients do.
And that data is from your network alone, or one hop out. All relays do, is facilitate discovery.
As for pear, I’ll have to discover that myself. Something weird about it…
pear aka hypercore aka dat? the thrice rebranded javascript code? nah im good.
Hypercore & holepunch & other open source modules have been combined to make pear. It already appears to be more scalable than Nostr so it seems to me like Nostr needs Pear more than Pear needs Nostr, & taking the UI from a good Nostr client is probably not as hard as solving Nostr's scaling problems 🤷♂