This article doesn't seem to contain any surprising information - yes, if you build a product on an API that's not under your control you should make sure you're always up-to-date with information about that API.<p>What I don't understand is why one would use yet another service (ways 3-5 in the article) to be notified about API changes. It basically means you're now relying on an API that might be changed at any point in time (it probably won't be without prior notification) without you having any say in it AND you now also rely on another service (that does not make a guarantee about a timely manner of notifying you) to get information about said API changes.