- python 2.7 (or 2.6 may suffice)
- scrapy 0.16.3 +dependencies
- pyquery
Aims
| # -*- coding: utf-8 -*- | |
| # phases = %w{🌑 🌒 🌓 🌔 🌕 🌖 🌗 🌘} | |
| phases = (0x1F311..0x1F318).to_a.collect{|c| [c].pack('U*')} | |
| clear_line = "\r\e[0K" | |
| 1000.times do |i| | |
| phase = phases[i % phases.size] | |
| print "#{clear_line} #{phase}\t#{i} #{phase.unpack('U*').map{ |i| "\\u" + i.to_s(16).rjust(4, '0') }.join}" | |
| sleep rand / 10.0 |
Do your part to resist Government surveillance and take back your privacy:
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
| #!/usr/bin/env perl | |
| use 5.010; | |
| use open qw(:locale); | |
| use strict; | |
| use utf8; | |
| use warnings qw(all); | |
| use Mojo::UserAgent; | |
| # FIFO queue |
| // ==UserScript== | |
| // @name Userscript Name | |
| // @namespace http://example.com/ | |
| // @description Userscript Description | |
| // @match http://example.com/* (or @include * to include all pages) | |
| // @version 1.0 | |
| // ==/UserScript== | |
| // Emulate Greasemonkey's unsafeWindow in Chrome | |
| window.unsafeWindow = window.unsafeWindow || (function() { |
In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)
| # source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list | |
| # A list of available STUN server. | |
| stun.l.google.com:19302 | |
| stun1.l.google.com:19302 | |
| stun2.l.google.com:19302 | |
| stun3.l.google.com:19302 | |
| stun4.l.google.com:19302 | |
| stun01.sipphone.com | |
| stun.ekiga.net |