RobSpectre | 4 years ago | on: The strange, sketchy emails a browser extension developer receives
I get four of these per month.
RobSpectre's comments
RobSpectre | 5 years ago | on: Scrollycoding – A new way to write code walkthroughs [video]
This is super tasteful and clean. Well done.
RobSpectre | 9 years ago | on: Tekserve auctions their vintage Mac collection
This is just heartbreaking.
RobSpectre | 10 years ago | on: Twilio announces $130M series E round
Very sorry to hear about your experience. Do you reckon you could reach out to rob [at] twilio?
Keen to hear more about the deliverability issues you are experiencing.
RobSpectre | 10 years ago | on: Twilio announces $130M series E round
Rob from Twilio here - the firms listed in the first two paragraphs are the new folks who are joining in this round, not the exclusive list of all participants.
BVP did participate in this round - great team to work with.
[edit] typo.
RobSpectre | 11 years ago | on: Twilio Video – Real-time WebRTC video infrastructure
Absolutely - we have a lot of ambition around where we want to take Twilio Video in the future.
This is only the first step.
RobSpectre | 11 years ago | on: Twilio Video – Real-time WebRTC video infrastructure
Check. Good feedback.
RobSpectre | 11 years ago | on: Twilio Video – Real-time WebRTC video infrastructure
Good question - one of Twilio Video's aim is to take a lot of the signaling headache away. We do expose the PeerConnection, but not the SDP object.
What would you want to use it for?
RobSpectre | 11 years ago | on: Twilio Video – Real-time WebRTC video infrastructure
Rob from Twilio here - appreciate the feedback.
Have you had an opportunity to check out TaskRouter yet? We released it a few weeks ago - definitely my favorite recent product that works with Twilio Voice:
RobSpectre | 11 years ago | on: Twilio Video – Real-time WebRTC video infrastructure
Rob from Twilio here - confirming this is an accurate description. Each peer in the conversation has a connection to every other peer.
RobSpectre | 11 years ago | on: Lookup by Twilio
Awesome - thanks for giving it a swing.
RobSpectre | 11 years ago | on: Lookup by Twilio
Mmmm - great feedback. We do provide this service for our phone numbers to do a CNAM lookup on inbound communications - can see how it would be useful for Twilio Lookup as well.
RobSpectre | 11 years ago | on: Lookup by Twilio
Yes. Yes we will. :'(
RobSpectre | 11 years ago | on: Lookup by Twilio
It would be based on the number itself. Obviously with local number portability this is not super accurate, but we do have some customers that find the data useful nevertheless.
RobSpectre | 11 years ago | on: Lookup by Twilio
Can't commit to anything yet - do appreciate the feedback though.
RobSpectre | 11 years ago | on: Lookup by Twilio
Much obliged on the bug reports. We've corrected the number on the demo page and confirmed it is working now.
If you both would like to shoot me an email to rob [at] twilio [dot] com, we'll ship you a t-shirt as thanks for pointing out the error.
RobSpectre | 11 years ago | on: Lookup by Twilio
Rob from Twilio here - thanks for using the service. Localization and fraud/spam protection are definitely the two most useful for Twilio Lookup, but suspect there are a couple more than might be less obvious.
1) Smarter Routing - quite a few developers have expressed they'd like to know whether or not a phone number is a landline or not before attempting to send a text message. Twilio Lookup will describe whether the number is mobile, landline, or voip so you can choose the appropriate communication to reach the number.
2) Error Checking - While libraries like libphonenumber are useful for determining if a number can possibly exist, there are some conditions where determining if a number does exist is more valuable. This can be used for error checking - if I as a user input a typo in my phone number (e.g. I mistype my personal phone number as '(347) 193-6073' which does not exist instead of '(347) 923-6073')
I also suspect across larger applications carrier info might also contain useful demography. For example, knowing that your users in Montana mostly use Verizon might inform your advertising to surface more CDMA devices in that market.
Ultimately this will probably end up like every other product we release - the killer use case is one we never even considered.
RobSpectre | 11 years ago | on: Lookup by Twilio
libphonenumber is definitely the jam for offline formatting - we use it all the time.
RobSpectre | 11 years ago | on: Lookup by Twilio
Hey Jon - Rob from Twilio here.
Good feedback - appreciate you sharing. We do have geographic information with each webhook sharing city, state and zip - agree it would be useful to have this in the Lookup resources as well.
RobSpectre | 11 years ago | on: Twilio Positions Itself for an IPO After Logging $100M in 2014 Revenue
Thanks Adam - we're rooting for you as you head out. Building a business serving developers is indeed as difficult as you say, but also - to be fair - an endless amount of fun.
Certainly nothing we'd rather be doing.
page 1