0xae65e700…46c0sent to0xb6d1eb1a…dab3·#19,216,276·view on Etherscan
(noun40 voting via agora)
had some time to think about this. i had this tweet and thread convo (https://twitter.com/hongkim__/status/1647654864858808321) about "mintReason" and wanting to give a way for our buyers to express why they bought a noun onchain. even then there was a view that bidWithReason is easier to do and might just fit the natural UX better b/c you have the attention of the bidder at the moment of bid rather than like a wall they can come back to to write something.
the concern with the bidWithReason view was that it wouldn't really lead to ppl writing substantial things b/c they don't even know if they are going to win. so it might lead to a playful bid comment as a in the moment type action but not really something that explains the WHY of why the person bought the noun.
looking at the result of bidWithReason having been launched in lil nouns i think most of that concern is true. there are mostly no comments or really short playful comments but the intended "capture useful information" goal that's expressed in this prop doesn't seem to have happened. also the way the comment is displayed in the UI wouldn't be conducive for anything more than a short comment.
if the goal here is to create space for a auction winner to say something meaningful that we can all give attention to (similar to propdates in a way) then i think we'd be better off with creating a UX where the winner (or just holder since someone can later buy at secondary too) can write something to the nouns world. gov clients like camp can show it on the activity page to give it attention. we could built sites that just show this information too. ofc the winner / buyer can just come say hi to the nouns farcaster channel which often does happen but increasingly as that space gets crowded a completely new user might not be able to say something that doesn't get filtered out by algos so having a onchain space does feel good to me. anyhow, i'm feeling that this doesn't really solve our need here.