Avatar
Gzuuus
40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451
Forever learning, continuously buidling⚡ cryptoanarchism student https://nostree.me/gzuuus #noderunner#Bitcoin | #technology | #art | #electronics

Spring brings the rain,

With winter comes pain,

Every season has an end.

I tried to remove it and that added it again 🤣

Replying to Avatar Gigi

GM

Sorry about the pepe reaction, fat finger 😅

Replying to Avatar Gigi

GM

Gm gigi 🧡

Lo haré en cuanto pueda 👌

Replying to Avatar Noshole

Hahaha seems that bubbles have some work to do

Happy new year everyone, new year, new GMs 🧡

Hey pues actualmente solo se pueden añadir a mano, puedo darte una si quieres, que nombre te gustaría? Idealmente esto se podría hacer a través de un formulario, pero debería de hacerle un buen mantenimiento a nostree para eso. De momento te puedo añadir manualmente 👌

Si, hace tiempo que no le doy un mantenimiento, pero debería funcionar sin problemas 👌

Nostr is awesome 🧡

I was testing with amber for android, maybe that is an easy way for you to debug👌

Replying to Avatar Sebastix

Hmm there is a MySQL extension 👀

https://duckdb.org/docs/stable/core_extensions/mysql

So I guess I can use this extension to make a (second) db connection available for NSD within nostr:npub1kdstrkmhv0yx8pdqcf9ed8l26752gqprx68twg7qp5nsd7qtegnsr3nsze 👀?

yes, i think the correct way would be to create a duckdb instance, use the connect method from nsd to instantiate it, and then with the same connection use the mysql extension to read or perform operations in the other db. you will have your mysql db and other duckdb db wired up by the same connection. i'm implementing something similar in relatr but in a single duckdb db, to have the nsd tables and other relatr specific metadata tables in the same db using a shared connection, as it is how duckdb recommends to manage concurrency. That also gives me the possibility to use the nsd tables to do any sql query crossing all

you can just clone the repo and play with it, it has a small social graph in jsonl and duckdb, which is used mainly for ci. but you could use it as is, or get a bunch of kind 3 events and make it ingest them. then you can do social graph queries. the main reason for this library is that it will be the core of relatr, so that serve as a demo :)

Hey thanks! :) Yes, I really like what they are doing. There are so many things and ideas to do around this piece of software. Yes, I saw that they organize meetups, that's awesome, especially if you are close by.

Let me know if you play with the NSD. Contributions are welcome! I'm thinking about adding mute lists support as well.