Not parsing response message for share locks

[skirwan]

william jacocks: interesting when /share /lock is used…. You lock sharing your experiences with Creed.
¬dd¬shYou begin sharing your experiences with ¬pnCreed¬pn.
You lock sharing your experiences with Lorikeet.
¬dd¬shYou begin sharing your experiences with ¬pnLorikeet¬pn.
You are sharing experiences with Creed () and Lorikeet ().

https://clieunk.slack.com/archives/C018PCWS9T2/p1599934119022200

Skirwan

Fun CL fact — almost every message from the server is tagged like that — clients parse them to extract state changes (And I think at some point someone had ideas for a far richer client experience than we’ve got today). I’ve got handlers for most but not all. Anyway, info and share messages sometimes get prepended with ¬dd and I cannot for the life of me figure out what the DD is for. Do you know <@U0193HD1CAX> ?

Del‘Arus

I think they stand for Don’t Display. At least I handle them that way. So use the content and update internal state, but don’t show the message itself.

Skirwan

Interesting. Thanks!

william jacocks

thank you!