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 

 Maybe put the torrent in the same note as the release note? 

 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 

 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. 

 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 

 Here it comes Other Stuff:
- Release Notes
- Torrent file

nostr:nevent1qqsqqqqcv29r062gg8tsa25czs2xf534jnhxmf4g3np40x6akkflcrqppemhxue69uhkummn9ekx7mp0qgsq4gu7tthengqq577mpdyezkxf90z25g8mvkf355ks2k67km0lwwqrqsqqqqqpe6yl8t 

 Looking good! https://image.nostr.build/db738dacbfa82c75a7f5522f6e15acabffd5ec7b0370ba437770ff0d252de793.jpg 

 I see that the magnet link includes tracker info, but the Nostr note does not. How does that work?