Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

I've made a bunch of improvements to the chat feature. The most visible changes are:

  • You can now use [user name] to deal with users with spaces in their names (or any users):
    • /msg [jon doe] text
    • /ignore [jon doe]
    • /unignore [jon doe]
  • You can't send a duplicate /msg to a single user unless you wait 500 seconds or until the recipient deletes the first message
  • There are a lot more cases where you get told what went wrong. These include:
    • Submitting duplicate text tells you that you already said that and "Don't 'reload'?".
    • /ignore and /unignore notify of success and tell you whether you were previously ignoring that user. (See ignored users for the full list of people you are currently ignoring.)
    • Sending a /msg to an invalid user now displays "Send failed (see Message Inbox)." just in case you have too many unarchived private /msgs such that the /msg from root informing you of the problem isn't visible.
    • "/msg bob Use <code></table></code>" no longer includes an unescaped </table> in the "You said ..." notice (which messes up the rest of the nodelets for that page load).
    • Trying the chat when you have /chatteroff tells you to enter "/chatteron" if you want to chat publicly.
  • All /commands ignore case so "/MSG TYE ME TOO!" actually works.
  • You can no longer send a blank private message with "/msg tye " (note trailing space).
There were also a bunch of minor changes or bug fixes or things that only affect certain administrative groups.

Note also that some things were intentionally not "fixed":

  • "/msh tye shhh", "\msg tye wait...", and " /msg tye now!" (note the leading space) will simply be displayed in public chatter. Previous attempts to do otherwise were very poorly received. If you want such "protection", then evaluate some of the other chatterbox clients as some of them offer such.

Previously I had made but not announced a fix that prevents an unclosed <!-- from hiding subsequent items.


        - tye (but my friends call me "Tye")

In reply to Chat improvements by tye

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.