RobSpectre

11 ms·

1. 61.▲
   by RobSpectre 13y ago

   Another stellar example of the promise of this community. Very proud of this group.
2. 62.▲
   by RobSpectre 13y ago

   Ngrok is one of the best tools in my belt for debugging webhooks at Twilio. Secure, fast, reliable and - above all - useful. Stoked for the new features Alan - thanks!
3. 63.▲
   by RobSpectre 13y ago

   Oh biscuits.
4. 64.▲
   by RobSpectre 13y ago

   Thanks for that feedback - we wanted to get Picture Messaging out of the door as soon as we had it before attacking the wealth of other features MMS has to offer. Really hope you enjoy it and check in often as we support more stuff.
5. 65.▲
   by RobSpectre 13y ago

   Truthfully, my personal track record for predicting protocol success isn't particularly good. There is an old essay on gopher's "resurrection" that I really hope no one is able to find anymore. All I know is that a whol
6. 66.▲
   by RobSpectre 13y ago

   Fully heard and appreciated. Obviously, the storage of this media does have real cost, but feedback on the pricepoint is helpful. Thank you.
7. 67.▲
   by RobSpectre 13y ago

   We wanted very badly to get this to you as well - it'll be released as soon as we can.
8. 68.▲
   by RobSpectre 13y ago

   I definitely hear you. We want it as badly as you do - can't wait to get them in your hands.
9. 69.▲
   by RobSpectre 13y ago

   btw - Thanks! We worked really hard on it.
10. 70.▲
    by RobSpectre 13y ago

    We are working very hard to bring this service to US phone numbers - we want it as badly as you. For now, we have it on US short codes and Canadian phone numbers.
11. 71.▲
    by RobSpectre 13y ago

    Hanging out on the floor at Twiliocon, Josh - you should come! Great questions - as you can imagine there's not a whole lot I can share about the relationships with our carrier partners. Working with them was essential to bringing th
12. 72.▲
    Envelopes - Python email for humans(tomekwojcik.github.io)

    119 points by RobSpectre 13y ago|34 comments
13. 73.▲
    Tech Writing Handbook(dozuki.com)

    4 points by RobSpectre 13y ago|0 comments
14. 74.▲
    by RobSpectre 13y ago

    Totally agree. Need to clear up a developing misconception - Redis does not serve as the primary store for the account balance of Twilio's customers. The billing system uses a double bookkeeping model common to many high volume desi
15. 75.▲
    An open source song I'd like the NSA to hear(nospoilersallowed.com)

    29 points by RobSpectre 13y ago|6 comments
16. 76.▲
    by RobSpectre 13y ago

    I'm not sure I know anyone who has tried such a topology with Redis. Would be interested to see how it affects writes as well.
17. 77.▲
    by RobSpectre 13y ago

    I'm not sure there is a "downside" to be had - it is an important requirement to every billing solution of any scale at all. The term is borrowed from accounting ( http://en.wikipedia.org/wiki/Double-entr
18. 78.▲
    by RobSpectre 13y ago

    An incident like this is pretty painful for every customer affected. Hope they feel this explanation, the prompt refund of the erroneous charges and credit represents to them it is a pain we very much share.
19. 79.▲
    by RobSpectre 13y ago

    Truthfully the billing system is one of the most fascinating parts of our stack to me. Twilio's utility pricing model generates an incredible volume of minute transactions, which is a fascinating engineering problem to solve at scale.
20. 80.▲
    by RobSpectre 13y ago

    Very true - in this business, it nearly always is a waterfall of small errors that produces large consequences. Part of why I love being a software person - the devil lies literally in the details.
21. 81.▲
    by RobSpectre 13y ago

    Agree completely. Ultimately the responsibility for getting this right is on us. We feel a thorough, dispassionate accounting of the human and technical errors when we come up short is part of living up to that responsibility.
22. 82.▲
    by RobSpectre 13y ago

    It is indeed. Proper procedure would be to pivot to a slave. We have reconfigured all our Redis hosts to prohibit a restart on masters to prevent exactly that temptation.
23. 83.▲
    by RobSpectre 13y ago

    I could have explained this better. Many usage events on the Twilio API generate a billing transaction (e.g. call, SMS message, phone number purchase, etc). When the transaction attempted to apply against a balance of zero and the custom
24. 84.▲
    Billing Incident Post-Mortem: Breakdown, Analysis and Root Cause(twilio.com)

    77 points by RobSpectre 13y ago|31 comments
25. 85.▲
    by RobSpectre 13y ago

    Truthfully? Our PR guy is on his honeymoon. Not kidding. Glad to hear you got the information you needed when you needed it - still a lot of work to do to resolve this to our customers' complete satisfaction. We'll get it done.
26. 86.▲
    by RobSpectre 13y ago

    Think it is the least we could do.
27. 87.▲
    by RobSpectre 13y ago

    Appreciate the feedback. Will get it fixed.
28. 88.▲
    by RobSpectre 13y ago

    Good feedback. Thank you.
29. 89.▲
    by RobSpectre 13y ago

    Very glad you found the stashboard useful during the incident. This is actually one of my favorite open source projects of ours. If you would like a similar service for your company, check it out here: http://www.stashboard.org
30. 90.▲
    by RobSpectre 13y ago

    It's a good question. As our service is delivered through a utility pricing model, most of our API requests are billing events - each call, text message or recording ends up having a debit to the account balance associated with it. As