51–60 of 132 posts
Ironically, the idea is more useful than intended. One could, for example, store on/off user's preferences in the cloud without the hassle of local storage, survey responses, or even control IoT devices remotely with just the switch of a boolean.
A boolean might indicate if it's snowing in NY, for example (Read-Only for most people)
HTTP 500 error on sending qubits
I'm concerned about the lack of authentication on this API. What's to prevent an attacker from modifying my booleans? just his ability to guess the guid?
Could you add an XML endpoint for your API, with an XSD describing it? All our systems are built to use XML, and adding JSON support to our infrastructure is still 6-9 months away.
Do you offer HIPAA-compliance, in case we'd like to store booleans from medical records on your servers?
I'm concerned about the lack of authentication on this API. What's to prevent an attacker from modifying my booleans? just his ability to guess the guid?
Good practice would recommend adding /v1/ to your API url. The state of the boolean ecosystem is moving so fast that we have no idea what booleans will look like in 5 years!
My company is willing to invest $2 Million, series A. But We want full control on the booleans.