People have their reasons, we respect that. But a default to https, why not? It seems reasonable to me.

I am not sure on how to get https:// by default while still supporting http:// for people who prefer it. It may take some advanced 302 redirect.

We will investigate and see what we can do there. Suggestions are much appreciated.

I'm still very unclear on a legitimate use case for this, and personally wouldn't do it until I had a good reason.

That said, a couple ideas on how to implement:

* Use an alternate domain, eg `insecure.domain.com`

* Use an alternate path prefix, eg `domain.com/insecure/` -- your app would have to be able to handle this

* Use a parameter that sets a cookie that your load balancer/reverse proxy can understand, eg, `http://domain.com/?https=false`, and will prevent redirect -- definitely the most complex from the proxy point-of-view, but means the URL (other than the scheme) is consistent for both types of user

I sometimes parse web data with uC based devices that are not capable of doing https with the memory space available. I appreciate the ability to use http when I need to.

I use http from embedded devices that cannot do https due to memory constraints. Http access is appreciated for this use case.

But.... Do you guys have a business model that is going to keep you around long enough for me to bother hardcoding your api into embedded devices? I build things that connect real world actions to cryptocurrency markets, diverting power, metering resource consumption, etc.

Please get in touch by email if you need something more than the free API.

For your embedded devices, we can make something special just for you

I use http from embedded devices that cannot do https due to memory constraints. Http access is appreciated for this use case.

But.... Do you guys have a business model that is going to keep you around long enough for me to bother hardcoding your api into embedded devices? I build things that connect real world actions to cryptocurrency markets, diverting power, metering resource consumption, etc.

We plan to remain online for a long long time

And if you make embedded devices using our API, maybe you need more than the free API?

We sell access based on subscription for 0.1 BCH per month.

Or maybe you need our 'special services'?

From the FAQ: "I'm wealthy. I have very specific crazy needs!"

"For the right price, the above rules may not apply to you. Right price means at least 1 BTC. If you can pay that, we can do many crazy things just for you"

Oops wrong place, sorry.

No wrong question :-)

Please get in touch by email if you need something special.

If you have hard constraints, we can provide you with a special API returning only the value(s) you need so you do not even have to parse anything.

GraphQL :)

Not attempting to be snide, this sentiment echoes exactly what GraphQL solves.