5 ms·
More like how not having a heartbeat message that confirms Twitter-based notifications are working killed the fish. And why Twitter? Seems like any of email, IM
by Zigurd 12y ago
More like how not having a heartbeat message that confirms Twitter-based notifications are working killed the fish. And why Twitter? Seems like any of email, IM, or SMS would be a better choice.
This is like not starting your emergency generators on a regular schedule and then being surprised that the fuel filter clogged.
- wpietri 12y agoThis is one of those comments that relies on hindsight to sound smart, so it's frustrating to me. The author surely can also think up a solution now that he knows Twitter can't be trusted. In fact, as he explains in the comments, he switched to SMS months ago.
- mikeash 12y agoRealizing that Twitter is not reliable is not hindsight! It is blatantly obvious! In terms of reliability, it's one step above putting a message in a bottle and tossing it in the ocean. If you didn't already know this then you're not paying attention.
- wpietri 12y agoHere I take it "blatantly obvious" is code for "thing I know" or, less charitably, "thing I can claim to know so I can sound superior, now that it's obvious in hindsight". If you want to persuade me that it's really obvious, that only a fool would make this mistake, you'd have to show me where in the Twitter developer docs they say, "Hey, this is unreliable, so don't think we're going to actually deliver your messages". And then that a reasonable person would have had to see that page, read it, and ignore it before proceeding. Half of people are below average. Everybody is ignorant about most things, and they're always learning. I have no reason to think that this guy didn't make a reasonable novice mistake. I'd rather encourage novices to try things. Telling them after the fact, "Fool, you should have known!" only discourages them and other novices. Personally, I appreciate him producing an interesting article that will help other novices avoid his mistake.
- mikeash 12y agoTwitter's terms of service are located here: https://twitter.com/tos https://twitter.com/tos Two choice bits: "We may suspend or terminate your accounts or cease providing you with all or part of the Services at any time for any reason...." "The Twitter Entities make no warranty and disclaim all responsibility and liability for: (i) the completeness, accuracy, availability, timeliness, security or reliability of the Services or any Content...." Emphasis added. Now I guess you'll say that a reasonable person won't read the TOS anyway so it doesn't count. And I say, that's all well and good when you're tweeting about last night's dinner, but when you're building something where you actually care about the consequences when it fails, you have to actually perform some form of research if you want reliability. I'm rather astonished that you're still acting like Twitter's unreliability is not only non-obvious, but something I wasn't aware of until I read this post, but am pretending that I knew before so I could act superior. Do you just assume that every random internet service out there is reliable until proven otherwise? Because that's the opposite of what's correct. Everything is completely unreliable until proven otherwise. This is, yes, obvious if you've been paying attention to the internet for any reasonable length of time. Twitter hasn't proven otherwise, therefore it is unreliable. I personally think that more than passes the threshold for "blatantly obvious". I disagree with you on the impact of pointing out that this was a bad decision. The fact that you can't rely on random internet services is an important lesson, and I don't think he learned that lesson. He just switched from one random unreliable internet service to another. When Zapier or Xively go down or change authentication requirements or decide he's a spammer and shut down his account, does he have some way to find out? I would much rather have someone tell me "that was pretty stupid of you, this was your real mistake here" than hide the truth from me because they're afraid of discouraging me. I want to be wrong for as little time as possible. Apparently this is an unusual sentiment, which I have a hard time coming to terms with.
- bryanh 12y agoThough I can't really comment on the discussion as a whole, I can say with good authority that if Zapier zaps fail (for any reason), we will try to send out alert emails to the best of our ability!
- 12y ago
- Zigurd 12y agoRereading it it does sound a bit unfair in tone, but it is not wisdom in hindsight to think of a heartbeat that provides affirmative notification that notifications are working, especially in a system that's got a lot of other data acquisition that could be provided on a heartbeat. He shouldn't blindly trust that SMS will work for for his application, using his setup, either. What if he forgets to top up the account for the device sending out SMS? That would not be the fault of the SMS system.