> 2. Sharing other people's stuff - several options.
>
> You can allow general reposts in your community and just put the ha tag in that event (that would be the Targeted Publication thing but without needing a new event kind).
That sounds like a good approach. Since (at least for me) this might be a common use case, can you imagine this being added to the spec? something like a best practice section for common use cases?
(could for your spec and add, but then again, hard to track when you make updates, something like a git based way for spec development would be nice. something like ngit but with similar things like github action and after each commit or merge in main a new spec version is published)
laoc42
npub1r3…xt9ma
2026-03-19 10:23:57 UTC
in reply to nevent1q…927q
Author Public Key
npub1r30l8j4vmppvq8w23umcyvd3vct4zmfpfkn4c7h2h057rmlfcrmq9xt9maSeen on
wss://relay.damus.ioPublished at
2026-03-19 10:23:57 UTCEvent JSON
{
"id": "fab641298cbe77e5f6107ca6df4046b8cb4ae766a79d34228259f1f74ef86b66",
"pubkey": "1c5ff3caacd842c01dca8f378231b16617516d214da75c7aeabbe9e1efe9c0f6",
"created_at": 1773915837,
"kind": 1,
"tags": [
[
"e",
"6f23b0436c897ed3c435bb0ae5195724a9370ca194caaf033cbb5c1cfb488f28",
"wss://relay.damus.io/",
"root",
"1c5ff3caacd842c01dca8f378231b16617516d214da75c7aeabbe9e1efe9c0f6"
],
[
"e",
"230bf3e6913208fb5ce6022471fd37221ee3164a77f92d646f044e4cbcc8c136",
"wss://theforest.nostr1.com/",
"reply",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
]
],
"content": "\u003e 2. Sharing other people's stuff - several options.\n\u003e \n\u003e You can allow general reposts in your community and just put the ha tag in that event (that would be the Targeted Publication thing but without needing a new event kind).\n\nThat sounds like a good approach. Since (at least for me) this might be a common use case, can you imagine this being added to the spec? something like a best practice section for common use cases?\n\n(could for your spec and add, but then again, hard to track when you make updates, something like a git based way for spec development would be nice. something like ngit but with similar things like github action and after each commit or merge in main a new spec version is published)",
"sig": "02e5c4ea8bbc8ce7913ab89e65827f76a51198e959bea9e1698f929563cf56d0a420887d6c9626b751c2d2d7561dd7a3ad2b116fc0295694679ed60f1086894a"
}