How being "flexible" can bloat a protocol (a somewhat absurd example, but you'll get the idea):
Iimagine some client decides to add support for a variant of nip05 that checks for values at /.well-known/nostr.yaml besides /.well-known/nostr.json. "Why not?", they think, "I like YAML more than JSON, this can't hurt anyone".
Then some user makes a nip05 file in YAML and it will work on that client, they will think their file is good since it works on that client. When the user sees that other clients are not recognizing their YAML file, they will complain to the other client developers: "Hey, your client is broken, it is not supporting my YAML file!".
The developer of the other client, astonished, replies: "Oh, I am sorry, I didn't know that was part of the nip05 spec!"
The user, thinking it is doing a good thing, replies: "I don't know, but it works on this other client here, see?"
Now the other client adds support. The cycle repeats now with more users making YAML files, more and more clients adding YAML support, for fear of providing a client that is incomplete or provides bad user experience.
The end result of this is that now nip05 extra-officially requires support for both JSON and YAML files. Every client must now check for /.well-known/nostr.yaml too besides just /.well-known/nostr.json, because a user's key could be in either of these. A lot of work was wasted for nothing. And now, going forward, any new clients will require the double of work than before to implement.
Twitter was only successful because it didn't use Markdown.
That is not inevitable at all.
If most clients do not support Markdown it will make no sense for some new client to come up and start writing and reading Markdown everywhere, it would be extra awkward.
That's the guy who made our worst enemy: the Ed25519 signature scheme.
Someone was asking for this some days ago (#[0] do you remember who?), so I added it to the NIPs repo README: https://github.com/nostr-protocol/nips#standardized-tags
A list of standardized tags in use. Please send fixes and additions.
Nostros looking better every day.
#[0]
Except that I can't login because the landing page icon is too big so I can't click the button on the bottom.
Why can't they just post the URL directly? The []() thing is so awful.
Crossposting is lame. It is better to write different things for different audiences. #[0]
But if someone is going to do a crossposting tool, make sure it posts from Nostr to Twitter and not the other way around!
Ha! #[0]
I don't know how to tag the guy who wrote nos2x-fox. Are you using that or the normal nos2x?
Important stuff: #[0]
#[1], NIP-05 validation is failing for #[0] on https://github.com/mikedilger/gossip. Why? It is valid, I've verified it manually. I've triggered a metadata reload but nothing happened.
NIP-21 unceremoniously merged: https://github.com/nostr-protocol/nips/blob/master/21.md
We need someone to make a curated list of Nostr things -- not just a list of all Nostr things.
Maybe do a weekly newsletter or something like that.
I don't know. I am getting lost with so many things happening. I imagine there are people more lost than me.
What do you think of these ideas, #[0]? https://t.me/nostr_protocol/77753
Is this really good? #[0]
I dislike the logo so much I can't bring myself to experimenting with it.
https://notes.blockcore.net/ has a button to copy follows from any account.
https://nostr.band/ has a thumbnail profile picture server: https://media.nostr.band/thumbs/459d/3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d-picture-64