5 ms·

This really looks like Bitcoin Cash propaganda, and really, not a very efficient way to do messaging at all. If you're interested in more practical approaches

This really looks like Bitcoin Cash propaganda, and really, not a very efficient way to do messaging at all. If you're interested in more practical approaches to do this instead of just shoving messages into a blockchain, Twister [1] does decentralized microblogging (a la Twitter) with e2e encryption for direct messages. Instead of using its "blockchain" to store every message, a Bitcoin-like protocol is used for authentication and a DHT network is used for the messages themselves. If the push came to shove, it'd be far easier to implement scaling or message pruning with this approach, while keeping the auth layer relatively limber. There's also Bitmessage [2] which uses a different approach and aims to hide metadata as well. Disclaimer: I've contributed to the Twister project. [1] http://twister.net.co/ http://twister.net.co/ [2] https://bitmessage.org/wiki/Main_Page https://bitmessage.org/wiki/Main_Page

marknadal 8y ago
Twister looks cool, I haven't seen it before. How long have you been helping with it? Using BitTorrent for these things seems like an obvious solution compared to everybody trying to do it on some blockchain (just not scalable). Although BitTorrent, in my experience, isn't the best at small rapid data, like tweets, versus large files/assets. Which is why I've worked on similar tech, for doing P2P stuff (short tutorial here: https://hackernoon.com/so-you-want-to-build-a-p2p-twitter-with-e2e-encryption-f90505b2ff8 https://hackernoon.com/so-you-want-to-build-a-p2p-twitter-wi... ), so I'd love to chat with you about how you did it for Twister and compare notes. Like, why couldn't you have done it all with BitTorrent, why did you need Bitcoin pieces? How did you get microblogging on BitTorrent to work efficiently?
- kemonocode 8y ago
  My contributions to Twister are relatively minor- mostly focused towards UI/UX stuff, something I personally loathe, but figured it'd be good learning. Also, out of all projects that itch for a nail to smash with the Bitcoin hammer, it's one of the few that make the most sense to me. The reasoning to use a Bitcoin-based protocol for the auth layer is detailed in the whitepaper [1] but it's basically in order to have unique identities tied to a given username while still remaining decentralized. Just like with Bitcoin, there's Proof of Work needed to perform these validations, but instead of getting paid in coin, whoever finds a block has a chance to get a given message promoted for people to find more easily on their client. Does it scale? I'm not sure myself, it's working pretty well right now, but it certainly scales way better than using Bitcoin for every damn thing. In theory, you could use different protocols to those the original developer chose for all three layers since they're mostly independent (the user registration/auth layer, the DHT layer for messages themselves and the BitTorrent swarm layer for distribution and notification) [1] https://arxiv.org/abs/1312.7152 https://arxiv.org/abs/1312.7152

marknadal 8y ago

Twister looks cool, I haven't seen it before. How long have you been helping with it? Using BitTorrent for these things seems like an obvious solution compared to everybody trying to do it on some blockchain (just not scalable). Although BitTorrent, in my experience, isn't the best at small rapid data, like tweets, versus large files/assets. Which is why I've worked on similar tech, for doing P2P stuff (short tutorial here: https://hackernoon.com/so-you-want-to-build-a-p2p-twitter-with-e2e-encryption-f90505b2ff8 https://hackernoon.com/so-you-want-to-build-a-p2p-twitter-wi... ), so I'd love to chat with you about how you did it for Twister and compare notes. Like, why couldn't you have done it all with BitTorrent, why did you need Bitcoin pieces? How did you get microblogging on BitTorrent to work efficiently?

kemonocode 8y ago
My contributions to Twister are relatively minor- mostly focused towards UI/UX stuff, something I personally loathe, but figured it'd be good learning. Also, out of all projects that itch for a nail to smash with the Bitcoin hammer, it's one of the few that make the most sense to me. The reasoning to use a Bitcoin-based protocol for the auth layer is detailed in the whitepaper [1] but it's basically in order to have unique identities tied to a given username while still remaining decentralized. Just like with Bitcoin, there's Proof of Work needed to perform these validations, but instead of getting paid in coin, whoever finds a block has a chance to get a given message promoted for people to find more easily on their client. Does it scale? I'm not sure myself, it's working pretty well right now, but it certainly scales way better than using Bitcoin for every damn thing. In theory, you could use different protocols to those the original developer chose for all three layers since they're mostly independent (the user registration/auth layer, the DHT layer for messages themselves and the BitTorrent swarm layer for distribution and notification) [1] https://arxiv.org/abs/1312.7152 https://arxiv.org/abs/1312.7152