Kayhan Sepanta 🪽's avatar
Kayhan Sepanta 🪽
_@kehiy.net
npub1h49w...9kay
Co-founder at dezh.tech, raxva.net 🏰🪽
As I said in my last event I don't know what is the Nostrs scope in your mind. But as you know we are able to bring roughly anything over Nostr. I just find some of them that are not exist yet interesting: 1. 2FA apps: like Google authenticator. If we consider future Nostr based apps, we may lose the need of them, but currently they are widely used and keeping the secret on encrypted events over relays will be cool. 2. DOI: if you need a digital object indentifier, you need to ask a central authority to register it for you. Retarded. You can just publish an addressable event and keep your digital object data there. Then reference it with `d` tag + kind + pubkey combonation. (Kind me be ignored if someone make an standard(?) one). 3. Datasets and ML models: like hugging face that you can share these kind of stuff there, you can simply publish them in Nostr as a protocol, not a platform. 4. Version control system: we already have GIT out there, working great. But any version control system can publish its records and logs over Nostr like GIT. So we can keep track of there. 5. Journal articles and technical papers: you can publish them on Nostr without any permission and it can gain credit overtime by getting reviewed permissionlessly from different people. This one is a little more complex but I believe it's possible. Also I think we have similar or even exact stuff out there. Difference are subtle sometimes.
After the Nostr and removing author names from NIPs, it's the third time I agree with @fiatjaf. It's still not clear for me (even after reading this event and looking up previous workarounds) that how we exactly can achieve this without losing the interoperability and nuking the entire ecosystem that just works now. But I believe this repo is a bottleneck and it's bullshit. Free NIPs. The second thing is achieving this goal in any way makes me nervous about what if we ran out of kind numbers? How much stuff we expect Nostr to do for us? How many stuff we are going to map to the Nostr? This makes me believe in DMZ kinds even more! Also defining a way to post a Nostr spec as an event will be good as a solution, maybe just using traditional long form contents. View article →
Just got some cool idea for Jellyfish services. 👀 Feel free to guess it. It's a new feature over our NIP-05 names on nostr.eco.
Do you guys really don't believe the Apollo project? So, then earth is flat too.
Nostr MCP server: https://github.com/dezh-tech/doms/tree/main/nostr A MCP server that let a LLM to: * Post events with a nsec from config or a random anon nsec. * Fetch events using a filter. * Connect, disconnect and manage relays. * Get NIP-11 document of relays. * Fetch an NIPs content to understand it. * Decode and Encode NIP-19 entities. > In future versions I'll try to add a SSE mode + NIP-05 + Zap features.
What is the best option for email on personal domain? I care about privacy and low price. I can not self-host the thing at the moment. #asknostr