RE: NIPs, implementations and compatibility.

Specs are hard. They often are unclear and miss edge cases. It’s why the only Bitcoin consensus spec I trust is the Bitcoin core source code - no written documentation or alternative project.

Nostr is moving at such a pace, and development individuals and teams are all self-funded, and frankly keeping up with their own development roadmap is hard enough - let alone trying to keep up with the latest NIPs; either draft NIP input, awareness around proposals, and where the most difficultly lies.. supporting NIPs that break user-space and create a negative user experience and feedback.

Solutions.. not sure exactly. But here are some ideas.

1. A regular 7-14 day reoccurring NIPs updates and presenting via community open video call session.

2. Implement breaking changes in smaller isolated test/POC projects - and not directly into popular app beta builds.

3. Difficult to say.. but perhaps slow down. We have major fundamentals in Nostr that are not great today.. we scrape by. Building on rocky foundations is a future curse - much works pretty well too.

4. Understand that creating work for other devs who are already struggling to keep up, builds more stress and tension.

I have around 500 TODO comments across my Nostr projects… some easy and some hard. It’s not easy to keep up.

Made the mistake of glancing at Twitter - sooooo depressing. I don’t know how people last there …

🤡

“Why should I sign up for nostr?”

What’s your answer?

#ChatBTC idea 💡

To build a powerful Bitcoin chatbot & LLM system that will actually impact skeptical humans, we need a comprehensive database of Bitcoin videos, podcasts, articles & content that's been converted into text & contextualized for keywords & subjects.

We can then use this data not only to train the LLM, but more importantly to help the chatbot refer people to other humans giving them relevant answers.

Think of the benefits of perfectly recommending content (with specific time stamps in videos) based on what people are discussing, in-line. This hand-off is a natural thing we all do when orange pilling.

It will be much more effective to refer someone chatting with the bot to a timestamp of Michael Saylor discussing a subject rather than having the AI bot give the point.

By having a database of all Bitcoin content, the LLM can refer people to real Bitcoin experts more effectively & I believe the conversion rate from bit curious to bitcoiner will be much better.

Which nip deals with shared relay lists then? That’s one of the issues with nostr, so much effort is put toward completely irrelevant crypto related work that has absolutely zero to do with a censorship resistant social network.

I’ve heard of several ppl losing followers after removing relays though. Isn’t there a nip that talks about publishing your relay lists to relays so ppl can find you? Clients should just add them or ask you or something so you don’t lose track of ppl you follow.

Bluesky vs Substack Notes

I wonder if anyone understood ₿itcoin from their initial encounter? I know I sure didn’t, sadly.

Apologies for misunderstanding, my bad. Yeah, the fiat is that we try to do more than we should, and this will not work. 🐶🐾😭

No, and no! Data are downloaded but the amount matters, a lot! Also, phone, vs tv, vs tablet, vs computer, vs wifi, vs mobile, vs 3g, vs 5g, vs dial up, etc. is a huge difference. Hashing entertainment media is a no go, DRM also plays role (some artists might want to use it, freedom right). Hash doesn’t belong here in Nostr protocol, and that’s where I draw the line. 🐶🐾🫡

Same can be said for any website! What’s the difference? Do you want to download hundreds of images 1Mb each? Daily? Video is even worse! 🐶🐾🫡

I think the concern is reputational risk. If you promote something with an image and then the image gets swapped by a third party, now it looks like you're promoting something you didn't. It's not too hard to see the damage this would cause, especially if your followers get scammed.