A client simply isn't enough. If I needed to collect lists manually, I have better "devices" (see: applications) to do so.
What nested NIP-51 lists would allow for is enabling entire protocol to have organized, managed lists.
Let's say I build a client for "managing friend lists," well, I've really just built a "list managing client."
This is basically a hindrance for any application that wishes to have modular list organization.
Nostr needs to manage lists natively.
Tekkadan š
npub12zā¦q99h8
2024-03-28 22:45:12
in reply to nevent1qā¦2zsm
Author Public Key
npub12zqf55l7l9vsg5f6ssx5pq4f9dzu6hcmnepkm8ftj25fecy379jqkq99h8Published at
2024-03-28 22:45:12Event JSON
{
"id": "8f3585d4bf74771807cf1f0ab3d72134451bea31f73d93141cd79bf3c9f5c7bd",
"pubkey": "50809a53fef95904513a840d4082a92b45cd5f1b9e436d9d2b92a89ce091f164",
"created_at": 1711665912,
"kind": 1,
"tags": [
[
"e",
"eaa180bb545efa77646bc7609cdf5e985d4a295aa8be0b5dd40ac39b43c2049a"
],
[
"e",
"25e336c9c8c9d1a3e363defc5fccb364cf03051638ca03b30c4369a9915d6941",
"",
"reply"
],
[
"p",
"50809a53fef95904513a840d4082a92b45cd5f1b9e436d9d2b92a89ce091f164"
],
[
"p",
"bb3555be5f416a17ac20d0b07d8f14b1137139d33a4c1d6eb4939b3287698522"
],
[
"a",
"30023:50809a53fef95904513a840d4082a92b45cd5f1b9e436d9d2b92a89ce091f164:1711430123292",
"",
"root"
]
],
"content": "A client simply isn't enough. If I needed to collect lists manually, I have better \"devices\" (see: applications) to do so.\n\nWhat nested NIP-51 lists would allow for is enabling entire protocol to have organized, managed lists.\n\nLet's say I build a client for \"managing friend lists,\" well, I've really just built a \"list managing client.\"\n\nThis is basically a hindrance for any application that wishes to have modular list organization.\n\nNostr needs to manage lists natively.",
"sig": "c81b583a401625c7e55df8bfb67c57912b4ed73e8fe8b41a9f34159110d63229c6b4c22e8a6f97d818279e04ee40a28f6e7671b4341cbb4f3920a1aa90864b60"
}