View suicidal-filter.php
<?php
/*
Use this just like `add_filter()`, and then run something that calls the filter (like
`new WP_Query`, maybe).
That's it. If the filter gets called again, your callback will not be.
This works around the common "filter sandwich" pattern where you have to remember to
call `remove_filter` again after your call.
View wp-update-plugins-git.sh
#!/bin/bash
PLUGINS=$(wp plugin list --update=available --field=name | tr -d '\r');
wp plugin update-all;
for plugin in $PLUGINS; do
git add -A "wp-content/plugins/$plugin";
git commit -m "Update plugin: $plugin";
done;
View iMessage.sql
SELECT COUNT(*) as messages_count, handle.id as person from message JOIN handle on handle.ROWID = message.handle_id WHERE strftime( '%Y-%m', datetime(message.date + strftime('%s','2001-01-01'), 'unixepoch')) = '2016-01' GROUP BY handle_id ORDER BY messages_count DESC;
View aaa.nginxconf
location ~* \.(jpe?g|gif|png)$ {
try_files $uri @photon;
}
location @photon {
rewrite ^(.*)-([0-9]+)x([0-9]+)\.(jpe?g|gif|png)$ http://i0.wp.com/$host$1.$4?resize=$2,$3;
rewrite . http://i0.wp.com/$host$request_uri;
}
View 0_reuse_code.js
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console
View gist:1d1c5f7e0ff502928e89
<?php
add_action( 'parse_query', 'gws_exclude_from_search' );
function gws_exclude_from_search( $q ) {
$exclude_from_search = array( 'gallery-entries' );
if ( $q->is_search ) {
foreach ( $exclude_from_search as $post_type ) {
$post_type_object = get_post_type_object( $post_type );
$post_type_object->exclude_from_search = true;
View gist:dd3e5cf2bcadd888284e
<h1 id="updatesinyourface">Updates in your Face</h1>
<h2 id="farfuture">Far Future</h2>
<ul>
<li>Make updates as smooth and magical and graceful as possible</li>
<li>Continuous releases</li>
<li>Move from shrinkwrap to more agile, continuous development</li>
<li>Perhaps a direction, not a goal</li>
<li>People hate change, and they hate change they didn’t opt in to</li>
<li>Language pack Plugins, Core, Themes, in that order?</li>
</ul>
View nginx.conf
upstream phpfpm {
server unix:/var/run/php5-fpm.sock;
}
upstream hhvm {
server unix:/var/run/hhvm/hhvm.sock;
}
# SSL
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
View keybase.md

Keybase proof

I hereby claim:

  • I am markjaquith on github.
  • I am markjaquith (https://keybase.io/markjaquith) on keybase.
  • I have a public key whose fingerprint is 6537 F2DF 3921 E11E 46C5 D6B7 56AD 3A85 0F62 922E

To claim this, I am signing this object:

View nginx.erb
server {
listen 80;
<% if @use_ssl %>
listen 443 ssl spdy;
ssl_certificate ssl/<%= @domain %>/server.crt;
ssl_certificate_key ssl/<%= @domain %>/server.key;
<% end %>
server_name <%= @domain %><% if @also_www %> www.<%= @domain %><% end %>;
access_log /var/log/nginx/access.log main;