Hi All.
Quick Question:
If Spark Core has enough power (ARM), why isn’t there a OAUTH2 Library that can login directly to twitter without any server or cloud intervention?
Is it that it needs someone to write it, or is it something else I am missing?
Maybe there’s already one!
i think the 
core is unstoppable for now with all the power it has got on board with an STM32 
It’s more like whether someone wrote a library/code to do it or not since it’s not a requirement for a micro-controller out of the box. 
I wish I have the knowledge to do so! It would be great.
At least get SSL support, so we can start working on the library 
HTTPS via the Spark core?
We have something like Webhooks in the plan and that might help. Also, HTTPs on the core has been mentioned a few times and i believe we will have it but not time to it yet.
Hope it helps!
Thank you. HTTPS it’s very useful to access SSL encrypted sites and web services (Twitter and most websites this days).
Hi @frlobo
Everyone understands that SSL/TLS would be great to have on the core, but there are resource limitations. The problem with SSL on the Spark core is not encryption part, but the certificate management. That is why the Spark cloud connection is designed the way it is, with symmetric public key crypto for AES key exchange and then AES keys for the link connection. This has similar strength to SSL without having to do any certificate management and checking on the core, but can only talk to the Spark cloud (or someday soon your own personal, local cloud).
The Spark team has talked about using the cloud as a proxy to connect to other internet services like twitter and gmail etc. using a feature they have been calling webhooks. The idea is that your core talks to the Spark cloud and the the Spark cloud server acts a proxy to do predefined actions that you set up and authorize it to do.
While this is a really great idea, it is hard to strike a balance between convenience for us and being a good citizen on the internet. So I think this feature is on the way, but it is taking some time to get it right.
This is, I think, the much more likely architecture for HTTPS on this system. It also symbolizes a big part of the reason the Cloud exists: to take the things that are difficult to do in a constrained microcontroller and make them easy to do by linking up to powerful servers.
Great to hear! Keep the good work up! I know priorities exist before this.. So no worries! Keep the good things coming!
I totally agree. However if the spark has the power, I think it would be useful in the future (when priorities allow) to have HTTPS/TLS onboard and be able to connect as a client to other clouds without the need of proxies, delays or middleware points of failure. Specially for simple applications like twitter, etc.