I had a couple of ideas for protocol additions/improvements I thought I'd run past everyone here.
Channel Message Improvements
Adding a new txt_type for NOTICE. This is borrowing from IRC, where if you are sending notifications or replying from a bot it is sent as a NOTICE which shows up as a different text color and/or formatting. Bots are also expected not to respond to NOTICE messages to avoid command loops and such. Simpler clients can just show the text normally like any other message or prefix it with some indicator or whatever.
I can't speak for anyone else, but I'd really like to see the sender's username and the actual text of the message in separate fields instead of in "username: text" format in a single string. It would be nice to have the sender's pubkey_prefix too, maybe as an optional field so users don't have to include it if they don't want to?
Direct Message Improvements
Same as in channels, adding a txt_type for NOTICE.
I had a couple of ideas for protocol additions/improvements I thought I'd run past everyone here.
Channel Message Improvements
Adding a new txt_type for NOTICE. This is borrowing from IRC, where if you are sending notifications or replying from a bot it is sent as a NOTICE which shows up as a different text color and/or formatting. Bots are also expected not to respond to NOTICE messages to avoid command loops and such. Simpler clients can just show the text normally like any other message or prefix it with some indicator or whatever.
I can't speak for anyone else, but I'd really like to see the sender's username and the actual text of the message in separate fields instead of in "username: text" format in a single string. It would be nice to have the sender's pubkey_prefix too, maybe as an optional field so users don't have to include it if they don't want to?
Direct Message Improvements
Same as in channels, adding a txt_type for NOTICE.