http://torzcd47rw4qh36g4yqxvv2tmifgmu6jjalkyqz4e4lzzwtfdfc7qaqd.onion/popular-jwt-cloud-security-library-patches-remote-code-execution-hole-mobile-hacker-for-hire/index.html
>
<data>
<name>Duck</name>
<job>
<employer>Sophos</employer>
<role>NakSec</role>
</job>
</data>
…might come out like this in JSON:
{"name":"Duck","job":{"employer":"Sophos","role":"NakSec"}}
Whether the JSON really is easier to read than the XML is an open question, but the big idea of JSON is that because the data is encoded as legal JavaScript source, albeit without any directly or indirectly executable code in it, you can parse and...