goleksiak

https://www.eatabit.io is built on it. We were one of their first beta clients. We used every M2M carrier previously and Twilio is easily superior in cost & reliability. The cellular data space has alot of problems especially with roaming: cell phones transparently switch between networks but data SIMs have a very limited set of networks they can operate on. If Twilio can get VZW access on these SIMs they will have a very strong product. As it stands, coverage is limited.

Heroku did their best here. They reached out to us (twice) advising of changes and linking to a document that describe EXACTLY the bug that we discovered (later). Honestly, I don't feel bad about his bug because even if I would have read the alert to the letter, we would not have audited the entire codebase because we don't have that luxury of time. Yes, it took our whole operation down...but we found it, fixed it and now we're back up. ...it's all in the game. -@eatabit

Heroku came back and said:

Looking through the system, I see that you were sent two emails (in August and September) as several of your apps were migrated to the new routing stack (https://devcenter.heroku.com/articles/heroku-improved-router). As mentioned in the documentation, the new router follows stricter adherence to the RFC specification, including sensitivity to spaces.

...and sure enough, there is a line that says:

The request line expects single spaces to separate between the verb, the path, and the HTTP version.

So the lesson is: RTFM

-G

ah - my bad

y, true

For us, the reason is that my co-founder and I (both are not hardware guys) were able to build a proof of concept in my garage and Arduino seemed like the best (easiest) choice. Since then, we hired a hardware guy who designed a custom PCB etc. HTTPS would be great but we don't transmit any personal data so it's not a high priority right now.

Yup

The asterisks hide this request's BasicAuth credentials between the cellular printer and our app servers...we don't transmit customer phone numbers between the printer and our app servers. Twilio transmits them to our app servers but that is HTTPS

We are at about $200 now for hardware. We have a custom PCB and 3d printed case. We also have an LCD and some control knobs in the mix. Checking out the Beaglebone stuff now...very interesting since there is basically no 3G/4G modems for Arduino right now...

Charleston represent!

I didn't want to hang our BasicAuth creds out to dry

We would really like to use HTTPS but it's not supported by the Arduino chipset as I understand it. Though I'm not the hardware guy here at eatabit...

Fixed. Thanks.

What browser are you using? I'm not seeing that here on my devices...? We are using pretty vanilla Bootstrap.

True but that doesn't bother me. Nothing is static on the web these days and everyone plays under the same rule set. Keeps things interesting...

We use Twilio so we know our customer's phone numbers. If there were ever an issue like this, we could easily assist with a request by law enforcement.

Yes, it's just pizza - no ccards or personal information is transmitted - except your choice of toppings. Could that be used to profile you? "...paging Dr. Freud"

This is about control - but control for what purpose? The short-term financial gain of elites? Maybe. To satisfy elite paranoia?. Maybe.

Maybe this is control for stability.

The government creates models of the future and with more and more data about climate change pointing to disaster in the next few decades, those models must be focusing more and more at that point. So instead of government "holding its people back from a bright future", they are pragmatically laying the foundations for the control structures that will be necessary in the unavoidably dark future.

How can stability be maintained when society is radically altered by climate change?

Answer: Control