One of the many pleasures of being a developer is that we're able to solve problems–no matter how obscure–through code. We can automate day-to-day tasks that might drive others mad. Our solutions may range from something as small as a bash script, to as elaborate as an entire application. I think nearly every developer is guilty of automation. One common task in this category of coding is screen scraping–the act of obtaining data from the web by parsing raw data, typically markup. Follow along as we build the skeleton for a simple screen scrape CLI in Go capable of notifying you whenever new content appears on your favorite web comics.

Authentication as we know it leaves a lot to be desired on the web. We've come to rely on our browsers and third party applications to manage our ever mounting collection of identities. Standards such as OAuth help us consolidate these credentials–but in many ways they serve more as a form of misdirection. Do you really understand the implications of the permissions you're granting when walking the painful OAuth dance? Are you sharing too much? Very few authentication options leave you with that warm and tingly sense of security. However, there's been some intriguing projects recently that aim to do away with the authentication headache–or at least the password portion of it. In this post we'll explore how to implement a passwordless authentication flow using Go to make your next web project's authentication process slightly less unpleasant for everyone.