Oddbean new post about login | logout https://github.com/nostr-protocol/nips/pull/1126
@IngwiePhoenix made a PR to close your Issue. Hope you don't mind.
Much appreciated! Had planned to do so too but completely forgot - must've gotten burried somewhere within my ~/work folder... ^^'
Corporates in censor-land social media are often semiautomated, and the human component is often plural and hierarchical, or even outsourced. I don't know if bot/not bot really captures the variability in note-sources. What decisions will people make based on this information?
It's an optional field and/or we can have a separate tag for individual notes. Just want to kick off the discussion, as it fits into the type of "reading" client we want to build and provides more information than we currently have. If they don't like the PR, we can change it, or they can refuse it.
I also would point out that npubs aren't rate-limited, or something. You can have a corporate bot and a human-led bot that replies to comments under the bot stuff. Or have - a project npub, that publishes release notes and stuff, (labeled as "bot", even if everything isn't automated) - a support npub, run by a group of people, that responds to questions or complaints - and then the developers have their own npubs You can create feeds that clearly separate things by source. That's less weird and creepy. 😅
If you have a Github account, please go there and tell me what you really think, even if you think it's a stupid idea. Thanks, in advance. nostr:note1a5z6asng4tj06uddnu6qkus8g584msld2kgr3plf3amal84wn3kq2jjpy2
i will check it out tomorrow and deliver my useless perspective 😂
🫶
I'm convinced that the perspectives of regular users are important to the success of the protocol. They often can think of benefits, use cases, or problems that developers don't see. And we should be aware of major changes evolving and why, so that we don't constantly get blindsided by seemingly arbitrary client alterations. That makes it feel more like chaos, than liberation.
i think better to add a whole tags field like the one in events, then we have options to put more data in there that doesn't have to be recognised by client or relay parsers so long as the syntax is correct
Thank you for commenting and reviewing. 🫶 I was nervous about my first PR, but I felt the Nostr love, fr. https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExamxocG1tdHM0cWJ2ODdwaGl6cTRsbHQwcTd3ZWtvaGdrbXA2aHdueSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/OoRYpoQy9uLss/giphy.gif
