I like what the go authors think about dependencies being backwards compatible, but not everyone thinks that way, and let's face it, people make mistakes and make incompatible changes unintentionally.
I started a project last weekend (still a WIP), go get version[1], that basically proxies the `go get` commands, but fools it into thinking the master branch is either a tag or a version to get around some of these problems, while aiming to still work with the go tool.
For example, if you have a tag named v1.0.3, you would change your import path to be something like this:
gogetver.com/github.com/user/project.v1.0.3
There's also gopkg.in[2] which does something similar, although it appears to only work with github.
I run into this a lot using a "+" in my Gmail address. I like to use "username+site_name@gmail.com" for easy filtering, but there are still quite a large number of sites that do not accept this as valid, and it is extremely annoying.
Years ago, I must have signed up or given my email address to Urban Outfitters with a +uo. They happily continue to send me emails, but their unsubscribe form does not accept it as a valid address! I've tried reporting the bug, but now just send the messages straight to spam.
I've been waiting for "Up Next" Since I migrated from Winamp - Being able to play a song, and then realize "I know what would go PERFECTLY after this", is very useful.
Or listening to music, selecting a much of tracks, and throwing them in the queue, without the hassle of creating a playlist ahead of time.
Hopefully more services start adding multi-factor authentication. So far, I have my Google Account, Dropbox, and now CloudFlare.
Hearing that Authy will soon support Google Authenticator tokens is great news! I have never encountered the "out of sync" problem with Google Authenticator described in the article, but the Authy app does feel more native on my iPhone.
What if the problem only affects a subset of users? Then wouldn't any application errors for unaffected users (e.g. a typo in code) say it is Heroku's fault when it really isn't?
I started a project last weekend (still a WIP), go get version[1], that basically proxies the `go get` commands, but fools it into thinking the master branch is either a tag or a version to get around some of these problems, while aiming to still work with the go tool.
For example, if you have a tag named v1.0.3, you would change your import path to be something like this:
gogetver.com/github.com/user/project.v1.0.3
There's also gopkg.in[2] which does something similar, although it appears to only work with github.
[1]: https://github.com/rsenk330/gogetver [2]: http://labix.org/gopkg.in