<story><title>Jailbreaking RabbitOS</title><url>https://www.da.vidbuchanan.co.uk/blog/r1-jailbreak.html</url></story><parent_chain><item><author>mikenew</author><text>Without any explicit admission of guilt on my part; what are some good options here? Protobuf is cool but I really don&amp;#x27;t want to mess with a special compiler and all that.</text></item><item><author>progbits</author><text>Welcome to the world where everyone is wasting time and space on JSON encoding rather than using some sensible serialization protocol that can handle raw bytes.</text></item><item><author>underdeserver</author><text>Base64 encoded MP3s? That&amp;#x27;s just ridiculous. All you get by base64 encoding them is 33% more data used.</text></item><item><author>mrbluecoat</author><text>&amp;gt; logs include:&lt;p&gt;Your precise GPS locations (which are also sent to their servers).
Your WiFi network name.
The IDs of nearby cell towers (even with no SIM card inserted, also sent to their servers).
Your internet-facing IP address.
The user token used by the device to authenticate with Rabbit&amp;#x27;s back-end API.
Base64-encoded MP3s of everything the Rabbit has ever spoken to you (and the text transcript thereof).&lt;p&gt;Nasty :0</text></item></parent_chain><comment><author>Spivak</author><text>The responses you got I think literally answer your question but probably aren&amp;#x27;t what you&amp;#x27;re going to reach for any kind of HTTP based thing. Your go-to should probably be multipart&amp;#x2F;form-data. It&amp;#x27;s well supported in every language and HTTP library and you can send both JSON and the file in the same payload.&lt;p&gt;There seems to be a common trend of people writing &amp;quot;JSON APIs&amp;quot; thinking that every other part of HTTP is off-limits.</text></comment>
<story><title>Jailbreaking RabbitOS</title><url>https://www.da.vidbuchanan.co.uk/blog/r1-jailbreak.html</url></story><parent_chain><item><author>mikenew</author><text>Without any explicit admission of guilt on my part; what are some good options here? Protobuf is cool but I really don&amp;#x27;t want to mess with a special compiler and all that.</text></item><item><author>progbits</author><text>Welcome to the world where everyone is wasting time and space on JSON encoding rather than using some sensible serialization protocol that can handle raw bytes.</text></item><item><author>underdeserver</author><text>Base64 encoded MP3s? That&amp;#x27;s just ridiculous. All you get by base64 encoding them is 33% more data used.</text></item><item><author>mrbluecoat</author><text>&amp;gt; logs include:&lt;p&gt;Your precise GPS locations (which are also sent to their servers).
Your WiFi network name.
The IDs of nearby cell towers (even with no SIM card inserted, also sent to their servers).
Your internet-facing IP address.
The user token used by the device to authenticate with Rabbit&amp;#x27;s back-end API.
Base64-encoded MP3s of everything the Rabbit has ever spoken to you (and the text transcript thereof).&lt;p&gt;Nasty :0</text></item></parent_chain><comment><author>LeoPanthera</author><text>Common alternatives are Apache Avro, MessagePack, FlatBuffers, and Thrift.&lt;p&gt;I have no idea which is best. Frankly it seems like there are too many choices.&lt;p&gt;Probably MessagePack, since it is JSON-like and I&amp;#x27;ve actually heard of it.</text></comment>