Nostr View

jb55 @jb55 - 3y

one of the slowest parts of receiving lots of events on mobile is actually json decoding. I wonder if it’s time to create an optimized binary transport for nostr notes. Could be a simple TLV format.

undefined
undefined
undefined

b3e43 - 3y

グッドモーニング☀️

undefined
undefined
undefined

0e460 - 3y

That’s what I call an idea 👍

undefined
undefined
undefined

jb55 @jb55 - 3y

ohaiou

undefined
undefined
undefined

f4db5 - 3y

GM Will 🌞💜🧡🤙

undefined
undefined
undefined

5abcd - 3y

I have no idea what you are saying but I know it will be awesome.

undefined
undefined
undefined

496d3 - 3y

That is correct, will. Now tell the people what the audiophiles prize. 📎

undefined
undefined
undefined

nostrnaut @nostrnaut - 3y

me reading this note:

undefined
undefined
undefined

b2dd4 - 3y

Using the inbuilt Apple JSON support? Maybe we can try swap out to a faster external library? The other major issue I see is websockets have no congestion management - it’s event by event, and a large event blocks all the smaller ones behind it.

undefined
undefined
undefined

Jack Chakany @Jack - 3y

Definitely

undefined
undefined
undefined

b2dd4 - 3y

This? “IkigaJSON is a really fast JSON parser. It performed ~4x faster than macOS/iOS Foundation in our tests when decoding a type from JSON.” https://github.com/orlandos-nl/IkigaJSON

undefined
undefined
undefined

0xtr @0xtr - 3y

I don’t see why not 🤷‍♂️

undefined
undefined
undefined

jb55 @jb55 - 3y

i tried a branch where I built my own custom json decoder, but you still need to walk every byte in the string and unescape things. json decoding is not trivial, where a TLV format would be as simple as copying bytes directly.

undefined
undefined
undefined

8eee8 - 3y

Yes. And there is more of what should be done: https://damus.io/note12044688xrg67tnc2lkv5whwrvycy0y2rsrg6lgd8s8ses2pr57nsfv85x5

undefined
undefined
undefined

gek @gek - 3y

I don’t think I understand what this man means but it talks about replacing json decoding with something else… if it’s j something it needs replacing, right? Thant’s how it works?

undefined
undefined
undefined

jb55 @jb55 - 3y

I need to automatically convert these links to note refs…. nostr:note12044688xrg67tnc2lkv5whwrvycy0y2rsrg6lgd8s8ses2pr57nsfv85x5

undefined
undefined
undefined

b3e43 - 3y

ohayo!

undefined
undefined
undefined

Duck Nebuchadnezzar @duck - 3y

Would this mean that relays would need to support both formats? (falling back to json if the client doesn't support it)

undefined
undefined
undefined

jb55 @jb55 - 3y

Nope, relays could advertise that they support it or not. Would be completely optional.

undefined
undefined
undefined

1e9d8 - 3y

But then you specifically request data in this firmat from the relay, so that you need no detection on client side, right?

undefined
undefined
undefined

jb55 @jb55 - 3y

It would be advertised in the relay metadata if it’s supported or not.

undefined
undefined
undefined

1e9d8 - 3y

That part is clear, but how does the relay decide which format to send events in?

undefined
undefined
undefined

jb55 @jb55 - 3y

When it sees a binary request it can respond in binary. The first byte could be a magic byte instead of [

undefined
undefined
undefined

496d3 - 3y

Learned a trick to filter the coffee beans. 🎟️ Filter the terminal with it. 😀

undefined
undefined
undefined

496d3 - 3y

🍎

undefined
undefined
undefined

4720b - 3y

Sounds like Avro

undefined
undefined
undefined
Showing page 1 of 1 pages