Brian, there is no TLS or root CA certificates on this platform. No
browser. No X11. No screen or keyboard for that matter.
On May 14, 11:13 am, Brian Smith br...@briansmith.org wrote:
Mr Blog wrote:
For example, the current 'tweet' code binary is 18K bytes. If you can add
oAuth
in 100K
Thanks. As I note, that is a non-trivial project/barrier.
FWIW, I'm putting together a generic service for this application,
where a user can oAuth to the site and then create proxy credentials
that can be used to tweet etc.
http://www.supertweet.net/
Feedback welcome.
On May 12, 7:35 am, John
Hi Glenn,
FWIW, the application and platform is extremely small and lightweight
- there is nothing as powerful or huge as 'curl' there. It is all raw
C code, stripped down libraries, etc. measured in K-bytes, not
Megabytes, to say nothing of Gigabytes.
For example, the current 'tweet' code
Mr Blog wrote:
For example, the current 'tweet' code binary is 18K bytes. If you can add
oAuth
in 100K bytes or less, that might work, but that one function would then
still be
bigger than the entire rest of the application. In fact, the entire file
system ROM
image, with all the binaries
oAuth is a big burden for microcontroller based devices like this -
OAuthcalypse will probably simply kill this app. It seems like way
too much overhead to push oAuth code into this little chip. oAuth
alone would probably exceed all the rest of the application code on
the device combined.
Why not have the controller proxy through a full-featured webserver
that can oAuth in to Twitter?
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Wed, May 12, 2010 at 2:03 AM, glenn gillen gl...@rubypond.com wrote:
oAuth is a big burden for microcontroller based