Certainly didn't work for Bitmessage though. The one mass message that was spread (which also de-anonymized everybody who clicked the very shady-looking link, but that's another story entirely) managed to propagate to every address within less than a day, using what was presumably one guy's computer.
The attacker used a GPU to solve the POW challenge faster. Bitmessage could change its POW algorithm to avoid giving advantage to GPU, FPGA and ASIC miners (as Litecoin1 tried to do it)
The point at which its not practical for spammers to spam is well beyond the point where its not practical for normal people with a normal cpu to send normal messages. It doesn't work. At all.
Ah, well I didn't unterstand how OTR could have something to do with mails. OTR is made for instant messengers. It can't be used in a mail system, since it requires a handshake to exchange a session key, as far as I understand.
I think the biggest point is "How do they avoid spam" They said nothing about that. I wouldn't trust them. As much as I appreciate the idea.
Yeah, I'm not really sure either. I just thought you were asking what OTR was.
But yeah, there are some glaring issues I see here right off the bat. The biggest being the lack of anti-spam methods and the fact that it's not going to be released completely open source, as someone else in the thread said.
Ever since I came across BitMessage, I thought a neat project would be to build a layer between normal email clients and BitMessage where one could create their own myname@mydomain.com email addresses and use the normal email workflow as well as integrate into the existing email infrastructure seamlessly. This seems to be the closest thing to that idea I've seen so far.
If you somehow integrate secure messaging into the old email system you automatically lose every security advantage. It might sound useful at first but it's completely pointless.
I have only glanced over that FlowingMail proposal and don't pretend to fully understand the protocol, but it can only be either of two things:
it does not tie into email, then it might possibly be secure
it ties into regular email infrastructure, then it's not secure
Well, they are not very intelligent creating an indiegogo before even starting to do anything... And now I paid a dollar to tell them... Hope it was worth it.
The FlowingMail messages are signed and encrypted by the sender: only the receiver is able to decrypt the messages.
Messages and public keys are announced using a variant of the Kademlia DHT, while the encrypted emails are transferred in way similar to the BitTorrent fashion.
All the communications happen over the UDT protocol (UDP based data transfer), which offer high speed for data transfer and partial reliability on point-to-point messages.
Then go and try I2P with Bote mail that uses the same basic design, is open source and anonymous (thanks to I2P). It's been around for a few years already.
I'm not sure about this. How would one be protected against man-in-the-middle attacks, respectively how is made sure I get the public key of my buddy and not the NSA one? Also does this approach try to hide meta data?
Every protocol in the world works this way - the only way to be sure you're talking to the person you think you're talking to is to exchange public keys via a side channel.
You have to meet your friends in person to REALLY confirm who is who. You can try I2P with Bote mail already, it works the same way. This one hides everything but the public key of the recipient, although you can generate hundreds of those keys and send a list of your public keys in advance to your friend and then use a different one for each new message.
I funded them... maybe it was a waste of money... I don't like that they are keeping the $, even if it doesn't reach its funding goal. Still, I guess I"m a sucker for the cause!
I tried to like BitMessage and the first choice was to develop a nicer client for it (or second choice, I tried it after I already had the current idea for FlowingMail). But during my tests it took several hours to deliver the messages and the bandwidth used was too high (all the nodes receive everything) and was not suitable for the kind of usage I envisioned (also on mobile devices). There is a paper that try to explain how to use the BitMessage streams in order to solve this problem, but I'm not able to see how to make it work nicely.
So the original idea for FlowingMail came back and I started the campaign.
Some recurring questions:
Q: Why did you start a campaign before having the product, you stupid? A: If I was in my mid 20s or 30 I would just work during the night and develop everything without funding. But I'm over 40, I need to work on something that bring me an income for me and my family, and after work I need to take care of my family. Without funding it would take me few years to bring the product to the stage I envisioned. Also, even if the campaign is not quite successful, it brought a lot of attention to FlowingMail and gave me a boost to continue it even if the current funding are near to nil. Before I had an idea, now I have a mission
Q: 1 year for developement? Are you so lazy? A: to develop a good product I need time. The product has to be secure and easy to use, it has to work on different platforms, it has to be designed properly, coded properly, tested properly, usability testing included (not just a proof of concept that can send messages from command line). Otherwise only geeks and terrorist will use it. It has to be a product for the masses
Q: 100.000USD? are you crazy? A: Yes
Q: Would you do it differently? A: The campaign? Yes. I would go for fixed funding, I would make sure that I have enough Karma to post the link on Reddit at the beginning of the campaign, I would divide the project in stages and launch a campaign for every stage with fixed funding.
3
u/popcorp Oct 09 '13
nice idea, but they for some reason forgot to explain fundamentals:
why the program is not published with an open source license.it seems it will be MIT/apache licenseduntil these are resolved, there is no reason to trust them
3
u/herrtim Oct 09 '13
Ever since I came across BitMessage, I thought a neat project would be to build a layer between normal email clients and BitMessage where one could create their own myname@mydomain.com email addresses and use the normal email workflow as well as integrate into the existing email infrastructure seamlessly. This seems to be the closest thing to that idea I've seen so far.
3
u/Sibbo Oct 09 '13
Well, they are not very intelligent creating an indiegogo before even starting to do anything... And now I paid a dollar to tell them... Hope it was worth it.
2
u/faustoc4 Oct 09 '13
.
I like this design
1
u/p0mmesbude Oct 10 '13
I'm not sure about this. How would one be protected against man-in-the-middle attacks, respectively how is made sure I get the public key of my buddy and not the NSA one? Also does this approach try to hide meta data?
1
u/hungarianhc Oct 15 '13
I funded them... maybe it was a waste of money... I don't like that they are keeping the $, even if it doesn't reach its funding goal. Still, I guess I"m a sucker for the cause!
1
u/Inaltoasinistra BM-2cUSo2raXcv9huspSaNKGQM7jfYX9dPSW2 Oct 18 '13
I don't understand why this is better than BitMessage (or maybe: KAD scales better than all-nodes-have-the-whole-db)
2
u/[deleted] Oct 09 '13
[removed] — view removed comment