Hacker News Reader

You can block their updates if you like (by editing your HOSTS file I imagine), but then you'd be running out-of-date software.

I don't think that you can blame Chrome's updates for breaking that extension. It's much more likely that the extension is broken.

In this case it was our (Chrome team's) fault. We broke an API, which we try to never do. The bug is: http://crbug.com/47726. I actually thought this had already been rolled to stable, but it hasn't yet. I will check if we can get it done more quickly.

Are you referring to this one?

https://chrome.google.com/extensions/detail/gbammbheopgpmaag...

It looks like it was updated yesterday with a bug fix.

Are you using the dev channel?

I've never had an extension killed by an update and I run several, so I'm guessing it's that extension's fault.