Event JSON
{
"id": "c11da6d32716f73936f93cc532423633a7d27759e008f0caba5ba1ed7cbab987",
"pubkey": "fc0b10e1453d336192d4c4f2d09816d52ecdc6cbac526ed68e053a84405a1484",
"created_at": 1694534611,
"kind": 1,
"tags": [
[
"p",
"e06c1f25be1e23f1c90a88ce823dd8f2a2c167db37cd429ebc5e85c1c8414d0d",
"wss://relay.mostr.pub"
],
[
"p",
"26cad6f140bf86de9c26b7c15419cab1aebdd7086358d26aa2d750e21cf3bf2e",
"wss://relay.mostr.pub"
],
[
"e",
"728b81dd68f79d72600bbde5ec748e0a51e8efc3367483ef849e33545ca3dee3",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/almenal99/statuses/111053020290389248",
"activitypub"
]
],
"content": "nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy what's the target audience? If you accept suggestions, I think having the commit names in chronological order might help (so first a111, then b222, then c333, etc). I find it tricky enough that arrows point to the previous commit, since I intuitively think of arrows as chronological order, but I get that it's conceptually wrong. However, I think \"chronological\" names could alleviate that confusion\n\nJust my two cents :)",
"sig": "4c4fba337afc832f442c2e487b890e553f37e0fbf0d6ecf0f99375e5bd42bc1a02d86776be825a3c8971fb7b421aa38d684acb028c05f6a89c86ea4949a9a7fb"
}