Mar 232015
 

NLOW5O

  1. NLOXDP  113301662: (aside: start of previously post 1 last edited “Apr 1, 2014 9:22 AM”)
  2. NLOXDX  title history in reverse start-order:
    1. NM1F81  “

      Everyone, including on Meetup, please POST often & properly, especially INSTEAD OF DOING calls & especially messages, including emails & even SMS, wherever posting would be betterother than tweet-like messages just to alert or remind of posts.

      ” –{per NM1F5J, remove unneeded caps, move “wherever ..”, to end, use “tweet-like” phrasing, add missing “or” & “,”, remove “[1 to ~3]”, replace no cut “~”, replace “including” with “especially”},{add “please”,}

    2. NLT9F1    formerly “Everyone, including on Meetupwherever it would improve things, POST Often & Properly, including INSTEAD OF calls & especially messaging (including emails & even SMS) other than a {“tweet”=very short message} to point to, so alert/remind of [1 to ~3] posts.” –{add “including on Meetup, ”},{links to keywords qty: 0 to 5}{put in h2-tag}.
    3. NLPFN3 “Everyone, wherever it would improve things, POST Often & Properly, including INSTEAD OF calls & especially messaging (including emails & even SMS) other than a {“tweet”=very short message} to point to, so alert/remind of 1 to ~3 posts.” –cleaned up phrasing, including reordering to put the promoted 1st and cutting all-caps to about bare minimum.
    4. MXNL2E prior (also original) version to next:
      “EVERYONE, {WHENEVER POSSIBLE|[wherever it would improve things, ]}, KINDLY

      AVOID PRIVATE MESSAGING&TALK (as calls,emails,&even SMS) other than to just direct-to-post
      AND INSTEAD POST OFTEN & PROPERLY”
    5. NLT3NX  similar earlier sentiment in a similar article ~2 years earlier.
  3. NLOXG8   This is detailed in this and about 5 other similar articles on this site covering “posting” (to be eventually merged) but seemingly the most urgent stuff especially for Meetup is best covered here.
  4. MXNL75   the direction

    1. NM1MLM   The top goal is that every potentially important piece of info be discussed else promptly be archived into a central & easily-findable web posting location.
      1. NM1NCG   Around the world, this very rightfully seems to be the growing trend & goal, but is still typically vastly incomplete; so compared to current popular communication methods, it means, for everyone, “short-term pain for long-term  HUGE gains”.
    2. N3D0UL As I do continually, before sending any message or making a call, stop & think “How can I instead do this via post?” and do that (instead post it) whenever that does it better, which is usually the case.
    3. MXO29Q For most anything, you can and should post it, including to originally propose it.
    4. MXO29E If you’ve got something to related to our group, it generally belongs in a post and not a message (other than to (alert/remind) to look at & Reply to the post). Below tells for common types; and if still unsure, ask “Where do I post this?” as we aim to have a place for posting everything.
    5. NLQ8QS  Why?  A big net pro typically over messaging & calls. Pros thru cons:
      1. NLQD9W   messaging & calling is like crack cocaine –super easy & fun & cheap to start, plus done everywhere, but extremely addictive and very quickly terribly destructive (1st publication of this). In contrast, posting is like eating healthy meals.
      2. NLQDLK   Posting takes the time to find best long-term locations for matters.
      3. MXNN55  Posting is all very much per the founding-cleverness and grass-roots collaborative-spirit of Meetup.com: without even knowing each others official names nor contacts, otherwise potential strangers post to plan a community event including readily without any official leaders–as grass-roots as conceivable!
      4. NM0JKF Posting especially electronic especially where each post & ideally item within it as an anchor, well achieves allowing reference it and its items especially without copying them, in contrast to messaging and other communication methods.
      5. NLQ8UT    Often & increasingly updatable, including generally you do not need to worry if your content is just an draft/outline, has bugs, and/or is incomplete, so not yet ready for wide or even narrow distribution
        1. NLQ96B   as unlike most all messages and verbal talk, from most significant:
          1. NLQ9BW   posts are typically not immediately announced
            1. NM1PD7   On Meetup this is true everywhere, indeed the problem is typically posts require additional manual announcement: indeed even after posting, you often still have to point people to it before anyone sees it!
              1. MXO4DQ   Also most posts on Meetup are NOT widely announced as emailed out unless a group leader does so, say after approving it or wanting to advertise it more.
          2. NLQ986  posts can often be entirely changed after putting it out there (as posting)
            1. NM1P83   On Meetup, this is possible for all post types except Greets & Event Comments which can only be deleted.
          3. NLQ99L   posts are typically easily amended to (as commented on) afterwards, including sometimes with nested/threaded comments
            1. NM1PH1   On Meetup, this is true everywhere, including with 1-level threading, except that non-members, including not-yet-members, are (incorrectly) not allowed to post nor reply-post on any of a group site.
          4. NM1OWM   in better posting systems as Google Drive, who can access the info is changeable after it has been released, indeed at any time & fully & finely
            1. NM1P3M   Meetup has limited control here; specifically an entire group site can be marked as private (generally seems a bad idea) and Meetup Discussion boards allow a forum to be set as “Leaders only” or “members only” or “public” and threads can be easily moved between forums.
      6. NLQDFF   Postings can be much better versioned, especially in better systems as wikis
      7. NLQDGS  more TBA
      8. NM1H3J   small but routine con/exception: until posting is done well, we often must manually do a tweet-like messages to alert or remind of posts.
      9. NLQDPP   con regularly today, but gradually turning into a big pro: while posts potentially can be even more private, present posting systems still often lack many levels of privacy
      10. NLQDU8  long-term lesser con: people are still transitioning from messaging to posting
    6.  NLOXJN 113302402: (aside: start of previously post 3 last edited “Dec 20, 2013 11:28 PM”
    7. MXNSVM MOST IMMEDIATELY, PLEASE:
      1. NLQFJZ  ASAP RSVP to our upcoming events 
        1. MXNS8P  where if MAYBE, say YES until certain it’s a NO, including since
          1. MXNSVS Assures you’ll get notified of updates
          2. MXNSVX Biggest easiest way for you to build attendance (your YES attracts more)
        2. NLQFKT   especially including your Why & more: see here.
      2. MXNLUZ ASAP, POST TOPICS, PRESENTATIONS, EVENTS, JOBS OFFERED & WANTED, Qs, AND ANNOUNCEMENTS YOU’D LIKE US TO DO & TALK ABOUT & SHARE WITH US! –click link
        1. MXNNY0 Per our past meeting & now our new agenda[ (latest archive)],
          we are now increasingly having “PRESENTATIONS: small & sweet & regularly many & BY ATTENDEES THEMSELVES, sometimes spontaneous” (quoting that).
        2. MXNNY2 SO *YOU* (THE MEMBERS) DIRECT OUR TOPICS, maximally very democratically, via your posts on our event pages!
        3. MXNNY7 Plus ALLOWS MEMBERS to Reply post, so to
          • MXO1PY post feedback & experience with that, and
          • MXO1Q0 have a place to make+keep+SHARE notes on each topic&presentation and other posting
      3. NLQJHS  if you have trouble with something, especially any directive to you, ASAP clearly & respectfully & completely share that with its source
        1. MXNO8E  –as is the standard in most any organization which truly values its participants
        2. MXNO8W  including if you phrase it constructively as is best, then, best of all, post it as this article details.
        3. NLQJTO   note this follows from the italics of the general core directive “We strive to be PARTICIPANTS & A QUALITY TEAM, who seek fairness&ALL-to-win, &who do what’s expected or/and respectfully share their reasons, esp. for our current leaders, & here one could be u!” quoting from latest Q1 on every profile of http://meetup.com/OCJavaScript/members .
        4. NLOXM2   113305032: (aside: this section was originally previous post 4 last edited “Dec 11, 2013 12:27 PM”)
  5. NLOXHU  113301762: (aside: start of previously post 2 last edited “Dec 20, 2013 11:10 PM”
  6. NLQC20   Rules including steps to properly post, in the order encountered when doing it:

    1. NLQBMJ   find & use the best posting location
      1. MXNLDV  OTPT&OTPT: ONE THREAD PER TOPIC and ONE TOPIC PER THREAD
        1. NLQCVB   Why?
          1. NLQCVX   “one thread per topic” is key so everything on that matter is found in one place.
          2. MXNNEH  “one topic per thread” is key including:
            1. NLQD2U   so topics aren’t scattered, again so everything on any matter is found in one place.
            2. NLQCTN  insuring our many readers here aren’t overwhelmed, including so one can Mute or otherwise ignore one thread on details not of interest w/o missing any other material s/he may want or need.
        2. NLSSXZ  Doing this for event comments is the most notable violation case on Meetup and there covers common problems & great solutions.

        3. MXNO8D  To help insure this, before posting, search for the best good matching existing post then click/add “Reply” on that; and ONLY IF none found, THEN create new top-level post
        4. NLQLGS   aside: “one thread per topic” is essentially “every topic in exactly 1 thread”
          1. MY5AHS  phrasing copied (and, for future, moved) from http://meetup.com/OCPython/events/147811512­ point {MKA77Q  ideally each topic in exactly 1 thread (a top-level event comment)}
      2.  NLQCA2   On Meetup.com, also…
        1. MXNNEJ post & reply-post in the right location from the start: it’s especially key to POST including reply-post IN THE RIGHT LOCATION!
          1. MXNO2R as Meetup very mistakenly does not allow anyone, even top group heads, to move a post even if it’s in the wrong location, nor compose a new post for anyone under his/her name but oneself, nor edit it (for event comments & Greets).
          2. NLSSYE   doing this for event comments is the most notable violation case on Meetup and there goes into details & solutions.
        2. MXO1Q4 For each,
          1. NLQE4B   RSVP, it belongs on the event listing per Meetup’s YES/NO Q there (where Meetup also effectively posts it).
            1. NLQE7Y   See full details at our RSVP policy
            2. NM071Q   in addition to your RSVP YES/NO, its desirable and often required to have a synced PARTCIPATION & REVIEW thread for each potential/actual attendee, ideally started by the attendee.
          2. MXNNYI TOPIC or PRESENTATION OR Q or ANNOUNCEMENT you’d like us to do at one of our events, 
            1. MIUN5J  ideally should be proposed ASAP, ideally before the event so they can be advertised so bring in more attendees for them and/or for the event; but can & commonly are first brought up during the event
            2. NLQMRX  should include the links to the relevant {entries in our Discussion board and other past/upcoming events} if they exist.
            3. MEQNS3 should be posted by all members (not just leaders), in our event (the listing’s comments) where you’d most like it shared and be discussed-else-summarized there per NLQMWC 
            4. MKA7CG   –to find the relevant events and/or discussions to post-on and link-to, see our Home Page for a complete directory.
            5. MY5ANE  aside: this section copied (and, for future, moved) from http://meetup.com/OCPython/events/147811512 “MEQNR7   The topics desired & offered:” to here then improved.
          3. MXO299 JOB WANTED OR OFFERED, or IN-DEPTH Q, or OTHER DETAILED ANNOUNCEMENT you want to ask/share-with the group especially if could span multiple events,
            1. NLQNHL  post it on our Discussion boards, in the appropriate forum for it (as “jobs” if that exists).
            2. NLQNHU   where this is not obvious (as for jobs offered & wanted), end your announcement with say “Please first reply on this thread” so all can see and possibly-benefit-from the responses you get
              1. NLQNM6   –we realize poster’s sometimes prefer first indeed all responses go privately to them but posters need to remember they’re getting the ability to speak and advertise to all our members at no up-front-cost and often never-a-cost, so this is the first way to pay us back for that.
          4. MXNO23 EVENT you’d like us to do that we aren’t already doing, including to tell of possibly-related events that are happening, as Meetup properly intends, on our Home Page, click “SCHEDULE A MEETUP”
          5. MXO4JY Meetup member(s) that you want to contact,
            1. NLQNUQ   follow Proper messaging & verbal use (compared to posting)
            2. NLYEKS   is it more than about 4 at a time?
              1. NLYELV   if YES:
                1. NLYEMI   Use Meetup’s “email members” capability
                  1. NLYENG   which is available to all group leaders and only them
                  2. NLYENR   which can specify not all but many common criteria of who to select (such as all who have been active in the last 3 months)
              2. NLYSC0  If NO,
                1. NLYRP0   Do the first solution here which works:
                  1. NLQCHY   post a Greet on his/her member profile with the URLs of whatever you want him/her to see.
                    1. NLYEG0   as, better than messaging, this keeps the message short & public and readily recorded & shared, especially for other group members especially leaders, on the member’s profile.
                      1. NLYEIE   especially important to share with other leaders, of this group & others, when a member does something notably good or bad.
                    2. NLYRRV  limitations
                      1. NLQCJE   On 2014.09~ Meetup HQ terminated & erased all Greets on all members profiles (a notable move backward IMHO)
                        1. NM06Q4  so these instructions need to be redesigned to this article’s post standards: done
                      2. NLYRSY   will not work if the recipient does not have web access in time or
                      3. NLYS75: will not work if the recipient doesn’t check his/her Meetup in time except if one can & does SMS the recipient their Meetup profile URL to check
                      4. NLYRUF   will not work if a detailed discussion is needed (as are mostly 1-way talk)
                  2. NLYQY4   email else SMS else call the person (later if more urgent)
                    1. NLYRX1   requires the person have the phone # and/or email of the person which Meetup won’t reveal and makes generally hard to get
                  3. NLYS1R   use the old Meetup messaging service asking to get emailed copy of each message you send
                    1. NLYS3M   problem: no longer available
                  4. NLYQMB   use the new Meetup messaging service (which does a private web discussion)
                    1. NLYRZB   generally requires a manual archive of the conversation be made as Meetup makes & supports no backups nor allows this conversation to be shared
        3. NLQEAT   Event listing comments
          1. NLSOMC  are terribly useful and near essential for sharing & syncing on finer event details for the many uses.
          2. NLQMWC   should discuss else summarize, so record, all what happened at the event, plus the prep for it and what came of it after including the reviews of it
            1. NLQN3X  so include/serve-as both the event’s agenda & minutes plus a central place to discuss & record all aspects of the event (except pics which are handled by the event listing’s picture upload).
            2. NLSNWG   via including the details there in the comments if they’re very short or, especially for longer and/or changing details, linking (giving the URL) to them elsewhere, as typically on the Meetup Discussion boards
          3. NLSO5R  In making every [event listing comment],
            1. NLSS1E  post & reply-post in the right location from the start, including:
              1. NLSS6F   full painful details here
              2. NLSNHT   Do OTPT&OTPT, including:
                1. NLSNIF   watch out: avoid the extremely common mistake: don’t create a new top-level event comment instead of replying to & on the existing thread for your reply –read that
                  1. NLQB0C  Examples:
                    1. MXNO8J For good example, see Jim’s reply post­
                    2. MXNO8R For mistaken example, see Ben’s 1st 2 posts on that event listing (both at top level when a thread already exists), what led me to make this cmt as Ben’s a sharp guy so others might have trouble, too.
                2. MXNNE9 so then, for example, for any event,
                  1. MXNTUM ONE THREAD PER PRESENTATION GIVEN
                    1. MXNTUP and including a link to the thread/page of every time it was given, if that exists
                  2. MXO1PT ONE THREAD PER A PERSON’S PARTICIPATION & REVIEW,
                    1. MXO1PW so if you want to update with why you’re coming or time you’re arriving/leaving or why or your overall review of the event, use exactly 1 separate thread for that
                3. MKA7I7   specifically, insure exactly 1 event comment thread exists to discuss & record (here quoting the thread titles):
                  1. NLSSFD    “{this happening & its listing} OVERALL –please put all on that here in this thread”
                  2. NLSSC3   “this happening’s WHERE & WHEN discussion & changes  –please put all on that here in this thread” (specification at Where & When, can be 1 thread but increasingly 2)
                  3. NLQN7P  each topic/announcement/Q/presentation
                  4. NLQN6D  each possible & actual person’s “PARTICIPATION at & REVIEW of this happening –please put all on that here in this thread” –quoting the phrase used to label each such thread there.
                  5. NLSSMB   and probably more given the comprehensive charter.
            2. MXNN58  it’s easier & better-quality to 1st draft each post in a text editor that that can count characters (as max 500 per Meetup event listing comment), ideally count any text selection: currently I use:
              1. MXO29I  for very small, an event listing’s main comment box (but typically avoid posting there as that’s top-level)
              2. MXO29J  for bigger, I use LibreOffice Writer, which nicely is also FOSS­ & cross-platform­.
              3. NLSNDP   also covered here.
            3. NLSO8F   also covered  here
          4. MKA7N5  and when you’re ready to absorb it all, see the full details at “Meetup.com event listing comments: all you need to know but Meetup.com doesn’t tell you”.
    2. NLQ9OO   For most any writing (posts, messages, & more), from most important:
      1. NLQG9W   the message-conveyed, starting with the author’s intentions for it, must be overall constructive, not destructive.
      2. NLZBHX    “repetition/repeating: as much as practical, really minimize it and make it obvious (what copied/converted from & to where & how) and automate it”
      3. NLQDZ6   Make the topic worded clearly and put at the start of the point and/or (if short) in ALL CAPS.
      4. MXNN5A Ideally use outline format, with 1 “*” bullet for each nesting level (as “***” before a level-3 point)
        1. NLT8WB  more covered here
      5. MXO29F For every keyword you use, include besides it a URL for it, ideally a the Wikipedia URL else the maker’s URL, unless it is the group’s main topic or would be found in the dictionary and even then if there might be someone who wouldn’t know it; do not assume everyone knows what you’re referring to AND where to find it.
    3. NLQEZL     after your post, it’s a good idea and sometimes essential to contact the Meetup person(s) needing to see it the URL else they may not see it in time or ever.
      1. NM1LMP  –especially if the person is likely not to see post (including isn’t automatically alerted of it, as is common) plus if you haven’t gotten a reply after reasonable time
      2. MXO4OM  unless maybe for an event comment post (which, ~5 minutes after posting, Meetup emails to every profile responding on that page unless the profile owner turned it off)
        1. NLQKRQ  but still regularly people miss email especially this including from having this turned off, else see it hours later which could be too late, so is often still needed to send a pointing “tweet” message.
      3. NM1LZO  such message should:
        1. NM1L8N   be tweet-like: that or nearly as short plus including pointers ideally URL(s) to the post(s).
          1. NM1LWD   including it should refer to only few posts, as 1 to say at most 4, as any longer instructions then it generally needs to be a post itself.
        2. NM1INB   as short as minimally needed to get to get the reader(s) to look at & operate on the posts especially those it refers to
          1. NM1INZ   it is particular important to here avoid redundancy, specifically only enough to get the reader to read the post by when s/he needs to read it.
            1. NM1IUG   watch out: it’s terribly easy to put too much info, such as saying “the event has moved to ___ per post [URL]” instead of just “the event has moved: see latest details at thread [URL]”, where then the reader doesn’t bother reading the post because the sender mistakenly enabled him to get the PRESENT info from the message, and then he gets messed up & angry at you the sender as he doesn’t then find out the original address and/or time was wrong and/or has changed again, which he would have known had the sender make it so he had to check the post for this info.
        3. NM1KI7   direct & encourage the reader to reply primarily by posting notably there and NOT by replying to inquiry message
          1. NM1KJF   it’s still very useful to get some quick basic status reply, and often it’s faster & typically more familiar to reply to the message (as SMS) rather than reply-post, so you can include questions for just that in the messages
            1. NM1KP5  as “Did you get Meetup’s email _ hours ago of thread [URL] for [date & time, as “tomorrow 6pm”]?  When before then can you reply-post that?”
            2. NM1M7Z  but avoid message-responses which have valuable info as then those too will have to be reposted.
        4. NM1M4H   soon itself be reposted, along with its responses, all quoted, on the relevant discussion threads it refers to, if it and/or its responses, contains any info valuable to others now or eventually (as historical record)
          1. NM1MAY  for this, follow reposting directions
      4. MXNN5C  example real SMS:

        12/10/13 7:01 PM 14 hours ago
        Me: Hey, Jim. Quite looking fwd to ur presentation tomorrow http://www.meetup.com/Node-JS-OC/events/152003902/comments/277208382/?read=1#event_comment-277208382 . So how’s it coming? -just Reply post there now with ur status, then Reply post there with ur slides if&when u have them. Thx!

        1. NLZUTH   aside: while needed to understand this example, that URL it gives points to thread which has bee {wrongfully deleted, as Meetup makes common}; the thread referred to can be found on our latest archive of this page at thread “Tentative Presentation: Restful API server..”.
      5. NLQKSG   More examples TBA.
      6. NM1HAJ  such message & verbal alerts to post typically must still be done manually, a lot or entirely, until posting support grows
        1. NM1HDP   that is we’ve got better automatic alerts of posts (as Meetup event comments which auto email out) and we are used to checking for our posts (as checking for our Facebook newsfeed)
    4. NLYESX   Proper messaging & verbal use (compared to posting)
      1. NLYEVA   Foremost, again instead use posting where it can be made overall better.
        1. NLYFWI   including take advantage of the increasing privacy features offered by posting
      2. NLYEXX   Generally keep messages, and verbal except at in-person meetings, as short & minimal as possible
        1. NLYEZK   ideally the only stuff which (1 or more):
          1. NLYFG6  can’t readily be posted
            1. NLYFLX  as commonly a person’s private contacts or full/exact/legal identity
          2. NLYFGH    gets the reader to, at the appropriate time, read the post(s) the message refers and reply-post there  –see that
          3. NLYFJZ   is truly better to be handled verbally than in writing
            1. NLYFUC  as very sensitive/personal material especially when first being brought up in hopes quick of resolution then
        2. NM04UA  Do proper (including minimal) repeating especially for messages
      3. NLQEWM Use a messaging & talk primarily just to direct-to & remind-of post(s), pointing to where the posts are, ideally the URLs
        1. NM1I7A   as ideally one would never doing private messaging as instead be doing all posting, but posting support is often not yet fully complete, and the primary exception is still needing to alert & remind of posts.
      4. NLYG2W  Wherever practical, copy-else-convert into posts verbal talk and messages (including SMS & email) then encourage the discussion be instead moved there as talk-via-posting
        1. NLYG69   ideally by following say JotHere’s standard methods encouraging & converting replies as & to posts (right column).
  7. NLOXMM   125001432: (aside: start of previously post 5 last edited “9/10/14 8:45 AM”)
    1. NLQKI2  –this section is notably less essential than the above but still to be eventually integrated into the rest of this article, especially the additional important points it makes.
    2. NBOZ2S Just now I’m replying to another on planning for today’s event, which Mark emails out instead of posting (of course since he sent it out before I had fully-written and told him of this thread), and in it I summarize perhaps the core essentials of my above very long reply pretty well
      NBOZA6 *well enough it makes good sense to instead move that summary here where it is on topic, and instead make that point in that email a link to here.
      NBOZAJ so here’s the summary

      1. Date: [today; exact TBA]
        From: Destiny
        To: Mark
        CC: Farsheed
        Subject: RE: [today’s event planning]
      2. Body: quote(NBNRIT Dear Mark,)
        1. ..
        2. NBODL2 I would take it you don’t yet know, but by our long established posting guideline/rule [also in the 1st post of this thread] taken from years of use in other successful Meetup groups and added & posted on our group in 2013.12 months before you joined our group, this written discussion (currently email thread), as most every group writing, instead is to take place in a proper post
          1. NBOE2C as here, since this for an event, ideally in event comments (broken into the thread), or else a Meetup discussion thread ideally only one for the event for more organizer mostly stuff, and avoiding all emails.
          2. NBOXBW But since here the talk about the group was started in email, correcting emails talk then require moving them to where their content would have been originally started –into posts, which by default all could access –as our group is public even-non-profit community group (so like public servants with public records as much as possible and of course by default -think open-source project where how the internals are done are shown, and list of helpers which is necessarily large (as typically no one is paid) changing and truly unpredictable) and definitely NOT say a private for-profit business (so private readily select clients and internals which are by default private even trade-secrets –think propriety closed-source project, and with a set of helpers which is small, well-known & highly-controlled, and typically-paid)
          3. NBOY5U Specifically by wherever possible making group writings as posting, most especially the start else ASAP, which by default can technically be accessed by anyone (important because the list of who could help if they had access is commonly unknown so impossible to predict including frequently changes -my last point) but which in practice really is only accessed just by helpers present past & future, and so usual privacy worries (where one would feel “I need to have private talk & messaging”) are generally far overrated, as clear far more practical, plus properly respectful as a public & community group, is to grant access to those who might need it, which again is impossible to determine changing list and routinely larger than one imagines (there’s always someone you never guessed who could help).
          4. NBOE4Z But this using posting following our rule, especially when it requires emails to be converted to such posts, has been put stopped, so put on hold, by you (as new Head) and Farsheed’s Monday preference statement to unilaterally (as worded) not to convert emails to posts [with different especially more public access levels] so to where the content would normally go (which others would have probably said too if they didn’t yet see this bigger picture as were deeply aware of this great term rule); so while I very want to see that worked out as possible notably back to our posting standard, until then I will continue this via email.
          5. ..
  8. NLOXPI (aside: end of source postings)

  9. NLOW6J section additional history, in start-time order:

    1. NLOW79 This content I originally posted as thread http://Meetup.com/Node-JS-OC/messages/boards/thread/40285992?SEE.POINT=MXNL2E
      1. NLOWE1  as I 1 of the effectively 2 major co-founders of that group
      2. NLOWEA   and heavily referred to it, for this and other groups I was managing, in every event listing and more, as “more via cmts” in http://meetup.com/OCAndroid/events/169934392?&_point=N235KA
      3. NLOWJJ   with latest forever archive copy here –wise to Meetup-enabled destruction, I backed it up, and indeed:
      4.  NLOWIO   then just now 2015.03.23Mon17 I discovered that that group’s new leader(s) (Meetup makes it easy to hide which ones but its likely its new head since 2015.08) has silently deleted this my post plus the agenda this references plus all my other postings there, among his/their other even worse erasure of the group’s co-founder –where all destruction fits the pattern of one attempting to erase all existence of those (in this case me) with knowledge of his serious apparent wrongdoings: here my witnessing he apparently stole our group so then me asking him so unknowingly revealing I knew
    2. NLOXB9  so ~1hr ago, as reliable home for this important content, I create from scratch this post http://1.JotHere.com/4512 then copy the archived content here, just sub-section per post.
      1. NLQ375 from the start, cut this text as it now applies, “N3D0Z9=This content I will move-so-redirect to and merge into http://1.JotHere.com…­ as it applies much more than to this group.”
      2. NLQ1ZP   -linking to this point are post start markers from the {previous=original} location and the last archived modification date of that post along with its anchor ID, preserved here especially so prior references to that point (that post) can still be found.
    3. NLOYE5  in title, added “[wherever it would improve things, ]” to be fully accurate
    4. NLOYKY todo: improve formatting some especially convert copied point ids (as “N3D0UL”) into proper HTML id/anchors and cutting unneeded “{..}”: done
    5. NLOYSU add to categories “writing LGYLMM” (esp due to NLQ9OO) and “post LXYYH2”
    6. NLOZ0X  create category “messaging NLOZ0X” (and add this to)
    7. NLOZ6H  create category “telephone calling NLOZ6H” and add to
    8. NLOZFJ  create category “verbal NLOZFJ” but don’t add to
    9. NLP0C2 create category “emailing NLP0C2” but don’t add to
    10. NLP0SA  Todo: update http://1.JotHere.com/N235ZE (as “more via cmts”):  done
      1. NLP0U5 from its original thru present target http://www.meetup.com/Node-JS-OC/messages/boards/thread/40285992?&_point=MXNNYI#113302402 –which no longer works
      2. NLQQI5   now replace to http://1.JotHere.com/4512#MXNLUZ , also a more motivating location.
    11. NLP0VT publish 1 2015.03.23MonPst18:53.
    12. NLPEWK  do NLOYKY & NLPFN4 & NLQ375;
    13. NLQ5I7   todo: clean up much of the writing clarity especially organizational problems: done
    14. NLQ5KK  publish 2 2015.03.24TuePst0924.
    15. NLQ721   NLOXDX: updated to new format of simple history including removing “NLPFLX   history in reverse start-order”
      1. NLQ8HD   doing NLQ5I7: ~4hours of work; cut as no longer needed “MXNN5G with more essentials in my next posts below.”; cut as not directly related: “MY5A8D Additional text copied (and, for future there, moved) from http://meetup.com/OCPython/events/147811512­ to here: [just MKA7N5]”; arranged “start of previously post” to fall nearest their original locations;  NLQQI5; publish 3 2015.03.24TuePst1702.
    16. NLTYB9 motivated by NLSR9J,
      1. NLSJ5Y did significant improving especially to NLQEAT; add NLT9F1; add to category “rule N0BY8E” as this is mostly rules; add ; add categories “Universal Rules & Guidelines for Meetup.com L2PFGY LR7MKT” and “Meetup.com bug LSXLEY”
      2. NLTYDG spellcheck; remove “ol class=”fakeOL” type=”1″” and other “fake”; apply N14GIY plus 2 manual fixes it mysteriously not spot; cut 1st point “NLOYC3   status: see section additional history” since universal #M7AUKR; publish again 2015.03.26ThuPst11:49.
    17. NLYDK1   fixing links that mistakenly open in new windows, by cutting “ target=”_blank””: ~34 removed; did NM06Q4; touching that, updated NLQNUQ including the article it links to; spellcheck;  apply N14GIY latest mod (from “( | |&nbsp;)*<sup>(~(<sup)(KENC7Z|KEP2FG|[^0-9A-Z]))*{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}~[0-9A-Z].@</sup>( |&nbsp;|\:)*”); publish again 2015.03.30MonPst0045.
    18. NM1F5J   NM1F5J: Lucy‘s review of this just now; including coming out of that:
      1. NM1MEQ   todo: make positioning to a page location animated so is notably more clear what is happening
    19. NM1L2Z  {contents of NLYFGH: factor out then significantly expanded}, {NLQ8UT: significantly update}; spellcheck; apply same N14GIY latest mod; publish again 2015.03.30MonPst1516.