[LewisVerstappen]

Interesting. I tried to create a Twilio account 2 weeks ago and it was the worse developer experience I've ever had by far.

Like seriously.

They first make you deposit $20 to get started. THEN, they tell you to talk to customer support to activate your account (customer support took forever to reply).

Oh and then I had to fill out like 3 applications and my text messages are still randomly getting blocked - I have no idea why.

To be clear, this is literally just me using Twilio to text myself to test out the API. I'm not some spammer or something. It was impossible to get started.

[Phurist]

You have to thanks the abusers and scammers for that. All nice things have to be locked down :(

[LewisVerstappen]

okay but if I only need to text ONE phone number (and I can prove ownership over that phone number), then why so many restrictions?

There should be an easier way to just test out the API.

[itinerantwarble]

This is industry self-regulation. See A2P 10DLC. Dealing with it at scale has sucked. If you want to send SMS, it's the price of admission everywhere--not just at Twilio. I know you said you wanted to send yourself an SMS, but you can test without sending using test credentials and magic numbers: https://www.twilio.com/docs/messaging/tutorials/automate-tes...

[DanielHB]

it is not just SMS, I just recently set up some AWS SES for sending emails (never done this kind of thing before) and boy is it a nightmare to get emails to not be flag as spam these days.

Like SPF, DMARC, DKIM. What the hell how many layers of security do I need to go through to get some emails delivered from a domain I own?

[aisha_mc]

There has been an increase in SMS phishing attacks too.

[EugeneOZ]

They had really nice APIs but they had not enough protection from spammers. But APIs were really sweet...