If you write software for the web that allows users to submit or share URLs (comment systems, mail clients, forums, URL shorteners, etc), you may find yourself in a position where you need to filter out malicious links.
When I talk about risk as it relates to web applications, people usually assume I’m talking about hardening applications from hackers, spammers and other ne’er-do-wells. While malicious attacks are absolutely a non-trivial part of risk management, there’s a lot more to it that’s just as important.
This is the first of what I hope will be a recurring feature. Once a week, I will write a blog post that covers things I’ve learned and links I’ve found. Hopefully it doesn’t suck, and hopefully I can keep up with it.
I am not going to turn this into a rant. I have a lot of strong opinions on the Women in Tech issue, but I’m keeping the scope of this limited to the fact that GitHub now offers a free private repo to women.
My company is in the awkward phase of small-transitioning-to-medium-sized. This means we’re small enough to not need (or want to spend money on) huge enterprise-class systems, but big enough to need to automate some stuff.
I’m a big fan of GitHub (and was a fan of Sourceforge back when it was what all the cool kids were using), but there’s one limitation that I’ve run into a few times that can be very frustrating, and that’s the inability to share deploy keys across multiple repos.