71–80 of 90 posts
Earlier quoted context omitted.
We could fix that, but I kinda like TOR. Keeping it in all caps (like when it was just an acronym) puts it forward. We want to emphasize our support of privacy.
Fair enough if that’s what you want but if you just make up how you name things it’ll confuse people. You wouldn’t spell PGP like PgP either.
Ok, we'll fix that.
This is really cool, great work! I am one of the developers of Blockmodo. It offer realtime data streamed directly from the exchanges via a WebSocket API. Alternatively, you can also go through our REST API as well to get this data. Data can be streamed aggregated or if you choose, you can also stream and poll the data on a per-coin basis. For example, if you want the aggregate price of Bitcoin you can do that but if…
Earlier quoted context omitted.
Why is it better to let people choose? That implies there is a downside to https:// or a reason some people prefer http:// -- can you elaborate? If you type just the domain name you get http:// by default, which, in my experience, is how most people type in site URLs.
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.
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
This is really cool, great work! I am one of the developers of Blockmodo. It offer realtime data streamed directly from the exchanges via a WebSocket API. Alternatively, you can also go through our REST API as well to get this data. Data can be streamed aggregated or if you choose, you can also stream and poll the data on a per-coin basis. For example, if you want the aggregate price of Bitcoin you can do that but if…
That being said, it is refreshing to see a barebones data site by geeks for geeks! I'll following up to find out what they have behind the client subscription.
This is really cool, great work! I am one of the developers of Blockmodo. It offer realtime data streamed directly from the exchanges via a WebSocket API. Alternatively, you can also go through our REST API as well to get this data. Data can be streamed aggregated or if you choose, you can also stream and poll the data on a per-coin basis. For example, if you want the aggregate price of Bitcoin you can do that but if…
I don't think you should be allowed to make a one-liner comment "This is really cool!" and then follow it up with a 15 line copy-pasted sales pitch for a potentially competing product. That being said, it is refreshing to see a barebones data site by geeks for geeks! I'll following up to find out what they have behind the client subscription.
Earlier quoted context omitted.
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, ` ht…
Earlier quoted context omitted.
During tests, we found it was better to let people chose. You can use whatever method you feel more comfortable with. Sometime usability and security go in different way. We could do HSTS but if you took time to type http:// maybe you really want http not https
Why is it better to let people choose? That implies there is a downside to https:// or a reason some people prefer http:// -- can you elaborate? If you type just the domain name you get http:// by default, which, in my experience, is how most people type in site URLs.
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.
Earlier quoted context omitted.
Why is it better to let people choose? That implies there is a downside to https:// or a reason some people prefer http:// -- can you elaborate? If you type just the domain name you get http:// by default, which, in my experience, is how most people type in site URLs.
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.
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.
Earlier quoted context omitted.
Why is it better to let people choose? That implies there is a downside to https:// or a reason some people prefer http:// -- can you elaborate? If you type just the domain name you get http:// by default, which, in my experience, is how most people type in site URLs.
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.