# By Jon Staab (1) and others
# Via fiatjaf
* origin/master:
nip01: remove misleading markdown example.
Rephrase Markdown special rule
Update old link to fiatjaf/nostr
Clarify how NIP 45 works with multiple COUNT filters. (#504)
# Conflicts:
# 01.md
# By frbittencourt (14) and others
# Via fiatjaf_
* origin/master: (23 commits)
Update 01.md
fix: re-add NIP-15 to the list
Add NIP-94 and kind 1063 to README.md
nip update to reach consensus with other nips
fixed text description
Apply suggestions from code review
change to regular event
Update 94.md
Update 94.md
Update 94.md
Update 94.md
Update 94.md
move nip-95 to other branch
ajusts description of decrypt tag
ajusts decrypt tag
ajusts formt text
minor fix
fix example image
fix format text in md
add hash tag
...
# Conflicts:
# 01.md
- "random" is not an accurate description
- I've noticed long (sha256 hashes in hex) being rejected by some relays. So there seems a need to specify a max length.
- "non empty", cause an empty string could be interpreted as `null`
To be decided:
- Max length number
- Are `subscription_id`s case sensitive?
- Will `subscription_id`s be white space trimmed?
Most implementation ignore this line. Enforcing that usernames not include spaces, special chracters, unicode, emojis, etc has no benefit and is unnecessarily user hostile.
It appears the regex given in NIP1 for setting the username in the setmetadata event was slightly off. I think the fix here is what was intended. Though I think what was meant here was pretty obvious, to make it easier on future developers, I updated the regex to something that should work with just copying and pasting.
