why not build it on nostr?
Discussion
It’s explicitly P2P, Nostr isn’t that and would need a P2P protocol for it. So it’s either Pear or BitTorrent really. Pear has a much more complete stack so I have to invent way less stuff.
We are using Nostr for what it’s great at. It will be the profile and ID and WoT for sharing and publishing public drives. Again, I don’t want to invent anything that I don’t have to, I just want it to work.
Nostr is great for its network and how to authenticate and communicate with users. Pear is excellent at directly connecting and delivering files without any port forwarding, DNS, hosting or any of that bullshit. So I use them both where they work best.
If this causes a problem and doesn’t work for some reason down the line, I’ll just use a different tool that does the job, but right now it seems like Pear + Nostr makes it work intuitively, and that’s all I care about.
thank you for your answer
Of course. Thank you for your doubt. Honestly. It gets me fired up 🔥🫡
Is this hyperdrive related?
If so ask Pablof7z about it, he had experience with it but said he eventually dropped it mentioning overcomplication / overengineering reasons.
Yeah it’s super complicated to build with because it’s a bunch if interworking protocols, but that’s what we’re building PearDrive for actually.
We are abstracting away all the Hypercore and hyperdrive stuff so you can build and use it intuitively as you would think a P2P drive ought to work. We’re trying to remove the complication.