Meetup.com/OCAndroid Meetup M5FF9H

CONSTRUCTING: Android user syllabus

Mar 282013

Posted by Lucy Parker on UTC 2013.03.28Thu at 17:25 Android OS LSIW3D, Meetup.com/OCAndroid Main Meetup M5FFB6, syllabus MKDUQ3, user MKDUZQ No Responses »

MKDTKW: http://1.JotHere.com/4080#MKDTKW

MAZBVC:POST

MAYCNN:currently updated every ~1 month; version ID is the ID of last entry in the post history.
M87XAJ:fully outlined with the most essential and/or timely details first and/or in-bold. So to skim, just read in order the top-level points and, when a match, its bold points.
M33YGV:title: CONSTRUCTING: Android user syllabus
MAZBWQ:subsections: WHAT & WHY, WHEN, WHERE, COST, WHO’S PARTICIPATING, WHAT TO DO, ADDITIONAL DETAILS, POST TODO, CREATORS, ADDITIONAL DETAILS FOR ORGANIZERS/DEVELOPERS, FOOTNOTES, POST H[……]MORE

OCAndroid Main Meetup #61(pdt2012.10.18thu1800-2200: including ANDROID AS A CONTROLLER OF OTHER DEVICES): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing

Sep 242012

Posted by DestinyArchitect on UTC 2012.09.24Mon at 17:59 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 11 Responses »

MAVROU:OCAndroid Main Meetup #61(pdt2012.10.18thu1800-2200: including ANDROID AS A CONTROLLER OF OTHER DEVICES): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing http://1.JotHere.com/3633#MAVROU

