The history of Nostr will be defined by before and after local databases.

We will need bigger storage options on phones.

nostr:nevent1qqsyx3zra83fu4jn5v7kd0vhurpw82z8f33sq4tmkcqknsu7eqjgfdgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3grqsqqqqqpen4gw4

Reply to this note

Please Login to reply.

Discussion

Like expandable storage making a comeback perhaps?

Is that a server in your pocket or are you just happy to see me?

6 months of use and the local db of my user is already 250MB (uncompressed).

We dont even have apps for everything yet.

Are we talking Amethyst? My local storage was like 8GB the other day and I nuked it.

Yep, but 250MB of just Nostr messages. Sum videos, photos, and translation models and we are up a few GB.

So much for 5G. 🤣

I’m measuring nostrdbs compact event format at around 4MB for 12,000 events

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.

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.

I was just telling nostr:npub1de6l09erjl9r990q7n9ql0rwh8x8n059ht7a267n0q3qe28wua8q20q0sd 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.

I don't think cleaning the cache does much these days. The OS fills it up with the latest from it's own cache. That's why the number goes back up very quickly.

Sad! Got to get an extra SSD to plug in on the mini USB.

Coincido Vitor, ocupa mucha memoria en el teléfono y cada vez va a ser más

Se viene algo grande que hermoso

#nostr

#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...