3 ms·
As a consumer I sort of like this (I do worry about unintended consequences tho), but as a developer this absolutely sucks. It's already a massive PITA to make
by freedomben 7y ago
As a consumer I sort of like this (I do worry about unintended consequences tho), but as a developer this absolutely sucks. It's already a massive PITA to make use of telephony (SMS/voice calls) through AWS and the like, and this will only make that 10 times worse. Even at a medium-sized company that spends 5 figures a month on AWS services we got totally burned by this.
Amazon has also done an abysmal job at facilitating between the deveopers (us) and the carriers. They will just shut down your production system without warning and yet their API will still return 200s as tho everything is fine, while silently sending your SMS to the bit bucket. Then when you open a support case it will take a while unless you pay for support, support that you only need because they are returning lies from the API and you have no way of finding out what is wrong without a support agent looking at the system. Yeah I'm still pretty pissed. I will pay more for Twilio until something drastic changes.
- coldpie 7y agoAt one point I was getting four bullshit calls a day. I'm beyond the point of caring. Charge everybody five thousand dollars per minute. Require a blood sample for every phone call. Burn the phone system to the ground. I don't care, make it stop.
- freedomben 7y agoThere will be a lot of less secure accounts then. Even tho I don't like SMS for 2FA, it is the only thing that many consumers will use. If you want to destroy the ability to send any SMS programmatically, the loss of security will be only one unintended consequence. We also use a robocall for the devops team when the site goes down. We can't afford to hire a human to do it, and that would be stupid anyway. That's a pretty useful feature that would suck to lose.
- JumpCrisscross 7y ago> Even at a medium-sized company that spends 5 figures a month on AWS services we got totally burned by this Good! I send all calls not in my contact list to voicemail, and then rarely check the voicemails. Businesses need to find a better way to reach me than autodialing.
- freedomben 7y agoFirstly, our customers specifically have to enable it, and can easily disable if they don't want it. Secondly, I don't see why the AWS returning 200s while silently discarding our stuff is the right way to handle this. If you want to block our numbers (which I aboslutely think you should be able to do) the API should return something that tells us that instead of pretending like everything is fine.
- JumpCrisscross 7y ago> If you want to block our numbers...the API should return something that tells us that As a consumer, I disagree. When I send a message to spam, it doesn't let the spammer know they should switch the e-mail address they're sending from. If I block a phone number, that's not something for the dialer to know.
- freedomben 7y agoTo be clear, it wasn't consumers that blocked our numbers, it was AWS. I wrote my previous message sloppily. AWS was sending our messages into the bit bucket and returning 200s. Our customers not only wanted the messages, but were complaining to support that messages were not getting through.