sebm

It was only the carry bit [1] and the saved space mention from the ChangeLog.

[1] http://seb.dbzteam.org/blog/2014/04/28/tweetnacl_arithmetic_...

Funny how small is the world, I reported them the same bug on February 13th, you might have been first though :)

It's exactly the algorithm I've decided to implement in one of my projects [1][shameless plug]. And although secret sharing is maybe not directly easy/relevant to implement in their context and for their type of use it would nevertheless be worth investigating what is currently done and is maybe related in the academic papers such maybe as [2]. At least it could give some ideas.

[1] http://coresecret.io/ [2] http://eprint.iacr.org/2013/629

> But the one book I am waiting for is Effective C++ 11/14 which should coming up next year.

Likewise! And from your first link there is a sort of preview of Scott Meyers' upcoming book http://channel9.msdn.com/Events/GoingNative/2013/An-Effectiv...

I think that despite the clichés in France (as anywhere else too) there always will be peoples that will try to do new things, different things, by themselves without relying on the old structures, even if they may be a minority. When I'm the most proud it's when I complete a project I set to do by myself even if it's small or if it fails. I literally live for these moments.

I use Firefox Nightly (since the beginning of this new releases schedule) as my main browser on OS X and I'm quite happy with it. The only (minor) inconvenience is to have to reboot the browser after every update every day.

BLE provides different ways of making requests, it seems the mode with the highest throughputs is when the central (client) subscribes to notifications for a service on a peripheral (server) and the peripheral writes data to the central with or without responses.

I don't have restested to look for the maximum throughput with notification without response but searching the bluetooth mailing list gives this interesting link http://lists.apple.com/archives/bluetooth-dev/2013/Jun/msg00...

Note that it certainly was tested on iOS 6 and iOS 7 has since improved its BLE stack implementation, for instance back then MTU was fixed to 22 bytes while it is now negociated and usually is around 112 bytes between 2 iOS 7 devices (iPhone 5).

Thanks for the advices! you're right my page is not explaining enough the purpose of the app. I'll try to improve it.

Indeed the distribution of the ciphertext when using Airdrop relies on the authentication made by Airdrop (I think that's why Airdrop requires iCloud to be enabled, but note I'm not sure of that). However the encryption of the ciphertext and the keys used are independant of Airdrop. In the worst case a wrong receiver would be selected, he would have the ciphertext but wouldn't be able to decrypt it.

edit: I think I've wrongly interpreted your question. Are you asking if Core Secret doesn't simply reimplement what Airdrop provides? If this is your question, the answer is no, the goal of Core Secret is to divide a secret between peers, each peer having a portion of the secret.

Yeah I know, I'm terrible at choosing names, I started my developements with this name then by lack of better idea i've kept it.