pattern flaw|bug LGB4B3

{NQ8C2V https://en.wikipedia.org/wiki/Software_bug{}NQ8C2V}
{NQ8C2W parent fr ‘None’ to ‘pattern NMG2ND’ {}NQ8C2W}

Oct 122015
 

NW0NUS  “intro & overall”

  1. NW0NYD  ‘This {post & its comments}’s ‘TOU(Terms Of Use) including copyright ©, confidentiality/privacy, info’s allowed use’ is JotHere.com’s default TOU(Terms Of Use) except: none.
  2. .
    .

    NW0NYO  post name:

    ‘WordPress plugin ‘Duplicate Post’ especially on 1.JotHere.com ’NVUVL5

    1. NW0O29  ‘‘section history additional’ ‘in reverse start order’:’ name…
      1. NW0O2S  now originally to next: present value
        1. NW0O3E    “per post name, add post to categories”
          1. NW0O41  ‘WordPress plugin LXI1Y7’
          2. NW0O5T   ‘this site’s documentation for[……]MORE
Dec 082012
 

MEQGSP:

MAZBVC:THIS POST

  1. M33YGV:Title: Meetup.com telling the creation of an event, notably telling who created an event when & ideally why 
  2. M33YH4:URL: http://1.JotHere.com/3912#MEQGSP
  3. MAYCNN:is currently being updated ~1x/6mo; ID of last item is version ID.
  4. M87XAJ:has all key details are in BOLD with most-essential & -timely first.
  5. MAZBWQ:has SUBSECTIONS: WHAT & WHY, WHEN, WHERECOST, WHO’S PARTICIPATING, WHAT TO DO, ADDITIONAL DETAILSPOST TODO, CREATORS, ADDITIONAL DETAILS FOR ORGANIZERS/DEVELOPERSFOOTNOTES, POST HISTORY.

MAXFOC:WHAT & WHY

[……]MORE

Oct 282012
 
 Posted by on UTC 2012.10.28Sun at 19:50 of dating MCIODJ, pattern flaw|bug LGB4B3 No Responses »

MCINQO:a woman disrespectfully-not-following-thru (as flaking) on a guy before-else-on their 1st date http://1.JotHere.com/3690#MCINQO

MAZBVC:THIS POST

  1. MAYCNN:is being updated daily so load/refresh it often! ID of last item is version ID.
  2. M87XAJ:All key details are in BOLD with most-essential & -timely first.
  3. MAZBWQ:SUBSECTIONS: WHAT, WHY, WHEN & WHERE, WHO,COST, PREVENTION & CURE, ADDITIONAL POST HISTORY.

MAXFOC:WHAT

  1. MCIQQK:1st a guy has & shows a gal romantic interest in her (else the reverse, though that’s way too rare).
    1. MCIQVY:Provided the[……]MORE
Oct 272012
 

human legs hanging out of trash canMCJ0IH:humans’ increasingly socially-disposable society http://1.JotHere.com/3707#MCJ0IH

MAZBVC:THIS POST

  1. M87XAJ:All key details are in BOLD with most-essential & -timely first.
  2. MAZBWQ:SUBSECTIONS: WHAT, WHEN & WHERE ,WHOCOST, PREVENTION & CURE, ADDITIONAL POST HISTORY.

MAXFOC:WHAT

  1. MCJ8MX:This is

    1. "How do I block you in real life?"MCJ8NO:where every person can, even on a whim, super-easily & wrongfully dismiss & escape from most any individual or organization plus sometimes swap out even their own friends & sex partners —so do
    2. MCJ8OT:created by & only possible[……]MORE
Jun 202012
 

M5XSYR: BUG: transferring/moving media (pics,video,etc) between/to-another Google Picasa account mostly impossible http://1.JotHere.com/3302#M5XSYR

  1. M3KEH0: Definition

    1. M5XOG3: for instance https://picasaweb.google.com/<OwnerGoogleAccountNum/>/<AlbumName/>?authkey=<KeyNum/>#<Photo?Num/>
    2. M5XT47: As far as doing this, according to the official docs on this(and additional sites seem to confirm), one can only do it for all the media in an account (in total bulk) and even then the destination account then looses any option to so transfer/move anything out[……]MORE
Jun 202012
 

http://1.JotHere.com/3298#M5XO9I: please comment here! -simply create an account if you don’t yet have one; the version ID of this post is the ID of the last entry of its history.

  1. M33YGV: Title:BUG: Google Picasa sharing URLs include owner’s Google account number

  2. M3KEH0: Definition

    1. M5XOG3: for instance https://picasaweb.google.com/<OwnerGoogleAccountNum/>/<AlbumName/>?authkey=<KeyNum/>#<Photo?Num/>
    2. M5XOJF: Problems this cause include, from least to most serious:
      1. M5XOMS: Causes URLs which are quite a bit longer than necessary
      2. M5XOK0: Chan[……]MORE
Sep 102011
 

LRBF47 Communicating in the Best Location, especially with Meetup.com http://1.JotHere.com/LRBF47

  1. This is the communication part of the intermediate level of On Meetup, etiquette & things-to-know, especially when RSVPing LEVV22

    –see that for more essential guidelines & rules.

  2. In communicating, where you communicate is King, so notably for most anything involving multiple people (groups & organizations & announcements more), you should (communicate foremost by appropriate posting)LRBX9W in-place-of private & direct messages & calls & talk.

    [……]MORE

Feb 082011
 

LEVV22: On Meetup, etiquette & things-to-know, especially when RSVPing LEVV22 updated 2011.09.10pst2040

  1. LEXLUA: Beginner-level

    1. as some aspects of an event listing are still messed up by event “expert” Meetup.com.

      1. The short answer here is easily NOT all who “Who’s coming” to this event (rather a very small subset), so if this list would ever stop you from co[……]MORE