spending some time today getting the “timeline” query plan working on damus android/notedeck/desktop. The multiplatform version of damus is build from the ground up using a local relay model, so basic things like querying your timeline is no longer a task delegated to the relay. *the relay is in the computer* Here’s me testing and making sure the it’s matching up with damus ios. Looking good. I can view my nostr timeline on my linux desktop now. yay! What’s everyone up to today 👀 https://cdn.jb55.com/s/android-timelines.mp4
I have to ask. How do you build for IOS on a Lenovo?
Was curious about this too!
Its not iOS, its a multiplatform version built in rust
Ok well riddle me this Batman, there’s a lovely translation feature in damus, but it still doesn’t translate dev talk into my imbecilic/native language.
Oh man. I need to learn about doing more rust development then.
Well…if you do, bring this https://image.nostr.build/ddb9974378b9adff6358ffd1636882e8cd0d846e2fa35ec5192b6a4b8d32a3e7.jpg
When you say local relay is it something like https://github.com/greenart7c3/Citrine Or just a local database that only damus use?
It uses https://github.com/damus-io/nostrdb which is a zero-copy custom C database built on lmdb with nostr query support. It currently powers damus ios (partially), notedeck, android, and notecrumbs.
That looks cool. I’m trying to finish my next episode of my podcast, been working on too many things at the same time and none is complete
Damus Android?
Does the desktop mean web client, which I prefer? Sounds cool. How the local relay model affects the power consumption on mobile phones? Does it sync every now and then or continuous? Can one set the sync interval?