Nostr Web Client

I think that sounds good from a simple concept, but never underestimate the cost of redoing someone else’s work. Plus the difficulty of getting Hypercore to behave in the very open and broadcast fashion of Nostr is unnecessary considering Nostr already works. I think there’s a lot of value in simply using them both and if one eventually takes over due to development benefits or hosting costs or whatever, then great, but the quickest and most robust way to solving our problems i think is to use what works, where they are each needed.

keet dont tweet 1y ago

i dont disagree much i just think there is a strong likelyhood a keet like twitter will work better, if our social content goes into repos ie a hypercore it would be similar to bluesky and make content discovery and replication easier, also more secure, i think nostr ends up coming to many of the same solutions pear and keet have, we already see hash addressed media with blossom the next step is a dht or indexes and a dht

i am not sure what you mean on hypercores not being able to be open? as i am aware they can replicate like a torrent if you want?

Reply to this note

Please Login to reply.

Discussion

No replies yet.