I think a lot of us are waiting for the feature the Spark team is calling “webhooks” where the Spark cloud acts as the proxy for https transaction on the Internet. Since the only secure connection to/from the core to the Internet is to the Spark cloud, this make a lot of sense. The idea is that you define an action to be taken by the cloud server when your core does a Spark.publish() or an action to be taken on the core via Spark.function() or variable() when another host hits an API on the Spark cloud server. The security implications here are important, so the team wants to get it right.
The problem with https is not the crypto for the link per se since the Spark cloud connection is AES encrypted. The problem is the certificate management and checking with the small resources available. There would be no RAM left if even one certificate had to be stored and checked on the core in my estimation.
If you don’t like the idea of the Spark cloud being your proxy, the team has committed to providing a Spark cloud you can run on your own server instead so you control it.
So look around: people are doing cool stuff and have found ways to not be limited by the lack of http until the webhooks feature is fully baked!