Replies (14)

Coincido Vitor, ocupa mucha memoria en el teléfono y cada vez va a ser más Se viene algo grande que hermoso #nostr
Fabiano's avatar
Fabiano 2 years ago
I was just telling @TheGrinder and the viewers on his chat that I have just cleaned around 3 Gigabyte of cache on my smartphone. And for a stream while on carrier connection it took over 1 Gigabyte of data in a few minutes.
Do those 12,000 events include Contact Lists? :) The one I measured was for ~50,000 events from me or with a p tag on my user, with 7 indexes. But I am just doing the dumb storing of full hexes in the DB, which is not great. A good use case is if you can download everything about your user (author + p-tags) to the phone.
Fabiano's avatar
Fabiano 2 years ago
Sad! Got to get an extra SSD to plug in on the mini USB.
Contact lists encode the most efficiently, because hex references are encoded as bytes. 55705 bytes -> 34322 bytes (1.68). But the main goal isn’t minimal size, it’s O(1) field access and mapping to Swift/Rust/etc data structures without encoding/decoding.
#confession Back in January I was trying to understand Damus source code, to see if something could be done about scrolling performance (its great now but was horrible back then). The first thing I was looking for to get a basic understanding was the database and I just couldn't find it. I thought my Swift/iOS skills were too far behind and had to learn modern Swift/iOS development first. So I started Nostur to learn. Turns out, Damus didn't have a database...