[twitter-dev] Re: oauth and embedded microcontrollers
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" wrote: > 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 and data is 114K bytes. > > How large is your TLS stack and root CA certificate database? > > Regards, > Brian
RE: [twitter-dev] Re: oauth and embedded microcontrollers
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 and data is 114K bytes. How large is your TLS stack and root CA certificate database? Regards, Brian
[twitter-dev] Re: oauth and embedded microcontrollers
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 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 and data is 114K bytes. On May 12, 2:03 am, glenn gillen wrote: > > 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. > > I couldn't find anything on the blog or the related sites given > examples of the code being used to run this GarageBot other than it > was running on uClinux. What code/libraries (if any) are you presently > using to connect to the API? > > The curl guys are working on building oauth support direct into curl, > so that should provide a fallback for these kind of apps. You could > probably use curl now provided you had a way of generating the > oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). > > If you could divulge a little more about your setup, and what kind of > constraints you have to work within, we might be lucky enough to have > someone in this group that can think of a solution. > -- > Glenn Gillenhttp://glenngillen.com/
[twitter-dev] Re: oauth and embedded microcontrollers
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 Kalucki wrote: > Why not have the controller proxy through a full-featured webserver > that can oAuth in to Twitter? > > -John Kaluckihttp://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > On Wed, May 12, 2010 at 2:03 AM, glenn gillen wrote: > >> 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. > > > I couldn't find anything on the blog or the related sites given > > examples of the code being used to run this GarageBot other than it > > was running on uClinux. What code/libraries (if any) are you presently > > using to connect to the API? > > > The curl guys are working on building oauth support direct into curl, > > so that should provide a fallback for these kind of apps. You could > > probably use curl now provided you had a way of generating the > > oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). > > > If you could divulge a little more about your setup, and what kind of > > constraints you have to work within, we might be lucky enough to have > > someone in this group that can think of a solution. > > -- > > Glenn Gillen > >http://glenngillen.com/
Re: [twitter-dev] Re: oauth and embedded microcontrollers
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 wrote: >> 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. > > I couldn't find anything on the blog or the related sites given > examples of the code being used to run this GarageBot other than it > was running on uClinux. What code/libraries (if any) are you presently > using to connect to the API? > > The curl guys are working on building oauth support direct into curl, > so that should provide a fallback for these kind of apps. You could > probably use curl now provided you had a way of generating the > oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). > > If you could divulge a little more about your setup, and what kind of > constraints you have to work within, we might be lucky enough to have > someone in this group that can think of a solution. > -- > Glenn Gillen > http://glenngillen.com/ >
[twitter-dev] Re: oauth and embedded microcontrollers
> 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. I couldn't find anything on the blog or the related sites given examples of the code being used to run this GarageBot other than it was running on uClinux. What code/libraries (if any) are you presently using to connect to the API? The curl guys are working on building oauth support direct into curl, so that should provide a fallback for these kind of apps. You could probably use curl now provided you had a way of generating the oauth_nonce parameter (http://oauth.net/core/1.0a/#auth_header). If you could divulge a little more about your setup, and what kind of constraints you have to work within, we might be lucky enough to have someone in this group that can think of a solution. -- Glenn Gillen http://glenngillen.com/
