| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
| // ---------------------------------------------------------- | |
| // A short snippet for detecting versions of IE in JavaScript | |
| // without resorting to user-agent sniffing | |
| // ---------------------------------------------------------- | |
| // If you're not in IE (or IE version is less than 5) then: | |
| // ie === undefined | |
| // If you're in IE (>=5) then you can determine which version: | |
| // ie === 7; // IE7 | |
| // Thus, to detect IE: | |
| // if (ie) {} |
| tell application "iTerm" | |
| activate | |
| set t to (make new terminal) | |
| tell t | |
| tell (make new session at the end of sessions) | |
| exec command "tail -f /Applications/MAMP/logs/php_error.log" | |
| end tell | |
| end tell | |
| end tell |
| WordPress is actually one of the most secure pieces of software available. It powers 17% | |
| of the 1,000,000 most visited websites, so it is being constantly tested both internally | |
| and by hackers. When an issue is discovered, an update is released which you can install | |
| with one click in the dashboard. | |
| The vast majority of hacked WordPress websites are running an out-of-date version of | |
| WordPress. Once WordPress is updated, any vulnerabilities that are patched are now publicly | |
| known, so old versions are vulnerable. | |
| The next most likely source of hacking is your host. If your server isn't secure, it doesn't |
This gist assumes:
| #!/usr/bin/env ruby | |
| # 1. export your RIL bookmarks | |
| # 2. save this file to the same directory where your ril_export.html is | |
| # 3. change username and password in the script bellow | |
| # 4. run 'ruby ril_to_instapaper.rb' in terminal | |
| require "cgi" | |
| require "net/http" | |
| require "net/https" |