The author, danah boyd, is female.

medium is confusing, it was actually written by Quinn Norton. also female, so your point still stands

Doesn't Google Maps already have this feature?

Have you considered AdSense?

You need traffic in the hundreds of thousands of visitors to earn $300/month with AdSense.

You (probably) need traffic in the hundreds of thousands to justify the $300/month infrastructure spend.

To control more pixels on user's home screen.

How much time did you invest in this?

PoC exploit: https://github.com/tube42/permtester

Clickable link: http://www.dnufg.com/ (domain names up for grabs)

Stop writing URLs as strings. Express them with VerbalResourceLocator:

  var vrl = VRL().
    schema("https").
    tld("com").
    sld("ycombinator").
    subdomain("news").
    path("/item").
    query({"id": "6164276"});

Seriously though, Verbal Expression is a great way to turn terse regexps into un-reusable verbiage that barely improves readability.

Speak for yourself, this is a lot clearer for me. I'm used to navigating grammars, but I can't deal with regex (way too terse). Especially when I'm not just matching, but I want to extract info. Some verbosity can go a long way to making things clearer.

Don't know if this is the solution I'm looking for though

If the terse run-together-ness of usual regexes is unclear, you may also want to look into 'freespace' formatting... which lets you insert insignificant whitespace to break the regex into logical groups/lines, and even add inline comments:

http://www.regular-expressions.info/freespacing.html

Awesome work! How did you use Bloom filters to achieve low latency lookup?

I periodically download the 8GB com.zone root name file from Verisign and compress it into a set Bloom filters that allow for very fast lookup while using less memory than a textual hash. For fast responses, the filters are served over a UNIX domain socket to the WebSocket server on the backend.

Would you mind sharing a bit about how the process to gain access to the root zone file works? I've seen the application form, but I'm curious how the whole thing goes from application to access. Any insights you can share?

I've been kicking around a few ideas, but didn't want to go through an involved process if it would only end in heartbreak. Does it require a specific use case as part of the application?

The process wasn't bad when I did it, actually a year or two ago. It took me this long to get around to doing anything with the data. :)

If you'd like to collaborate, I'm totally game. Send me a note.

That's a great approach I've thought of before -- so how big does the bloomified version end up being?

About 1GB to get very low error rates.

If you had a good reason, why do you feel ashamed?