Mar 142013
 
MJMSJX: http://1.JotHere.com/4065#MJMSJX

MAZBVC:POST

MAXFOC:WHAT & WHY

  1. MJNW02: Every event listing comment grouped-into & part-of 1 thread and each thread with a subject

    1. MJNX50: is possible & always the case now that that threading is possible.
    2. MJNWX5: dramatically improves the event info & discussion & collaboration vastly, almost night-vrs-day, like “how did I live without this?”
    3. MM5B8N: must read threads & threading within websites for background & instructions.
  2. MJN0FZ: the thread of a person’s attendance & review of this event done on Meetup

    1. MM5BU9:do it as a top-level comment on the event listing where s/he did/would have RSVPed.
    2. MM5C3N:Many examples can be found in The groups Destiny is now primarily heading in virtually every event starting 2013.02.15~ in the event listing comments.
    3. MJNXCV: To be continued
    4. MJN0KL:  Advanced early example: comments of OCAndroid visiting SCALE 2013 aka SCALE11x –FREE for our booth volunteers!
  3. MJN22R: (comment) threading & display & display order

    1. MJN231: From <=2004 to next, comments
      1. MJN25V: could not be threaded (all at the same top level) and
      2. MJN26J: were listed in order the occured
    2. MJN25A: Starting 2012Q3~, comments.
      1. MJN28F: could be threaded 2 levels (top-level & 2nd/sub-level comments)
      2. MJN29Z: Threads listed from the one containing the most recent comment first.
        1. MJNVBQ:  I can see why this is done but as always, I suspect this is a mistake.
          1. MJNVGP: While it seems at first to put the new items top, in the long-term persepctive, it almost always works out overall simpler to always put the newest items last.
      3. MJN2AE: Within each thread,
        1. MJN2BF: comments listed in the order posted (newst last).
        2. MJNU1S:  regularly subcomments are collapsed/hidden by default:
          1. MJNUQO::  Notable pro: allows one to see “the forest despite the trees”, to collapse the outline/threading to see the top-level comments.
          2. MJNURC/a>:: Con: the “expand” link is easy to miss, referring to the “expand” link.
          3. MJNUVC:  Mixed: some but regularly not all (indeed typically most but not all: not the latest) of the subcomments are hidden by default
            1. MJNV0R: Notable pro: Allows the familiar person to see if anything’s new w/o expanding.
            2. MJNV4A: Notable con: with the “expand” link is easy to miss, causes person unfamilir with this or not into the habbit of how it’s to be used, to miss there are more comments they need to see.
          4.  MJNUTR: big con: there is no way I can find to, in 1 operation, expand to unhide everything (all comments in all threads)
            1. MJNV5J: Makes page search (as Ctrl-F) very hard.
            2. MJNVA5: Makes a complete printout hard/impossible (unless by default, printing does an expand-all: haven’t checked).
          5. MJN2CJa>: specifically, all but the last 2 2nd-level comments are hidden by default.
            1. MJN2D3: To show hidden comments, one has to do one of:
              1. MJN2EX:  click the ~”read more” link displayed in place of the comments hid.
              2. MJN2FV: u use a comment reference url with the parameter “read=1″
  4. MJNQZE: Keeping up with your comment reading

    1. MJNR5N: is essentially reading, of the matters which could pertain to you, the comments you haven’t yet read, generally in order
      1. MJNRHK: Meetup will alert you fairly well by email, and in this order, if you you have things setup right
        1. MJNSHI: If you don’t use & use properly these email alerts, that’ very bad: you will virtually gurantee missing comments, which will limit your participation & ability to cooperate.
          1. MJNSL9: You may show up & find nobody there or not have brought what you needed so can’t well participate. Things could be changed which you were depended on.
          2. MJNSOI:  Other participants will likely be rightfully annoyed/upset with you for having not kept up to what they wrote you and now having to tell you specially.
          3. MJNSLW: If a leader or volunteer, you can readily loose the job because you’re not clued in so hare costing more than you’re helping.
        2. MJNRLD: You must have event comment emails turned on
          1. MJNRU2: “On” by default; only turned off if you (mistakenly) turned them off.
          2. MJNRP2:  Controlled, for each one of your groups, on the group page->My Profile->Email & Notifications, aka http://meetup.com/OCAndroid/settings where replace “OCAndroid” with your group’s URL name)
            1. MJNSAK:  I’m guessing (as haven’t ever turned this off) that they seem to be set only by the paramenters under “Meetups“: of  “comments
              on a Meetup I’m attending
              ” and “post event greetings for Meetups I’ve attended“.
        3. MJNRIW: You should your client’s email threading turned on
          1. MJNRKJ: In Gmail, this is on by default.
        4. MJNSVZ: When you look at an email to you of a new comment post (be it for an event, picture, Greet, etc)
          1. MJNSXU: If it’s something you might need to deal with, mark it so (as Star it) else go deal with it.
          2. MJNT2J: To deal with it, start by viewing the page where it’s displayed so giving you the full picutre including subsequent updates; don’t depend on just the email as that’s almost always an incomplete picture.
          3. MJNT4G: If the comment/post is something you don’t need to deal with (as you or someone has now dealt with it) but is something that might possibly come up in the future for you, then Archive the email notice, else (and only if not then) Delete it.
            1. MJNTDG: Meetup wrongfully does not archive comments on their website and does not send the author a copy of his/her comment, so if a comment gets deleted off the website, typically the author won’t have it and the emailed copy(s) will be the only backup, and most people (rightfully or wrongfully) delete them, so don’t delete your copy if this might come up for you.
      2. MJNSDU: Manually searching the web page (as event listing) for comments you haven’t yet seen.
        1. MJNSQP:  certainly doesn’t catch everything that email notices do, including possibly related notices on other page
        2. MJNSTO:  does give you a much better big picture than the email, including the fully update picture.
        3. MJNTKM:  Simply follow (comment) threading & display & display order to find what is new:
          1. MJNTQL:TRICKY: when reading a thread, whenever the oldest subcomment displayed is something you haven’t seen before, be sure to click the “unhide collapsed comments” as there very likely then are other comments there you haven’t seen.
      3. MJNTRU: Semi-manually searching the web page (as event listing) for some particular text in a comment
        1. MJNU09: Normally one’s web browser’s page search (which is Ctrl-F in windows) would do the trick here no problem, but with collapsed
  5. MJN1IQ:  Every such comment

    1. MJN1PY: is emailed after a small delay (a few minutes) to to everyone RSVPing or commenting on the event page by default
      1. MJN1T0:  unless the person has (wrongfully) turned this setting off which cannot be seen except by the profile owner him/herself.
    2. MJN1PS: once posted, cannot be edited
    3. MJN27P:  once posted, cannot be moved.
    4. MJN1L3:  can only contain plain ASCII text, any type including line breaks.
    5. MJN1MP:  has all f the form “<separator/>http://..<separator/>” and “<separator/>https://..<separator/>” converted to live a hyperlink to that address/URL where only the first ~37 characters are displayed.
    6. MJN1K4: can be up to 1000 characters except as noted.
    7. MJN1JD:  can be linked to.
  6. MJN1E7: Comment types:

    1. MJN1EM:  created by the top-level comment box
      1. MJN15X:  created via typing into the box containing “Ask a question, share something, or leave a comment…” which is unfortunatlely listed at the top of the comments not the end.
    2. MJN1G2:  created via an RSVP comment
      1. MJN0U9: aka to a comment starting with HTML <li id=”reply-[0-9]+” data-commenttype=”REPLY”>
    3. MJN1HF: created by clicking “Reply” on an existing comment.
  7. MJN01B:  Linking to a comment (of a Meetup event listing)

    1. MJODZY:  is extremely useful to refer to prior discussion
      1. MJOE1A:  including given, even if on the same page, that prior dicussion is often collapsed/hidden and this is the only way known to expand it.
    2. MJOE1G:  is very tricky and a bit hard
      1. MJOE7E:  due to Meetup
        1. MJOE8U:  especially not bothering to include a simple comment link-to-self next to each comment.
        2. MJOE7R:  making it excessively complex
        3. MJOE86:  not bothering to give any documentation that I’ve found
      2. MJOE3L:  Only a few IT folks like myself would be likely to figure it out
      3. MJOE5N:  Complex enough to take ~2 or 3 minutes to do even if you know what you’re doing plus you may still have to refer to these directions unless you work to memorize them.
    3. MJODTB: to a top-level comment:
      1. MJN17Z: You can cut the “www.” and probably should for bevity.
      2. MJN147:  to a comment created by the top-level comment box
        1. MJODYH:  more TBA
      3. MJN0ER: to a comment created via an RSVP comment.
        1. MJN194:  Inherits everything of to a comment created by the top-level comment box except as changed here.
        2. MJOEC4: append to the URL “&itemTypeToken=REPLY
        3. MJOEWO:  Real example: “..pls download this book http://meetup.com/common-ground-spiri… onto
          your Kindle
          ..”in on Lucy’s profile Greet “Mar 14, 2013 5:36 PM” (motivating me to create this post).
        4. MJODYW:  more TBA
    4. MJN20N: to a comment created by clicking “Reply”
      1. MJODQN:  Take the (link) to a top-level comment and append essentially “&read=1#reply-29098122” where replacing “29098122” with the appropriate #.
      2. MJN0Z3: Real example: http://meetup.com/OCAndroid/events/95400372/comments/27869542/?itemTypeToken=REPLY&read=1#reply-29098122 in comment “OCAndroid’s “hand-picking” who’s a mbr..”.
  8. MJNQRI: Making a new comment

    1. MNKMXQ: It’s best if you are familiar with else skim all the above topics before making a comment as it affects how you write it. Most essential:

      1. MJNQRY:  Really aim to get it right at time of 1st post, as:
        1. MJNQU5: cannot be edited
        2. MJNQUB: cannot be moved
        3. MJNQUI: near-instantly emailed out
      2. MJNQW4: 1st search if any of the points & Qs you are about to make have already been done
        1. MJNQYK: Easiest if you’ve kept up with the commenting reading; if you haven’t, catch up now.
    2. MNKN05:  Not obvious: COMPOSE YOUR COMMENT NOT IN THE COMMENT BOX BUT IN AN ASCII TEXT EDITOR THAT DOES CHARACTER COUNTING.

      1. MNKN2O:  few exceptions: when your comment is:
        1. MNKN6P:  not a reply to another comment (as there if you accidentally press return, your comment instantly gets sent)
        2. MNKN7H: so short its really wouldn’t be more readable with any line breaks (returns).
      2. MNKNNC:  A tool to count your characters as you compose is essential as
        1. MNKNNZ:  Meetup event comments are limited to 1000 characters (sometimes a few less) but
        2. MNKNO2:  Meetup displaying of the characters in an event comment being composed is crap: displayed only for a top-level comment and only when it’s between around 900 to 1100 characters.
      3. MNKNCR:  For this purpose, I keep open at all times a text editor editing say “character count.txt” which I constantly reuse to make & hold drafts of comment posts.
      4. MNKNBQ:  Possible editors, starting with best,
        1. MNKNEX:  There’s probably something better but I haven’t found it.
        2. MNKP3I:  The proper & probably-best editor with character counting could be done in a web page (as it’s only ASCII editing)
          1. MNKP4L:   I haven’t been able to find one
          2. MNKP4Q:  I may eventually code one
        3. MNKNFF:  LibraOffice-else-OpenOffice Writer
          1. MNKP0B:  with Tools->Word Count menu open and View->Web Layout mode.
          2. MNKP00: unfortunately I see no way to turn rich/formatted/non-ASCII text off, so
            1. MNKP1H:  saving in ASCII-text only mode
            2. MNKP2C:  pasting ideally with Ctrl-Shift-V (Edit->
          3. MNKP5R: Other pros: Cross-platform & and converts “” to “” enabling much bestter nested quotes, test (& visit) URLs by just by ctrl-clicking on each.
        4.  MNKNKW: all the below don’t well-count characters:
        5. MNKNQQ:  for short comments, a top-level event comment (which, if it is to be a reply commment, when done, you select-all then cut then, in the reply comment box, paste).
        6. MNKNIR:  MS Expression Web in “text file” mode
        7. MNKNGI:  Notepad.exe
    3. MNKNTG:  Doing a longer comment (especially above the 1 comment limit)

      1. MNKNUX:  All or the bulk of it must be and probably should be Reply comments, not a top-level comment. The top-level comment just needs to be a thread name and thread description and maybe summary.
      2. MNKNWV: Break the comment into consecurive blocks each as near as possible to 1000 characters (except maye the last one)
      3. MNKO3A:  Prefix each block with a line of just “cmt1of3:”, “cmt2of3:”, “cmt3of3:” (in general “cmt1of<n/>:” to “cmt<n/>of<n/>:”) respectively in order.
      4. MNKO74:  only when all blocks are properly composed, then go post them, and in order.
    4. MNKNYG:  ideally outline your comment

      1. MNKNZO:  as level 1 points beginning (left-flush) with “*”, level 2 with “**”, level 3 with “***”, and at most only 1 level 1 point (beginning with “”).
      2. MNKNZ9:  for
        1. MNKNZK:  clearer & much-faster reading (one can skip the parts that doesn’t interest/apply)
        2. MNKOGX:  for fewer words & repeats, as the topic(s) of the point are in the parent point(s) so don’t have to repeated for each sub-point
        3. MNKO1O:  for readability of longer points when they must be broken over comment posts.
    5. MNKPE6:  Before posting, insure all your included URLs work (notably by opening each)

      1. MNKPGW:  “Writer” makes this particularly easy by Ctrl-click on each.
    6.  MNKOAX:  real examples TBA.

    7. MNKO7Z:  I do all the above for all my daily Meetup commenting (dozens of comments every week) and it works & works well

      1. MNKPP0: –as best as one can do given Meetup’s limitations making good full commenting quite painful, including needing all the above instructions, which are also all missing!
    8. ML7WJJ:To be continued:
    9. MNKOK5: section history
      1. MNKOKI:  earlier updates not recorded
      2. MNKOQO:  in prep for Lucy replying to this thread,
        1. MNKOKO:  moved this section the end of parent as it depends on all the earlier sections and explained that per its point MNKMXQ
        2. MNKONC:  added importatant missing points MNKN05 MNKNTG MNKNYG MNKOAX MNKO7Z MNKPE6

-end of WHAT & WHY

MAX1LQ:WHEN

  1. MJN04F:  Applies to the the Meetup site from 20012Q2~ to present

-end of WHEN

MAX1N4:WHERE

  1. MJN06O:  of Meetup.com event listings

-end of WHERE

MAX1VD:COST

  1. MJN07G: Free.

-end of COST

MAXDSI:WHO’S PARTICIPATING?

  1. MJN08N:  Groups subscribing to this site’s universal rules of Meetup.com.

-end of WHO’S PARTICIPATING?

MEG922:WHAT TO DO

  1. MJN094:  All that’s described here.

-end of WHAT TO DO

M33M3R:FUTURE PLANS

  1. MJNXNQ:  Within a week or so, remove the “(soon)” in the title; see the end of the post history for status.

-end of FUTURE PLANS

MAX22R:ADDITIONAL DETAILS

  1. MM5BYY:The groups Destiny is now primarily heading are http://Meetup.com/OCAndroid , http://Meetup.com/OC-Polyamory and Meetup.com/”OC-Python”

-end of ADDITIONAL DETAILS

MDE167:POST TODO, roughly in order:

  1. .

-end of POST TODO

MAYJ80:CREATORS

  1. MEMPEO:The author

  2. MEMPF1:No one else unless attributed.

-end of CREATORS


MDAIRC:ADDITIONAL DETAILS FOR ORGANIZERS/DEVELOPERS

  1. .

-end of ADDITIONAL DETAILS FOR ORGANIZERS/DEVELOPERS

MDAIRC:FOOTNOTES

  1. .

-end of FOOTNOTES

M31R7R:POST HISTORY, in order:

  1. MJOF3G:  over the last month or so, after discovering the complexity of this matter yet that all Meetup users should know this, knew I had to create a post.
  2. MJOF15:  the final straw was want to create this link to a comment but myself had forgot the keyword for that so even I need this as notes for myself
  3. MJMSFP: so now create this post
    1. MEHCSP: for an article sharable among many Meetup events & groups & more.
    2. MEHCCA:via Copy to a new draft of http://1.JotHere.com/4036#MJ917Z latest release MJMAS4 then create new IDs & edit to fit.
  4. MJNXVU: ~30% complete 1st version,
  5. MJNYFM: POST: several impovements in wording & formatting.
  6. MJNZ0D: now 1st publishing; pst2013.03.14Thu1127; NOPE, more to add.
  7. MJOF82:  now 1st publishing pst2013.03.14Thu1756.
  8. ML80AH:update ML7ZOK
  9. MM5BGR:added MM5B8N removing its content to where it points to; added missing h3-tags; pst2013.05.01Wed1844.
  10. MNKPT5: added all of MNKOK5; pst2013.05.29Wed1159.

-end of POST HISTORY

  One Response to “Meetup.com event listing comments: (soon) all you need to know but Meetup.com doesn’t tell you”

  1. You can, of course, use Open Office or Libre Office to compose posts, but a much handier option for short posts is the free online service, Character and Word Counter Online — http://www.characterscounter.com/ — which allows you to enter quite a few words, several hundred at least (I don’t see a posted word limit) and counts both words and characters very clearly at the top of the post AS YOU COMPOSE — something you can’t do in the above text editors. It has a clean, easy-to-use design and also provides reminders of word/character limits in frequently-used services such as Twitter and AdSense. Looks pretty good to me. I’m going to start using it.