7 ms·
I had an idea like this a bit ago, where essentially you would dump your tiny (PGP) message in a giant noise haystack at a random, or generated offset. These me
by kbaker 10y ago
I had an idea like this a bit ago, where essentially you would dump your tiny (PGP) message in a giant noise haystack at a random, or generated offset. These messages would get rolled up into a big torrent that gets served every so often.
This is similar to PGP over Usenet, but has the advantage of fooling traffic analysis as well.
It is actually more like dead drops, storing something secret or obfuscated in a very public place, and agents check it only every so often. Since it would just look like a giant torrent, it would be very hard to detect legitimate torrent mirroring from also pulling information out.
Only problem is still the message expiration, which I don't really believe is possible except when using a third party server.
- Matt3o12_ 10y agoThis doesn't scale well and is impossible if you want to send any media. If such an app were to become as popular as iMessage, it would need to handle 200k message per second. I can't download so many messages per second on my phone. You could send blocks with 2000 messages but you could easily be deanonymized (look, out of those 2m messages, he requested 5 blocks with the same author. I think they talk to each other). Don't get my started with kilo to megabyte big images. If you would not want to scale the app, you could also be deanonymized because you're talking with a niche that has less then 10,000 users. I wish there was an easy solution to this problem but we already see how badly Bitcoin scale and there are great articles why Bitcoin with its current design can't be used in the real world simply because the block chain has a pretty low limit on transactions per second.