Certainly the date ranges filtering we have nowadays are insufficient on a network where the consensus points to zero. And there is no much proposals for relays on that sense.
Is there a proposal for it already? Would love to see how that performance works on the relay side, I guess it would be an inverse proportion with the IDs array size
How Merkel trees helps here? Merkel trees helps to identify if an item belong to it, but I don't see how it will help to fetch results
THE NOSTR REPORT
💜HAPPY ZAPPENTINE’S DAY💜
Feb 14, 2023
Block Height 776,556
Moscow Time 44:91 ⚡/ $
—--------------------------
🎙️Quote of the Day🎙️
—--------------------------
#[0] “There are no bitcoin podcasts providing $130K worth of value every month. You are the yield.”
#[1]
—--------------------------
🚨Headline Nostr News🚨
—--------------------------
#[2] A blunder of wizardly proportions. Even 🧙Gandalf the 🍊Orange was no match for Nostr after he accidentally published his nsec instead of his npub on Twitter. He tweeted a new npub after discovering his mistake. https://twitter.com/BTCGandalf/status/1625540929821065247
#[3]
#[4] Asked twitter to post their npubs, 700 people responded 🤙 https://twitter.com/ODELL/status/1625015501700177920
#[5]
#[6] details how he uses ⚡Zeus⚡ wallet, Tail Scale and his ☂️Umbrel to quickly access his non-custodial lightning node.
#[7]
#[8] Could the answer to Jack’s GitHub replacement bounty be sitting under our 👃noses? Stu posits a way to use a multisig private key to create a repository of notes that could be extracted. Experts are weighing in.
#[9]
#[10] announces 9-million sats bounty for creation of a Nostr Marketplace. See post for details.
#[11]
#[12] talks at MIT about ⚡lightning addresses. Posts informative video providing a great explanation on the future of payments with ⚡lightning.
#[13]
—--------------------------
🏝️Nostrica Update🏝️
—--------------------------
#[14] announces #Nostrica is now fully booked. Nostrica in-person attendance is MAXED OUT! You can still join virtually. Visit https://nostrica.com for more info.
#[16]
—--------------------------
🖥️nostr Clients🖥️
—--------------------------
#[17] posts updates to Nostrgram and adds the ability to record 🎙️audio🎙️ directly into notes. #[18] tests it out!
#[19]
#[20]
#[21] Damus Build 2 🔥is out !!
#[22]
#[23] Snort now has pinned posts
#[24]
—--------------------------
🏃nostr Relays🏃
—--------------------------
#[25] says that ☂️ Umbrel is working on a solution that will sync the history of events to your private relay.
#[26]
—--------------------------
⚡nostr Business⚡
—--------------------------
#[27] DMNYC 🟠orange 💊pills his coffee guy. Time to 🟣purple 💊pill him too!
#[28]
#[29] Mutiny, a self-custodial Lightning wallet using Nostr to sign-up for their waitlist (the first as far as we know)
#[30]
#[31] The 69th node has just been admitted to #Nodestrich 🤙
#[33]
—--------------------------
💜ZAPPENTINE’S PICK UP LINES💜
—--------------------------
We asked for your favorite Nostr/Bitcoin pickup lines and you delivered! Here are a few of our favorites:
“Show me your NIP and I’ll give you access to my private relay.”
#[34]
#[35]
“Nice hash, wanna come back and tap my root.”
#[36]
#[37]
“Did you get zapped or are you just happy to see me?”
#[38]
#[39]
—--------------------------
🔥🔥Meme of the Day🔥🔥
—--------------------------
#[40]
#[41]
—--------------------------
Stay Classy Nostr.
Nostros has the option to push the historic to Umbrel since 2 weeks ago 😄
Los eventos tardan igual en llegar a cualquier cliente, pero todo es mucho más fluido y puedes seguir operando con la aplicación porque los datos pasados que ya recibiste están disponibles en tu local
Los clientes que no almacenan los eventos en base de datos propia van mucho mejor en épocas en baja demanda pero son inoperables en épocas de alta demanda.
El problema es que últimamente la solución que han estado aplicando estos clientes es añadir aún más relays para mantener así el tiempo respuesta, pero esto es simplemente algo que no escala desde el punto de vista del cliente, de ahí los reportes de drenaje de batería y clientes consumiendo 5Gb de datos en dos días.
Mi opinión es que llegará un punto que añadir más relays simplemente no funcionará, y el ancho de banda será el recurso escaso por el que los clientes tengan que luchar y gestionar.
Nostros since 2 days ago 😄
Acabo de descubrir esta herramienta:
https://github.com/jeremyd/nostr-contacts
Por si os interesa para hacer puntualmente backup de los follows.
🫂
Tenemos pendiente incluir un botón para esto, lo investigare para seguir el mismo formato y que sea compatible 🙂
Nope from here, I did quick search on the repos and none of the clients seems to be using that format, maybe a newbie?
¡Y cualquiera puede aportar! En Nostros siempre nos faltan manos 😄
Lo que es bonito es que nostr = Twitter es solo ras ar la superficie, se agradece que haya gente que solo lo quiera usar de esto porque supone parte de la masa que lo mantiene encendido. En el podcast con Luna en solo hora y media perdí la cuenta de la cantidad de ideas que sacamos que no tenían nada que ver con la "alternativa a Twitter" y donde funcionales que no aportan nada al shitposting son tremendas en otro campos.
Como se dice con Bitcoin, esto es solo el principio.
"El sentido común es por lo general lo que opina tu círculo más cercano de 7 personas"
Si eso es lo único que generas claramente está feature no es para tí 😄
I understand the problem paid relays are trying to fix.
But there are consecuentes. paid relays might end up being the worst case scenario for a centralised network, where the data of the most active users goes ruining away of bad latency and spam.
I think there is another way, I might be end up creating a NIPfl for that😄
What can be broken, should be broken.
And I''m also thinking on the size of `authors` it woul increase the size of the JSON by orders of magnitude