There is no Official Lexicon Committee. ATProtocol Lexicons are much more decentralised that Nostr NIPs and Kinds (at least in the current PR and merge context). Any ATProtocol dev team can just create a lexicon shrink-wrapped to that team's already well-formed application design. Any other team can use that lexicon. Groups are free to get together to discuss lexicon norms before embarking on similar projects. Lexicons can't be deleted. Lexicons are backwards and forwards compatible. Any one lexicon can reference any definition in any other lexicon in an open manner.
It makes sense that it's a better thought out system. The team that designed lexicons had years of painful experience trying to clean up interop messes with SSB (very much resembling the interop messes we have on Nostr now) and this is their fresh "take two". Nostr is repeating many of the mistakes of SSB and now what we're seeing is lots of suggested ways to fix these mistakes, most of which are evolutionary steps towards the ATProtocol lexicon system anyway—so why not just skip up the evolutionary ladder and import the whole finished system? At least that's my take.
JoeRuelle / Joe Ruelle
npub1hy…wtqnx
2025-03-30 08:25:00
in reply to nevent1q…csne
Author Public Key
npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnxPublished at
2025-03-30 08:25:00Event JSON
{
"id": "68d01ef9df45e343e5f504e2bea48b0a4cc526e5ec2428e4c45b88d3d8ac3c09",
"pubkey": "b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823",
"created_at": 1743323100,
"kind": 1,
"tags": [
[
"e",
"2fce773d43cd47c008aee0728e626cd0a6f99aa097f36d079bb94903fb340aa3",
"wss://puravida.nostr.land/",
"root",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93"
],
[
"e",
"03af74107e4357688fb0c7ab0e6e066198d2446844d3fead74b0874b3934fff9",
"wss://relay.primal.net/",
"reply",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93"
],
[
"p",
"592295cf2b09a7f9555f43adb734cbee8a84ee892ed3f9336e6a09b6413a0db9"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
]
],
"content": "There is no Official Lexicon Committee. ATProtocol Lexicons are much more decentralised that Nostr NIPs and Kinds (at least in the current PR and merge context). Any ATProtocol dev team can just create a lexicon shrink-wrapped to that team's already well-formed application design. Any other team can use that lexicon. Groups are free to get together to discuss lexicon norms before embarking on similar projects. Lexicons can't be deleted. Lexicons are backwards and forwards compatible. Any one lexicon can reference any definition in any other lexicon in an open manner. \n\nIt makes sense that it's a better thought out system. The team that designed lexicons had years of painful experience trying to clean up interop messes with SSB (very much resembling the interop messes we have on Nostr now) and this is their fresh \"take two\". Nostr is repeating many of the mistakes of SSB and now what we're seeing is lots of suggested ways to fix these mistakes, most of which are evolutionary steps towards the ATProtocol lexicon system anyway—so why not just skip up the evolutionary ladder and import the whole finished system? At least that's my take.\n",
"sig": "4ec265747e6895bbe4a6dabde0bd6cc6810cdb3d30ebb6d05234714938af46c81688d94f5255eb77066153cdf89de2f5e1cf7d431ead96bad595a97b6c13f5c1"
}