-
This is a numbered list.
-
I'm going to include a fenced code block as part of this bullet:
Code More Code
#!/usr/bin/env ruby | |
# | |
# Convert blogger (blogspot) posts to jekyll posts | |
# | |
# Basic Usage | |
# ----------- | |
# | |
# ./blogger_to_jekyll.rb feed_url | |
# | |
# where `feed_url` can have the following format: |
mkdir heroku | |
cd heroku/ | |
virtualenv --no-site-packages env | |
source env/bin/activate | |
pip install bottle gevent | |
pip freeze > requirements.txt | |
cat >app.py <<EOF | |
import bottle | |
import os |
pm list packages -f |
import logging | |
import logging.handlers | |
log = logging.getLogger(__name__) | |
log.setLevel(logging.DEBUG) | |
handler = logging.handlers.SysLogHandler(address = '/dev/log') | |
formatter = logging.Formatter('%(module)s.%(funcName)s: %(message)s') |
An introduction to curl
using GitHub's API.
Makes a basic GET request to the specifed URI
curl https://api.github.com/users/caspyin
import os | |
import sys | |
import traceback | |
from functools import wraps | |
from multiprocessing import Process, Queue | |
def processify(func): | |
'''Decorator to run a function as a process. | |
Be sure that every argument and the return value |
(defadvice gist-region (around su/advice/gist/gist-region/around/dirty-hack | |
a c pre) | |
"Dirty hack to prevent gist-region from choking on buffers which contain | |
`%' character" | |
(save-window-excursion | |
(let* ((delete-old-versions t) | |
(dummy "foo") | |
(beg (ad-get-arg 0)) | |
(end (ad-get-arg 1)) | |
(min-beg-end (min beg end)) |
#!/bin/bash | |
#Set colour prompt using the name, platform or instance id and avzone | |
if [ ! -f "/opt/aws/AWS-INSTID" ]; then | |
curl -s --fail http://169.254.169.254/latest/meta-data/instance-id > /opt/aws/AWS-INSTID | |
fi | |
export INSTID=`cat /opt/aws/AWS-INSTID` | |
if [ ! -f "/opt/aws/AWS-AVZONE" ]; then | |
curl -s --fail http://169.254.169.254/latest/meta-data/placement/availability-zone > /opt/aws/AWS-AVZONE |
So I was reading Hacker News and decided to read the comments in the thread about H.265 being approved. Pretty close to the top was this comment about VP9, Google's future video format. I have some words of my own about it and other future formats at the bottom of this post, but what jumped out from the comment to me was this part:
Many have already implemented VP8 (which is also slightly better than h.264 at this point)
The comparison linked to back up that statement is faulty for several reasons, such as not providing the source material used (hell, he doesn't even name the source material), exact encoding settings used (no, some random profiles are not enough), not providing the resulting encodes, only providing a