{"action":"created","issue":{"url":"https://api.github.com/repos/conradkleinespel/rooster/issues/3","labels_url":"https://api.github.com/repos/conradkleinespel/rooster/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/conradkleinespel/rooster/issues/3/comments","events_url":"https://api.github.com/repos/conradkleinespel/rooster/issues/3/events","html_url":"https://github.com/conradkleinespel/rooster/issues/3","id":108045105,"number":3,"title":"some ideas","user":{"login":"qmx","id":66734,"avatar_url":"https://avatars.githubusercontent.com/u/66734?v=3","gravatar_id":"","url":"https://api.github.com/users/qmx","html_url":"https://github.com/qmx","followers_url":"https://api.github.com/users/qmx/followers","following_url":"https://api.github.com/users/qmx/following{/other_user}","gists_url":"https://api.github.com/users/qmx/gists{/gist_id}","starred_url":"https://api.github.com/users/qmx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/qmx/subscriptions","organizations_url":"https://api.github.com/users/qmx/orgs","repos_url":"https://api.github.com/users/qmx/repos","events_url":"https://api.github.com/users/qmx/events{/privacy}","received_events_url":"https://api.github.com/users/qmx/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-24T02:40:09Z","updated_at":"2015-09-24T21:50:02Z","closed_at":null,"body":"I hate issues for discussing stuff, but there we go:\r\n\r\nI was trying to build the same thing you've done with rooster, with two big differences\r\n\r\n- using [libsodium](https://download.libsodium.org/doc/) via [sodiumoxide](http://dnaq.github.io/sodiumoxide/sodiumoxide/index.html)\r\n\r\nThe library is ultra fast and provides encryption which is going to last. (It's taken from djb's nacl after all), and the main consequence for this one would be having a better key derivation scheme - we definitely don't want to have SHA256 for keys :)\r\n\r\n- using sqlite3 as storage instead of a single flat file\r\n\r\nmy reasoning for this one is having a file format which is well documented, stable and with all the bonus points of being almost drop-in compatible with android - which means less hassle for doing the mobile app.\r\n\r\nThoughts? I'd be more than happy to discuss more on this, since I don't want to duplicate effort :)"},"comment":{"url":"https://api.github.com/repos/conradkleinespel/rooster/issues/comments/143059760","html_url":"https://github.com/conradkleinespel/rooster/issues/3#issuecomment-143059760","issue_url":"https://api.github.com/repos/conradkleinespel/rooster/issues/3","id":143059760,"user":{"login":"conradkleinespel","id":1234006,"avatar_url":"https://avatars.githubusercontent.com/u/1234006?v=3","gravatar_id":"","url":"https://api.github.com/users/conradkleinespel","html_url":"https://github.com/conradkleinespel","followers_url":"https://api.github.com/users/conradkleinespel/followers","following_url":"https://api.github.com/users/conradkleinespel/following{/other_user}","gists_url":"https://api.github.com/users/conradkleinespel/gists{/gist_id}","starred_url":"https://api.github.com/users/conradkleinespel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/conradkleinespel/subscriptions","organizations_url":"https://api.github.com/users/conradkleinespel/orgs","repos_url":"https://api.github.com/users/conradkleinespel/repos","events_url":"https://api.github.com/users/conradkleinespel/events{/privacy}","received_events_url":"https://api.github.com/users/conradkleinespel/received_events","type":"User","site_admin":false},"created_at":"2015-09-24T21:50:02Z","updated_at":"2015-09-24T21:50:02Z","body":"Hi @qmx,\r\n\r\nThanks a lot for your comment !\r\n\r\nAs can be seen in the updated `README.md`, the `sha256` KDF will soon be replaced with something more solid like `scrypt`.\r\n\r\nOther people have suggested using `sqlite3` too. And it does sound interesting. I like that we could have access to database level constraints. We'd still need to document the schema and specify migrations if the schema changes.\r\n\r\nI plan to address these 2 issues (better KDF and file format) soon. Including a way to easily change the schema as Rooster evolves, without the need for the end user to know about that.\r\n\r\nFeel free to post a link to your project. I'd be happy to see what's in there :smiley: \r\n\r\nBest regards,\r\nConrad"}}