Oddbean new post about | logout
▲ ▼
laanwj | 1 months ago (raw) | root | parent | reply | flag +9 
 this is a complete release announcement and download without reference to either github or bitcoincore.org

(the idea is to automatically generate this from the yaml descriptor https://raw.githubusercontent.com/bitcoin-core/bitcoincore.org/refs/heads/master/_releases/28.0.md )

still working on it; it would, for example, make sense to put a reference to the torrent event directly in the release notes
▲ ▼
provoost | 1 months ago (raw) | root | parent | reply | flag 
 Maybe put the torrent in the same note as the release note?
▲ ▼
laanwj | 1 months ago (raw) | root | parent | reply | flag +3 
 in the same event? that wouldn't work, torrents are kind 2003, whereas markdown notes are 30023

however, markdown notes can reference other events through the normal link syntax and "nostr:" scheme, so adding a reference would be straightforward
▲ ▼
provoost | 1 months ago (raw) | root | parent | reply | flag +2 
 Ah yes, in that case it makes sense to have the release notes link to the event. And if l the  🧲 URL is in the release notes that's a nice fallback.
▲ ▼
laanwj | 1 months ago (raw) | root | parent | reply | flag +1 
 i've experimented a bit with nostr: URLs in the markdown, but this embedding doesn't seem to be handled great in clients (nostrudel generates a unusable link back to itself, habla keeps the nostr: link assuming that the browser will handle it...)
even though NIP-23 explicitly mentions this

so yes, putting in the magnet URL directly makes more sense for now