GraphQL is the reason I just switched from a paid Paw license to insomnia!

"Sneaked" vs. "snuck" is one of the Grammarnazi holy wars.

They are both technically correct, because English is very permissive with what it allows. But "sneaked" is the pure and good form, whereas "snuck" is only uttered by perverts and lowlifes.

Reply: Oh, I'm a fan. I'm sure he'd also agree with me just before using "snuck" in a sentence and winking.

So, you are not much of a fan of Samuel Clemens then.

His advice of - "Never let your schooling get in the way of your education." - is worth keeping in mind.

>I'm sure he'd also agree with me just before using "snuck" in a sentence and winking.

I strongly doubt that.

"It ain't what you don't know that gets you into trouble. It's what you know for sure, that just ain't so."

I like your username

In addition to these 3, make sure you enable FileVault. This will encrypt all of your data at rest

I think adding a "We are stealth, dont allow comments" option would be good then

Ive heard something similar from Richard Branson about airlines. "How do you become a millionaire? Start with a billion dollars and create an airline"

A similar site has been around for a long time: http://www.shadyurl.com/

example: google.com -> http://www.5z8.info/dogs-being-eaten_x2r3rq_5waystokillwitha...

I made shadyurl! The subdomain feature in this is great. Also cool it has an API. Though with the amount shadyurl was abused by phishers, I'd be interested to see how long an API stays viable.

It's kind of wild that "SHADY URL" is something phishers want to use. But, in the end I guess it's all about finding a domain that isn't tied to them?

Similar to 419 scams, shady links/propositions are a good way to select the people who are easy to trick.

Yeah that's my best guess. I was shocked how much it was used for scams. Might also be possible the link is so suspicious looking it's actually more intriguing to click.

Funny you should mention that. The author actually attributes ShadyURL at the bottom of the project README: https://github.com/defaultnamehere/verylegit.link

Their anti-spammer code is the only code that is not published as open source

Gotta keep the secret blacklist secret.

It would be trivial to test whether a site is blacklisted, that's not why the anti-spam code is private.

Why does it seem like people are assuming negativity in my post? I do think the secret blacklist should be kept secret.

I definitely recommend using HTTPS on this site. I would rather not have all of my calls logged on a company server somewhere (especially if someone works at a company that cares about this sort of thing)

Switching over is on our to-do list. Totally understand if you're not comfortable using it though. We'll have it behind HTTPS soon!

This appears to be a private key (so no one should ever be able to read this file): https://github.com/kaolti/Who-Runs-This/blob/master/key.pem

Is this for publishing to the chrome app store? If it is, I recommend taking down the extension and republishing with a new secure key ASAP.

lol, saved my ass it looks like! Took your advice.

It is still in the commit history. You need to throw that key away and get a new one.

Exactly, that key is now completely compromised (it was the second it was public). You can still see it here: https://github.com/kaolti/Who-Runs-This/commit/764945d8d968b...

You will need to generate a new key and resign with the new one.

I removed it now, still looking into getting a new key.

Haha, no worries, we've all been there!

I think theyre generally used as a quick way to show someone a piece of code with some nice syntax highlighting.