"military-grade AES encryption"<p>Can we please, as an industry, agree to stop using bogus terminology like this?<p>"Even the NSA won't be able to read your dirty secrets"<p>And can we stop using ~"Our encryption beats the NSA" as a selling point, given that:<p>1. It doesn't take into consideration the various side-channel attacks the NSA would actually use<p>2. It's unlikely to be true even discounting side-channel attacks<p>3. It's a scare tactic at best, akin selling boats that are rated "kraken-proof".
I keep a coding journal of all those unsettled questions and thoughts that pop in my mind. The questions I ask myself, the things I could improve,... It turns out to be highly valuable in my projects and I recommend anyone to try it.<p>I started a comment but it became gargantuan so I turned it into a blog post : <a href="http://tburette.github.io/blog/2014/06/25/the-power-of-keeping-a-coding-journal/" rel="nofollow">http://tburette.github.io/blog/2014/06/25/the-power-of-keepi...</a>
Nice util. Just a suggestion for the encryption: You should consider using a password-based key derivation function (PBKDF) rather than just hashing the key once with SHA256. This could help deter brute-force attacks particularly if the chosen hashing function is computationally intensive; e.g. scrypt
I've been using vim and text files. If you want to create a journal entry for today: $ vim $(date +%a_%d_%m_%Y.txt)
type your text and you are set.<p>If you want to search/sort/filter, etc your journal files, Unix has already all the tools you want. (grep, find, less, cat, sed, etc).<p>Don't sweat the small stuff.
I almost really like this tool. It's close to being seamless and Unixy, offering a pretty small command-line-option-language that expresses a bunch of journal-related commands. I like that idea, a lot. But the recipes dive right into piping text through wc and grep, so I wonder: what exactly does this offer over some bash functions and raw textfiles? I've already got cat, grep, find, tail, xargs et al.<p>More nitpicking: the * escaping bothers me. That's a core feature, using the * to mark things, but you have to avoid letting bash expand it. Are there any better characters? Does 'single quoting' help anything?<p>The fuzzy date parsing looks great. (: I also think the no-dash (new entry) vs dash (filters..) vs double-dash (action) convention is fairly neat as far as calling conventions go. Tagging things with @ seems like a useful convention, too, even if I end up using notepad.
I'm a big fan of self-analytics. I also like small-but-useful command-line tools of this nature. This is pleasantly documented and purpose-driven.<p>If you're looking for something more focused on short daily summaries of what you've done, I wrote a similar tool called wj:<p><a href="http://tylerneylon.com/a/wj/" rel="nofollow">http://tylerneylon.com/a/wj/</a><p>It's more about organization and presentation than privacy. For example, it can generate a tex file that converts your entries into a nicely formatted pdf file.<p>I also like the automated self-analytics Stephen Wolfram uses:<p><a href="http://blog.stephenwolfram.com/2012/03/the-personal-analytics-of-my-life/" rel="nofollow">http://blog.stephenwolfram.com/2012/03/the-personal-analytic...</a>
I've been tracking various git actions (commits and branch creates and checkouts) in a file via git hooks for the past year or so and it's been super valuable to go back and look at, especially to remind myself what I was doing yesterday for standup meetings.<p>This is far and away a better solution, since I can have `jrnl` auto-tag those things and filter them in/out when I want to look at regular journal entries.
Consistently journaling has been my most valuable habit over the past 5 years.<p>It's the only way to relive thoughts I'll never have again because I become jaded. It's also a great way to grasp just how much of everything I forget. I wonder if I'd even have any personal stories to tell from the time I studied in Prague if I hadn't written so much of it down while enamored by it all.
I use vimwiki diary mode, and a cronjob that pops up a vim window (with pre-populated timestamp) every 30 minutes.
Been doing that for over 18 months now.<p>Original article where I got this idea : <a href="http://www.stochasticgeometry.ie/2012/11/23/vimwiki/" rel="nofollow">http://www.stochasticgeometry.ie/2012/11/23/vimwiki/</a>
Looks great! though I'd have loved it even more if there were binaries available. I just like having all my favorite applications in one portable folder. I'm guessing using something like py2exe to create one won't be hard.<p>Also, what are the chances that the jrnl[encrypted] package will work on Windows? (without using Cygwin?)
This sounds great. I use Day One for my personal diary and org-mode for work stuff. This setup was quite good but now it is much better because, if it works as promised, Jrnl will allow me to add personal entries in Day One from the linux computer I use at work. Thanks! :-)
I just tested this with zimwiki, works perfectly, as it's all plain text files.
<a href="http://zim-wiki.org/" rel="nofollow">http://zim-wiki.org/</a>
I didn't try it with encryption as zim wouldn't understand it.
Very cool! I built a command line tool to solve a similar problem a few years ago: <a href="https://github.com/christiangenco/t_time_tracker" rel="nofollow">https://github.com/christiangenco/t_time_tracker</a>
I've been using <a href="http://www.geeknote.me/" rel="nofollow">http://www.geeknote.me/</a> for a while now. Jrnl looks interesting, I'll have to try it out and see how it compares.
Fantastic! I made a quick and dirty BASH solution two years ago and I've been meaning to rewrite it in python ever since. It's uncanny how similar this design is to what I was planning, though.
This tool writes journal entries to a local file and you have to read them back via this tool, am I right?<p>Can it play with an external service, e.g. can my journal be public via Tumblr or some static site generator?