Its the latter. The project does good work so don't want to dump on the project.
When one sees source code on Github, one assumes that its OSS, but its not and thats why I share that.
The license is a fair code license and it says "is commercially restricted by its authors" and its not clear what commercially restricted really means here.
This is so nostalgic. I actually met my cofounder on github due to a discussion on twisted vs gevent back in 2011. I had my inital code in twisted and he wrote the gevent piece. Fast forward 12 years and we still use gevent at http://plivo.com :)
I shared my exp below on one of the comments, sharing here too - I think overall the quality is significantly poorer on GPT4 with plugins and bing browsing enabled. If you disable those, I am able to get the same quality as before. The outputs are dramatically different. Would love to hear what everyone else sees when they try the same.
I have some first hand thoughts. I think overall the quality is significantly poorer on GPT4 with plugins and bing browsing enabled. If you disable those, I am able to get the same quality as before. The outputs are dramatically different. Would love to hear what everyone else sees when they try the same.
Founder of https://www.plivo.com here. We have seen similar patterns of fraud on our customers primarily in the international markets, outside the US & Canada. It typically happens on repeating number ranges that are sometimes not even in service. MaxPrice approach did not work well based on our experience as this would lead to just blocking certain destinations completely. Alternatively, what we found better was have a geo permissions related options where customers could block destinations that are never used at a network level and additionally introduce rate limits for those networks, so its not open to an attack. Plivo's console screenshot here: https://www.dropbox.com/s/kbw3l0oyw7fcjmr/plivo_console_sms_...
Founder & CEO of Plivo - https://www.plivo.com/ here. At Plivo we offer similar API services to Twilio for voice calls and SMS. While API offerings have made it easier for developers and tech team to integrate communications into their applications, one of the challenges here is the scale at which spammers and folks using stolen credit cards are always attempting to abuse all of our platforms.
Most of us companies, work quite hard to deter these spammers at sign up and later using automated systems to analyze usage patterns including content filtering, but its quite a cat and mouse game.
Something that has worked for us has been to restrict signups to only work emails. It does have it's disadvantages but we have been able to limit the random gmail id signups at scale by bot/spammers that abuse the system for use cases like robocalling and more.
Plivo's API above is updated on a daily basis for portability information.
Caller ID as you mention for voice calls is quite easy to spoof, however with the STIR SHAKEN rollout, the intention is to make carriers accountable. SMS however with 10DLC is almost impossible to spoof the number.