M31R7G:Definition
1. M325R1:For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!
2. M90U53:series post:all,(event:prior,next).
M33Q1M:Additional document history, in order:
1. MAVRUV: I Destiny create this by, on the (the prior one=http://1.JotHere.com/3477[……]MORE

ACCIDENTAL DUPLICATE: OCAndroid Main Meetup #60(pst2012.08.27mon1800-2200: including TBA): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing

Aug 192012

Posted by DestinyArchitect on UTC 2012.08.19Sun at 14:55 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 3 Responses »

M92VRO: Duplicate post!; see instead the original.

M87UOR:ACCIDENTAL DUPLICATE: OCAndroid Main Meetup #60(pst2012.08.27mon1800-2200: including TBA): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing http://1.JotHere.com/3477#M87UOR

M31R7G:Definition
1. M325R1:For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!
2. M90U53:series post:all,(event:prior,next).
M33Q1M:Additional document history, in order:
1. M87UNY:I Destiny create this by, on the (the[……]MORE

OCAndroid Main Meetup #60(pst2012.08.27mon1800-2200: including NOVEL USES OF ANDROID, as TV entertainment center PC): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing

Aug 032012

Posted by DestinyArchitect on UTC 2012.08.03Fri at 22:49 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 7 Responses »

M87UOR:OCAndroid Main Meetup #60(pst2012.08.27mon1800-2200: including NOVEL USES OF ANDROID, as TV entertainment center PC): D ISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing http://1.JotHere.com/3477#M87UOR

M31R7G:Definition
1. M325R1:For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!
2. M90U53:series post:all,(event:prior,next).
M33Q1M:Additional document history, in order:
1. M87UNY:I Destiny create this by, on the (the prior one=http://1.JotHe[……]MORE

OCAndroid Main Meetup #59(pst2012.07.30mon1800-2200: including BEST TABLETS,OUYA GAME CONSOLE,GOOGLE JOB): discussion thread of what will, is, & did happen beyond the event listing

Jul 292012

Posted by DestinyArchitect on UTC 2012.07.29Sun at 12:35 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 25 Responses »

M7XSSM:OCAndroid Main Meetup #59(pst2012.07.30mon1800-2200: including BEST TABLETS,OUYA GAME CONSOLE,GOOGLE JOB): discussion thread of what will, is, & did happen beyond the event listing http://1.JotHere.com/3440#M7XSSM

M31R7G:Definition
1. M325R1:For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!
M33Q1M:Additional document history, in order:
1. M7XSU2:I Destiny create this by, on the (the prior one=http://1.JotHere.com/3308#M671TZ) latest M7XSKO , doing Copy to a new d[……]MORE

OCAndroid Main Meetup #58(pst2012.06.25Mon1800-2200: also USER ISSUES, as LOW-COST TABLETS): discussion thread of what will, is, & did happen beyond * the event listing

Jun 252012

Posted by DestinyArchitect on UTC 2012.06.25Mon at 15:14 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 15 Responses »

M671TZ: OCAndroid Main Meetup #58(pst2012.06.25Mon1800-2200: also USER ISSUES, as LOW-COST TABLETS): discussion thread of what will, is, & did happen beyond * the event listing http://1.JotHere.com/3308#M671TZ

M31R7G: Definition
1. M325R1: For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!
M33Q1M: Additional document history, in order:
1. M671TY: I Destiny create this by, on the (the prior one=http://1.JotHere.com/3250#M5FESY) latest M5GQAP , doing Copy to a new draft, t[……]MORE

OCAndroid Main Meetup #57(pst2012.06.11Mon1800-2200): discussion thread of what will, is, & did happen beyond * the event listing

Jun 102012

Posted by DestinyArchitect on UTC 2012.06.10Sun at 17:01 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 3 Responses »

http://1.JotHere.com/3250#M5FESY: 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.

M2OXUB: Title:OCAndroid Main Meetup #57(pst2012.06.11Mon1800-2200): discussion thread of what will, is, & did happen beyond * the event listing

M325R1: For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!

M33Q1M: Additional document history, in order:

M5FESY: I Destiny create this by, on[……]MORE

OCAndroid Main Meetup #56(pst2012.05.28Mon1800-2200, also user issues as ANDROID MEDIA MGMT): discussion thread of what will, is, & did happen beyond the listing

May 282012

Posted by DestinyArchitect on UTC 2012.05.28Mon at 06:17 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 9 Responses »

http://1.JotHere.com/3218#M4QIBO: 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.

M2OXUB: Title:OCAndroid Main Meetup #56(pst2012.05.28Mon1800-2200, also user issues as ANDROID MEDIA MANAGEMENT): discussion thread of what will, is, & did happen beyond the listing

M325R1: For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!

M33Q1M: Additional document history, in order:

MORE

OCAndroid Main Meetup #55(pst2012.05.14Mon1800-2200, COMPARE-YOUR-CODE): discussion thread of what will, is, & did happen beyond the listing

May 142012

Posted by DestinyArchitect on UTC 2012.05.14Mon at 15:41 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 14 Responses »

http://1.JotHere.com/3159#M41B3P: 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.

M2OXUB: Title: OCAndroid Main Meetup #55(pst2012.05.14Mon1800-2200, COMPARE-YOUR-CODE): discussion thread of what will, is, & did happen beyond the listing

M325R1: For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!

M33Q1M: Additional document history, in order:

M41B3O: I Destiny create[……]MORE

OCAndroid Main Meetup #54(pst2012.04.30Mon1800-2200, User Issues): discussion thread of what will, is, & did happen beyond the listing

Apr 262012

Posted by DestinyArchitect on UTC 2012.04.26Thu at 12:24 event (within spacetime) LX7RHI, Meetup.com/OCAndroid Main Meetup M5FFB6, of Meetup.com/OCAndroid M2CI1L 14 Responses »

M33PZ6 Version 1.2

M2OXUB: Title: OCAndroid Main Meetup #54(pst2012.04.30Mon1800-2200, User Issues): discussion thread of what will, is, & did happen beyond the listing

M325R1: For what is posted here & how, please read each link above, especially the last one; then PLEASE COMMENT HERE AND ADD MORE TOPICS & POINTS!

M33NXM: URL: http://1.JotHere.com/3024#M33PZ6

M33Q1M: Additional document history, in order:

M33PZ5: I Destiny create this by, on the (the prior one=http://1.JotHere.com/2958#M2WN3M) latest “Version 1.2”, doing Copy to a new draft, then th[……]MORE

Older Entries

“Select & Display Category”N10H7P – – –over 250 categories, each with (its post count); use typing and up&down keys to scroll & select

“How to Use this Website”N10FZM

“^M8K00L

^N0IDXM Like most websites, this operates best via a laptop or desktop!
1. ^N0QW6N Still truly need to view & use this website on mobile OS, as on smartphone & tablet? (instead of just using a normal laptop or desktop) –Then please be ready to experience some problems and find & do workarounds, and ideally report these to be helpful, as, unless say you can help, this site has not been ported-to & well-tested-on mobile OSes since that's much harder, including: many times more devices to test, plus mobile web browsers often are incomplete & buggy, such as: following a link to a position within a page strips off the position(the "#id" anchor tag) so instead positions to just the start of the page.
^N0QWYV section history in order:
1. ^N0QWZS prior not recorded here
2. ^N0QX0J Per #N0P4V6 and more ideas, rewrite including name sub N0QW6N.
3. ^N0SF78 ~12hrs ago, especially as this point needs to be 1st but #N0QW6N is so seemingly-unavoidably {long an negative}, plan move this to its own article, then making the additional here short as quote(–click for details and especially to operate on other devices as via smartphone & tablet);
  1. ^N0SQ88 until then, temporarily make #N0QW6N small, via q( style=";font-size:84%">)
4. ^N0SEHV Title (q(As with most websites, this website is best viewed & used on a laptop or desktop!)) as a problems as "best viewed & used on" can be viewed as what would be best for the user (rather than the website) and also it repeats "website" and also "As with" (with perhaps grammatically correct) is less familiar & more stuffy, so replace with present.
5. ^N0SR31 instead of standard sized, placed title in q( style=";font-size: 133%;") as this is probably a big problem plus still too much attention to #N0SQ88
6. ^N0YHZH now replace q(Then be ready) with q(Then please be ready) as the politeness helps, including makes the transition to a negative less jarring
7. ^N0YI37 now replace q(unless you can help us) with q(unless say you can help) as sounds less desperate & more hopeful.
^M79S95 “content terms-of-use including copyright .. –follow this especially before & when reproducing any content-or-info from here, including copying or printing or quoting & paraphrasing of it.”
^N0SFVA section history in order:
1. ^N0QXNZ prior not recorded here
2. ^N0QXP6 per #N0P4H0 and source's new title, change from “content {use-terms including copyright}: ~“by default ~“properly-including-minimally copy but fully refer- especially link-to info..”” & why” to present, also using "reproducing" above "copying" per present Winter Olympics on MSNBC saying ~"Do not reproduce or transmit without written permission of...",
3. ^N0SGFW replace quote(–follow this before & when reproducing any content-or-info here, including any printing or copying of it.) with present: adding "especially " plus "or quoting" plus making all links to instead of some external definition (as Wikipedia) links the point on the matter in the target doc (which also includes the def links) (well "reproducing" as that word is not (yet) mentioned); also cut spurious quote-mark.
4. ^N0W7PE title: updated with latest values and made entire a single quote with ".." in middle.
5. ^N0YHJW This currently right after #N0SFIK (about); and was thinking about moving to the bottom as it's standard to have a copyright; but since this is short very (plus standard) and very important (indeed needed now for an upcoming legal post where the recipients (insurance adjusters) might be tempted to copy; plus not-respecting copyright is very serious problem for movies and so their copyright notice placed in very front of all DVD & Blu-ray "Play film"), decide to move it as far up as possible, so right after #N0IDXM.
^N0SFIK “about this website” –click for details
^N0RLQ5 section history in order:
1. ^N0SFKJ now created & added to #M8K00L, even though that's on the topic of "Use" not general "about", as no other better spot (including links in tagline impossible) and a link to site "about" expected on every page of a website but otherwise missing, and added right after #M79S5K as that seemed to well introduce it as well as being at right detail; don't include slogans as those already mentioned in tagline and again at (below) #M7A5F8.
2. ^N0YIB6 after move #N0YI6M, replaced from q(“about this site 1.JotHere.com”) with present
1. ^M79S5K This website is IN ALPHA-TESTING, most especially & obviously its aesthetics are to be improved though slowly, as
  its first-priority and increasing-accomplishment is offering regularly-essential functionality that's missing from most-or-all other websites.
  ^N0RLQ4 section history in order:
  1. ^N0RLQH prior not recorded here
  2. ^N0RLR6 per #N0P6FB, move this from right after #N0AD69 to present (right after best viewed & used on); plus move up "achieves" & some improved wording.
  3. ^N0YI6M instead of right after #M79S95, decided, as this logically belongs, to be a (1st) sub of #N0SFIK
^N0BQ1C communication especially writing conventions used here unless a post here does & especially-says otherwise:
^N0WDZ8 section history in REVERSE order:
1. ^N1404R to present as prior name "writing conventions" doesn't other communication forms of #N0AD0Q but since that is the only exception it seemingly doesn't deserve its own section (though barely as that point is very important"
2. ^N0WE01 from begging q(standard redaction: in reasonably public content here, certain info must be standard-redacted else otherwise-not-included) changed to present formatting including to match new #N0W7PE.
3. ^N0WDZP other prior exists
4. ^N14065 at creation (I think) headlined q(writing conventions)
1. ^N0AD69 “standard redaction .. in reasonably public content here, certain info must be standard-redacted else otherwise-not-included to appropriately both respect privacy & insure security. ..”
  ^N13QXQ section history in REVERSE order:
  1. ^N1485T move this right above #N140QE as it is more important; indeed make it top as, for privacy/security, it's really most important, and short.
  2. ^N1481U other prior exists.
  3. ^N1482M for some/all time before, was last (in #N0BQ1C)
2. ^M87XAJ fully outlined with the most essential and/or timely details first and/or in-bold. So to skim, just read in-order the top-level points and, where a match, the bold sub-points.
  ^N0RQTI section history in REVERSE order:
  1. ^N1472X now decide to (again) place this 1st as compared to present 1st #N140QE, it's more {immediately relevant since we're reading} and (as the 1st got longer plus a bit more complex with #N143OV) shorter & sweeter
  2. ^N140LX added hyperlinking to "outlined" and cut "placed " and replaced q(the bold points) with present.
  3. ^N140HW (again) decided to place this 1st as its super short & important including it extremely applies to this text widget section.
  4. ^N0RQUW Replace fr(in order) to(in-order) and fr(when a match, the bold points) to present, as a tiny bit clearer.
  5. ^N0RQU6 other prior exists
3. ^N140QE minimal repeating, especially by instead hyperlinking, else other means to easily-and-exactly point, to what was already expressed.
  ^N0SVK8 section history in REVERSE order:
  1. ^N141B7 Decided to make this 1st it should overall sound overall good to anyone and applies say even for those not choosing outlining & bolding
  2. ^N141A5 minutes ago, created this
  1. ^N143OV a key & simple way to achieve: for any content repeated, designate a source instance and replace all other instances with a link to this source, then on the whole resultant content (which should now be much shorter where the repeats were), repeat this process until no more replacements can be done.
  2. ^N141P1 This seems the #1 easy way to cut down on our information overload, indeed hugely cut down, plus properly credit sources & minimize maintenance & maximize control.
4. ^N0ACYQ replying to content here is done by 2 basic ways, from most preferred:
  ^N0SVK8 section history in REVERSE order:
  2. ^N14128 from subsequent sibling changes, this now falls right after #N140QE which is okay as that & above apply to everything including this (very) important thing and are short.
  3. ^N13Z7O move this (up) to 1st (in #N0BQ1C) as this feels even possibly more important than really-important top item #N0TF0C (probably so because the material IS often ready for folks to look at when they are pointed to it, but they still need to know about this reply matter); so plus is not (well not just) a #N0BQ1C"writing convention" (parent) but really a communication convention
  4. ^N0SVMF some improvements, most notably replacing q(where you assume your reply will be reposted after what it replies to else within that article page (again per this site's top goal: to communicate via proper post) with just the standard redactions unless you in your reply specify something different (as the additional redactions desired for its repost).) with present as seemingly much clearer including use of {} to break up & group simultaneously-applying concepts plus adding link to the mentioned site feature and more.
  5. ^N13Z3C at this history point or before, placed this right after #LG4OWH then only this morning that fell right after #N13OG4
  6. ^N0SVKV other prior exists
  1. ^N0ACZQ The vastly preferred method to reply is for you the replier to reply directly yourself, and via proper posting here: via a reply comment on the content being replied to else in the best matching thread (including creating a thread for your point, but only if it doesn't already exist), else via a new article which in its title-else-intro tells including links-to what it is replying to.
  2. ^N0AD0Q Failing that, reply by other methods (as ideally reply in writing (as posted here except in not the best place, or posts on other sites, or via email or txt/SMS) else reply verbally (as phone calls or in-person))
    where you assume your reply will be reposted...
    ^N142AC section history in REVERSE order:
    1. ^N142JD make each sub-point a separate point, cutting the {} and br-tags
    2. ^N142BZ start each sub-point (4 of them) on its own line to improve readability of such necessarily-long sentence.
    3. ^N142AX other prior exists
    1. ^N142LD adjacent especially right-after what it replies to else within that article's page
    2. ^N142LU with just the standard redactions
    3. ^N142MK per every quality website's top goal to communicate via proper post, so here on JotHere still get all related info centrally-gathered and, as needed, centrally-discussed, even including the (potentially many) replies-to-it made NOT via posting here
    4. ^N142OF unless in your reply you specify something different (as the additional redactions you desire for your reply's repost)}.
5. ^N0TF0C Unlike blog and other usual postings (which, shortly after posting, typically become dated & "die" as just yesterday's news), here posts can be live wiki pages so typically are, similar to Wikipedia pages, so here, frequently articles, and sometimes even comments, are forever works-in-progress indeed visible from their earliest beginnings sometimes & ideally, including just being constructed posts, especially on our Home Page, and then get updated, ideally regularly, so don't assume the (too) well-displayed 1st-post date, which is often just the creation date, is also when the content was last updated, plus some posts have multiple authors plus could have owner(s) of the included content who are not it's author(s).
  ^N0TGHC section history in REVERSE order:
  2. ^N13RU3 present version, significantly extended & clarified from q(.., typically posts here are live wiki pages -similar to Wikipedia pages- so here, frequently articles, and sometimes even comments, get updated, ideally regularly, and some have multiple authors (plus potentially owner(s) who are not the authors))
  3. ^N13RNP now located as 1st item of #N0BQ1C as this indeed appears the most needing-alert-thing, as now reminded when doing removal such alert at 4250#N13QPB
  4. ^N0YK11 replace q( and sometimes comments, get updated, ideally regularly, and can have multiple authors) with present more clear & accurate.
  5. ^N0YJ2H replace beginning of q(Here articles are typically wiki pages here rather than blog posts) with present, adding "die" vs. "live" comparison and q(-similar to Wikipedia pages-)
  6. ^N0YH4Y per #N0YGKD, replace from q(are periodically updated) to q(get updated, ideally regularly, ) plus put all bold in large, too'
  7. ^N13RJZ at creation time, since this is really important including to make the removal of #N0TG9B, wanted to place high but placed right after #M87XAJ since it's short & quick
  8. ^N0TGHP now created, motivated to introduce including introduce the need for #N0TFGY, and then found this also served as an intro & parent container for #M7AUKR.
  1. ^N0TFGY So among numerous benefits of a wiki, this means, on this site, creating a post including comment is lowest-stress, including since: (1) it need not be initially complete and regularly isn't, as it readily can be updated as convenient & more is known and often is, and (2) one can use additional authors to help create it, and (3) more lowest-stress reasons.
  2. ^N0TFGY But this site doesn't yet automatically alert on the post itself of any additional updates to it and authors on it; so the post author(s) must maintain this info manually in the post itself and the featured (initial) date & author on a post are often just its beginning so readers must look at a post contents, generally the bottom of its text, to see how recently & frequently it's been updated & how, plus to see its additional authors & owners if any.
    ^N0TG8Q section history in order:
    1. ^N0TG9B created now, motivated by having to continuing to declare & update 4250#MAYCNN there and its many copies: this is needed including so if that's not declared, then it's implied.
    2. ^N0W5KH appended q( (and owners when different from the authors)), plus similar in parent, in response to new 4254#N0W55M linking here.
    3. ^N0YGKD want to cut having to place at the top of every post say 4250#MAYCNN q(possibly recently updated: see post history bottom(newest).) so:
      
      ^N0YGP6 replace q(readers must read the post, generally the bottom of it, to see how recently & frequently & how it's updated plus see any additional authors (and owners when different from the authors).) with present.
  3. ^M7AUKR as feasible, every content item & sub-section includes&maintains its history (who changed it when & how & why) and each version's details (ID & date & completion status).
    1. ^M7AUSO After 2012.06~, in better {articles and even sub-sections & comments}, the author(s) has created & maintains a sub-section “.. history in order:”, which almost always is its last section.
      ^N0SHYX section history in order:
      
      ^N0SHZF prior not recorded here
      
      ^N0SI3R Replaced fr(In better posts after 2012.06~ plus a few comments & sections,) to present as much clearer plus more accurate.
    2. ^M7AUTO for the version of text, see its sub-section “.. history in order:”'s last entry: the ID (at the entry's beginning) will also be the version ID, moreover if the entry ends with a date as "; pst2014.02.01Sat0806." that also tells when last edited.
    3. ^M7BKAZ automatic maintenance including self-labeling {of history sub-section and version-ID & -date} is planned (for every post, comment, & section, and eventually every text snippet)
    ^N0SH8H section history in order:
    1. ^N0SH8X prior not recorded here
    2. ^N0SHAE title fr(every post, comment, & section's history & version: ) to present (making a statement of what's done) to be in line with title of {the parent section=#N0BQ1C} and just be considerably clearer.
6. ^LG4OWH ideally a special unique tiny ID on every item, as “LG4OWH” on this point. While initially a bit odd-looking so made small & tucked-to-the-side wherever possible, these are very-powerful permanent short IDs for most any item, including for any point, step, sentence, or sub-content, or function/procedure, or folder or file, or change or version, or even a physical item or a name itself, enabling it to be uniquely & permanently portably-tracked & referenced (so then also easily commented upon: just refer to it by this ID), plus creation-stamped (tellable when it was created down to the second, plus often who created and even where and in what context including sometimes why), even eventually telling the item's full history
  ^N0RPTG section history in order:
  1. ^N0RPTY prior not recorded here
  2. ^N0RPUL Replace fr(What are these codes as “LG4OWH” on this paragraph? They're very-powerful permanent short IDs for most any item, ) to present, especially to fit {the topic heading=#N0BQ1C} plus to share a bit more informative, congelializing info.
  1. ^N084ML so achieving the lion's share of this site's goal {to point & link to anything, then also enabling easy commenting on it}.
    ^N0SV2F section history in order:
    1. ^N0SV2U prior not recorded here
    2. ^N0SV3N replace q(this site's goal N084LL (to point & link to anything, then also enabling easy comment on it)) with present as more readable by humans.
    3. ^N0YIUA until now this right after #M87XAJ(outlined) but, while an immediate curiosity of any onlooker, it's not that intrusive now that codes are IDs are typically stashed on the right and more important is point #N0TFGY so now place right after #N0TF0C.
  2. ^N0ZU2S
    ^N0ZUKM section history in order:
    1. ^N0ZULK prior not recorded here
    2. ^N0ZUM1 created this as it seems important basic stuff to explain plus especially, thanks to 4250#N0T3FD, #N0ZSRS and #N0ZSXP now working (as each page converted) so seem worth mentioning.
    Some key ID navigation goals: ideally,
    1. ^N0ZSRS every display of an ID is a working virtually-permanent hyperlink to the content it points to
      1. ^N0ZTN5 so you can easily save (including bookmark) and share that location indefinitely
      2. ^N0ZTDB typically to a URL of form as http://1.JotHere.com/3374#N0ZTDB where the ID is the last & anchor component (so that one points to here!)
    2. ^N0ZTYA clicking on an ID:
      1. ^N0ZSX5 positions your web browser window (so bringing you) to where the content it points to is (and so then your browser Back button gets you back to where you were before, etc.)
      2. ^N0ZSXP highlights that content it points to or at least highlights its adjacent ID label, so you know what you've been-pointed and gone to
  3. ^N13OG4 Full & Proper inclusion of hyperlinks-else-best-approximation.
    ^N13QXQ section history in REVERSE order:
    1. ^N13R4P positioned right after #LG4OWH as (including unlike that) this style stuff an ordinary reader can pick up just the examples in the existing content.
    2. ^N13QY3 created at time of its ID; placed right after #M87XAJ as (then) seemed simple & quick
    1. ^N13PE1 at least to the degree expected by at least scholarly publications as say Wikipedia which this site is similar to in this aspect
    2. ^N13O16 Every use, or at least the first recent use, of a word or phrase here which could possibly be unfamiliar to any readers (except perhaps the very rare) is to be a hyperlink, else have an adjacent link, to its definition in this context, notably to the author(s) definition else to this website's definition (web search here can usually find it) else the definition by a reputable source most notably on Wikipedia else Google Maps.
    3. ^N13OPV Every reproduction and ideally derivation here should have adjacent-or-on-it a telling-of-its-source including a hyperlink-else-best-approximation to its source, including as required by copyright here.
    4. ^N148NO also enables the most minimizing of repetition.
    5. ^N13P24 Tremendously facilitating all this is this site's maximal ability to well-point to items here.
^M79SQB Powered by YOU!
^N0WE9Q section history in order:
1. ^N0WEAA prior not recorded here
2. ^N0WEAJ title: from font-size:100% to present for emphasis.
1. ^M7A5F8 “Got a thought? Jot it Here!™ –this website is for everyone's original & accurate writings on any topic” plus 1.JotHere.com offers regularly-essential features offered sometimes nowhere else,
2. ^N0NAWO So please:
  1. ^N12MAN
    ^N12MCW section history in order:
    1. ^N12MDA starting as a target for "read" in #N12L8B(salutation), at time of its ID, created this, placing it as 1st item (since "look first") of #N0NAWO
    2. ^N12OXO Add to this 4 points: #N12MH8 (new), #N12NEV (new), #N0SRK8, #N12NTO (new).
    Read our Content! –especially whatever you were linked/referred to here
    1. ^N12MH8 Our Writing Conventions (above) enable for very efficient reading here and give answers on how.
    2. ^N12NEV If you were pointed to some point here, especially pointed to an exact point in the middle of some page (as this site maximally supports),
      1. ^N12O00 be sure to also read the text immediately prior to where you were pointed to, including the titles & ideally other-bold-parts of all the larger sections containing it, in order to get the context of that point.
      2. ^N12NSL And to find again where you were pointed to, all you need to do is re-follow or refresh the link pointing you to here.
      3. ^N12O0K And if you're signed in here, be sure to workaround for WordPress's bug of its top status bar covering what you were pointed to: after the page scrolls to that point now at the top of the page, up-scroll a tiny bit (typically just 2 lines; use the up-key ideally) searching for the ID & text you were pointed to (IDs are typically floated right) knowing ideally at least the ID will be highlighted.
    3. ^N0SRK8 Use your web browser's page search/find (Ctrl-F or ⌘-F) to quickly find, on any web page here, certain text, including our IDs especially when the direct-link doesn't work.
      ^N0SROW section history in order:
      
      ^N0SRPB now create this as while this is definitely true for ~95% of websites, it's an extremely important feature which many seem to forget (including Lucy!) or don't yet know. Place it as 1st item of #N0SISW
      
      ^N12MU7 As this is something everyone needs to know as part of (new) #N12MCW(reading), move this into there, specifically right after#N12MH8
    4. ^N12NTO And for more advanced reading, we also have some cool browse functions.
  2. ^M79SX0 Fully refer-especially-link to here, including point your associates to the content & info here, notably give them links to here
    ^N0SJ0N section history in order:
    1. ^N0SJ1T prior not recorded here
    2. ^N0SJ2L moved from right after #M7BJUZ to its real rank here #1.
    3. ^N0SJ76 Rewrote title fr(Tell your associates of the content here, notably give your associates links to info here ) to present
  3. ^M7BJUZ Register/Create an Account –100% free –CLICK!
    ^N0SOH7 section history in order:
    1. ^N0SOHK other prior not recorded here
    2. ^N0SOID updated ending from q( -CLICK!) to present, prepending the very important " –100% free"
    1. ^M7BJVL Then Signin/Logon and stay logged-in so
    2. ^M7BJW4 Throughout the day, frequently & easily JOT HERE!...
      1. ^M7BJX0 Comment on Content by simply clicking “Reply” on the post or comment you want to reply to, else reply by other means, as we want your constructive comments!!
        ^N0SP25 section history in order:
        
        ^N0SP2X other prior not recorded here
        
        ^N0SP3E from q(we want your honest constructive comments!!), cut "HONEST " as "CONSTRUCTIVE " sufficiently implies that & "less is more".
      2. ^M7BJXZ Draft a new Post/Article: each can be very simple (& short is generally better) plus can contain top standard HTML formatting including pictures & video and with WYSIWYG ease.
        ^N0SKK3 section history in order:
        
        ^N0SKLV other prior not recorded here
        
        ^N0SKMN break into subsections; but then decide not as then created better: summary #N0SKQJ.
        
        ^N0SLUZ cut q(ideally get yourself ranked among our Top Posters;) as probably too stressful a thought for most readers.
        
        ^N0THOA renamed fr(Make Posts/Articles) to present as more accurate and especially less intimidating.
      3. ^N0SKQJ In short, jot here! –a great place to jot & share your more involved thoughts
        
        ^N0SL8V instead of a sending a longer email-or-message or writing additional document(s) then attaching them, instead just make a post here including making your post private if needed then just email/message the link to your post, then getting you a super short&sweet message (including even small enough to txt or tweet!) plus getting you all the other tremendous additional benefits of posting instead of messaging!
        
        ^N0SLAL instead of having to post somewhere without full HTML for max-power multimedia formatting and WYSIYG ease plus often where your post could get messed-up or deleted (as on as Meetup or Wikipedia), instead post it here then instead link your readers to here.
        
        ^N0THK0 instead of using your word processor, jot here, and so save your work with versioning + backup plus in a data format which is already ready for publishing (no conversion necessary) and where it still doesn't need to be released to anyone until you're ready as explained next:
        
        ^N0TI8S best of all, dramatically better than a book or a magazine or newspaper or newsletter article or even an email or tweet --where one easily ends up saying stuff they then can't later correct, and is regularly expected well-complete plus maintain their publication even though they now may very much want and need to move to something else-- here release info & publish with the lowest possible stress: Create & save drafts (of articles) until you're ready, if ever, to share them; and even when shared, limit who can access until you're ready, if ever, to allow a wider audience. Plus, for articles AND comments: write under one or more pseudonyms , and, per wiki incremental collaborative design, eliminate the expectation it needs to be complete or all worked out on first release and, at any stage, bring in others to help you so it's not all on you; plus at all stages, even after publishing to the world, per wiki system and matching copyright controls, still have full freedom to subsequently make full even massive additions, corrections, & improvements, and in both content & who shared to!
        
        ^N0SKV1 The normal use of this site is ordinary folks posting their written communications here (via articles & comments) then emailing/messaging/posting to their readers the link to their post and/or having their posts found by web search.
        
        ^N0SL21 So think of 1.JotHere.com as a web document repository (document management system) as Google Docs or Zoho but better organized & introduced, especially as a potentially-public portal.
        
        ^N0RLQ7 section history in order:
        
        ^N0SIPT: now created & added right after #M7BJUZ (so last) as #M79SX0 is the real task intended.
        
        ^N0WCJR replaced "or other[ web document repository (document management system)]" with "a [same] as " and added example " or Zoho"
    3. ^M7BJYI Only sign/log-out when truly needed for privacy/security so your ability to post here will most always be at your fingertips.
  4. ^N0SISW Last, browse content here. Notably,
    ^N0RLQ6 section history in REVERSE order:
    1. ^N12XBA added #N12MYK(new) & #N12VY2(new); updated all rest.
    2. ^N0SPVN some wording & formatting improvements, most notably prefixed title with q(Last, )
    3. ^N0SIPT now created & added right after #M7BJUZ (so last) as #M79SX0 is the real task intended.
    1. ^N12MYK First know all the reading tricks, then also:
    2. ^N0SJW2 On every article, click one of its categories to also see all the other articles here explicitly placed in that category or any of its sub-categories.^N12VVL For every article you find here, there is a reasonable chance there are more of them on the topics listed in its categories.
    3. '^N12VY2 You can also explore All “..Category”N10H7P in the right sidebar.^N12W33 It's a pretty long list, but don't expect it (yet!) to already have every topic similar to Wikipedia as here of course is just what folks so far have published... that is without you adding more here :-) and here very nicely without the notable drawbacks of Wikipedia of your stuff getting brutally edited or often more likely removed.
    4. .^N0SJWO
      ^N12QKO section history in order:
      
      ^N12QL0 prior additional not recorded here
      
      ^N12QLV was q(The right side bar has: Search plus lists of Categories, Recent Articles/Posts, Recent Comments, top Authors & Editors (click on each to see o see his/her articles).) with improved wording including exact references to named widgets now that they've just yesterday been very-well-named plus add some more.
      This right sidebar is very useful, including for browsing: see above&below its “Search” right at top plus it's many useful lists: All “..Category”N10H7P plus the sidebar's many useful content lists: “..Most Recently-Modified Articles”N10HDO & “.. Most Recently-Posted Comments”N10HID, and even “Authors..”M8AQ0E & “Editors: All & With Bio+Stats”M8AUVK plus click on each to see his/her articles! Plus more lists following those, as “Articles per Month for all History”N10VKE.
    5. ^N0SJYI But likely DON'T look to the Home Page for its unique content but rather to the right sidebar including for the latest news here, as do realize when browsing here: this site encourages all & every topic and by anyone, indeed similar to Wikipedia and especially similar to Google Docs, so likewise this website's entry point is normally some page here (it could be any) somebody is pointing folks to, indeed often to some point on that page , including regularly to point which has been here some time, and NOT to the website's home page (per default WordPress, the articles summarized on the home page are the latest first posting (but NOT updates) of ANY topic by ANYBODY, similar to a random new page plus typically under-construction since this is also a wiki, so that will probably not be your thing, well unless you want find & explore random pages starting construction), so typically the only (but rather) interesting thing on our home page is the right sidebar that's on every page, understandably per the site's normal use of typically being entered by being directed to NOT the home page but to some now-relevant point here.
      ^N12X1P section history in REVERSE order:
      
      ^N12U7P was q(But do realize, especially as this site encourages all & every topic and by anyone, similar to say Google Docs, likewise its entry point is generally not its home page and its specialty is not random browsing, understandably per its normal use.
      ); considerably extended & improved to present.
      ^N12X29 other prior exists
  5. ^M79V54 Make sure our authors get money for their creations here, especially when they're helpful; please:
    1. ^M79SVN Donate .
      1. ^N0J3AW --button broken (discovered now) so to be fixed.
    2. ^M79ST1 Browse our relevant embedded ads (when we have them) and, if interesting, click them to find out more! Every ad click brings authors a few pennies, which add up!
  6. ^N11PZP
    ^N12B6L section history in order:
    1. ^N12B7C At time of ID, added just after #N11PLG
    2. ^N128FX WP suggested feed links found at #M7A66P & #N129S2
    3. ^N12KPA This is news {about something (RSS) which seemed hot a few years ago but it feels RSS is mentioned less seemingly rarely including steadily decreasing trends and FeedBurner's apparent ending)}and here is negative, so now move this to right after #M79SQB(Powered by You)
    RSS feeds: this website offers 2 feeds (of our articles w/o comments and of our comments), but, respecting copyright here, do not use these nor share this data and/or links to it except per official written authorization from us this website's management; but do let us know of need for this feed info and we may grant access to this.
  7. ^N12L8B
    ^N12LMD section history in order:
    1. ^N12LMX At time of ID, added as the last item of #M8K00L as want readers to read what's here, at least this overview of most critical stuff, before contacting with Qs.
    Want to share your feedback? Need something? Contact us website management!

^M79XCH So, as always, wishing and hopefully enabling you the best... including best reading, sharing, replying & best-of-all jotting JotHere! —last updated pst2014.02.16Sun1725

^N12LYD section history in REVERSE order:

^N1497X replace "M79XAV" with more meaningful "last updated pst2014.02.16Sun1725" to be replaced with latest
^N12LZ2 Was nothing more than just the source. Prepended the present salutation.
^N12LYM prior not recorded here

”

“Authors: All, &their Bio+Stats+Articles”M8AQ0E –16 authors and increasing as of 2014.02

bigwavedave
At DestinyArchitect's suggestion, I started posting here to record DestinyArchitect helping me with the custom Web 2.0 site I built from scratch WikiTimeTraveler.com after my presentation of it. From most-to-least active roughly, here's my profile on: Meetup, Google Plus, Facebook.
1 post
5 comments
cdcookjr
As part of OCAndroid Developers Meetup #46 on pst2012.04.02, I created an account here. From most-to-least active roughly, here's my profile on: Meetup.
Chetspalsky
As part of OCAndroid Main Meetup #55 on pst2012.05.14, I created an account here. From most-to-least active roughly, here's my profile on: Google+, Meetup.
1 comment
Chris Lasher
I am a meat Popsicle.
1 comment
DoctorGingee
2 posts
1 comment
dstromberg
1 comment
ebonyj
3 posts
9 comments
goldenone
last mod 2012.08.09fri1112: Hi, I'm Kundan. I work M-F 6am-4pm at a dream job: Marketing Director at Social Marketing in Santa Ana. On the side, I founded & run SoulGasms.Info where I am a Dream Life Alchemist (personal life coach); also I founded & Head 4 Meetup groups, including Meetup.com/OC-Polyamory. 1.JotHere.com I joined at DestinyArchitect's suggestion on pst2012.07.14sat2049 to post my 1st comment & other comments on our promotion of Showtime's exciting Polyamory series. Here's my other profiles roughly from-most-to-least active: Google+ and not yet listed there: Meetup, Tumblr, LinkedIn, OkCupid, POF x5, POF x2, fReado, Google Search, about.me (replaced by SoulGasms.Info). Bio history.
12 comments
In Bed With An Atheist
Written by DestinyArchitect in the user's absence: "In-Bed-With-An-Atheist was, as I used to be, in the habit of writing huge long emails to individuals, including to me; so I strongly recommended she create a JotHere account then instead put here much or all of that text & share the good writings to the world!; so on pst2011.11.27 she created an account and quickly posted several of her short-stories and it went well. Her posts are no longer here but due to no fault of this site. From most-to-least active roughly, user's profile on: Meetup, Google+."
Jacob Christ
1 comment
jameshofstra
CSUF alum (computer science) and student (software engineering). President of CSUF Linux User Group and regular attender of OCLUG and SimulSquad. See also my personal website for my bio, resume, and social media.
1 comment
jean
On pst2012.06.17sun1855 I first met DestinyArchitect at Starbucks on Paseo & El Toro where, in passing, he told me about this exciting site so I signed up right there using my my mobile tablet. I'm interested in reading & commenting on the "romance"-category posts plus posting my research in psychology. In the long term I hope to become a forensic psychologist, starting in US police departments. I also have a husband and kids. From most-to-least active roughly, here's my web profile on: --none known.
1 comment
jimmyamash
1 post
3 comments
Kenneth Allen
Serial Entrepreneur. Founder of number of high tech companies.
1 post
Martin
Language Agnostic Software developer. Member OCandroid, OCJUG, OCLUG. OCPython, etc.
7 comments
Mickey
I'm a office assistant. In 2000, I moved from my birthplace Japan to California. I wanted to practice & learn English including writing, so DestinyArchitect encouraged to post on JotHere, so minutes later I created this my account (at pst2011.11.27sun2323) and made my 1st web page post! then every few days added `my thought for the day' as a comment to my post, each which Destiny then replied to --this site is fun! From most-to-least active roughly, here's my web profile on: Meetup.
1 post
4 comments
msrtech
Hi, I'm Kathy. I founded & run MSRTech.com, a custom Android app developer with over 30 apps; I also write & web-publish articles on Android & tech marketing. As part of my job as an OCAndroid developer leader. I 1st joined this site pst2012.01.27fri1242 (in response to leading SoCalAndroid Hack Night via OCAndroid 11); I use 1.JotHere for posting points & presentations & other comments in OCAndroid Main Meetings happenings plus promise to post some of my tech articles here. From most-to-least active roughly, here's my web profile on: Meetup, LinkedIn, MSRTech, Google.
2 posts
3 comments
Orio39
An aspiring artist of sorts. My main passion is in story-telling, and I'm exploring many mediums through drawing and music and whatnot. I'm also a bit of an anime geek and a huge Vocaloid fanboy.
1 comment
Protector2077
I'm the 1st instance I know of a certain type of privacy & security protector I invented, as detailed in my post on that type (TBA). And can you guess what my username is based on? :-)
3 posts
1 comment
raul
redcharlie
sung2kim
szahn
2 posts
1 comment
William R. Zwicky
I started posting here as a member and Assistant Organizer of OCAndroid, and this has now become my primary blogging site. Here are my profiles on: Meetup, LinkedIn, Google Plus, Facebook, SourceForge.
12 posts
46 comments

“Editors: All, &their Bio+Stats+Articles”M8AUVK –5 editors as of 2014.02

DestinyArchitect
last update 2017.03.03: I'm a Software- & Social Architect in ‘US.92654(CA.south.Orange County.south.Laguna Hills)’ seeking collaborators, friends, & long-term romance. I'm also founder & head of ‘SimulSquad™(Co-Work/Learn&Social on Your Topics)’ including the Laguna Hills BYOD SimulSquad™ chapter which I put on ~weekly since 2014! For a long-term overview of me, see my Google profile (presently tricky to open, including requires Google Drive sign-in & app, due to Google bugs). As far as this website JotHere.com, I love it! --indeed starting about 2010, I daily post-or-edit-or-comment-on an article here; this page gives all my my 1.JotHere.com articles; typically I write on my biggest interests: challenges & solutions for modern information technology & {social technology™ -except those posts thru 2011.01 at http://LoveRules-Info.Blogspot.com}, especially on collaborating, romance, & friendship; please give constructive comments plus I encourage you post here, too! –tricky to start but otherwise easy: follow 1.JotHere.com's default methods for reply & discuss. —this bio's source & comment-page
265 posts
833 comments
Glyph
4 posts
7 comments
Lucy Parker
I'm a retired writer & graphic designer. I 1st joined JotHere 2011.03.19sat0936 to publish my scripted-talk "A History of Aprons"; I also use it to publish comments & posts as part as my job as Users Leader #1 of OCAndroid; and I have many more writings I may publish here. From most-to-least active roughly, here's my web profile on: Meetup, Amazon author, LibraryThing author.
9 posts
28 comments
MissionFirst
N0LPYY: "Always place the mission first" says the US Military's Warrior Ethos which I wear around my neck
19 posts
26 comments
SaberPen
Around 2012.06 I created an account on this fine site, starting first to publish problems I saw when using, plus text which doesn't well-format on, date- & friend-finding site OkCupid. For full info on me, see my OkCupid profile.
7 posts
8 comments

JotHere.com –Got a thought? Jot it Here!™

Meetup.com/OCAndroid Meetup M5FF9H

CONSTRUCTING: Android user syllabus

MAZBVC:POST

OCAndroid Main Meetup #61(pdt2012.10.18thu1800-2200: including ANDROID AS A CONTROLLER OF OTHER DEVICES): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing

M31R7G:Definition

M33Q1M:Additional document history, in order:

ACCIDENTAL DUPLICATE: OCAndroid Main Meetup #60(pst2012.08.27mon1800-2200: including TBA): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing

M92VRO: Duplicate post!; see instead the original.

M31R7G:Definition

M33Q1M:Additional document history, in order:

OCAndroid Main Meetup #60(pst2012.08.27mon1800-2200: including NOVEL USES OF ANDROID, as TV entertainment center PC): DISCUSSION THREAD OF WHAT WILL, IS, & DID HAPPEN beyond the event listing

M31R7G:Definition

M33Q1M:Additional document history, in order:

OCAndroid Main Meetup #59(pst2012.07.30mon1800-2200: including BEST TABLETS,OUYA GAME CONSOLE,GOOGLE JOB): discussion thread of what will, is, & did happen beyond the event listing

M31R7G:Definition

M33Q1M:Additional document history, in order:

OCAndroid Main Meetup #58(pst2012.06.25Mon1800-2200: also USER ISSUES, as LOW-COST TABLETS): discussion thread of what will, is, & did happen beyond * the event listing

M31R7G: Definition

M33Q1M: Additional document history, in order:

OCAndroid Main Meetup #57(pst2012.06.11Mon1800-2200): discussion thread of what will, is, & did happen beyond * the event listing

M2OXUB: Title:OCAndroid Main Meetup #57(pst2012.06.11Mon1800-2200): **discussion thread of what will, is, & did happen beyond * the event listing**

M33Q1M: Additional document history, in order:

OCAndroid Main Meetup #56(pst2012.05.28Mon1800-2200, also user issues as ANDROID MEDIA MGMT): discussion thread of what will, is, & did happen beyond the listing

M2OXUB: Title:OCAndroid Main Meetup #56(pst2012.05.28Mon1800-2200, also user issues as ANDROID MEDIA MANAGEMENT): discussion thread of what will, is, & did happen beyond the listing

M33Q1M: Additional document history, in order:

OCAndroid Main Meetup #55(pst2012.05.14Mon1800-2200, COMPARE-YOUR-CODE): discussion thread of what will, is, & did happen beyond the listing

M2OXUB: Title: OCAndroid Main Meetup #55(pst2012.05.14Mon1800-2200, COMPARE-YOUR-CODE): discussion thread of what will, is, & did happen beyond the listing

M33Q1M: Additional document history, in order:

OCAndroid Main Meetup #54(pst2012.04.30Mon1800-2200, User Issues): discussion thread of what will, is, & did happen beyond the listing

M33Q1M: Additional document history, in order:

MAZBVC:POST

M31R7G:Definition

M33Q1M:Additional document history, in order:

M92VRO: Duplicate post!; see instead the original.

M31R7G:Definition

M33Q1M:Additional document history, in order:

M31R7G:Definition

M33Q1M:Additional document history, in order:

M31R7G:Definition

M33Q1M:Additional document history, in order:

M31R7G: Definition

M33Q1M: Additional document history, in order:

M2OXUB: Title:OCAndroid Main Meetup #57(pst2012.06.11Mon1800-2200): discussion thread of what will, is, & did happen beyond * the event listing

M33Q1M: Additional document history, in order:

M2OXUB: Title:OCAndroid Main Meetup #56(pst2012.05.28Mon1800-2200, also user issues as ANDROID MEDIA MANAGEMENT): discussion thread of what will, is, & did happen beyond the listing

M33Q1M: Additional document history, in order:

M2OXUB: Title: OCAndroid Main Meetup #55(pst2012.05.14Mon1800-2200, COMPARE-YOUR-CODE): discussion thread of what will, is, & did happen beyond the listing

M33Q1M: Additional document history, in order:

M33Q1M: Additional document history, in order:

M2OXUB: Title:OCAndroid Main Meetup #57(pst2012.06.11Mon1800-2200): **discussion thread of what will, is, & did happen beyond * the event listing**