Ian Webster

I think I've restored functionality for providers like Verizon and AT&T that stopped working last week. This probably doesn't fix the TMobile problem because they seem to have blocked textbelt.com.

Can you guys try hitting the endpoint at `txtblt.co` instead of `textbelt.com`? eg. `curl -X POST http://txtblt.co/text -d number=2121234567 -d "message=foo bar testing"` I've been playing around with various fixes...

Great. I will try to confirm a few other providers via people I know. If the other providers work, I will point textbelt.com to the txtblt.co server and see if...

I redirected textbelt.com to the new server. Anecdotally (read: my Verizon phone + my friends with AT&T and TMobile) people are now receiving texts. I will merge the carriers pull...

There are a handful of users who run spam campaigns via Textbelt. I have banned a few but I don't spend enough time tracking these. I'll probably add more monitoring...

Hi guys, I'm aware of an issue but am traveling abroad with very low connectivity (Ethiopia). I won't be able to fix this for at least a few days. This...

Any improvements recently? I think some providers temporarily blacklisted - I am getting texts just fine on Verizon. I'm thinking of adding a global daily limit to prevent these sorts...

@karlderdmann Can you show us your code? The site and service are up and you shouldn't be getting a 404.

@trevalexandro I assume you are self-hosting. Can you provide details of your setup? Outputs on the server and client?

Agreed this would be great. Hoping someone makes a pull request for this :) On Sat, Oct 17, 2015, 3:36 PM David Luu [email protected] wrote: > FYI, if this is...