- Freebase: http://www.freebase.com/query
- DBPedia: http://dbpedia.org/snorql
- Scroll for dbpedia examples: https://wiki.base22.com/display/btg/SPARQL+Query+Examples
- Factforge: http://factforge.net/sparql
#! /bin/bash | |
BLOG_DIR=/where/is/your/jekyll/blog | |
ASSETS_DIR=$BLOG_DIR/subpath/for/your/assets/like/images/or/whatever | |
function join { local IFS="$1"; shift; echo "$*"; } | |
MAKE_TITULAR_DIR=false | |
if [ $# -eq 0 ] | |
then | |
TITLE="new_post" |
by Timm Murray
This is a compilation of the "Perl Encryption Primer" series of articles by Timm Murray, as published on http://www.wumpus-cave.net/category/encryption/. I have taken the liberty of moving the content here (as is), formatting it as Markdown and ordering them chronologically from top to bottom to easen the reading experience. Enjoy!
Timm also made a one-hour video of the presentation he gave at MadMongers, which summarizes the content below.
Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution
I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)
#!/usr/bin/env perl | |
# | |
# http://daringfireball.net/2007/03/javascript_bookmarklet_builder | |
use strict; | |
use warnings; | |
use URI::Escape qw(uri_escape_utf8); | |
use open IO => ":utf8", # UTF8 by default | |
":std"; # Apply to STDIN/STDOUT/STDERR |
# html5 pushstate (history) support: | |
<ifModule mod_rewrite.c> | |
RewriteEngine On | |
RewriteCond %{REQUEST_FILENAME} !-f | |
RewriteCond %{REQUEST_FILENAME} !-d | |
RewriteCond %{REQUEST_URI} !index | |
RewriteRule (.*) index.html [L,QSA] | |
</ifModule> |
# Change YOUR_TOKEN to your prerender token | |
# Change http://example.com (at the end of the last RewriteRule) to your website url | |
<IfModule mod_headers.c> | |
RequestHeader set X-Prerender-Token "YOUR_TOKEN" | |
</IfModule> | |
<IfModule mod_rewrite.c> | |
RewriteEngine On |
We're doing a small year-end news nerd countdown on Source. Lists are too much, so please send us ONE THING—an app, a tool, an article, a tweet, an image, a map, or something else entirely—that you loved this year. Might be something that made your job easier or made you smarter, or it might have more obscure relevance. All we ask is that you can link to it.
Don't think too hard about it, just take 30 seconds and send one in now to source@mozillafoundation.org. We'll be posting an assembly of favorite things and all we can say about it right now is that there will be GIFs.
Wooo.
by Gavin Lazar Suntop @gvn
I love clean code. There, I said it. I pride myself on passing strict linting standards and keeping my code easy to read. It's not just a personal proclivity, but a choice I hope benefits other developers.
My general experience with teams has been that code style is something people care about and have strong personal preferences. Typically, at some point people get tired of dealing with inconsistency and a standardization meeting is called. This is, of course, an important discussion to have. The problem that tends to occur is either lack of documentation or lack of enforcement of the agreed upon style. Additionally, new team members or contributors may not have access to a clear set of rules.
#!/usr/bin/perl | |
use Mysql; | |
use strict; | |
use vars qw($school_name); | |
use vars qw($pass); | |
require "./cgi-lib.pl"; |