Cool, thank you. Here's a couple suggestions, things I pondered about, I didn't fully think them through yet, pick or reject as you wish:
(1) To stay true to the BU brand, I think the opt-in FRBF should stay fully available on the 'plumbing level'
(2) An FRBF 0-conf txn should create a big red warning on the receiving side
(3) the UI should default to 'don't send as FRBF'
(4) People have criticized 0-conf for being 'dangerous'. I think that is to a large part FUD and manipulation. But maybe we can ease peoples worries here in a good way: I do see the danger only for 0-conf-receiving TXN of large value (House, Car, ..), not for a $5 coffee. One could have a default limit on transaction value above which
any 0-conf TXN would generate a warning to wait for confirmations, similar to case (2)
EDIT: Clarified.
[doublepost=1449130933,1449130196][/doublepost]
@cypherdoc , @21: I was quite sceptical with their release, but integrating a lot of these 'micropayment' type services (SMS, MP3, ...) into the system does make it a little bit more interesting.
Many have said that what 21 did can be redone with a RasPi + USB miner. As I am prone to technical tunnel vision, too
I of course still agree that is the case.
However, I can now also see that what they're really trying to sell is the polished product and integration of all this onto a common platform. That might indeed make sense.