Rabble on Nostr: I think if we do a flexible system with free form we should also define in the nip ...
I think if we do a flexible system with free form we should also define in the nip the conventions that a bunch of nostr apps are using in order to make it easier for those who want to support new fields to know the naming.
Like for the ethereum folks is it eth.address or ethaddress or eth_address?
Alex (npub1q3s…d26p) ’s proposed nip should be popular because it’ll allow support for linking to every kind of crypto wallet address. ;-D
Published at
2024-11-20 19:08:47Event JSON
{
"id": "c827b8095f89c3aa18f3920a629252050a7108f14ca6fef06887864b702b23a2",
"pubkey": "76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa",
"created_at": 1732129727,
"kind": 1,
"tags": [
[
"p",
"0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd"
],
[
"p",
"e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
],
[
"e",
"a4b4563cd7bc8b084a1d2fb3a89706a236b87c8a4d516b49c3eac20d0e83bad4",
"",
"root"
],
[
"e",
"daca9ef381da25f6025aee5a9c55a0ead29cbd10c9bbc399da93888be141b379",
"",
"reply"
]
],
"content": "I think if we do a flexible system with free form we should also define in the nip the conventions that a bunch of nostr apps are using in order to make it easier for those who want to support new fields to know the naming. \n\nLike for the ethereum folks is it eth.address or ethaddress or eth_address? nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p ’s proposed nip should be popular because it’ll allow support for linking to every kind of crypto wallet address. ;-D",
"sig": "47da3beb65668ed07deb39ad4218e4e5d1351bd65a54e62f03dd348cbef20fe9bce790222ed563e0c4ed0a2425987ee0cdc3d9aa326d00245de11218bd65a599"
}
