May 012013



  1. MM4VRO: -especially important due to Wherever practical, communicate, including reply, via a good shared-document typically via proper-posting within websites

  2. MHNX5O:including aim to get the post location & content right the 1st time

    1. MHNWQP:including, before posting, PLEASE FIRST SEARCH
      1.  MHO20U:if answers have already been given
      2. MHO234:if thread on this topic already exists –if so, click “Reply” on that thread rather than creating another thread.
    2. MHNX6Q:especially as Meetup doesn’t allow you or anyone to move your post/comment if you put it in the wrong place (except 1 small case: a high-enough group leader can move a Message Board thread to another forum)
    3. MHNX6T:and as Meetup immediately emails out your content & doesn’t allow you to then edit it (except in one significant case: a Message Board post you & admin can freely edit, and alerts (just link to the new post) isn’t emailed out until midnight)
    4. MHNX2A:so if the content and/or location needs fixing, unless it’s a Message Board post, all you (and only you) can do is both:
      1. MHNXK3:post it again with the better location & content
      2. MHNXLW:then edit-else-reply-to your prior post with a link to this new location, else delete your prior post but only if you’re sure no one has significantly looked at it including it has no replies.
  3. MNFMPQ:Communications for events & groups: since clearly you should be foremost posting, this is how to do so properly.

    Following are all common examples plus the 1 exception: no posting of private-communication contacts (as phone #s & email addresses) including your own except as noted.

    1. MHKNY6:For an event, want to give your RSVP and/or reason? Or change it? Then instead of telling anyone effectively-privately, post it as A RSVP! (as RSVPing on Meetup is effectively posting your RSVP)
      1. MHO39Q:Know every time one sets & change one’s RSVP, Meetup emails all event hosts of his/her prior & new RSVP (except for the ones who have turned this off, which should not be done). But know Meetup wrongfully excludes the post creator from being emailed his/her creation so s/he typically has no copy especially in case his/her post is removed.
      2. MHPVNZ:Also know Meetup wrongfully & permanently erases RSVP comments ~1hr after the event starts.
        1. MHPVTO:So if your comment is something others (or you) might want for later and it’s tolerable emailing potentially ever member replying on the event listing, better to use an event comment which you just refer to you in your RSVP comment (ideally link to it: advanced & TBA).
    2. MHNWJY:On an event, do you want to ask a question or provide additional info,or give feedback or a review or thank the hosts or anyone there? Then instead of telling the event hosts or anyone effectively-privately, post it as AN EVENT LISTING COMMENT!
      1. MHO1VE:including note (starting 2012) event listing comments are now threaded (down to just 2 levels, but still a notable improvement) so:
        1. MHO2AF:search for & click “Reply” on the appropriate thread instead of creating another thread by say posting everything as a top-level event comments.
      2. MHO37Y:Know every time one makes an event comment, it is, within 1 minute, emailed by Meetup to everyone (but the creator) posting an event comment on that page plus everyone RSVPing YES-or-MAYBE and maybe also those RSVPing NO (except for those who turned this off, which should not be done). But know the creator is (wrongfully) not given a copy. Also know Meetup wrongfully excludes the post creator from being emailed his/her creation so s/he typically has no copy especially in case his/her post is removed.
    3. MHKO13:Want to say something relevant to the group about you? Such as the related projects your working on and/or related company you work for and/or related people you know? Then don’t just tell people effectively-privately, post/put it on your GROUP-PROFILE ANSWERS!
    4. MHPRKN: Want to tell something to less than ~5 people, for which the above posting forms aren’t suitable (as isn’t regarding a particular event or event series or is but they aren’t RSVPed or commenting on it or  posting it as an event wouldn’t be as good)? Then post it as A GREET on his/her group profile! -or main profile if not regarding any group.
      1. MHGKVM:Know within ~1 minute of posting, also emails the Greet to the profile being greeted (so they will be alerted to it, and have a permanent copy), but Meetup wrongfully excludes the post creator from being emailed his/her creation so s/he typically has no copy especially in case his/her post is removed.
    5. MHK6IJ:VENUE possibilities & reviews must be handled via posts.
      1. MHK7F1:How & where to do this?
        1. MHK7JV:Ideally 1 thread per venue (per group or per event series), to keep all the details on a venue together.
        2. MHK7LV:Additional details under development as I see no obvious universal way.
        3. MHK8CS:OCAndroid has a venue forum with 1 thread per venue
          1. MHK8IE:Some key pros thru cons:
            1. MHK8TI:Notable pro: easily captures minute details such as notes on a phone call.
            2. MHK8HA:Pro: currently still used
            3. MHK8K5:Con: can only list by date proposed; impossible to automatically summarize & sort venues by useful characteristics, such as # of times used, most recently used, # of seats, etc.
      2. MHK7RR:This section is a replacement for /452#M7ZS3K which replaces LTED3B.
    6.  MHK6US:JOB OFFERINGS/ADS must be handled at least initially via posts –recruiters especially, take note.
      1. MHK863:How & where to do this?
        1. MHK87I:Ideally 1 thread per job offering (universally else per-group) linked to by everywhere the job is advertised.
        2. MHK9TY:At least the 1st response of every ad/offer respondent must be immediately else within days posted onto the thread as a reply to the solicitation
          1. MHKA8C:done ideally by the respondent him/herself (by reply-posts) else via the advertiser (by reposting the reply communication (email, call transcription, or other) they got).
          2. MHKA0V:with the person’s name obscured, but not underlying profile link, should the person not want to share his/her full name. Aka, respondent can request his/her name obscured, but not underlining-profile-link.
          3. MHKA57:so especially:
            1. MHKA5K:everyone can timely see the response the ad is bringing, including the group can get credit for bringing this ad
            2. MHKA7A:questions & problems & benefits of the ad & advertiser, which is typically unknown to the group, can be revealed to everyone.
        3. MHKDO7:Handling that the prospective employee/contractor might not want his present employer/client know s/he’s looking fearing reprisal.
          1. MHKDQV:This desire fights this posting principle. To what degree should this privacy desire win?
            1. MHKDTR:Certainly not fully. As
              1. MHKE5C:This is catering to individual short-term fear (and which may not be founded and is assuming the negative/bad) instead of to long-term group effectiveness.
            2. MHKDTY:Not at all? Possibly; TBA.
            3. MHKDV0:Partially? That is my current determination.
              1. MHKDWY: so respondent can request his/her name obscured, but not underlining-profile-link.
              2. MHKE15:the jobs can be posted in a forum which only group members can see.
        4. MHK9SN:Additional details under development as I see no obvious universal way.
        5. MHKAJG:OCAndroid has a job forum
          1. MHKEAM:Currently it’s set only visible to group members.
          2. MHKE9E:Pros thru cons:
            1. MHKEKW:Pro: currently in use. Haven’t surveyed to see if it’s finding results.
            2. MHKECS:Serious con: Meetup Message Boards do not support HTML, can be replied to only be group -members, and, worst, poorly announce so requiring a group leader to manually send out an email to the group.
          3. MHKAN7:This section is a replacement for /452#M7ZS6X which replaces LTED7B.
    7. MHK7TN:No posting of PRIVATE-COMMUNICATION CONTACTS (as phone #s & email addresses) including your own except as noted here.
      1. MHKB73: Why?
        1. MHKB82: encourages-else-enables use of these communication methods which, by their nature, typically causes violations of this post principle.
        2.  MHKB9X:When needed, Meetup enables private communication already to you & every user, plus optionally without exposing the sender’s email and/or phone # if s/he doesn’t yet trust the solicitor with that, via the “Send email” link on every Meetup user -just don’t disable this.
        3. MHKCBZ:often unnecessarily compromises the privacy and exact- and/or legal-identity of owner (which could be you) of the posted phone #, email address, or other private-communication address.
      2. MHKBQ5:exceptions:
        1. MHKBRD:for when important communication must happen in a very timely manner (as within minutes) where it might not be possible to receive and/or sent posts (notably Meetup event comments)
          1. MHKBZT:as cases of:
            1. MHKC0V:meeting someone to carpool/rideshare
            2. MHKC1K:finding the party (group attendees) at a location (as where there many times more other people there)
          2. MHKC3M:but do note need for this is diminishing as increasingly people are using their smartphones for email, web browsing, & the Meetup app.
        2.  MHKCF7:contacts for an entity, typically an organization (as many venues), who can’t be reasonably expected to have a Meetup user account, including don’t advertise on Meetup, and who wouldn’t be justly offended by this info being posted.
      3. MHK7SV:This section a replacement for /452#M7ZSB3 which replaces LTECMG.

  4. MM514C:threads & threading (within websites)

    1. ML7W6K:A thread is defined by its top-level “post” or “comment” and all “comments” which are subordinate to (so included under) it.
    2. MM518L:By allowing commenting on a topic by people other than the original/official author(s),
      1. MM51W3:threading turns a Web 1.0 site into Web 2.0
        1. MM51LH:indeed threading is the #1 way this is done; and
        2. MM51JZ:and Web 2.0 means many authors & collective intelligence  not just 1 author, so is a revolutionary improvement.
        3. MM51ZE:but also…
      2. MM51WK:can & readily does make a huge mess of the publication for everyone –unless most everyone  follow certain authoring rules & standards, so spelling those out is the foremost goal of this post.
    3. MM51O4:The subject/topic of a thread

      1. MM5246:(the subject/topic of a thread) is, well it depends: (Does if the thread has an official “subject” or “title” field, or, if not, is there a rule for declaring the subject text) AND (Is this text there meaningful (not say “Hello” or blank))?
        1. MM527T:   If Yes, then the subject is whatever that text says, though the meaning of it, especially its special terms, can be further defined in the post/comment body(s) as well, though ideally in the 1st else early ones.
        2. ML7W7Q:If No, then the subject is il-defined, but likely generalization of the matters/topics of all its comments, especially the earlier ones, especially the 1st one.
      2. ML7W9G:only 1 topic/subject per thread and max 1 thread per topic/subject -see subpoints
      3. ML7Z7Z: per thread, only 1 topic/subject (else very few)
        1. ML7YO6:consequently:
          1. ML7WAN: if you want to talk about multiple topics, break each into a separate comment post.
          2. ML7WTS:there is a standard for properly declaring the subject of a thread.
        2. MM54QW:Cons thru pros:
          1. MM55S9:Often-fixed con: “On the 1st pass, it’s too much trouble to read as it creates too many separate alerts”.
            1. MM55UN:dBetter
          2. MM54OJ:” Typically fake con: “It’s too much trouble write.  Just post a bunch of points at once.”.
            1. MM55TO: Nah, that’s not thinking ahead nor being considerate our readers, as see If we have multiple topics per thread, we then create many problems.
          3. MM54TN: If we have multiple topics per thread, we then create many problems:
            1. MM55XF: It’s that many times (the # of topics) that we’re going to make a mistake on one one of them and/or not give it the attention it deserves, so then still have to post additional corrections & addition, and now on the whole thing, or suffer from the mistakes & incompleteness.
            2. MM54YZ:we typically also fail for each topic/subject, max 1 thread, and then a topic is divided up among multiple places.
            3. MM55HT:The readers cannot “mute” being notified on the subset of topics they don’t want to be notified. Indeed, if there is just 1 of the topics they want to be alerted to, they have to then be alerted to all of them.
            4. MM550P:that readily gives too much for a person to reply to; so then
              1. MM5538:they may typically not reply (since it’s overwhelming to read, and reply to everything, and they may reasonably feel they need to have read and perhap to have addressed everything, if they gave their reply)
              2. MM554T:When someoone does reply, they will typically reply to just one or a few of the topics, but then
                1. MM558Z: that makes them look like they have no response to the other topics when in fact often they just didn’t have time to read the other stuff yet and/or formulate a response to it.
                2. MM55C4:seeing they made a reply there, they & nobody will have any good reminder that there is still other stuff they haven’t replied to & likely haven’t even read.
          4. MM561R:It follows per Less in More, including the latest trend of SMS & especially tweets & other micro-blogging.
      4. ML7ZA8:for each topic/subject, max 1 thread
        1. ML7ZE3:consequently
          1. ML7WQ1: if it’s a common topic or question, there probably already is an existing:
            1. ML7WQK:thread for it where the info should be
            2. ML7WRU:standard for how the thread and topic should be formatted: notably see Good thread subjects.
          2. ML7WEY:REALLY search carefully for & use an existing thread on the topic before creating a new thread:
            1. ML7WL6:especially given that a comment cannot be changed (as moved) after posted.
            2. ML7WM3:see Making a new comment for further details
      5. ML7WYY:properly declaring the subject of a post including a comment
        1. MM56MQ:is very important
          1. MM57I0:most especially if the comment is might or could-get replied to (so will effectively start a discussion thread)
          2. MM57JO:as if not done well:
            1. MM56VB:in the short term it may seem fine, indeed very nice  (as by instead just using informal discussion phrasing)
            2. MM56VS:but in the long term causes overall problems as people miss the subject (partially or fully) so then post
              1. MM56W3:reply comments (so under this thread) on other subjects, so violating per thread, only 1 topic/subject
              2.  MM56YP:elsewhere post comment(s) on the same subject (so often starting new threads on it), so violating for each topic/subject, max 1 thread
        2. MM56DO:Follow (the subject/topic of a thread) is (definition)
        3. MM56GD:Systems which don’t have an official/explict thread subject field
          1. MM56KC:are hurt because properly declaring is so important (but fortunately there’s a fix but it’s a bit tricky).
          2. MM56HL:are common
            1. MM5702: Typically fail from not having topic for comments
              1. MM57TR:For example, in Meetup, every group has a title/name plus “About” area telling its subject, and each of its
                1. ML7X0K:event listings has a  title (so subject) but unfortunately for every listing’s comments, every of them  doesn’t  have an official subject field and even though sub/reply comments are now possible.
                2. MM57F5:discussion forums has a title and each of its threads has a title, but the subsequent reply posts within each thread do not have a title (and cannot be nested).
              2. MM57KA: For example, in WordPress, a category has a title (though unfortunately no typically-displayed description) and collects many posts, and each post has a title, but each comment (on the a post, or on a comment) does not have any official title/subject field, and even though they can be nested up to ~12 levels.
        4. MM5939: a fix
          1. MM593W:Works fairly well.
          2. MM594R:Unfortunately must be learned & done manually by every one making any post/comment which could/would have comments, which is most generally most-everyone.
          3.  ML7X1O:-the thread’s subject should be:
            1. ML7XKU:NOT implicit but still as explicit as possible.
            2. ML7X2E:in the 1st (top-level) comment of the thread, else, when that’s not done, in a as soon as possible sub-comment
            3. MJNVW2: in ALL CAPS
              1. ML7XF6:except for names & phrases which contain mixed caps where case-sensitivity is  important.
            4. ML7Y0W:is ended with a period “.”
            5. MJNVVL:on it’s own line (really paragraph) of the comment
              1. ML7XCQ:notably on the 1st line (really paragraph)
      6. MJNWHK:Bad thread subjects include, starting with the most common, are ones which:
        1. MJNWM5: worded where the subject isn’t clear.
        2. MJNWLR: needlessly span multiple subjects/topics.
      7. MJNW0D:Good thread subjects include, starting with the most common & needed:
        1. MM59JG:for an event (and often for many things, as venues, which can be viewed as event)
          1. MM5DWZ:Aside: each of these headings:
            1. MM5B25:is  worth memorizing.
            2. MM5DYA:is to be subject of thread (comment) on the event listing, typically at top-level, and added by potentially anyone but typically by those most involved with the matter.
          2. MJNW1H:  a person’s attendance & review of this event thread, aka the thread of a person’s attendance & review of this event
            1. MM5BR8:typically with subject “<user_name/> <user_GroupProfile_URL/> ATTENDANCE & REVIEW OF THIS EVENT.”
            2. MJN0P8: 1 per person, else per member & their guests.
            3. MM5ABT: Here’s full details for doing this on Meetup.
            4. MM5A6W:Reviews & Why this is important, both logically & empirically.
              1. MM59JY: Especially if a person important, just as s/he deserves a seat at the event, s/he deserves his/her own attendance&review thread for the event.
              2. MM5AK7:I near-1st-used this, and with remarkable success, for each RSVP for group MIComm’s annual visit SCALE & manning their booth with volunteers, where it gathered together & managed the details of each of our attendee and their booth shift scheduling & rescheduling. As quick example, see the thread for Lucy’s attendance, working out all her attendance & booth shift schedule.
              3. MM59MZ:This thread topic works wonders in terms of capturing & sharing, into 1 neat thread, all the many details of a person’s attendance&review, indeed overall experience, of the event,including a lot of stuff not easily capturable into a simple table (with 1 row for each person), including:
                1. MM59PX: When s/he RSVPed & HOW & WHY.
                2. MM59SC:Changes in plans, including what, when, why
                3. MM59QP: Additional details, as anything special she is/did bring or forgot.
                4. MM59U3:Reporting, including last minute, that s/he will be late and/or leave early.
                5. MM59Y4:The person’s review of the event, and other’s responses to that review.
                6. MM5AXX:Collecting the person’s reason for being a no-show & responding to that.
              4. MM5A2C:Allows for collective reporting (so collective intelligence) on this info by the person it’s for, the leaders, every RSVP, indeed every group member.
              5. MM5A05:And any time these details become overwhelming for any other RSVP, because it’s all in 1 neat thread, the person can just “Mute” the thread.
              6. MM5AW3:Something similar may also be used by Facebook events, which I recall makes each RSVP setting or change a status update to the event, hopefully similarly grouped by potential attendee.
              7. MM5A9P: Con: it’s still new & non-traditional, and sometimes hard for folks to get used to.
            5. MM5AB8:I got this idea ~2012Fall from Meetup changing its software so instead of a separate RSVP comment for  each RSVP (which then also disappeared after the event started if not erased before by a replacement RSVP comment), the RSVP comment is instantly moved to an almost-regular top-level listing comment.
          3. MJNW9M: the location of the event, be it potential or actual, typically called “WHERE.”
          4. MJNW96:  the date & time of the event, be it potential or actual, typically called “WHEN.”
            1. ML80FO:Real example: event_comment-157771462.
          5. MJNW4K:  a topic (potential or actual) for that event, typically called “TOPIC: <description/>”
          6. MJNX24:  a potential future event 1st suggested at this event.
          7. MJNWDI:  the topic for the event (if it is to have only 1 topic, which is probably not a good idea)
        2. .
      8. ML7W4A:Rules: see the parent section since it is exclusively rules.
    4. ML7XN5:section additional history
      1. ML7ZUC:Prior history not recorded here
      2. ML7ZWV:Motivated to make a reference to max 1 thread per topic/subject violated by #event_comment-179454912.
      3. ML7XNU:Renamed title from  q((comment) thread subjects) to present
      4. ML7XOK:Added several points including explicit Rules
      5. ML7XTQ:Cut text fragments:
        1. MJNVNQ:Every comment which can have sub-comments, especially every top-level comment
          1. MJNWIP: has a potential thread subject which its subcomments should refer to (to stay on subject).
          2. MJNWJY:  should determine & feature its thread’s subject.
            1.  MJNVQH:  as by
              1. MJNX0Q:  picking & giving a good & clear subject.
        2. MJNWA7: a potential location for the event
        3. MJNWAL: a potential date and/or time for the event
      6. ML7ZOK:update seemingly complete, pst2013.04.13Sat1808.
      7. MM5C57: Moved this section out of another post to here; added all points beginning with MM5 thru MM5D; pst2013.05.01Wed1845.


  1. .

-end of WHEN


  1. MKNE0Q:See WHEN and WHAT & WHY.
  2. .

-end of WHERE


  1. .

-end of COST


  1. .



  1. .

-end of WHAT TO DO




  1. .


MDE167:POST ADDITIONAL TODO, roughly in order:

  1. .

-end of POST TODO


  1. MEMPEO:The author

  2. MEMPF1:No one else unless attributed.

-end of CREATORS


  1. .



  1. .


M31R7R:POST HISTORY, in order:

  1. MM4VML: shortly after writing rules as 4065#ML7W9G I realize this applies to posting in general not specifically there to Meetup event posts.
  2. MM4VMA:I Destiny now created this post by Copy to new draft (of latest MM1L7U) then gave it fresh IDs & content.
  3. MM4W69: 1st draft with just title, categories, & importance; (note next undones); pst2013.05.01Wed1218.
  4. MM50VB:Updated URL (at top); did #MM5C57 dated there; 1st published.
  5. MNFMD4:Move content from & per 4105#MNFM3B to here:  MHNX5O and 4105#MHK6GB content (but not header) into new  MNFMPQ; pst2013.05.26Sun1825.