5 ms·

So I don't want to "bash the competition" but these sites are exactly the problem I ran into when I tried to find a way to do this before building it myself. O

So I don't want to "bash the competition" but these sites are exactly the problem I ran into when I tried to find a way to do this before building it myself. On the first one my calls just fail for no reason. And on the second one my call is limited to 5 minutes and it looks like they only allow a certain number of calls per day. That's the issue. There's a ton of "demos" of this online but nobody that actually takes it seriously or makes any effort to really refine the experience as a core of their product. That's exactly what I want to do.

cbhl 10y ago
> On the first one my calls just fail for no reason. And on the second one my call is limited to 5 minutes and it looks like they only allow a certain number of calls per day. Have you considered that maybe there is a good reason that your competitors have these restrictions? For example, because scammers might abuse your service by pretending to be the IRS? http://www.npr.org/2016/05/20/478886076/money-transfer-companies-fight-back-against-irs-scammers http://www.npr.org/2016/05/20/478886076/money-transfer-compa... http://www.npr.org/sections/money/2016/01/29/464859624/episode-680-anatomy-of-a-scam http://www.npr.org/sections/money/2016/01/29/464859624/episo... Granted, these are really heavy-handed ways to solve this problem. There might be better ones, like using machine learning or something.
- lionheart 10y ago
  Oh yeah, definitely. In fact, I believe that dealing with fraud will be the #1 concern for this business aside from getting traction in the first place. Thats why even my prototype is protected using Google's reCaptcha. However, I also believe that this is something that can be handled while also providing a good experience for real users. I've run other web telephony businesses for several years now and those get hit by scammers at least once a month, but I've learned how to automatically block them out. I'm sure there's a way to do that here as well.
trome 10y ago
What browser are you using? Both work for me in Firefox ESR 45.7.0. Without money to encourage you to spend time on it, how are you going to refine the experience? How are you going to refine the experience? Debugging browser incompatibility issues with non-Evergreen browsers sounds like a nightmare to me, and is part of what holds back WebRTC today.

cbhl 10y ago

> On the first one my calls just fail for no reason. And on the second one my call is limited to 5 minutes and it looks like they only allow a certain number of calls per day. Have you considered that maybe there is a good reason that your competitors have these restrictions? For example, because scammers might abuse your service by pretending to be the IRS? http://www.npr.org/2016/05/20/478886076/money-transfer-companies-fight-back-against-irs-scammers http://www.npr.org/2016/05/20/478886076/money-transfer-compa... http://www.npr.org/sections/money/2016/01/29/464859624/episode-680-anatomy-of-a-scam http://www.npr.org/sections/money/2016/01/29/464859624/episo... Granted, these are really heavy-handed ways to solve this problem. There might be better ones, like using machine learning or something.

lionheart 10y ago
Oh yeah, definitely. In fact, I believe that dealing with fraud will be the #1 concern for this business aside from getting traction in the first place. Thats why even my prototype is protected using Google's reCaptcha. However, I also believe that this is something that can be handled while also providing a good experience for real users. I've run other web telephony businesses for several years now and those get hit by scammers at least once a month, but I've learned how to automatically block them out. I'm sure there's a way to do that here as well.

trome 10y ago

What browser are you using? Both work for me in Firefox ESR 45.7.0. Without money to encourage you to spend time on it, how are you going to refine the experience? How are you going to refine the experience? Debugging browser incompatibility issues with non-Evergreen browsers sounds like a nightmare to me, and is part of what holds back WebRTC today.