Avatar
Jason
eb3a338922741d7014d78ade8c53f138534b6603b032a8289b1cc9b645adfa83
Person who makes things.

Builders, the best builders, regard themselves as craftspeople; as creators. And just like any artist, we feel that our creation is never good enough.

Nostr demands that we be more than passionate craftspeople who love our work. Its sustainability demands that we also be pragmatic entrepreneurs. That we solve the challenges of incentives, revenue generation and equitable distribution of that revenue.

Unless we are retired, foregoing a family, living with our parents, etc. we have to monetize, or end up working for a person who does.

I restarted my computer after doing mine yesterday. Like a ceremonial cleansing of energy. 🧘‍♂️

Replying to Avatar jack

Yes

So I’m considering proposing the following NIP to introduce basic join support in relays to smooth out UX and simplify client code. Cameri was kind enough to take a look at it and raised the point that it might not get merged because it makes assumptions about relay tech choices (perfectly valid reason), but he didn’t want to deter me from putting it out there either. So I thought I’d ask non-relational db relay devs if they felt supporting the NIP would be problematic.

https://github.com/jason19710815/nips/blob/NIP-121-Basic-Joins/121.md

Any devs out there who have built a relay without using a relational database (including nosql varieties)? I’m looking to propose a new nip, but would like to get your thoughts before submitting a pull request.

Haha. Luckily… I love it. Look out for the 21 sat hot potato 🥔⚡️

It’s nascent. Still a lot to do. But let me know if you have any questions. This graph is great btw

Super bullish on this. Keep up the great work! 🤙