Argh - sorry, I'd assumed that just having OAuth would be enough. At the moment there's no way to do HTTPS. It might be possible to implement natively in the Pico, but the memory + processing requirements are absolutely huge.
It's very frustrating of Twitter - requiring HTTPS seems a bit heavyweight when the information you're sending is going to be displayed publicly anyway!
© Espruino, powered by microcosm.
Report a problem