Newsletter #25 fixes: remove Vector dup, fix dates, correct NIP-F prefix#98
Merged
Conversation
…t ISO dates to prose, correct NIP-F prefix explanation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three post-publish corrections to Newsletter #25:
Remove Vector v0.4.0 from Top stories — already covered in Newsletter Improve fetch_project_updates.py with commits, open PRs, and auto-detection #24 (Tor, NIP-46 signers, MCP, emoji packs, wallpapers, swipe-to-reply). Repeat coverage violates the no-duplication rule.
Convert all ISO dates (YYYY-MM-DD) to prose format in newsletter body — "2026-06-01" → "June 1", etc. Frontmatter dates remain ISO (Hugo requirement).
Correct NIP-F prefix explanation — NIP-F0–NIP-FF are plain hex-numbered NIPs (same as NIP-0A–NIP-0D), not "experimental NIPs awaiting numeric assignment." The 0–FF hex range serves as overflow now that 01–99 decimal is filling up. Verified against
nostr-protocol/nipsREADME.After merge: edit the kind 30023 long-form on Nostr using the same
dtag.