ManiMe on Nostr: Thinking about nip-89… Wonder if it the user recommendation kind could be ...
Thinking about nip-89…
Wonder if it the user recommendation kind could be “repurposed” to serve the end user “social” needs (recommending and rating of “best recommended” clients by user) AS WELL as “client discovery” by clients themselves.
What I mean is that event “content” could be used for user comments pertaining to the client being “recommended.”, and users could publish recommendations “per client” rather than just “per event kind”.
Problem is that kind 31989 is (by convention) “parameterized replaceable” keyed on the event kind being recommended.
WHAT IF a kind 31989 WAS NOT replaceable but a user could simply author as many as desired for a given “event kind recommendation”? This would open up possibility for so much more…
Thoughts?
I wonder if we could create some kind of a ‘whiteboard’ where folks could add their favourite updates or interesting things from the week? No idea how to do that or if it would just be abused… ? 🤔
Published at
2024-05-08 01:37:06Event JSON
{
"id": "a2c99a243c30203f92f24fc68859d0b9134c61df7a34cc4e9467325042a51226",
"pubkey": "df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200",
"created_at": 1715125026,
"kind": 1,
"tags": [
[
"e",
"81ac3861fc24ee2a53ab32101f5b4eae2dd529bf718accf977f1cfa2023b2a7a",
"",
"root"
],
[
"e",
"25841e1075f30315e2b590f5e9ca0e26c3fc968b3d651c414d3d443a976e904f",
"",
"reply"
],
[
"p",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"q",
"a1db13fa93a152f407507e238933c489e06ad3d08a8d225c5589446a3e7b3284"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "Thinking about nip-89…\nWonder if it the user recommendation kind could be “repurposed” to serve the end user “social” needs (recommending and rating of “best recommended” clients by user) AS WELL as “client discovery” by clients themselves.\n\nWhat I mean is that event “content” could be used for user comments pertaining to the client being “recommended.”, and users could publish recommendations “per client” rather than just “per event kind”. \n\nProblem is that kind 31989 is (by convention) “parameterized replaceable” keyed on the event kind being recommended.\n\nWHAT IF a kind 31989 WAS NOT replaceable but a user could simply author as many as desired for a given “event kind recommendation”? This would open up possibility for so much more…\n\nThoughts?\nnostr:note158d3875n59f0gp6s0c3cjv7y38sx457s32xjyhz439zx50nmx2zq5eswds",
"sig": "44d66a90ad8186a4d60b72d48308bc78e4bf36711203b6314836438b547f38a03209cbd025ba2953aec289c8b1027b07bce189279c1775b5a82d759651fbe9e7"
}
