goleksiak
Joined 15 years ago
Karma
336
Submissions
20
Member since
Aug 29
Recent submissions
Comment · 6 years ago
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.
Comment · 12 years ago
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
Comment · 12 years ago
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
Comment · 12 years ago
ah - my bad
Comment · 12 years ago
y, true
Comment · 12 years ago
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.
Comment · 12 years ago
Yup
Comment · 12 years ago
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
Comment · 12 years ago
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...
Comment · 12 years ago
Charleston represent!
Comment · 12 years ago
I didn't want to hang our BasicAuth creds out to dry
Comment · 12 years ago
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...
Comment · 12 years ago
Fixed. Thanks.
Comment · 12 years ago
What browser are you using? I'm not seeing that here on my devices...? We are using pretty vanilla Bootstrap.
Comment · 12 years ago
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...