Hi @chadselph. We recently stumbled onto your smssplit repo and like to use parts of your code. Therefor we wanted to kindly ask whether you consider putting it under some license which would allow usage of it?

I use Plivo and Twilio to send SMS. Starting on 6:30am EST 2/15/17, Plivo started encoding some of my texts as Unicode. Texts that previously didn't require Unicode. Texts that Twilio still sends without encoding as Unicode. Here's an example.

Su receta(s) estan listas para ser recogidas en XXXXXXXX XXXXXXXX. Si tiene alguna pregunta, favor contactar la farmacia al 999-999-9999. ¡Gracias!

I tested this on your website http://chadselph.github.io/smssplit/

According to your program the message uses valid GSM characters and will fit in a single text. I think you're correct but Plivo disagrees. I've been arguing with Plivo for two weeks and they still insist this message must be encoded as Unicode and are charging triple since using Unicode obviously requires three texts. They say the reason they previously only charged for one text was a bug in their system. They fixed the glitch and are now charging triple.

I'm sorry to bother you. But since Plivo insists your web site is invalid I thought I should at least bring this to your attention.

It would be useful if the demo page had a link to this GitHub repo.

Hey there, thanks for creating this tool, its been super helpful. I'm using your logic to track how many segments are being created (and I'm being charged for) for each message that I send. I had to port it to python though, which I did here.

Not sure if this is a cool thing to do or not, but I was wondering if you wanted to link to my port in your readme so that other travelers don't have to port it again? No worries if not, just want to save others time.