Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

RFE against certain Humiliating situations

by Skeeve (Parson)
on Sep 05, 2003 at 10:19 UTC ( #289153=monkdiscuss: print w/replies, xml ) Need Help??

Do you use Cassiopeia webchats?

Did you ever use "/nickname whisper whisper" to talk with other chatters there?

Then you will surely have forgotten some time or the other to enter "/msg" if you want directly contact someone here in CB.

If you never had that situation of private text appearing in public in the CB, let me tell you: this can be very humiliating.

RFE: It would be great if /nickname has the same effect as /msg nickname.

  • Comment on RFE against certain Humiliating situations

Replies are listed 'Best First'.
Re: RFE against certain Humiliating situations
by liz (Monsignor) on Sep 05, 2003 at 10:43 UTC
    You might remember this recent discussion: warn for !/m(e|sg) in CB?. I think the consensus was that everybody likes the glitches and the (other Monks') humiliation too much to have anything changed in this respect ;-)


      Okay. I Surrender after 2 -- votes :-/
Re: RFE against certain Humiliating situations
by wufnik (Friar) on Sep 05, 2003 at 11:42 UTC
    yes, i agree monsieur Skeeve, being no stranger to humiliation miself... tho i have to say that, personally speaking, the humiliation is useful counterbalance against excessive hubris...


    -- in the world of the mules there are no rules
Re: RFE against certain Humiliating situations (better)
by tye (Sage) on Sep 05, 2003 at 15:53 UTC

    My preferred solution would be to add a "To:" field (with a radio button beside it) in Message Inbox so you can use the "Reply text" field to send private messages that aren't replies1.

    This is better than the other solutions because it has zero risk of exposing your chatter to public view. All of the other proposals handle a few specific typo cases but still leave plenty of room for embarrassment: you might leave off "msg ", "/", or both, mispell "msg", use "\" instead of "/", insert or leave of a space, etc. And some of those cases are impossible to trap (while many are annoying to trap -- to me all of them are).

    It even prevents misdelivery when you leave off the monkname (I know and has gotten some very juicy private messages by mistake) or forget to deal with the spaces in a monkname. You could still typo the monkname and send to the wrong person, but getting a typo that matches a different active monkname is very unlikely.

    It also has the advantage of allowing you to send full-length messages instead of messages shorter than $maxmsglen - length("/msg []") - length($monkname).

    Thanks to PodMaster for reminding me that I wanted to implement this (and sorry I didn't see your question until after you'd made that patch).

    1 So that field will probably be relabeled.

                    - tye
Re: RFE against certain Humiliating situations
by Ovid (Cardinal) on Sep 05, 2003 at 16:18 UTC

    I doubt this functionality will be changed any time soon, but it's a risk we live with. Remember, private chatrooms are only private if no one decides to turn their attention your way. If you want privacy, stay off the Web. (Sorry if that sounds harsh, but it's true).

    That being said, I was once horribly humiliated by a private message gone astray when a girlfriend was in a chat room with me. I feel your pain.

    And no, I won't tell you what was said :)


    New address of my CGI Course.

      If you want privacy, stay off the Web.

      Yeah, well we're at it why don't we get rid of this whole encryption thing? It seems a little difficult for most people to understand. Making people think of new solutions is obviously undesireable, so let's just not try.

      If you want a solution to your problem, here it is: every message that starts with '/' will be sent off to a sub with a dispatch hash, it will then check the letters following / and if the first letters before the space aren't a valid command (such as 'msg') or doesn't contain the valid parameters (such as username for /msg) it will return an error to the user. So if someone tried to type '/mseg Ovid blah' they would get an error saying "you tried to type /mseg Ovid blah blah. Then since they're lazy, they can cut and paste and switch /mseg to /msg and resend.

Re: RFE against certain Humiliating situations
by Abigail-II (Bishop) on Sep 05, 2003 at 11:29 UTC
    Perhaps I should create a login 'msg' .... (if that one doesn't already exist).


      Of course should commands take precedence over names. :-)

      Nevertheless: Nice Try :-)

Re: RFE against certain Humiliating situations
by krisahoch (Deacon) on Sep 08, 2003 at 15:59 UTC
    What kind of humiliating situations? Have you been having $chatterbox->net('sex');#-) j/k

    Kristofer Hoch
    Si vos can lego is, vos es super erudio

      I would have asked whether this is an offer...
      But then I saw that you're not +O but O->
      So I won't ask... Maybe someone else? ;-)

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: monkdiscuss [id://289153]
Approved by castaway
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (7)
As of 2022-08-12 14:54 GMT
Find Nodes?
    Voting Booth?

    No recent polls found