We're all somewhere on the journey. I'm happy to answer questions any time if I happen to be further along a particular branch of the path.
In case it's interesting to you, what I meant in non-dev speak is:
Say I have some new Event Kind I want to introduce. I have in mind a handful of ways the kind might be used in an **eventual** app. I want to check that the design of the kind I have in mind will support those features. nak is basically a bare-bones nostr client - simple requests and simple responses all in text only - so if I have a relay running that understands my new Kind, I can use nak to make sure that the kind of requests I would send to the relay do what I hope.
Since it's a CLI tool, once I have a little collection of interactions tested out in nak, I can basically write those commands into a script (with a bit of extra diagnostic printout, etc.) and now when I run that script it either goes well: "okay great, the Kind makes sense, the relay handles it properly, and the user interactions work like I thought" or things fail and I can look into it further.
That "happy path" (the minimal actions a user might take in order to basically use the new features. not yet taking into account errors or weird edge cases, etc.) then acts as a kind of proof and assurance that "upgrading" those features into a client app UI is worthwhile and will work well.
In a nutshell: that "prototype with nak first" approach is like 1,000x faster to whip up than going straight from Idea -> UI. And sometimes you falsify some hypothesis you had really early and don't waste your time determining which color your buttons should be :)
vinney
npub19m…8axkl
2025-05-08 17:08:33
in reply to nevent1q…gvl2
Author Public Key
npub19ma2w9dmk3kat0nt0k5dwuqzvmg3va9ezwup0zkakhpwv0vcwvcsg8axklPublished at
2025-05-08 17:08:33Event JSON
{
"id": "89904e8e5334a21dc9557843e37039fbd97a5ce4a61613cf795dc5e0ec2b1b76",
"pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
"created_at": 1746724113,
"kind": 1,
"tags": [
[
"e",
"ac63b28f8b6fdadebb84e5375910d7cdce711e81b5ed9f6fce4e33f451c421ad",
"",
"root",
"2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331"
],
[
"e",
"c830ac02cd2911ebd55da7a0b22735c6d3c5d737d895d62c33ab261964299865",
"wss://relay.damus.io/",
"reply",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"p",
"16d76f262b689bb1a33faa2df954dbe7ac717937fad4765a05ddfae3dac92856"
],
[
"p",
"e8ed3798c6ffebffa08501ac39e271662bfd160f688f94c45d692d8767dd345a"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
]
],
"content": "We're all somewhere on the journey. I'm happy to answer questions any time if I happen to be further along a particular branch of the path.\n\nIn case it's interesting to you, what I meant in non-dev speak is:\n\nSay I have some new Event Kind I want to introduce. I have in mind a handful of ways the kind might be used in an **eventual** app. I want to check that the design of the kind I have in mind will support those features. nak is basically a bare-bones nostr client - simple requests and simple responses all in text only - so if I have a relay running that understands my new Kind, I can use nak to make sure that the kind of requests I would send to the relay do what I hope. \nSince it's a CLI tool, once I have a little collection of interactions tested out in nak, I can basically write those commands into a script (with a bit of extra diagnostic printout, etc.) and now when I run that script it either goes well: \"okay great, the Kind makes sense, the relay handles it properly, and the user interactions work like I thought\" or things fail and I can look into it further.\nThat \"happy path\" (the minimal actions a user might take in order to basically use the new features. not yet taking into account errors or weird edge cases, etc.) then acts as a kind of proof and assurance that \"upgrading\" those features into a client app UI is worthwhile and will work well. \n\nIn a nutshell: that \"prototype with nak first\" approach is like 1,000x faster to whip up than going straight from Idea -\u003e UI. And sometimes you falsify some hypothesis you had really early and don't waste your time determining which color your buttons should be :)",
"sig": "5b25f004783b2121db7f22948f4102f8ade94decdbd24c4db71b609bacee77871f4eb7d36459763c672b5cad8b1975b00e315e1aa3f9cab9fa98721d7aac43d3"
}