to much dev wasted redoing the same functions while big problems of content replication are not well solved
bittorrent is sha256 now
scales fine just depends how you use it
'the concurrent number of users of Mainline DHT is from 16 million to 28 million' https://wikipedia.org/wiki/Mainline_DHT
why not just use a p2p platform? clients can then load files via multiple servers at once, can use index and dht lookups, anyone can add servers
you can still have dedicated hosts for torrents, called seedboxes, deploying additional 'servers' is very easy in a p2p network, you dont need domains or relays
? you can still make files censorship resistant its just a matter of distribution, look at torrents
there is already established tech to solve these problems, webtorrent is meant for p2p but browsers are not, mafintosh the creator of webtorrent has largely given up on browsers and is now running this company called holepunch making pear and keet, there is no other p2p codebase getting more dev on in the last 3 years and the results show
its way too complicated to be distributing files via many notes, usenet is way obsolete, many p2p systems since replaced it, bittorrent is the most used and stable currently, pear is an evolution of bittorrent and could be used for all nostr content files and text, blossom is not even using a merkle hash
it does store the data encrypted at rest and there is plans to lock the app tho some android can already do that, but what app can prevent data leak if a device is compromised? are you refering to revoking access for a device? i would assume that is planned
yes the data is local, not all may be tho which is unlike signal for example, keet can store part of the data but it must live somewhere to exist
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?
What if and hear me out there was a nostr client that integrated pear runtime or keet for direct messaging.
When one npub initiates a DM a request to accept is sent with the other half of the keypair and there is now a secure p2p connection for parties to speak. Relays only have to store the initial and close without storing the data from the conversations
nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev
#dev
#thoughts
what about build twitter on keet and abandon nostr?
this is an interesting use case
wireshark the connections, it will be open source and the performance will improve
there is this app by the guy that made webtorrents called keet.io
twitter for censorship resistance?
the place for this exists
Join me on Keet.io - The Epstein Archive (invite expires on 2024/6/27 9:31 UTC)
pear://keet/yrbt3drgixr8gg41nngphrtj14f57pgtn7q1rty5wzppsiu1tqdzrfq5juk9nanjjk959x3adkzch84u51op11t8fp7zkqay7g8a4am55fsun9mg