Oddbean

Yeah that's the best thing about Nostr, its very flexible. You don't really have to exactly follow the protocols as defined. You can leave the NIPs. You can even make many changes on client side without break the protocol. In the future, if we have consensus, we can implement a new NIP alternative to the current NIPs. So that is one plus point of Nostr. It's very flexible, unlike Bitcoin.

Yes So if someone using proposed NIP which is not adopted by others - that's fine too so long some relay <-> client has implemented it - it doesn't break/interfere with others - that's another good this about nostr - optional to few who finds it suitable for their use!

Yeah, Nostr in itself is very different from Bitcoin. Apart from the Bitcoin libraries it uses to generate public and private keys, everything else is very different. Nostr is very versatile; you can do a lot of experiments on it, this is the exact part that makes devs so excited about it.

You only need a client to publish a new event, and a relay to accept that event. Anyone connected to that relay, using a client with an interface to display the new event, will be able to see it. You can even have your own relay attached to a client; in that case, you don't need relays to accept your new event.

You're welcome to have your own island. Make a Jackson Pollock of an App, and do what you want. However, you're now responsible for any issues with the island and you're not going to have anyone else's support because you don't speak the common language.

That depends. Suppose the event is genuinely useful; anyone can build an interface to display it in their client and connect to the relay. This way, all apps across the network will have access to those events and the feed.

That's where the "protocol" comes in; clients have agreed to index and broadcast events, such as notes, follow lists, and profile data, in a predetermined manner. This cooperation is between the client and relay, as they both follow the same protocol. Here's a fun fact: you can add "tags" to events, providing additional information. You can use this new tag info to create variations of the same kind of event, while other clients can choose to ignore it. Example of event structure. https://image.nostr.build/049ae86040c4bbb5ee2334310ed785ba9287d491b0520202493aaa0010925dfe.jpg#m=image%2Fjpeg&dim=1080x1902&blurhash=%5D384Sst%2B00%23UDiTLt7rqW%3DbFl.%252z%3BJ6IovfR*E%24xHxu%3DuX8ENr%3FspR%24WBs%3Bt6j%5DIns%3BxbNZbb.8n%2BRPX7NGrYNuNa%23%3Axa&x=c532b7722ace8e456f86a6496250858012dc3a735b4cd1fd705a9cfa8716e6c8