đ¤ I'm thinking about how to group these kind of events with ...

liminal đĻ
npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf
hex
e5c1011ccfdb37738c830f901041a7f6ac3998170938b67567e633bc0debf0e0nevent
nevent1qqswtsgprn8akdmn3jpslyqsgxnldtpenqtsjw9kw4n7vvauph4lpcqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcps2uqlhrKind-1 (TextNote)
âŗ Reply to Event not found
4e69b8289e99bdd64db42aaba2d566cda686009a16e890a7ebcb6ef35ccdfe51...
đ¤ I'm thinking about how to group these kind of events with minimal context. Nostrub organizes for a specific grouping even if it doesn't have a "spec" tag.
To be adversarially interoperable, you could add in that client tag to work with the grouping, and your events will show in nostrhub if the client filters by client. It would be nice if everyone confirmed to some pre agreed label, but we can just make connections this way without asking others to adopt a different scheme.
Raw JSON
{
"kind": 1,
"id": "e5c1011ccfdb37738c830f901041a7f6ac3998170938b67567e633bc0debf0e0",
"pubkey": "dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06",
"created_at": 1772262131,
"tags": [
[
"alt",
"A short note: đ¤ I'm thinking about how to group these kind of e..."
],
[
"e",
"0110aa4b38001e92556fe174cf26feb0df4afa6b1a91e7e11c749d86fe7e5b7b",
"wss://nostr.land/",
"root",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"e",
"7c3377e01d1555a8b58099dbd7ef401634c3d0d8713c4b5737f26f0f97cb240d",
"wss://theforest.nostr1.com/",
"",
"dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06"
],
[
"e",
"4e69b8289e99bdd64db42aaba2d566cda686009a16e890a7ebcb6ef35ccdfe51",
"wss://theforest.nostr1.com/",
"reply",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06",
"wss://theforest.nostr1.com/"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"wss://theforest.nostr1.com/"
]
],
"content": "đ¤ I'm thinking about how to group these kind of events with minimal context. Nostrub organizes for a specific grouping even if it doesn't have a \"spec\" tag. \n\nTo be adversarially interoperable, you could add in that client tag to work with the grouping, and your events will show in nostrhub if the client filters by client. It would be nice if everyone confirmed to some pre agreed label, but we can just make connections this way without asking others to adopt a different scheme.",
"sig": "a58d1c997a048347f7c60c744e962a0e780976d6f19e1dc33e5e5a61ece5c8842570dd7af33fbb6e62ace1462645c60d8d25640ced8424739e4a88eb57965e22"
}