spatten's comments

Ansible has a nice workaround for this that might partially solve the problem and be less work than migrating away from GitHub. When you submit a ticket it forces you to fill in some required fields. Here's an example of a filled in issue:

https://github.com/ansible/ansible/issues/6112

They have more info here: https://github.com/ansible/ansible/blob/devel/CONTRIBUTING.m...

From what I can see, it's not available for OS X at all. According to Wikipedia[1], it is currently available for PC and PS4 and will be released for iOS "at a later date"

https://en.wikipedia.org/wiki/The_Witness_(2016_video_game)

I used org-mode for about a year, but then switched to Vim and none of the vim org-mode plugins looked great.

So I thought about what I used it for, and realized it was mostly cycling items between TODO and DONE with a keystroke and text folding.

So I forked vim-markdown and added syntax highlighting for TODO and DONE on header lines, and a mapping to cycle between TODO and DONE. Been using it for a couple of months now and I'm reasonably happy.

If you want to give it a shot, code is here: https://github.com/spatten/vim-markdown

Cool, didn't know about that. Does it search multiple files in a directory? I use it for work logs and keep one file per week.

I have a bunch of org-mode files that I save into a Dropbox folder.

That gives me backups, and access from other computers / laptops.

Search is via ack or grep.

It theoretically also gives me access from my phone using MobileOrg[1], but I have never actually set that up.

[1]: http://orgmode.org/manual/MobileOrg.html

If you both review, then the reviews show up immediately. If only one of you reviews, then the review shows up after a waiting period (I think it's ~2 weeks). So presumably the negative review will show up soon.

Amazon publishes a command-line tool called Kindlegen[1] that converts epub => mobi pretty seamlessly.

[1]: http://www.amazon.com/gp/feature.html?docId=1000765211

Ahh, good point. That makes more sense.

> ...it has been downloaded more than 500 million times and used to identify some 30 million songs ...

That doesn't sound right. On average one identification for every 16 downloads? I'm guessing that second million should be a billion.

Maybe I'm just rationalizing it because I want to think of myself as a calm, non-ragey person, but to me it feels like something else.

I agree with others that it feels rude when someone else takes up the whole sidewalk.

But it's also that I walk a lot, and use it as a form of transportation. I go twice as fast as a lot of people on the sidewalk, and it seems like if people just sped up a bit they'd find walking more useful, which would make them drive less, which is a good thing, and it drives me crazy that this isn't obvious to them.

Like I said, I'm probably just rationalizing :)

If you're using AWS Elastic Load Balancer, then the quick fix is:

1) Select the load balancer you want to edit 2) Click the "Listeners" tab 3) Click "change" under the "Cipher" column for the HTTPS row 4) Select the most recent pre-defined security policy, from 2015-02.

This should get you an A on SSL Lab's test[1]

https://www.ssllabs.com/ssltest/

I'm confused by the caption under the photo (and I live in Vancouver, right next door to Victoria):

> Victoria MP Murray Rankin: "I heard 10 gunshots at least and huddled with colleagues under a desk."

It feels like a mistake. Anyone know what this refers to?

I did a bit more reading, and found this crazy and scary graph. It's under "Uranium-232 Series Activity" near the bottom of this paper[1]. It shows that gamma ray output from U-238 increases > 5x a year after U-238 is first refined, and stays higher than originally was for >100 years.

It's due to the decay products of U-238 (and their decay products) all producing radiation that adds up to more than the original's.

I never would have guessed that.

[1]: http://www.wise-uranium.org/rup.html

So it's now almost 30 years after Chernobyl, so if I read this naively:

> When this photo was taken, 10 years after the disaster, the Elephant’s Foot was only emitting one-tenth of the radiation it once had.

the Elephant's foot will currently have 1/1000th of the original radioactivity it had right after the disaster, and 10 years from now it will be down to 1/10,000th. At that rate it would be indistinguishable from background radiation within a century or so (just guesstimating here, but that's a lot of powers of 10 -- I'm probably being pessimistic).

I'm guessing that this is wrong, though, and that the radioactivity from longer half-life radionuclides will eventually start to dominate and the "effective half-life" will be much longer.

Does anyone have any idea how long it will be until Chernobyl blends into the background radiation?

We (mostly my cofounder at Leanpub, Peter, but I've done it once or twice) do the same thing when talking about "the rise of serial fiction via fanfiction" to a publishing audience.

We show them the "books" page of fanfiction.net[1] and then note that the numbers there are the number of stories written in each book's universe, not the number of readers or views or anything like that. Go look if you haven't seen it, it's amazing.

[1]: https://www.fanfiction.net/book/

True, and cool (I hadn't heard of zero-crossing before, thanks!) but an FFT gives you the ability to do interesting things like chord recognition.

I may have to play around with the code here and see if I can get it to pick out multiple notes being played simultaneously, and maybe get it to measure how fast I can do chord changes (like Justin Sandercoe's "1 minute changes" practice method[1]).

[1]: http://justinguitar.com/en/BC-115-1MinuteChanges.php

Interesting. My take on it is slightly different: it feels like a necessary condition of economic progress is that you trust that you will get to keep the fruits of your labours.

The way this happened in our history (I'm assuming that it's not the only way) is through institutions like The Old Bailey and the codification of laws and the visibility into the not always completely fair, but always getting fairer, application of those laws that they provided.

If you're interested in the main thesis of this article -- that the reason that our attitudes to violence declined steadily was due to a feedback loop "feeding the output of the Old Bailey the day before to the input of the Old Bailey the day after.", I highly recommend "The Better Angels of our Nature" by Steven Pinker.

The end of physics has been predicted many times. I remember reading an article in Sci Am about the end of physics a few months before starting my physics undergrad in the late 80s.

The exciting thing is that it has often been followed by huge breakthroughs -- if I remember correctly, the last time it was widely believed that we had it all figured out was at the turn of the 20th century, just before Quantum Physics and General Relativity were discovered.

I'm still patiently waiting for string theory to die and us to start working on something that we can actually do experiments on.

No, it definitely doesn't do that. I use the `limit_posts` option when I'm writing a single blog post, and then have a "rake deploy" task that re-generates the site fully (without the `limit_posts` option) before rsyncing it up to the server.

I guess I should put the full Rakefile up on that post. Here are the relevant parts:

    desc "generate and deploy"
    task :deploy => ['jekyll:generate', 'deploy:deploy']
    
    namespace :deploy do 
      task :deploy do
        `rsync -r _site/ #{USER}@#{HOST}:#{DEPLOY_DIR}/`
      end
    end
    
    namespace :jekyll do
      desc "start the jekyll server in auto mode"
      task :server, :num_posts do |t, args|
        num_posts = args[:num_posts]
        cmd = "jekyll --auto --server --pygments"
        cmd += " --limit_posts #{num_posts}" if num_posts
        puts "running #{cmd}"
        exec(cmd)
      end
    
      desc "generate the site one time"
      task :generate => :clean do
        `jekyll --no-auto --pygments`
      end
    
      desc "remove the generated site"
      task :clean do
        `rm -rf _site`
      end
    end