You are reading content from Scuttlebutt
@Anders %lGmXssdy9pEhsateV8gE5BXXlacjA4VMXH3uc6mFqRU=.sha256
Re: %+Cd1qTxNW

Hah yeah @mix I have been watching that as well. We established that json parsing and stringifying is a big part of the performance problems we are seeing. I tested turbo-json and the 5x speedup is real. Also he optimizes for bytes that will fit perfectly with us. There are two problems right now with using it for messages: 1) We need anyOf otherwise our null or string for backlinks won't work and 2) we probably need something like an old school json.parse in the middle for the content part.

Join Scuttlebutt now