rich1.0npub18yq2ukhtlnkuzzykluyjvxap3vtvdqf0arvtag6rx02klk6gymgqp3txp2https://nostr.ae/npub18yq2ukhtlnkuzzykluyjvxap3vtvdqf0arvtag6rx02klk6gymgqp3txp2njumphttps://nostr.ae📅 Original date posted:2011-12-19 🗒️ Summary of this message: HTTPS should be used for Bitcoin websites dealing with financials. JSON support is common, but it cannot represent binary data. Custom output script needs clarification. 📝 Original message:I still think HTTPS should be used, at the minimum. Using HTTPS is standard to every website out there that deals with financials, even if it is not a perfect system. Why should Bitcoin adopt a more lax policy than everyone else? I thought that JSON support was fairly common these days. I personally prefer XML in most cases, but since JSON is already used with the RPC, it seemed like a natural fit here. Binary data can be base64 encoded, although I'm not sure why you would need to send back binary in an alias response. What exactly do you mean by "custom output script"? On 12/19/2011 8:30 AM, Luke-Jr wrote: > I'd prefer we stick to simple standards. > HTTP alone should really be fine to build on... > > JSON in particular has very poor language support, and cannot reasonably > represent binary data (such as a custom output script). The HTTP > specification, however, allows binary data in multipart content just fine.