| #!/usr/bin/env python | |
| """ | |
| Check that a particular email address exists. | |
| Adam Blinkinsop <[email protected]> | |
| WARNING: | |
| Checking email addresses in this way is not recommended, and will lead to | |
| your site being listed in RBLs as a source of abusive traffic. Mail server | |
| admins do like it when they get connections that don't result in email being | |
| sent, because spammers often use this technique to verify email addresses. |
| /* | |
| I've wrapped Makoto Matsumoto and Takuji Nishimura's code in a namespace | |
| so it's better encapsulated. Now you can have multiple random number generators | |
| and they won't stomp all over eachother's state. | |
| If you want to use this as a substitute for Math.random(), use the random() | |
| method like so: | |
| var m = new MersenneTwister(); |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| // ==UserScript== | |
| // @name Convert_iframe_to_link | |
| // @namespace https://gist.github.com/ihsoy-s/ | |
| // @version 0.2.3 | |
| // @description Remove iframe tag and create link | |
| // @include http://*/* | |
| // @include https://*/* | |
| // @match http://*/* | |
| // @match https://*/* | |
| // @run-at document-end |
| import imaplib, serial, struct, time | |
| class Mail(): | |
| def __init__(self): | |
| self.user= 'USER' | |
| self.password= 'PASS' | |
| self.ser = serial.Serial('/dev/tty.usbmodem621', 9600) | |
| self.M = imaplib.IMAP4_SSL('imap.gmail.com', '993') | |
| self.M.login(self.user, self.password) | |
| 0-mail.com | |
| 0815.ru | |
| 0clickemail.com | |
| 0wnd.net | |
| 0wnd.org | |
| 10minutemail.com | |
| 20minutemail.com | |
| 2prong.com | |
| 30minutemail.com | |
| 3d-painting.com |
| var FormRepo = function (namespace) { | |
| /// <summary>Persistent form values, saves to localStorage</summary> | |
| /// <param name="namespace" type="String">the namespace to store values in localStorage</param> | |
| // should also protect per page, since we could have the same forms in various places | |
| this.N = namespace + '.' + window.location.pathname; | |
| }; | |
| $.extend(FormRepo.prototype, { | |
| namespace: function (key) { | |
| return this.N + '.' + key; |
#The Shadow DOM Diaries
Feature design is hard, and takes time. With time, it doesn't matter how public and consistent you are with communication during design process. In the end, it all will look like a jumbled mess of emails and bug comments. That seems bad. To make things less bad, I decided to start writing these little docs. Here they are. I may add more. Or not. Whatevs.
Sometimes You Need to Build a Larger Thing First looks back at the road we've traveled.
Shadow DOM Evolution outlines the path forward.
Why Do We Only Allow Children in Insertion Points provides a glimpse into the reasoning behind current insertion point design.
#Composition is the Goal
I see several discussions now that vacillate around on encapsulation qualities of Shadow DOM and the flavors thereof. It's all my fault. I stuck encapsulation into the problem statement of the spec. I even glued the somewhat irrelevant term functional encapsulation on top of it. What a dork.
It was a couple of years ago, when one of my colleagues read the spec and noted: "Dude, it's like your story and whatever, but the way you tell it, Shadow DOM is not about encapsulation. It's about composition". The world went blank around me. I was blinded by insight.
My hipster colleague was right, of course. Encapsulation is just a tool. Composition is the goal.
This is why the people who'd never used Shadow DOM in real life get really hung up on the details of encapsulation, while those who actually use Shadow DOM stare at them quizzically.
| #!/usr/bin/python | |
| # Connects to servers vulnerable to CVE-2014-0160 and looks for cookies, specifically user sessions. | |
| # Michael Davis ([email protected]) | |
| # Based almost entirely on the quick and dirty demonstration of CVE-2014-0160 by Jared Stafford ([email protected]) | |
| # The author disclaims copyright to this source code. | |
| import select |