Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Caller ID Made Simple

rdegges.com

Post reply on HN
Print view View original

31–40 of 66 posts

Re: Caller ID Made Simple

#31

Post by b14ck »

premchai21 wrote: post #18
mikeknoop wrote: post #11

Earlier quoted context omitted.

You might make this more obvious. Also, you might state how to distinguish between "sorry we need more time to look this up" and an actual 404 or error. HTTP code 202 Accepted seems appropriate for this ( http://en.wikipedia.org/wiki/List_of_HTTP_status_codes )

504 Gateway Timeout would be the obvious one, since if I'm reading this correctly it's essentially a timeout of zero; 5xx status codes are indicative of retriability later on. But I think that sort of performance would make the free tier essentially worthless. “All you have to do is hit our API endpoint, and BAM, you get results back.” Except you really don't. Analogy: a caching DNS resolver that returned an instant…

Hey premchai21, thanks for the feedback! You're completely right. I'll be making some adjustments to the way this operates over the coming days to make things much simpler.

Thanks for taking the time to check us out!

Re: Caller ID Made Simple

#33

Post by sunsu »

I would ONLY be willing to use this if it returned better data than Twilio's CNAM lookups (costs $0.01) for a cheaper overall price.

So far, I've tested my number, and a few others, that I know have CNAM data that this service only provides a STATE for. Hopefully it will get better but it's not there yet for me.

Re: Caller ID Made Simple

#34

Post by toomuchtodo »

drivebyacct2 wrote: post #21
mwally wrote: post #13

Earlier quoted context omitted.

An Android app is currently in development, and will be released free of charge. We are having an issue, however, because non-GSM carriers rarely allow data transmissions during a voice call, including the ringing state of incoming calls.

Without Voice-over-LTE, I'm not sure how you're going to get around it. It's not a carrier limitation, it's a limitation of CDMA radios and implementations.

The best you could do is do the query after the call, and cache it locally if the caller calls again.

Re: Caller ID Made Simple

#35

Post by toomuchtodo »

mwally wrote: post #24
kcbanner wrote: post #15

Earlier quoted context omitted.

Even a lookup app would be handy for seeing missed calls, etc.

Give us a few more weeks of development for this, and it will be ready. The current working title of the Android app is "FreeCallerID," but we may change this before launch. Just look for the Round OpenCNAM logo to make sure you found the right app.

Need beta testers?

Re: Caller ID Made Simple

#36

Post by w1ntermute »

mwally wrote: post #13
mikeknoop wrote: post #6

Earlier quoted context omitted.

My thoughts exactly! I easily get less than 60 calls per hour so this would be perfect. Interestingly, the caller ID for my number is tied to the first owner of my account before it was transferred to me (which happened many years ago).

An Android app is currently in development, and will be released free of charge. We are having an issue, however, because non-GSM carriers rarely allow data transmissions during a voice call, including the ringing state of incoming calls.

This shouldn't be an issue with LTE, right?

Re: Caller ID Made Simple

#37

Post by JoshTriplett »

premchai21 wrote: post #18
mikeknoop wrote: post #11

Earlier quoted context omitted.

You might make this more obvious. Also, you might state how to distinguish between "sorry we need more time to look this up" and an actual 404 or error. HTTP code 202 Accepted seems appropriate for this ( http://en.wikipedia.org/wiki/List_of_HTTP_status_codes )

504 Gateway Timeout would be the obvious one, since if I'm reading this correctly it's essentially a timeout of zero; 5xx status codes are indicative of retriability later on. But I think that sort of performance would make the free tier essentially worthless. “All you have to do is hit our API endpoint, and BAM, you get results back.” Except you really don't. Analogy: a caching DNS resolver that returned an instant…

> But I think that sort of performance would make the free tier essentially worthless.

Not at all. It lets you try out the API, figure out if it works for you, and get back "best effort" results. That seems perfect for a free tier.

Post reply on HN