<story><title>Jetstream: Shrinking the AT Protocol Firehose by &gt;99%</title><url>https://jazco.dev/2024/09/24/jetstream/</url></story><parent_chain><item><author>Ericson2314</author><text>I gotta say, I am not very excited about &amp;quot;let&amp;#x27;s throw away all the security properties for performance!&amp;quot; (and also &amp;quot;CBOR is too hard!&amp;quot;)&lt;p&gt;If everyone is on one server (remains to be seen), and all the bots blindly trust it because they are cheap and lazy, what the hell is the point?</text></item></parent_chain><comment><author>skybrian</author><text>Centralization on trusted servers is going to happen but if they speak a common protocol, at least they can be swapped out. For JetStream, anyone can run an instance, though it will cost them more.&lt;p&gt;It’s sort of like the right to fork in Open Source; it doesn’t mean people fork all the time or verify every line of code themselves. There’s still trust involved.&lt;p&gt;I wonder if some security features could be added back, though?</text></comment>
<story><title>Jetstream: Shrinking the AT Protocol Firehose by &gt;99%</title><url>https://jazco.dev/2024/09/24/jetstream/</url></story><parent_chain><item><author>Ericson2314</author><text>I gotta say, I am not very excited about &amp;quot;let&amp;#x27;s throw away all the security properties for performance!&amp;quot; (and also &amp;quot;CBOR is too hard!&amp;quot;)&lt;p&gt;If everyone is on one server (remains to be seen), and all the bots blindly trust it because they are cheap and lazy, what the hell is the point?</text></item></parent_chain><comment><author>hinkley</author><text>If you’re going to try data reduction and compression, &lt;i&gt;always try compression first&lt;/i&gt;. It may reveal that the 10x reduction you were looking at is only 2x and not worth the trouble.&lt;p&gt;Reduction first may show the compression is less useful. Verbose, human friendly protocols compressed win out in maintenance tasks, and it’s a marathon not a sprint.</text></comment>