Event JSON
{
"id": "060009431311184245e6999672c11d199ac4888f7dc4a15d97fe77042b7ac2a5",
"pubkey": "c3e23eb5e3d00f18b2f4f588d8cdbc548648be761bdd90812186df4603d7caa9",
"created_at": 1746211881,
"kind": 1,
"tags": [
[
"p",
"3d2e51508699f98f0f2bdbe7a45b673c687fe6420f466dc296d90b908d51d594",
"wss://nos.lol",
"mention"
],
[
"e",
"1e799d98835ee94a061bf0c709f1c8ca288c5c859951e8e38f23b0e88b2ac7b3",
"wss://nostr.oxtr.dev",
"root"
],
[
"r",
"wss://bitcoiner.social/",
"write"
],
[
"r",
"wss://relay.damus.io/",
"write"
],
[
"r",
"wss://nos.lol/",
"write"
],
[
"r",
"wss://relay.primal.net/",
"write"
]
],
"content": "Thanks for pointing out that small pools benefit from less strict mempool policy nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy0hwumn8ghj7mn0wd68yttjv4kxz7fwvf5hgcm0d9hzumnfde4xzqpq85h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qtyz2zr . I hadn't considered that. \n\nDo you think Bitcoin core could benefit from moving the social interactions around the repository to nostr? gitworkshop.dev features nostr based pull request and issue management for instance.",
"sig": "f1ac093a2645533571aa7005f998d62f2f8d0a943c487749be7e22f0387e7459ccdddde78a106fd7dd8ede530d9a881a9c8c92fa7e697c043b4b8d13ed02c92a"
}