May 272015
 

NOLZ16: NOLZ16: ‘-’

  1. NYM1X1: ‘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.
    1. O3KV8Y: section id change from ‘NOLZ1G: ’ to the standard
  2. NZ23L1: ‘completeness stage’ CONSTRUCTING
    1. O3OLXT: version 4 updating every ~2 weeks
  3. O3KUE6: ‘picture’
    .
  4. NZ3GR7: ‘name anew’

    ‘‘1.JotHere.com’ or similar ‘WordPress’ site’ {content {standardized aka boilerplate & template-ish} other than ‘NOLDef’} :NXBB3L

    :http://1.JotHere.com/4670#NOLZ16

    1. O3DAXT: ‘‘section history additional’ ‘in reverse start order’:’ :O3DAXT
      1. O3OMLW: title present as ‘factor out everything but that section :O3OLLY
      2. O3L3TO: title ‘‘‘1.JotHere.com’ or similar ‘WordPress’ site’ ‘‘WordPress’ document’
        1. O3L453: set to quote from NXBBX6
        2. O3L3ZB: all else: cut has handled elsewhere, including
          1. O3L8QH: move {‘starting for ‘post template .. NOLWCZ’’ talk} to new ‘a post serving strictly as a template master :O3L6RV
        3. O3L3U3: cut ‘constructing:’ cut as now handled by #NZ23L1
      3. O3KVME: id & title change from ‘NRE70N: post name & ‘post image’:’ to the standard
      4. O3KV6I: {this section} id change from ‘NOME8R: ’ to the standard
      5. NXJZMA: ‘‘‘constructing:{‘1.JotHere.com’ et al. {boilerplate & templatish} other than ‘NOLDef’, starting for ‘post template .. NOLWCZ’} ‘in ‘NOLDef’’NOLZ16
        1. NXK0JA:‘definition in ‘NOLDef’’ of ..’ rephrase to simpler form
        2. NXK0IZ: add notable clarity
      6. NX930G: ‘‘constructing: ‘definition in ‘NOLDef’’ of {‘post template .. NOLWCZ’ including instantiations & other templatish JotHere.com content} ’NOLZ16’ following /5143#NX913P
      7. NWUJW0: ‘‘constructing: ‘‘‘definition in ‘NOLDef’ of concept’s’’ of {‘post template .. NOLWCZ’ including instantiations & other templatish JotHere.com content} ’NOLZ16
        1. NWUY3N: add ‘templatish ’
        2. NWUSRC: fix NOLZ16 link.
        3. NWUJZD: per #NWUJ6E , cut ‘‘NOLDef’, &’
      8. NRE3QD: now to next: ‘‘constructing: ‘‘‘definition in ‘NOLDef’ of concept’s’’ of {‘post template .. NOLWCZ’ including instantiations, ‘NOLDef’, & other JotHere.com content} ’NOLZ16
      9. NOLZ4H: now originally to next: ‘definitions for {‘post template .. NOLWCZ’ instantiations} for starters & easily more NOLZ16
  5. NYM1YF: To reply & discuss, please use JotHere.com’s default methods (click) except: none.
  6. NWUAVB: remaining sections ‘definition’ + ‘post’

  7. NYM1YV: ‘definition’: concept(s) definition in NOLDef’ else in NOLDef-to-be
    1. NXBB3L: ‘‘1.JotHere.com’ or similar ‘WordPress’ site’ {content {standardized aka boilerplate & template-ish} other than ‘NOLDef’} :NXBB3L
      1. NWUJRD: ‘novelties’: there are many novelties of this section, but probably most notably:
        1. NWUNXK: its major content is fully defined in ‘NOLDef’, indeed it is the 1st major use of it (besides it defining itself 🙂
        2. NWUNXT: it invents & defines collapsing history for every section, including most advanced form CSS class NUBSOO
      2. O4I9SJ: post layout
        1. O4I9SU: where main section is post body…
          1. O4I9Y3: per se :O4I9Y3
            1. O4IAUG: ‘completeness stage’
              1. O4IAUP: constructing
            2. O4I9Z1: use
              1. O4I9Z8: #1: /5467
            3. O4ICK1: section ‘‘‘Pretty Link’ entry’ ‘anew’’ /O4ICK1
            4. O4ICS7: ‘‘definition’ ‘anew’’
              1. O4ICVQ: most in ‘component :O4IAM8
              2. O4ICVW: {ID so KCGUID} declarations are to be all removed on template copy :O4ICVW
            5. O4IAM8: component :O4IAM8
              1. O4LSDL: -search for ‘O4IAM8’ to find entries
          2. O4I9VZ: (post id) ‘definition’ kid
            1. O4I9X5: used: since 2014.10
            2. O4I9WE: example: this post layout presently
            3. O4OEIT: elements changed by {next: ‘per se :O4I9Y3’}
              1. O4IBHC: cut
                1. O4IBHP: –quite a bit
                2. O4IBHV: in order formerly present
                  1. O4IB68: post ID declaration as ‘O4ES28: ‘-’
                    1. O4IB76: cut that as now ‘per se’
                  2. O4IA5P:NZ23L1: ‘completeness stage’ CONSTRUCTING… ’
                    1. O4IB5N: cut as to be covered more completely entries of :O4IAMY
                  3. O4IAJ2:NZ3GR7: ‘name anew’

                    Bernie Sanders 2016 support events designed & normally-hosted by me :O42CD6

                    :http://1.JotHere.com/5467#O4ES28

                    1. O3DAXT: ‘‘section history additional’ ‘in reverse start order’:’ :O3DAXT
                      1. O4HZXH: present-value

                    1. O4IB9U: cut that as now covered by the ‘per se’ title plus history in entries of :O4IAMY
                  4. O4IB87:NWUAVB: remaining sections ‘definition’ + ‘post’
                    1. O4IBKG: cut as no longer needed
                  5. O4IBM0: cut the following as these aren’t needed
                  6. ‘’
      3. O3ON3D: in order in order (as of last update) it generally 1st occurs {in-use else logically} –title now factored out of NXBB3L
        1. NXBC3E: remaining sections TBA
        2. NXBCP8: sectioning
          1. NOPO30:‘IDed section NOPO30’
            1. NOPOBZ: ‘definition ‘in reverse start order’’
              1. NOPO74: ‘<li>[[id] in format aself_KEP2FG] [heading][subs]</li>’
          2. NX7L8P: ‘-’remaining sections
            1. NX7MQO: ‘‘definition’ ‘anew’’
              1. NX7MQX: a field who’s value gives, for the present section, the linked names of every top-level sub-section which follows in the order they follow, with each pair typically separated by ‘ + ’.
            2. NX7LIV: ‘per def’
              1. NX7LIL: ‘notable pros thru cons:’
                1. NX7LF0: most any section so post which lacks a table of contents, provides with maintenance which is about as painless as any manual method could be. –notable pro
                2. NXBHGD: allows section contents/overview for any number of levels –big pro
                3. NXBHI0: via ‘for remainder’, enables saving defining section mapping for what comes first, which are {generally and intended to be} a few short points –pro & unique
              2. NX7LU8: ‘same or similar’ ‘sub’
                1. NX7LTW: near 0: https://www.mediawiki.org/wiki/Manual:Table_of_contents except here 1 paragraph and don’t cover sub-sections.
            3. NX7L9C: ‘name anew’
              1. NYMKYQ:remaining sections
                1. NYML6A: ‘rendering anew’remaining sections
                2. NYML0E: 1/2 the words including
                  1. NYML1B: cut ‘overall’, seemingly from the ‘TOC’, as that seems assumed.
                3. NYML2E: ‘remainder’ ‘replacement’ ‘remaining’ as seems clearer
              2. NX7LLZ: ‘for remainder, sections overall
                1. NX7MI7: changes
                  1. NX7N57: cut ‘:’ as felt it was cluttery.
                  2. NX7MKL: ‘contents’ replace with ‘sections’ as more accurate and familiarity of ‘contents’ then doesn’t offset its redundancy.
                  3. NX7MJ4: cut ‘table of’ as inaccurate NX7LV6
                  4. NX7MIK: ‘for remainder’ to start
                2. NX7N6Q: ‘‘rendering’ ‘anew’’‘for remainder, sections overall
              3. NX7LAZ:table of contents overall for remainder:’
                1. NX7LD8: ‘usage’
                  1. NX7LDP: From search, {started seemingly /4875#NV8YKK so by that ID 2015.09.25} and ~22 posts using.
                2. NX7LV6: ‘table of’ misleading as, due to use of a-tags instead of page #s, is not really a table.
            4. NX7MVU: ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
          3. NUBOQC: CSS class KMW3VO notes (to be filed elsewhere)
            1. NUBN99: KMW3VO bug: things as pics floated right cause collapsed text to appear below them instead of along-side
              1. NUBNBD: with present settings
              2. NUBNCE: cause: finding…
                1. NUBO77: still happens if all settings removed from N9ID06 so due to other settings, seemingly from http://0.jothere.com/L8IPUB/JotHere_LXK5OS/info_distros_LPCDST__LXK5Z4/LXKDST.min.combo.css’, possibly ‘ width: 100%;’
          4. O4IAMK:‘section’
            1. O4KS0F: create initially for ‘component :O4IAM8’ -indeed the highlight of that
            2. O4KS3Q: ‘‘definition’ ‘anew’’
              1. O4KS4X: refers to, aka makes the topic be, the parent section, with each kid giving a statement about that.
                1. O4KS79: so a kind of meta-property
                2. O4KSBZ: so allows such properties to be conveniently grouped together and ideally ordered
              2. O4KS4B: parent section covers a topic which usually isn’t the immediate section, but can be with a nested use of this operator.
              3. O4KSB7: so far intended to be the 1st child of the parent
            3. O4LQ9I: ‘‘name’ ‘anew’’ ‘section’ ‘‘rendering’ ‘anew’’
              1. O4LQAN:‘section’’ :O4LQAN
              2. O4LQFF: ‘‘section #O4IAMK’’
                1. O4LQHV: the ID display is too loud given name {{use is so prominent & regular}+{length is so short}}, so resume ‘‘section’ :O4LQAN
            4. O4KSBZ: component
          5. O4KASJ:‘additional’
            1. O4T4A8: template for use ‘as ‘section’ kid {1 of} :O4T44C’ :O4T4A8
              1. O4I52M: latest quote:
                1. ‘additional’
                  1. ‘post category’
                  2. ‘success’
                  3. ‘advertising/lessening additional’
                  4. ‘motivation’
                  5. ‘contributors including their {contributions & relevant background}’
                  6. {to be put elsewhere} so ‘annex’
                  7. ‘comments –here or/and elsewhere per the ‘To reply & discuss’ #O4KA53
            2. O4T4PU: ‘‘definition’ ‘anew’’
              1. O4T4TI: a section heading
              2. O4T4X6: with kids which are
                1. O4T4TR: only items which are not typically essential for reader-only users
                2. O4T4W8: sorted by roughly most ‘typically essential for reader-only users’
                3. O4T50J: generally at least those of O4T4A8
                4. O4T554: can include additional item(s), including any ‘‘section’ kid’, as long as it satisfies the other constraints
            3. O4T430: ‘display place’
              1. O4T44C: as ‘section’ kid {1 of} :O4T44C
                1. O4T468: last
                2. O4T471: none
                  1. O4T47E: if no custom values
                  2. O4T485: as cuts down on clutter & needless maintenance
            4. O4KB1L: CSS class O4KB1L
              1. O4KIKC: ‘;max-height’
                1. O4KIL0: displays just the 1 line so just the title, so
                  1. O4KIRU: ‘:1.6em’ per times ‘line-height: 1.6em’
                  2. O4KILU: ‘:1em’
              2. O4KBRN: first pick up all ‘CSS class O4IEZZ’ settings
            5. O4NS7V: ‘‘name’ ‘anew’’ ‘additional’ ‘‘rendering’ ‘anew’’‘additional’
              1. O4NSE6: to be {analogous with O4LQAN} & more
            6. O4NS4A: created for initially ‘component :O4IAM8
          6. O4LS55: category of post
            1. NOKXS2: ‘-’‘post category’’ :NOKXS2
              1. NX4MYV: ‘‘definition’ ‘anew’’
                1. NX4N31: for the present LHS (notably section), specifies category(s) that this content should be in
                  1. NX4N8N: notably that this content’s post should be in
                2. NYNA6Q: unless explicitly specified, includes the category(s) in the section name
                  1. NYNA91: and those they imply from the lack of a category having multiple parents so the post having to include this
                  2. NYNADT: inspired by /5236#NYMEJA as latest example of stuff this could cut.
              2. ‘per def’
                1. ‘same or similar’ ‘sub’
              3. NX4MV7: ‘‘name’ ‘anew’’
                1. O4KGH8: ‘post category’
                  1. O4QJS1: ‘‘rendering’ ‘anew’’‘post category’
                  2. O4OEAT: rename per initially ‘component :O4IAM8
                2. NX4MXN: ‘so post category’
                  1. NX7HMB: ‘‘rendering’ ‘anew’’‘so post category’
                3. NX4MTB: ‘‘per post name, add post to categories’’
                  1. NX4N9F: ‘notable pros thru cons:’
                    1. NX4N9O: ‘post name’ limits excessively
                  2. NX4MQS: ‘‘rendering’ ‘anew’’‘per post name, add post to categories’
                    1. NX4MTW: created likely at time of its id NOKXS2
                4. NX7HAP: ‘aside: per section subject, now add post to 3 categories: ’ where {‘3’ is set the #} and {‘aside: ’ is dropped if the point is placed within the ‘‘‘section history additional’ ‘in reverse start order’:’’}
                  1. NX7HCM: ‘usage’
                    1. NX7HD4: for sections, the solution for period from coming up with it 2015.03~, last ~/5129#NREFRD, until replacement #NX7HMB
              4. O4KGHZ: label/KCGUID ‘NYWZWX: category so ‘post category’
                1. O4ONTG: now cut at least for & per O4ICVW
              5. NX7H28: ‘‘‘Pretty Link’ entry’ ‘anew’’ 1st
              6. NYEX5P: ‘‘section history additional’ ‘in reverse start order’:’
                1. NYEX64: location: from /5138#NWZ067 kid to here
          7. NOTOR0: ‘-’‘[above is done; below is in construction] NOTOR0’
            1. NOTORP: ‘‘name’ ‘in reverse start order’’
              1. NOTOSD: ”[above is done; below is in construction] NOTOR0”
                1. NOTOXU: first use: /4697#NOTOXC
        3. O4KSO9: past+present+future :O4KSO9
          1. O4RRXH: section ‘‘‘Pretty Link’ entry’ ‘anew’’ #1 /O4RRXH
          2. O4KSOI: history
            1. O4IAMY:‘history in reverse order’
              1. O4IAP2: was former’s style’s ‘NYM1ZP: ‘history’: ‘‘post history additional’ ‘in reverse start order’:’
              2. O4T8AY: ‘name anew’
                1. O4T8DX: ‘history in reverse order’
                  1. O4T8Q0: ‘rendering anew’‘history in reverse order’
                    1. O4T8TS: as {displayed ID less, which appears key for frequent use}
                  2. O4T8F8: ‘additional’ replacement ‘’ as O4T8JO
                  3. O4T8OM: ‘start’ replacement ‘’ as O4T8M6
                2. O4T8BI: ‘history additional in reverse start order’
                  1. O4T8KR: where ‘start’
                    1. O4T8M6: ‘start’/‘begin’ is mostly implied so cluttery :O4T8M6
                    2. O4T8LE: should really be ‘begin’ as can’t re-start –problem
                  2. O4T8JO: problem: while ‘additional’ is logically correct, most people will just be confused thinking {ok, then where is the main history?} :O4T8JO
                  3. O4T8D9: ‘rendering anew’ ‘‘history additional in reverse start order #O4IAMY’’
              3. O4IEZZ: CSS class O4IEZZ
                1. O4KJB2: ‘;line-height’
                  1. O4KJHK: set to 1em as this text is just for reference not for general reading, so
                    1. O4KJHZ: ‘:normal’
                2. O4KDFH: ‘;max-height’
                  1. O4KGQ3: should display 1st 2 lines so have heading 1 line + data only 1 line :O4KGQ3, so
                    1. O4KGRN: ‘:3em’
                    2. O4KDGJ: ‘:2em’: only displays heading & under-space, so not enough
                3. O4IF0C: ‘first pick up all NUBNKF CSS settings #NUBTI7’ except
                  1. O4KGVR: as have collapsing, do no size down the font & lines, so
                    1. O4KGXC: do not inherit CSS class MBSHIS
            2. NRHITQ: ‘-’‘section history additional’ NRHITQ
              1. overall review:
              2. NRHKMS: ‘definition ‘in reverse start order’’
                1. NRHIH3: the heading so label of the section which…
                  1. NRHIPM: with regards to its parent section
                    1. NRHIMN: gives all its additional history
                    2. NRHIQQ: is to be the last item
              3. NUBKKU: usage
                1. NUBKL9: in normal output, is displayed minimally or not at all, ideally with mouse-over to display.
                  1. NUAEN5: by putting in a CSS class
                    1. NUAEP5: as CSS class N0QX1H so does not display in normal output
              4. NUAEQ2: ‘notable pros thru cons:’
                1. NUAEQM: Huge pro: keeps editing notes & even past versions very near where they occurred
                  1. NUAERP: including then causing this history & notes to move with the text.
                2. NUAES9: small con: In default WordPress, to create generally requires dropping into HTML code.
              5. NRHIBO: ‘-’ ‘section history additional in start order’
                1. overall review:
                2. NRHIOJ: ‘definition ‘in reverse start order’’
                  1. NRHIN0: where all its items are sorted by increasing begin time so in the order they naturally occurred
              6. NUAE5L: ‘-’‘‘section history additional’ ‘in reverse start order’:’
                1. NUAE6E: ‘name ‘in reverse start order’’
                  1. NUAE9A: now until next: ‘‘section history additional’ ‘in reverse start order’:’
                  2. NUAE6W: originally until now: ‘section history additional in reverse order:’
                    1. NUAE83: used for months now in several 1.JotHere.com docs
                2. NUBNJO: usage
                  1. NUBNK2: CSS class
                    1. NUBNKF: class NUBNKF to display the 1st ~2 lines small then when moused over display the full thing in normal size
                      1. NUBNOE: now starting development
                      2. NUBNS5: start by picking up all defs of KMW3VO
                      3. NUBQ8X: overflow handling
                        1. NUBQ9A:text-overflow: ellipsis;
                          1. NUBQG1: so far no effect and Chrome reports ‘invalid property value’
                            1. NUBQGL: http://stackoverflow.com/questions/17779293/css-text-overflow-ellipsis-not-working has fix? -maybe
                          2. NUBY7X: instead use scroll
                        2. NUBQK3: ‘;overflow-y:scroll’
                          1. NUBQQW: works
                          2. NUBY9Q: bulky but that tolerable
                          3. NUBYAD: needs undoing: done
                          4. NUBYAN: Big pro: text can still be found via Ctrl-F!
                          5. NUBYEH: Big pro: text can still be found via #<anchor/> URL! (example: http://1.jothere.com/4906#NU7LDM
                        3. NUBRYB: ‘;max-height:’
                          1. O3XRRK: set to just enough so it can be seen something is hidden
                            1. O3XTGG: ‘0.333333ex’
                              1. O3XTIH: looks perfect including
                                1. O3XTNU: RHS has just a top silver of scroll bar & section ID to let user know something is hidden.
                                2. O3XTM7: displays the top 0 lines so no distraction
                            2. O3XSCR: ‘0.4ex’
                              1. O3XTD5: same as ‘‘0.5ex’ :O3XS3J’ except ~50% entries have no visible lines
                            3. O3XS3J: ‘0.5ex’ :O3XS3J
                              1. O3XSCE: a fragment of scroll-bar & section ID is still visible: good
                              2. O3XS7E: displays the top ~1 pixel of lines which is mostly not visible but on close inspection looks like a line of dust on the screen so no ideal.
                            4. O3XRY9: ‘1ex’
                              1. O3XS1V: displays the section history just enough: nice but seemingly unneeded.
                              2. O3XS26: displays the top ~.25 lines which is notably detracting & messy-looking
                            5. O3XRSL: due to the problems of {#O3XR5A & #O3XRNH}
                          2. NUBSJE: set to just enough to typically display the ID of the 1st entry so to get the update version.
                            1. O3XR5A: looking at http://1.jothere.com/5408?preview_id=5408&preview_nonce=aba6f28dae&post_format=standard&preview=true#NRHRK5 (which has high use of this: nearly every point), when collapsed,
                              1. O3XRIM: ‘the ID of the 1st entry’ displays only the 1st 2.5 to 3 characters as the rest, which is most key, is hidden behind the scroll bar seemingly unavoidably
                              2. O3XRQ0: all the ‘ ‘‘section history additional’ ‘in reverse start order’:’’ being displayed, even in the small font, are very distracting.
                            2. O3XRNH: but ‘display the ID of the 1st entry’ is never really useful in practice as seemingly nobody memorizes this tiny & 1x id to detect an update.
                            3. NUBT5M: at default (100%?) font size, this now is ‘5.1ex’
                              1. NUBTA9: so at ‘font-size: 85%; ’ at 4.335ex=5.1ex*.85
                        4. NUBQT1: undoing (when hover over)
                          1. NUBQTI: ‘;overflow-y:inherit’ –undoes
                        5. NUBSCO: ‘;transition-delay:.5s’
                          1. NUBSEZ: originated by copying NIFF32
                          2. NUBSF6: tries to smooth the transitions
                        6. NUSN3D: ‘;overflow-x:hidden’
                          1. NUSN5I: after doing update NUSLN9 (to NUBNKF), http://1.jothere.com/4900#NTMXCH long text caused that section when collapsed to display a horizontal scroll bar which was notably-cluttersome & useless, so NUBQK3 copied then altered creating this, which worked.
                      4. NUBSX7: content sizing
                        1. NUBSXQ: use same as MBSHIS
                      5. NUBUXZ: bug: /4906#NUBC7Q doesn’t display (but most work)
              7. NXVSVU: ‘-’‘doc stage’
                1. ‘replacement’
                2. NXVVJP: ‘usage’
                  1. NXVVJZ: 1st, which inspired it: NXVVGQ
                3. NXVTO9: ‘‘definition’ ‘anew’’
                  1. NXVU1T: goals:
                    1. NXVTNF: a way to concisely refer to the stage posts are it, thus minimizing the todo content to just custom stuff
                    2. NXVU2X: define a process for brining standard concept to good standards.
                  2. NXVTPG: in typical order
                    1. NY0UAL: base level :NY0UAL
                      1. NY0WD5: –requirements
                        1. NY0UZQ: to define the bare minimum for publication to readers which could be any including unknown
                        2. NY0UT1: must be quickly doable on demand by the author, notably for {NY0W9H & equivalent}
                      2. NZ273E: All {‘existing text to be {‘moving’ into doc ‘ :NVSWPG’} this one :NZ27B6’ where that can be done quickly}, now do it.
                        1. NZ27AL: where
                          1. NZ27B6: existing text to be {‘moving’ into doc ‘ :NVSWPG’} this one :NZ27B6
                            1. NZ27D4: happens because of, from biggest cause roughly
                              1. NZ27DT: the cost of ‘open for editing :NZ0PL7’ was not don ‘open for edit’ for the target
                                1. O3KSI8: section title is messed up but notes of it in O3KR84 may enable correction
                      3. NY0VC0: ensure (doc) is constructive else definitely not destructive, including
                        1. NXVUC1: fix all reported problems, including broken links, which are inexpensive to fix now and reasonable
                        2. NY0VSN: in both
                          1. NY0VIL: appearance as is practical
                          2. NY0VH4: action/effect, including, in order it’s generally best done:
                            1. NY1BAV: ensure no {copyright infringement or other terms-of-use violations}
                            2. NXVU4E: ensure no claims which are destructively misleading
                              1. NY18GB: where, to fix that, especially quickly,
                                1. NY18EZ: limit scope, including
                                  1. NY18EH: tone down superlatives
                                2. NY18HG: when not certain/proven, add ‘apparently’ & ‘seemingly’ or ‘IMHO’
                                3. NY1876: for incompleteness, make complete by…
                                  1. NY1897: adding an entry, usually last, saying {‘possibly more TBA here’ or equivalent}
                                  2. NY18B1: title the section to include:
                                    1. NY18C6: ‘additional’, as done in ‘‘‘section history additional’ ‘in reverse start order’:’
                                    2. NY18DE: ending with ‘including’
                                  3. NY18NX: possibly more TBA here
                              2. NY19Y7: often partially implied by #NY1BAV
                              3. NY1A5W: doing this as one expresses oneself (notably as one writes & speaks)
                                1. NY1ACX: –to reasonable degree is generally best & necessary & healthy
                                2. NY1AE5: –fully aka 100% (so never go-back to correct) is generally counter-productive.
                                3. NY1AJ2: little or none (as via pathological or compulsive lying) is universally agreed bad & indeed totally impractical
                                4. NY1AGS: by the average person today, seems done not enough but improving
                                5. NY1AEP: by more educated/intelligent people, seems to be less violated actually or/and visibly
                              4. NY1AWP: not always but often implies #NXVU6H as otherwise the content misattributes
                            3. NXVU6H: ensure sources & inspirations are clearly attributed/cited/credited
                              1. NY0W65: at least if the sources are things which would reasonably expect credit, as publications, products, persons
                              2. NY0UW9: as not doing this is very bad including disallowed by Wikipedia plus readily plagiarizing.
                              3. NY0UEA: one should attempt to do this one writes especially as it’s much slower & problematic to do it later.
                              4. NY1BDO: foremost to avoid
                                1. NY1BRN: the content having misleading claims that that it came from places else in amounts where it didn’t
                                  1. NY1B76: including from the normal so implicit assumption, that unless the content says otherwise, it 100% came from its immediate creator(s)
                                  2. NY1AV8: which then is case of{idea & other intellectual property} theft including plagiarism
                            4. NY0U62: ensure access amount is set best/optimal
                              1. NY19DW: where it’s normally specified in
                                1. NY0U70: the ‘‘This {post & its comments}’s ‘TOU(Terms Of Use) ..’
                                2. NY19E5: the post/page’s ‘Visibility‘ settings (as ‘Public’ or ‘Password protected’, etc}
                                3. NY19FU: redacting
                                4. NY19G7: factoring out sensitive info into more private documents
                                5. NY19HM: possibly more TBA here
                              2. NY1918: Note limiting sharing can & should be used as a non-long-term panacea: specifically to “address”, by notably hiding, the other problems until they are fixed, but only to that degree that the then behind-the-scenes fixing is progressing effectively.
                        3. NY0VZP: –this point modeled after #NX95DV
                      4. NY2M7D: ensure document (so far only for post) is the appropriate categories –as can be tested quickly
                      5. NY1C0F: ensure links working: keep fixing until when testing important ones, 3 in a row work
                      6. NXS2YK: do substitutions :O3MKQI
                        1. O3MMGB: of, in order,
                          1. O3MKVJ: in source code, replace all {nbsp represented as 1 character} with {a regular space notably ‘ ’}
                            1. O3MKYT: where
                              1. O3MKZ5: the nbsp here
                                1. O3MLN0: utility
                                  1. O3MLNJ: notably breaks lines too soon, looking odd & wasting display space especially on the new narrow devices
                                  2. O3MLPP: no positive that I’ve seen
                                2. O3ML2G: on obtaining,
                                  1. O3ML0N: cannot be included say quoted here as this process will substitute it out
                                  2. O3ML13: is saved in my ExWeb recent replacements
                                  3. O3ML1Q: can be found via the docs per O3ML3Z
                                3. O3ML3Z: is created in WP posts & probably pages :O3ML3Z
                                  1. O3ML50: at least in version currently running 4.4.0
                                  2. O3ML75: seemingly by the editor
                                    1. O3ML85: right {before or after or both –varies} a a-tag at least which the editor builds thru the link-button
                                    2. O3MLAP: when posting in KCGUID generated by the template of ‘class=”aself_KEP2FG”’
                                    3. O3MLFZ: possibly when pasting in expressions copied from browser output, as ‘The backup of this post in your browser is different from the version below. Restore the backup.’ :O3MLFZ
                                    4. O3MLIJ: no other locations I recall seeing but I haven’t checked carefully
                          2. O3MLSG: in source code, replace all ‘href=”/’ with ‘href=”/’
                            1. O3MLVK: where the unseeded ‘http://1.JotHere.com’ is seemingly regularly created mostly by {pastes as in O3MLFZ}
                            2. O3OI5S: notable pros thru cons :O3OI5S
                              1. O3MLUO: as makes source code smaller & more portable
                              2. O3OI6O: neutral
                              3. O3OI6Z: in WP editor (at least current 4.4.0), stupidly cannot browse links
                                1. O3OIBP: as 1st noticed ~20min ago at NXEIW3
                          3. O3MKUB: {spellcheck} –point now factored out of #NXS2YK
                          4. O3MKQI: {update IDs to latest format: __ replacements} –point now factored out of #NXS2YK
                        2. O3MMIT: via
                          1. O3MMJY: MS ExWeb
                            1. O3MMKJ: –what I’ve been using so far
                            2. O3MMKX: heavily depends the Replace function: carefully selecting the options & having it remember recent searches, which is tricky
                          2. O3MMP4: a script/program I write
                            1. O3MMPI: —planned; TBA here
                    2. NY17XM: add more coverage/completeness…
                      1. NY17YM: per actual {need specifically upcoming use}
                        1. NY182S: so not just for the aesthetics of appearing complete unless this can be done very inexpensively also counting the cost to later main this stuff not actually used.
                    3. NXVU7N: ensure every key phrase, at least 1st use, is a link to its definition
                      1. NY19S7: This is kind of like an extension of #NXVU6H including
                        1. NY19N4: #NY0UEA also applies here.
                      2. NY0V62: ‘‘section history additional’ ‘in reverse start order’:’
                        1. NY0V6D: move #NXVU7N from after say #NXVU6H to present due to this failing #NY0UT1
                    4. NXS2X2: better introduce
                    5. NXS2WV: better organize
                    6. NXS2XQ: add/complete {‘remaining sections’ & equivalent}
                    7. NY0UIU: fix reported problems not fixed by #NXVUC1
                    8. NXVVFW: full-read through proofreading
                    9. NXS2YD: ensure at least a hefty random sampling of links work
                    10. NXVVE5: add transitions
                    11. NXVUAS: repeat #NXS2YK
                    12. NY0UKY: ‘‘section history additional’ ‘in reverse start order’:’
                      1. NY0UL8: add all points beginning {‘NY0’ thru ‘NY2’}
                4. NYCB0M: ‘‘name’ ‘anew’’doc stage’ ‘‘rendering’ ‘anew’’‘doc stage’
                5. NXVTR6: ‘‘motivation or source or change’ ‘in reverse start order’’
                  1. NXVTRF: first inspiration: to organize /5168#NXS4QF
                6. :
                7. NY2OBM: ‘‘‘Pretty Link’ entry’ ‘anew’’ to section: #1
              8. NUBJXJ: ‘-’‘post history additional ’NUBJXJ
                1. NUBK1N: definition:
                  1. NUBK1X: ‘section history additional’ for a post in particular.
                2. NUBKCX: usages
                  1. NUBKDM: is supposed to include regular post.status.snapshot entries as this recent example ‘‘{post.status.snapshot: date ’20150907Mon1056pst‘; after ID’ minutes 0~‘; revision ’8‘; words ’3785‘; version ’1.8‘; as ’finished resort sections plus a few changes outside of moves (plus just small ones within moved text, as that’s hard to diff), but more proofing to do‘, do ’Update then continue editing‘}’.’
                  2. NUBKGG: is ideally formatted so the latest entry is displayed and hovering over gives all the entries.
                3. NUBJY3: ‘name ‘in reverse start order’’
                  1. NUBJZF: originally now to next: present
                4. NUBK4I: ‘-’‘‘post history additional’ ‘in reverse start order’:’NUBK4I
                  1. NUBK5J: ‘name ‘in reverse start order’’
                    1. NUBK7N: originally now to next: ‘‘post history additional’ ‘in reverse start order’:’
                      1. NUBK9M: create by copy NUAE9A then update appropriately
                  2. NUBSNW: usage
                    1. NUBSOO: CSS class
                      1. NUBSPB: NUBSPB
                        1. O4IEW2: from creation, same as NUBNKF but when minimize display they key parts of the latest entry so ~2 lines of data besides heading.
                        2. NUBTI7: first pick up all NUBNKF CSS settings #NUBTI7
                        3. NUBTZ3: ‘;max-height:’
                          1. NUBU00: try 2x greater so ‘8.67ex’
                          2. NUQI93: /4906#NUQG2P is now latest update and, displayed at small width, displays 3.5 lines when needs to display at least 6 to show the ‘TODO’, so set to =8.67*6/3.5=‘14.86ex’; seems to work.
                  3. NUBV1E: alternatives
                    1. NUBV29:“post edits overall history table, by increasing start-time”
                      1. NUBV2J: the former designed to replace the latter
                5. O4OIC4: see ‘‘‘{post.status.snapshot{;date20150915Tue0915pst‘;after ID ’minutes 3~‘;revision ’1‘;version0.1~‘;words ’1400‘;as ’snapshot & share progress‘;do ’save & publish & continue editing‘}}’’ :NOTPON
          3. O4OI7M: stage/status
            1. O3QEYO: section ‘NZ23L1: ‘completeness stage’ CONSTRUCTING…’
              1. O3QF0E: kids
                1. O3QF1K: the latest entry telling relevant stats
                  1. O3QFGD: of the version & update frequency
                  2. O3QFGM: which before was the 1st kid of ‘O3KVOI: section ‘completeness stage’ in reverse order: :O3KVOI’ which {{was 1st kid of ‘definition’} + {is replaced by this new structure} :/4830#O3QFGM
                  3. O3QFL2: with all additional entries moved & merged into ‘history’ keeping the latter sorted
                2. O3QF16: none –originally until now
            2. O4T94C: status snapshot with optional operation
              1. O4T998: ‘-’‘op’
                1. O4T9A1: as replacement for ‘post.status.snapshot
                2. O4T9PX: ‘‘definition’ ‘anew’’
                  1. O4T9QB: same as ‘post.status.snapshot’ except
                    1. O4TA2I: fixes O4T9FA
                    2. O4T9R3: syntax
                      1. O4T9UD: ‘[atr] ([val]|{(;[O4T9UD] )*})’
                      2. O4TF4V: no quoting except for 1st term
                    3. O4T9YC: better ‘NXB1SF: component’ selection
                    4. O4TL2V:  sub-operations
                      1. O4TL71:  nested when appropriate
                      2. O4TL55:  ordered from right-to-left carefully to match section {container, notably ‘history in reverse order’}…
                        1. O4TL8R:  {typically only displaying ‘data only 1 line :O4KGQ3’ generally} to get  details {most crucial to the typical reader} {soon (plus bolding the most critical}}
                        2. O4TL6B:  historical sort order
                3. O4T9K8: ‘name anew’ ‘op’
                  1. O4T9N1: ‘rendering anew’‘op’
                  2. O4T9LF: as short for ‘operation’ due to high use
              2. NOTPON: ‘-’ ‘‘{post.status.snapshot{;date20150915Tue0915pst‘;after ID ’minutes 3~‘;revision ’1‘;version0.1~‘;words ’1400‘;as ’snapshot & share progress‘;do ’save & publish & continue editing‘}}’’ :NOTPON
                1. O4T9DD: ‘notable pros thru cons’
                  1. O4TF40: compact
                  2. O4T9EJ: neutral
                  3. O4T9FP: ‘post’ is already implied in every use.
                  4. O4T9FA: tied to ‘post’ instead of fully general :O4T9FA
                2. NOTPOZ: ‘‘name’ ‘in reverse start order’’
                  1. NUQ6O6: ‘‘{post.status.snapshot{;date20150915Tue0915pst‘;after ID ’minutes 3~‘;revision ’1‘;version0.1~‘;words ’1400‘;as ’snapshot & share progress‘;do ’save & publish & continue editing‘}}’’
                    1. NUQ8KN: for clarity, wrapped sub-variables with ‘{}’ then also cutting the preceding ‘:’
                    2. NUQ8IC: preceded every variable with ‘;’ instead of ‘; ’ for all but 1st.
                    3. NUQ8E8: ‘;after ID ’minutes 3~‘’ space issue after variable: fixed.
                    4. NUQ7VV: for ‘date20150915Tue0915pst‘’, updated to present and {added bolding as info key to general reader}
                    5. NUQ6TF: for ‘;version0.1~‘’, placed right after ‘; revision ’1‘’ since it is partially determined by that plus ‘; words ’1400‘’ is a subordinate measure of both.
                    6. NUQ6R9: for ‘;version0.1~‘’, added the bold since this info important to the general reader.
                  2. NOV4L7: ‘‘{post.status.snapshot: date ’20150523Sat1509pst‘; after ID’ minutes 3~‘; revision ’1‘; words ’1400‘; version ’0.1~‘; as ’snapshot & share progress‘, do ’save & publish & continue editing‘}’’
                    1. NOV4OV: ‘motivations & sources & changes ‘in reverse start order’’
                      1. NOV4VY: from NOV4QA, starting there, replaced wording to ‘as’ refering to ‘as’ meaning ‘because’ as:
                        1. NOV5CL: ‘as’ appears the notable shortest wording of meaning ‘because’ –notable pro
                        2. NOV54M: meaning matches underlying wording ‘why’ (so also most general) –notable pro
                        3. NOV56N: will require ‘to’ situations to
                          1. NOV59M: be more exact –seems notable pro
                          2. NOV59E: take more words (as ‘need to’ or ‘desire to’) –small con
                    2. NOV5FG: done
                      1. NOV5FQ: starting with 1st use
                  3. NOTYAB: ‘‘{post.status.snapshot: date ’20150523Sat1509pst‘; after ID’ minutes 3~‘; revision ’1‘; words ’1400‘; version ’0.1~‘; to ’snapshot & share progress‘, do ’save & publish & continue editing‘}’’
                    1. NOTYBZ: done
                      1. NOTZ6T: starting now, with 1st use
                      2. NOV5H1: stopping with NOV5FQ
                    2. NOV4PR: ‘motivations & sources & changes ‘in reverse start order’’
                      1. NOV4QA: found ‘to‘ wording problematic uses 2 NOUIV2 & 3 NOV3MG (leading to NOV4VY)
                  4. NOTPPL: ‘‘{post.status.{latest, so <5min from now}: revision ’1‘; words ’1400‘; version ’0.1~‘; to ’snapshot & share progress‘, ’save & publish‘; time ’20150523Sat1509pst‘}’’
                  5. NOTPAT: ‘post status: {a few minutes from now, specifically 2015.05.23Sat1509pst} post is revision 1, 1400 words, version 0.1~; to mark & share progress, save & publish.’
                    1. NOTYBD: earliest revision on record.
                3. NOTYG1: ‘motivations & sources & changes ‘in reverse start order’’
                  1. NOTYCF: to ideally replace ‘‘post edits overall history table, by increasing start-time’’ with something with {net-benefits for here per comparison}
                  2. NOTYJI: ‘compared to’ table
                    1. NOTYM0: Notable Pro: Can easily fit as an outline point.
                      1. NOTYQT: as ordinary HTML text span (inline)
                        1. NOTYL3: PRO: No special editor required to produce additional rows
                        2. NOTYLR: PRO: more compact & wraps
                      2. NOTYTM: as separable & self-labeling
                      3. NOTZ5J: -the motivation for 1st use
                    2. NOTZ3F: Pro: each entry reads more like natural language.
                    3. NOTYO9: CON: slower to compare entries in any given column
                    4. NOTYVP: Notable CON: would require (likely coding) special software to collectively (over several entries):
                      1. NOTYWG: well export-to & import-from a table
                      2. NOTYWS: add, delete, rearrange, & re-label columns
              3. NXB1SF: NXB1SF: component (except any also used in other context) in order referenced roughly
                1. O4TFXY: ‘-’end
                  1. O4TFZ5: ‘name anew’‘rendering anew’end
                2. O4TFGJ: ‘-’begin
                  1. O4TFJ2: ‘name anew’‘rendering anew’begin
                  2. O4TG9S: ‘per def’ generally should match the creation (time & place) of the KCGUID used to identify the operation :O4TG9S
                3. NNPIWX: ‘-’date
                  1. NUQ9KY: value example: ‘20150915Tue0915pst’
                  2. O4TJNF:  ‘definition ‘in reverse start order’’
                    1. NUQBGS: value is the date & time (of the subject) in format per the example
                    2. O4TJM6:  the most-significant digits, if omitted, are the same as those elsewhere specified for the same operation
                      1. O4TJQH:  for example, for the ‘end’ is fully specified, then allowing the ‘begin’ to be effectively fully specified by only giving the digits which are different.
                4. NOTXPJ: ‘-’‘after ID’
                  1. O4TJIL:  replacement {do foremost else instead O4TG6Q}
                  2. NOTXZ4:  ‘‘definition’ ‘anew’’
                    1. NOTY25: ‘the duration else distance of the present subject, as ‘post.status.snapshot:’, compared to that of its section ID’
                  3. NUQ8CG: example value: ‘minutes 3~’
                  4. O4TG5K: ‘notable pros thru cons’
                    1. O4TG5W: gives the duration
                    2. O4TG7Q: reference to ‘ID’ is generally accurate per :O4TG9S but {to average reader is meaningless & distracting}
                    3. O4TG6Q: duration is not as key as the begin & end date :O4TG6Q
                  5. NOTYDK: ‘motivations & sources & changes ‘in reverse start order’’
                    1. NOTY3U: if the section ID is close to the subject’s date, the most desirable case, then the ID number may be easily used to find points before the subject occurred (lexically lower) and after (lexically higher)
                5. O4TJTR:  ‘-’ ‘polish
                  1. O4TJXW:  ‘‘definition’ ‘anew’’
                    1. O4TK09:  how polished the subject is, where
                      1. O4TK28:  ‘the subject’ is usually textual else multi-media content
                      2. O4TK34:  measured from 0 to 1 or 0 to 100%
                      3. O4TK4A:  0 is none & 1 is full
                  2. O4TKBJ:  ‘motivations & sources & changes ‘in reverse start order’’
                    1. O4TKBX:  to alert general readers that ‘hey, we know it’s not fully polished’
                    2. O4TKD6:  to assign an amount/rating (of polish) so to prioritize what needs attention as far as raising the polish to more desirable levels
                    3. O4TKGU:  especially key for what-I-call {new live, not traditional one-shot} {writing & other content}, as ‘one-shot’ content isn’t traditionally substantially released until its polish is very good (but then it also doesn’t substantially update, either)
                  3. O4TJUW:  ‘name anew’‘rendering anew’polish
                6. NNPJ6Z: ‘-’revision
                  1. NUQ9PK: value example: ‘1’
                  2. NUQCT9: value is the revision # of the subject
                    1. NUQCUO: else what it should be if the # has not been assigned.
                    2. NUQFFL: where iff ‘0’ is the very start of the container’s creation
                    3. NUQCYE: which by default is determined by the revision control system for managing the content
                      1. NUQCZD: so in a WordPress post, when the post is being edited-including changed in the default editor, is the sum of:
                        1. NUQDCP: the ‘15’ or whatever value displayed by the status ‘[Previous ]Revisions: 15 Browse
                          1. NUQDDO: or if no value is displayed, as unfortunately generally happens when 0 or 1 previous revisions, then the author’s best guess at how many explicit-user-saved revisions exist.
                        2. NUQDH4: 1, as that version being edited once saved will be given {1 more} for its #.
                7. NNPJ04:version
                  1. NUQ9NR: value example: ‘0.1~
                  2. NUQBK0: value is the version number (of the subject)…
                    1. NUQBO3: using by default SemVer.Org convention
                      1. NUQC2B: where every ‘counter’ is 1 of, from largest first, ‘MAJOR’+‘MINOR’+‘PATCH’
                      2. NUQC5F: where an effective value of ‘0′ aka ‘0.0′ aka ‘0.0.0’ is the creation point of the present container
                      3. NUQBXJ: where a ‘MAJOR’ value of ‘0’, as ‘0.3’, means 1 or more of:
                        1. NUQCGW: before ready for substantial use ever
                        2. NUQCG0: before any release ever
                      4. NUQBOK: where, for the smallest ‘counter’ used)
                        1. NUQBS6: {the present value minus the previous value} is {equal else a little greater than} {{the present value minus the previous value} of {the ‘revision’}}
                8. NNPJ1Z: ‘-’words
                  1. NUQ9OM: value example: ’1400‘;
                  2. NUQCLG: value is the # of words in the present content when 100% seen as a natural language
                    1. NUQCNX: which is by default the value given by the editor used to edit the content
                      1. NUQCPB: so in a WordPress post, by its editor.
                    2. NUQCRU: so gives a meaningful common measure of the size of at least textual content.
                    3. NUQFI0: which is by default a somewhat imprecise value
                      1. NUQFRF: due to
                        1. NUQFNS: whenever {the value and other review parameters are being entered into the text being counted, as done for ‘post.status.snapshot’} as unspecified is if the count is before or after these changes.
                        2. NUQFKM: to the imprecision & differences of what constitutes a ‘word’ (so bigger variances if using different meters/counters)
                      2. NUQFLF: so accurate to say 10%
                9. NNPIYQ:as
                  1. NUQ9M9: value example: ‘snapshot & share progress’
                  2. NUQBID: value is the-reason/why of ‘do’ or equivalent (for the subject)
                  3. NXB250: records web browser crashes including of {tab {as Chrome’s ‘‘Aw, Snap!’ crash :NX7AQV’} and system} .
                10. NNPIU4:do
                  1. NUQ9JR: value example: ‘save & publish & continue editing’
                  2. NUQBFI: value is the action performed (on the subject).
                1. NXVSUO: ‘‘section history additional’ ‘in reverse start order’:’
                  1. NXVSKT: location: from right after #NUA7NJ in #NXBB3L to after #NUBK4I as it is placed in that section
          4. O4QK1Q: before / after
            1. NEFIV2: ‘-’‘success’
              1. O4QKBO: ‘‘‘Pretty Link’ entry’ ‘anew’’ /NEFIV2 :O4QKBO
              2. O4QK3F: use
                1. O4QK3T: actual #1 at time of id of link ‘/NEFIV2 :O4QKBO
              3. O4QKKX: ‘‘name’ ‘anew’’ ‘success’ ‘‘rendering’ ‘anew’’
                1. O4QKM2: ‘success’
              4. O4QKPQ: label/KCGUID ‘O3KZ33: ‘success’
                1. O4QKR2: now cut at least for & per O4ICVW
            2. NOKVJ1: ‘-’‘motivation’
              1. O4RQ32: ‘‘‘Pretty Link’ entry’ ‘anew’’ /NOKVJ1 :O4RQ32
              2. O4RQDD: use: actual #1 at time of id of link ‘NOKVJ1 :O4RQ32
              3. O4RQ0G: ‘‘name’ ‘anew’’
                1. O4RPY4: .. ‘‘rendering’ ‘anew’’‘motivation’
                  1. O4RQHN: resume as top per O4RQF2
                2. O4RPZ9: .. ‘‘rendering’ ‘anew’’‘motivation’ & its achievement’’
                  1. O4RQF2: a few days ago, realize ‘its achievement’ isn’t needed as it and {other ‘achievement’} is covered by ‘‘success’’ :O4RQF2
              4. O4RPXA: label/KCGUID ‘O3KZ2Q: ‘motivation’ & its achievement’
                1. O4RPXM: now cut at least for & per O4ICVW
            3. O4RRRE: ‘-’‘contributors including their {contributions & relevant background}’
              1. ‘‘‘Pretty Link’ entry’ ‘anew’’
              2. use: actual #1
              3. O4RRP0: ‘‘name’ ‘anew’’
                1. O4RRKH:‘contributors’ including their {contributions & relevant background}’ ‘‘rendering’ ‘anew’’
                  1. O4RRQH:‘contributors including their {contributions & relevant background}’
                  2. O4RRPR:‘contributors’ including their contributions & relevant background’ -until now
                2. O4RRJR: .. ‘‘rendering’ ‘anew’’ other forms –probably
                3. O4RRHZ: .. ‘‘rendering’ ‘anew’’relevant background’ –possibly
              4. O4RR2S: label/KCGUID ‘O3KZ2Q:NWV4HX: ‘contributors’ including their contributions & relevant background :NWV4HX
                1. O4RR3K: now cut at least for & per O4ICVW
        4. O4KSP7: use
          1. O4OLKK: ‘section’ ‘‘‘Pretty Link’ entry’ /O4OLKK
          2. NOM14K: ‘-’TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}}’
            1. NUA12F: ‘name ‘in reverse start order’’
              1. O4OLSX:TOU(Terms Of Use) including {copyright © and info‘s {confidentiality/privacy & allowed use}}’
                1. O4OM3X: ‘‘rendering’ ‘anew’’TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}}’
                2. O4OM06: added {..} for clarity
                3. O4OLXU: promoted ‘ info‘s
              2. NUA15S: now to next: ‘‘TOU(Terms Of Use) including copyright ©, confidentiality/privacy, & info‘s allowed use’’
                1. NUA397: ‘motivations & sources & changes ‘in reverse start order’’
                  1. NUA4YM: replace ‘use of [the ]knowledge obtained’ with ‘info‘s allowed use’ as clearer
                  2. NUA4VD: replace ‘confidentiality, privacy’ with ‘confidentiality/privacy’ as the terms are closely related including per vs. search
                  3. NUA46H: move ‘ confidentiality’ forward 1 item as is alliterative with ‘copyright’ and sounds smoother.
                  4. NUA43K: cut ‘ all’ as only used this case and seems to add more drama than function.
                  5. NUA3NF: replace ‘terms of use’ with ‘TOU(Terms Of Use)’ as it’s a useful acronym also defined by its link
                  6. NUA0Y4: do relevant edits of /4906#NU9W98 version NU6DDS (so here cutting ‘the ’ and ‘ of it’ and ‘ from it’).
                  7. NUA3AE: Factor TOS concepts out of NOM0RW and merge into here
                  8. NUA1YQ: then followed by ‘ ©’ per ‘copyright ©’ convention seen in image samples
                  9. NUA0UB: follow /4900#NTEOVR version NU6DDS which has added ‘ including copyright’ as
                    1. NUA1H0: that’s an ad, which is taken casually, so alerting of its copyright is key
                    2. NUA1HP: to be safe, provides basic copyright notice even though as of 1989 that’s optional
              3. NUA14W: originally to now: ‘terms of use
            2. NOM15C: ‘definition ‘in reverse start order’’
              1. NOM1QT: now originally to next: ‘{contractual terms or, more clearly, rules} which one must agree to abide by in order to use something’
                1. NOM21K: adding missing ‘{contractual terms or, more clearly, [rules]}’
                2. NOM22N: generalizing from ‘service’ to ‘something’
                  1. NOM3QD: it could be medium-generalized from ‘service’ to ‘resource’ as http://1.jothere.com/wp-admin/edit-tags.php?action=edit&taxonomy=category&tag_ID=538&post_type=post but that feels awkward and the term generally could apply to anything.
                3. NOM1X7: taken from then latest Wikipedia for ‘Terms of use’
            3. NOLV3E: (section) terms of use section heading ‘TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}} is JotHere.com’s default TOU except:
              1. NOLV80: ‘‘name’ ‘anew’’
                1. O4OMB8:TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}} is JotHere.com’s default TOU except:
                  1. O4OMU8: ‘‘rendering’ ‘anew’’TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}} is JotHere.com’s default TOU except:
                  2. O4OMPF: cut 2nd ‘(Terms Of Use)’ as just clutter immediately repeating again.
                  3. O4OMDR: create for initially ‘component :O4IAM8’ so cut ‘This {post & its comments}’s ’ as will be in its own section
                2. NWU989: now to next: ‘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:
                  1. NWU9A2: ‘motivations & sources & changes ‘in reverse start order’’
                    1. NWU9AN: added highlighting to value, also analogous to #NUAFD2 present formatting.
                3. NUA0K2: now to next: ‘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:
                  1. NUA348: ‘motivations & sources & changes ‘in reverse start order’’
                    1. NUA5TQ: change ‘standard’ with ‘default’ as better parallels the ‘ except’
                    2. NUA5RH: Take ‘JotHere…’ out of italics as nothing unusual.
                    3. NUA5OB: Symmetrically for JotHere’s, do NUA3NF
                    4. NUA5NP: do update NUA0Y4 (so here replace ‘JotHere’ with ‘JotHere.com’ as is key to printouts)
                    5. NUA5IV: do update NUA15S
                4. NOM0RW: now to next: ‘The ‘terms of use’ of {this post & its comments, including the privacy & confidentiality of it plus all knowledge obtained from it} is JotHere’s standard Terms of Use except:
                  1. NOM5NE: ‘motivations & sources & changes ‘in reverse start order’’
                    1. NOMC8V: (in order) replaced ‘JotHere’s(right column)’ (also semi-broken link; should just be ‘#M79S95’) with what it links to, as the former is easily missed plus not much info and all info it has is also in what it links to.
                    2. NOM4F0: wrote but did not include ‘must be specified by the content owners here in writing and ’ as that can better be included in the standard TOU.
                    3. NOM5PM: clarified subject considerably
                5. NOLAW3: (in order): ‘this-matter’s terms-of-use including privacy/confidentiality: JotHere’s(right column) except:’
                  1. NOM4G3: ‘motivations & sources & changes ‘in reverse start order’’
                    1. NOM0OJ: copied from latest published post with this wording then added quotes around semi per constant standard.
                    2. NOM0OU: for better indeed proper content control
                6. NOM0IW: (in order) then made ‘post & its comments terms of use’
                7. NOM08T: originally specified only when needed
                  1. NOM0GT: but would be easy to forget and not have good uniform specification
              2. NOLV50: for
                1. NOLV5F: this template
                2. NOLV6D: possibly more
              3. O4ON4R: label/KCGUID ‘NYM1X1: ‘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.’
                1. O4ON6K: now cut at least for & per O4ICVW
            4. NRDW7T: ‘-’ ‘To individuals who have same sentiments as expressed here ..’
              1. NRDX30: overall review: probably not good.
              2. NRDWL0: ‘definition ‘in reverse start order’’
                1. NRDWLG: a possible answer-to/value-for ‘‘The ‘terms of use’ of {this post & its comments, including the privacy & confidentiality of it plus all knowledge obtained from it} is JotHere’s standard Terms of Use except:’ which makes the latter somewhat less restrictive as the former specifies
              3. NRDWQJ: ‘notable pros thru cons:’
                1. NRDWV6: might be {needed, as no better solution} when referring to source reasonably could compromise privacy –pro
                  1. NRDWRB: never used with no current plans for use though possibly it could be needed –con
                2. NRDWTO: weakens TOS possibly needlessly –bigger con
              4. NRDWE5: ‘‘name’ ‘in reverse start order’’
                1. NRDWFL: ‘To individuals who have same sentiments as expressed here and want to express them via ideas & content originating here but do not want to fully reveal the source (here) solely for reasonable reasons but will not mis-claim nor mislead on the source nor sentiments, the content owner is open to granting that use and has granted it to a few individuals.’
                  1. NRDW95: ‘motivations & sources & changes ‘in reverse start order’’
                    1. NRDW9O: originated as /4812#NR4L9A (created in /4812#NR4L94 but seeming not used)
          3. O4KSW2: communicating
            1. O4OFKI: sharing
              1. O4OFMX: ‘-’‘{advertising else lessening} additional’’ :O4OFMX
                1. O4R9ZF: ‘‘definition’ ‘anew’’
                  1. O4RA0A: “sharing” specifically all of
                    1. O4RAIR: advertising
                    2. O4RAKF: promotion
                    3. O4RB3L: lessening including
                  2. O4RAHH: beyond given by both the… :O4RAHH
                    1. O4RALF: {location, so far always JotHere.com}
                    2. O4RAMC: TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}}’
                2. O4RBGE: ‘per def’
                  1. O4RBH2: the ‘beyond’ quality of O4RAHH can be characterized by
                    1. O4RBKI:‘additional’
                      1. O4RBN2: similar to ‘‘additional’
                    2. O4RBJ6: ‘beyond’
                  2. ‘notable pros thru cons:’
                  3. ‘same or similar’ ‘sub’
                3. O4RB64: ‘‘name’ ‘anew’’
                  1. O4RPHH: ‘‘advertising’/‘lessening‘additional’
                    1. O4RPIO: ‘‘rendering’ ‘anew’’‘advertising/lessening additional’
                  2. O4RAW5: ‘{‘advertising’ else ‘lessening’} ‘additional’
                    1. O4RBCN: ‘‘rendering’ ‘anew’’‘{advertising else lessening} additional’
                  3. O4R9CB: ‘advertisement ‘additional’
                    1. O4OFPJ: create for initially ‘component :O4IAM8
                  4. O4R99S: ‘sharing beyond ‘TOU’’ –until now
                4. O4OFMH: label/KCGUID ‘O3DC5I: sharing beyond ‘TOU’
                  1. O4OFP0: now cut at least for & per O4ICVW
            2. O4OEX4: commenting
              1. O4KA53: comments –here or/and elsewhere per the ‘To reply & discuss’ :O4KA53
                1. O4OESM: created for initially ‘component :O4IAM8
              2. O4OEZ3:NYMK00: comments: are next & elsewhere per ‘To reply & discuss’
                1. O4KA3N: replacement O4KA53
            3. NUA7NJ: ‘-’‘Discussion via electronic writing preferred wherever that can be made do the job best’
              1. NUBDO0: definition:
                1. NVWGLU: This section moved to /4685#NT5IKW so please redirect links to latest location.
              2. NUA7OZ: ‘name ‘in reverse start order’’
                1. NUBEEG: use the title of NT5IKW.
              3. NUAAVS: ‘-’‘JotHere.com content’s default reply & discuss instructions ’
                1. NUAB99: definition:
                  1. NT5R88: For 1.JotHere.com content you want to reply to, please reply by…
                    1. NX94Q9: doing 1 of the following 4 reply methods, listed from by-default most preferred:
                      1. NTMDA0: post on the content a reply-comment using your free JotHere commenting & posting account (create)
                        1. NVT5SA: This is reply method is
                          1. NXD24S: the most powerful by far
                          2. NXD2G8: BUT still hard at first
                            1. NXD254: due to ‘WordPress’s out-of-box bugs
                              1. NXD2IH: —mostly that out-of-box WordPress offers a spammer’s haven
                                1. NXD3I7: which its makers well know, and then sell & push a fix on all users, but the new installer seemingly typically has no idea of this
                                2. NXD3JB: so every WordPress site every day receives 100s of spambots trying to login and post their spam ads, as both comments & posts and sometimes more, which take place!…
                                3. NXD3LE: unless serious fixes applied which can be found free but aren’t so simple as…
                                  1. NXD3MI: WordPress’s maker’s featured official fix just works for comments (not posts) & aims to charge for fixing WordPress –while neglecting to mention they are also knowingly releasing it broken out of the box but
                                  2. NXD3O4: there are actually 10s of fixes to pick from and well picking is tricky
                                  3. NXD3O4: the newcomer doesn’t know of all this and is not sophisticated enough to reliably make the best choices until serious problem so then needs both prevention AND cure.
                              2. NXD5A2: ‘so post category’ –the one specified in heading
                            2. NXD2LP: until one knows the workarounds where after it’s super easy, and to get you that point…
                              1. NXD2NB: for everyone, this site documents the WordPress caveats & workarounds everyone needs to know (yes, necessarily a lot of reading, but 1 time).
                              2. NXD2MG: those directing you here will be delighted to help you with getting up to speed with posting on this site, even help you interactively likely even help you live-on-the-phone.
                        2. NVT51I: After login, is the content the usual case (a comment or post) so features a ‘Reply’ button/link? Then just click on that to reply. Otherwise try to find an appropriate post/comment to so reply to, which ideally the content will link you to.
                      2. NTMD82: else reply to the {message/post/ad else person} which/who directed you to the content via foremost electronic writing.
                      3. NUAH67: else if the content gives an email address or phone # or other additional method of communication, use that as the content specifies
                        1. NX94TU: Unless specified otherwise, these additional means of communication are a backup in case the earlier (2) mentioned means aren’t working, so why this point is listed after them.
                      4. NWWLSC: else, as last resort, contact 1.JotHere.com admins at {the email address just for this purpose: NWWLYB@1.JotHere.com}.
                    2. NX94R3: your reply wording,
                      1. NX95DV: ensure its is constructive, in both effect & appearance
                      2. NX95CI: please be detailed, specifically giving as much as possible detail as can be made effective, including
                        1. NX9544: specifying every possible detail to avoid {phone-tag and equivalent}, including
                          1. NX94SQ: specifying what point(s) you’re referring to exactly as possible, giving the point(s) URL else KCGUID(s).
                    3. NUAGF9: ‘‘section history additional’ ‘in reverse start order’:’
                      1. NXD5D3: to #NXD254 add ‘class=”NUBNKF”’ –a 1st for this NOT on a ‘section history additional’
                      2. NXD5CM: #NVT51I: rewrite to be more functional and{cut ‘Done right, this works excellent for the usual case where’ as covered by #NXD24S}
                      3. NXD5GX: #NVT5SA: break into outline and add kids of #NXD254 thru #NXD5A2
                      4. NVT60L: broke #NTMDA0 into 2 sub-points and well-expanded on each, especially support offer of #NVT5SA.
                      5. NVT5YR: cut ‘, here listed starting with typically most preferred’ as that is handled well enough by the order and ‘else’s’;
                      6. NUAGQ6: original to now: ‘Please reply by comment-posting on the post (create account), else by replying to the electronic message (as email or SMS) which directed you to the post, else by remote-verbal reply as phone call else in-person (just reply asking for a call or meeting).’ (from source NUAA6X)
                      7. NUAHV2: move to here general points from /4900#NTX2F4 version NU6DDS
                  2. NUBE68: and for JotHere and ideally everywhere, please do ‘Discussion via electronic writing strongly preferred wherever that can be made do the job best’.
                  3. NUBCYB: To be merged with these instructions: reply instructions & background at ‘replying to content here’ also in the right column.
                2. NUAAWD: ‘name ‘in reverse start order’’:
                  1. NUBG6F: now to next: ‘JotHere.com content’s default reply & discuss instructions’
                    1. NUBG5M: per adding ‘ content’ for accuracy
                    2. NUBFKE: per following lead NUBFD5.
                  2. NUAAYE: originally to next: ‘JotHere.com‘s default reply instructions’
                3. NUAFD2: ‘-’ ‘‘To reply & discuss, please use JotHere.com’s default methods (click) except:’’
                  1. NUAFE1: ‘name ‘in reverse start order’’:
                    1. NVT43L: now to next: ‘‘To reply & discuss, please use JotHere.com’s default methods (click) except:’’
                      1. NVT4EW: STOP: instead of reading on, you likely want to click-on that last link then do its instructions.
                      2. NVT4BS: so rendering ‘To reply & discuss, please use JotHere.com’s default methods (click) except:’NUAFD2
                    2. NUBFG6: now to next: ‘To reply & discuss, please use JotHere.com’s default methods (click) except:
                      1. NVT40K: so rendering ‘To reply & discuss, please use JotHere.com’s default methods (click) except:
                      2. NUBFD5: so adding ‘ & discuss’, as realized from NUBEMQ this aspect covered could use appropriate announcement here.
                      3. NUBEX6: so cutting ‘ to this web page’, as shorter plus realized from NUBEMQ that this may necessarily apply to an entire web page (as a comment may want a different reply plus on auto-generated web-pages (as category lists) it wouldn’t be accurate)
                    3. NUAFGR: now to next: ‘To reply to this web page, please use JotHere.com’s default methods (click) except:
                    4. NUAFEH: originally until now: ‘To reply to this web page,’
                      1. NUAFFT: used on several recent 1.JotHere.com pages
                  2. NUBF9D: definition:
                    1. NUBEMQ: is a link which can be added to content to fully yet compactly specify how to {reply to & discuss the content, aka, handle content replies & the discussions resulting}
                    2. NUBFTH: is followed by the content’s exceptions here, which is ideally typically ‘none’ for none, but can be:
                      1. NUBFYA: to further encourage replies, enable them by also giving additional communication means
                        1. NUBG02: first example: /4900#NTX2F4
                  3. O4ONGK: label/KCGUID ‘NYM1YF: To reply & discuss, please use JotHere.com’s default methods (click) except: none.’
                    1. O4ONJ5: now cut at least for & per O4ICVW
        5. NXAWP8: {image so including video & picture} handling
          1. O4ID19:O3KUE6: ‘picture’’ :O4ID19
            1. O4JPGL: content :O4JPGL
              1. O4JPGX: is typically a div so can include a caption
              2. O4JPHG: floated right is a must generally
            2. O4ID5U: location
              1. O4LSC4: create initially for ‘component :O4IAM8
              2. O4JOE1: should consider O4JOI9
              3. O4JPBX: from most preferred so far,
                1. O4NRDS:‘section’’…
                  1. O4JPER: title…
                    1. O4JPJD: beginning
                    2. O4ID2N: end
                      1. O4ID6Z: under consideration
                      2. O4JZL1: right after O4JP3S :O4JZL1
                      3. O4NRIV: if {point ID is right-float: the norm}, then it occurs to the right of the pic, causing an ugly right-margin –pretty bad
                  2. O4JOP8: kid #__
                    1. O4JP5A: what have often/typically been done so far
                    2. O4JP2Q: notable pros thru cons
                      1. O4JP3S: most straightforward & consistent & semantically logical :O4JP3SL
                      2. O4JPDZ: –neutral
                      3. O4JZON: wastes lines… :O4JZON
                        1. O4JZ8H: 1 from the li entry
                        2. O4JZ8Y: 0 or 1 because WordPress inserts an extra blank p-tag –can be eliminated at least sometimes.
                    3. O4ID1N: #1
            3. O4JOI9: the label (as ‘O3KUE6: ‘picture’’) :O4JOI9
              1. O4JOTW: location: __ the pic div, from most preferred currently:
                1. O4JPPN: start-of ‘content :O4JPGL’’s text
                2. O4JOVM: in-front of ‘content :O4JPGL
                  1. O4JOWG: what have often/typically been done so far
                  2. O4JOXV: has notable pros thru cons
                    1. O4JOYC: most straightforward & consistent
                    2. O4JOZ5: –neutral–
                    3. O4JOZH: looks cluttery
                    4. O4JOZR: if in a li-item, ‘wastes lines… :O4JZON
                3. O4JPN4: hidden
                4. O4JP21: cut
                  1. O4JPOC: –bad: lacks visible or any ID
            4. NDNKX2: ‘-’‘post image’’ NDNKX2
              1. NOMDTA: ‘definition ‘in reverse start order’’
                1. NOMDUW: starting ~2015.05.17~: image to be positioned flush right so text can wrap around it and won’t hurt outlining indent on the left.
                2. NOMDTO: originally until as changed: specifies the featured image for the post to be included inline & centered
          2. NOME7E: several more TBA soon, starting with completing all those in the post template
          3. NXAWR8: HTML class ‘NTMUOJ’
            1. NX921U: ‘max-width’
              1. NX9249: ‘453px’
                1. NX926E: as ‘style=”max-width: 453px;’ since its inception & in all recently-created posts with image
              2. NX926P: as better than ‘width’ as shrinks when no smaller or no content
              3. NXAXM4: without other height & width constraints, image resized will scale {not evenly, only horizontal} –from test just now
            2. NX96V9: ‘width’
              1. NXB1MP: CUT per #NXB1M4
              2. NX96VS: ‘100%’
                1. NX96WE: per #NX96PP
                2. NXAY5S: from empirical test, this may not be needed
            3. NXAY79: descendant class ‘img’
              1. NX96OL: ‘height’
                1. NX96OZ: ‘auto’
                  1. NXB1HD: per http://stackoverflow.com/questions/2076284/scaling-images-proportionally-in-css-with-max-width/17689392#answer-23001224
                  2. NX96PP: per http://stackoverflow.com/questions/2076284/scaling-images-proportionally-in-css-with-max-width#answer-17689392
                    1. NXB1M4: per comment, replacement #NXB1HD
                  3. NXAXUA: adding this alone to caption-div doesn’t change #NXAXM4 –from test just now
          4. NX91CQ: ‘-’ ‘HTML class ‘NX91CQ’’
            1. NX91LX: ‘‘definition’ ‘anew’’
              1. NX91M2: class of the main image of a post or page in {1.JotHere.com and readily more}
            2. ‘per def’
              1. ‘notable pros thru cons:’
              2. ‘same or similar’ ‘sub’
            3. NX91KR: ‘‘name’ ‘anew’’
              1. NX91FN: ‘HTML class ‘NX91CQ’’
                1. NX92JF: ‘‘rendering’ ‘anew’’‘HTML class ‘NX91CQ’’
              2. NX91HR: HTML attribute ‘id=”NV8LHT”’
                1. NX91I2: bad as uses ‘id’ instead of class.
            4. NX91RG: inspiration & use 1st in /5143#NX3P31
            5. NX92BN: ‘‘‘Pretty Link’ entry’ ‘anew’’ #1
          5. O3L8IM: ‘so post category’ ‘image NTLQ8N’
        6. NX93ZI: aside: per topic ‘other templatish JotHere.com content’, see category Description field for 1.JotHere.com
        7. O3OQJT: ‘post category’ :O3OQJT
          1. NWZMX3: ‘in NOLDef NWZ6UN’ (as now available) –when cat list refresh
          2. NOLZMY: this ‘for {this site, so 1.JotHere.com} NOLZSH’
            1. NREFYA: some days ago replace that with more exact ‘this site’s documentation for its users’
          3. NOLZKE: (cut per implied by #NWZMX3): ‘definition LG5DEF’
      4. ‘this site’s documentation for its users’
    2. O3KWBH: section id changed from ‘NOM41B: ’ to the standard

  8. O3KYPL: ‘post’: post… –where its subsections don’t specify

    1. O3KZL1: ‘TOU’ + ‘completeness’ +‘picture’ + ‘name’ + ‘To reply & discuss’ + ‘remaining sections’: already above & in that order since these are key
    2. O3KZ2I: ‘‘‘Pretty Link’ entry’ ‘anew’’ example /O3Bern
    3. NYWZWX: category so ‘post category’
      1. O3OQLI: section content: core: moved into new O3OQJT
      2. O3L30O: section id changed from ‘NOM9WV: ’ to the standard
    4. O3L134: remaining sections ‘success’ + ‘sharing’ + ‘motivation’ + ‘contributors’ + ‘annex’ + ‘history’ + ‘comments’
    5. O3KZ33: ‘success’
    6. O3DC5I: sharing beyond ‘TOU’
    7. O3KZ2Q: ‘motivation’ & its achievement
    8. NWV4HX: ‘contributors’ including their contributions & relevant background :NWV4HX
      1. NWV4HQ: more authors possible, all the way from giving feedback to helping edit this wiki-page; just follow to reply
      2. NWV4IK: from most contributing
        1. NREHNZ: DestinyArchitect
          1. NREHPL: so now add this post to category ‘DestinyArchitect creation N0L9VW’
          2. NWV5UT: so far all work here except as noted.
        2. NWV58V: AnytimeInnovator
          1. NWV5TQ: some constructive feedback by external means.
      3. ‘‘section history additional’ ‘in reverse start order’:’
        1. .
    9. NZ3KAG: {to be put elsewhere} so ‘annex’
      1. O3L39A: section id changed from ‘NXEMWQ: ’ to the standard
    10. NYM1ZP: ‘history’: ‘‘post history additional’ ‘in reverse start order’:’
      1. O4TH3Z: ‘op’{;end{;date 2016.03.29TuePst1348 ;polish .7~ ;version 5} ;do{resume editing after {NY0WO6 with replacement qty {326+3+978}} after {update {determined by wikiEd} {#O4TG9S content restored} after ‘Post restored successfully. Undo.’ after ‘The backup of this post in your browser is different from the version below. Restore the backup.’} after {;words 10928 ;revision 36} after {‘Post restored to revision from March 29, 2016 @ 19:47:07 [Autosave].’ after updates {determined by WP} {#O4T4A8 thru #NOKXS2 + #O4KGH8 thru #O4OEAT + #NX4MTW + #O4T8AY thru #O4KGXC + #O4OIC4 thru #O4T9FA + #NXB1SF thru #NNPIWX + #O4TG5K thru #O4TG6Q + #O4QK1Q thru #NOM14K + #O4OLSX thru #O4OLXU + #O4ON4R thru #O4ON6K + #O4OFMX thru #O4OFMH + history {#O4OG2K + {broken line to fix} #NXER4S}} after ‘There is an autosave of this post that is more recent than the version below. View the autosave’ after reload}} ;as{got Chrome ‘Aw, Snap!’ ago min 5~} ;begin date Pst1303}
      2. O4OG2K: ‘{post.status.snapshot{;date2016.03.26SatPst‘;after ID ’minutes t since Pst1953‘;revision ’35‘;version5‘;words ’10088‘;as ’due to {just now Chrome ‘Aw, Snap!’ at time of entry TBA update}‘;do ’now on reload get {‘There is an autosave of this post that is more recent than the version below. View the autosave’+ updates {#O4I9SJ thru #NYNA6Q + #O4KRN8 thru #NX4MXN + #NOTOR0 thru #O4KGXC + #O3QEYO thru #O4KSP7 + #O4KSW2 thru #O3L8IM: lots of rearranging/moving} + ‘Post restored to revision from March 27, 2016 @ 02:50:32 [Autosave].’} +{‘The backup of this post in your browser is different from the version below. Restore the backup.’ + ‘Post restored successfully. Undo.’ + updates from wikiEd {#O4KSP7 kid 1 /NWU3EV}} then NY0WO6 with replacement qty {206+3+847} then continue editing‘}}’
      3. O4EMM5: ‘{post.status.snapshot{;date2016.03.21MonPst1310‘;after ID ’minutes 30 since Pst1240‘;revision ’34‘;version4‘;words ’9169‘;as ’due to some Chrome close/crash’; do ’now on reload get {‘There is an autosave of this post that is more recent than the version below. View the autosave’+ updates {#O3XRRK thru #O3XRNH + #NUBTA9 + history {#O3XO2Q + #O3OGRX}} + ‘Post restored to revision from March 12, 2016 @ 17:55:35 [Autosave].’} + no {‘The backup of this post in your browser is different from the version below. Restore the backup.’ + ‘Post restored successfully. Undo.’ + updates from wikiEd {}} then NY0WO6 with replacement qty {35+3+706} then continue editing‘}}’ :/4670#O4EMM5
      4. O3XO2Q: ‘{post.status.snapshot{;date2016.03.12SatPst‘;after ID ’minutes t since Pst0751‘;revision ’t5‘;version4‘;words ’t7825‘;as ’due to {OS reset O3RUZ8}‘;do ’now on reload get ‘There is an autosave of this post that is more recent than the version below. View the autosave’+ {updates found by WP} {title + #O3OLXT + #NZ3GR7 + #O3OMLW thru #O3L3TO + #NWUAVB + #NWUJRD thru #NWUNXT moved + #NXBB3L thru #NWUNXT + #NXEG8I~ thru #NXBIBW~ moved out + #O3ON3D + #O3OI6O thru #O3OIBP + #O3QEYO thru #O3QF16 + #NXEH09 thru #NXEN0D moved out + #NWZMX3 thru #NOLZKE moved + history {#NWUHIR thru #NYM1ZP moved out + #O3OGRX} + #O3QFYY } + ‘Post restored to revision from March 9, 2016 @ 00:28:48 [Autosave].’ then NY0WO6 with replacement qty {63+0+687} then continue editing‘}}’
      5. O3OIPU: per last failure, break up doc as
        1. O3OLK1: following O3MO54, in reverse order
          1. O3OLLY: factor out everything but that section :O3OLLY, notably doing post creation /5432#O3OKXY
          2. O3OLKW: determine that section was here first
      6. O3OGRX: ‘{post.status.snapshot{;date2016.03.07MonPst0913‘;after ID ’minutes 36 since Pst0836‘;revision ’32‘;version3‘;words ’13434‘;as ’due Chrome ‘Aw, Snap!’ ~10min ago’; do ’now on reload get ‘There is an autosave of this post that is more recent than the version below. View the autosave’+ {updates found by WP} {#NWUAVB + #O3MNHA + #O3MNO6 thru #O3N5TH + #O3N8TJ thru #O3N9MM + #O3MMWZ thru #NZ25WM + #O3MN5D + #NZ266R + #NXS2YK thru #O3MMPI + #NXEIW3 thru #O3OG0D + history #O3NAB3 thru #O3MJ4F } + ‘Post restored to revision from March 7, 2016 @ 16:25:52 [Autosave].’ +{‘The backup of this post in your browser is different from the version below. Restore the backup.’ then ‘Post restored successfully. Undo.’ which gave just addition ‘ first then do in order <ol><li><sup><a
        class=”aself_KENC7Z” id=”O3OGBX” href=”#O3OGBX”>O3OGBX</a></sup> click ‘Update/Save’,</li></ol>’ } then add content {section O3OI5S} then NY0WO6 with replacement qty {172 + 12 + 1132 } then continue editing‘}}’
      7. O3NAB3: doing ‘format update to {latest: that of /5426#O3L134, no, /4670#O3N9JI} :O3NA0G
        1. O3NABZ: merge from there into here ‘“author(s) background (on the topic)”’ updated into NWV4HX
      8. O3MO54: if post proves too big, seems best to factor out ‘‘‘content standardized’ :NXBB3L’ ’ or other sibling(s) :O3MO54
      9. O3MJ4F: ‘{post.status.snapshot{;date2016.03.06SunPst‘;after ID ’minutes t since Pst10730‘;revision ’31‘;version3‘;words ’12446‘;as ’due Chrome crash O3L9DL‘;do ’now on reload get ‘There is an autosave of this post that is more recent than the version below. View the autosave’+ updates {#NYM1X1 thru #NXEG0Y + #NXEY0W thru #O3L6VP + #O3KWBH thru #O3L39A + #NYM1ZP thru #O3KR84} + ‘Post restored to revision from March 5, 2016 @ 22:52:50 [Autosave].’ + ‘The backup of this post in your browser is different from the version below. Restore the backup.’ then ‘Post restored successfully. Undo.’ which {undone updates back to shortly after #O3KV8Y, so about 1/2, so did ‘Undo’} so ‘’then {got rid of nbsp ‘ ’: 108 replacements} then NY0WO6 with 1043 replacements then continue editing‘}}’ :O3MJ4F
      10. O3L3DW: section id changed from ‘NOLYU4: ’ to the standard
      11. O3KVPO: version 3 updating every ~1 month
      12. O3KTUW: update doc to format {latest: of /5426#O3JJZQ}, :O3KTUW including
        1. O3KZIE: notable format standard updates including
          1. O3KZJP: add ‘post’’ & and in there
            1. O3L1DU: append to title ‘–where its subsections don’t specify’
              1. O3L1SB: so enabling to apply to every kid and in every kid (that has it) cutting the ‘additional’
        2. O3L1ZZ: sort order: priority 1st: achieving: much work on that.
      13. O3KR84: ‘{post.status.snapshot{;date2016.03.05SatPst1000~‘;after ID ’minutes 91~ since Pst0831‘;revision ’30‘;version3‘;words ’12025‘;as ’due to some Chrome tab loss’; do ’now on reload get ‘There is an autosave of this post that is more recent than the version below. View the autosave’+ updates {computed automatically} {{#NZ27DT: looks like editing was interrupted, including prior version a tad more complete with wording ‘was before not done as too costly, usually’}} + {load error during restore so didn’t get ‘Post restored to revision from March 1, 2016 @ 17:52:17 [Autosave].’ equivalent but post appeared restored} then {updates manually determined by looking at KCGUIDs unconverted} of { #NZ0QZF + #NZ0PL7 thru #NZ0QTZ + #NZ10MH + #NZ229N thru #NZ219Z + #NZ273E thru #O3KSI8} + {got rid of nbsp ‘ ’: 1197 replacements} then NY0WO6 with 998 replacements then continue editing‘}}’ :O3KR84
      14. NZ0OAC: NZ0OAC: ‘{post.status.snapshot{;date20151207Mon1819pst‘;after ID ’minutes ~15‘;revision ’30‘;version3.1‘;words ’10943‘;as ’OS crash NZ0HER causes this http://1.jothere.com/wp-admin/post.php?post=4670&action=edit&revision=4830 giving ‘There is an autosave of this post that is more recent than the version below. View the autosave’ + updates {#NYMLKX thru #NYMM8C + #NYMKYQ thru #NYML2E + #NOKXS2 thru #NYEX64 + history #NY2PXG thru #NY2PAC} + ‘Post restored to revision from December 1, 2015 @ 23:45:31 [Autosave]’‘;do ’continue editing starting with #NXS2YK with 918 replacements‘}}’
        1. NZ0OT1: point location originally thru prior: ‘‘NZ0OAC’ :NZ0ONG
      15. NY2PXG: continue updates:
      16. NY2PAC: ‘{post.status.snapshot{;date20151119Thu0945pst‘;after ID ’minutes 0‘;revision ’29‘;version3.0‘;words ’10473‘;as ’just got Chrome ‘Aw, Snap!’ so on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave giving updates {#NVSWPG thru #NXBIBW (a move) + #NY0UAL thru #NY0V6D + #NY0UIU thru #NXS2YD + #NY0UKY thru #NY0UL8 + #NY2OBM + #NY0RWK thru #NY0S9X + history #NY0TLL thru #NY0RM9}
        + ‘Post restored to revision from November 19, 2015 @ 17:29:15 [Autosave]’ which looked current on good look’; do ’continue editing starting with #NXS2YK with 875 replacements‘}}’
      17. NY0TLL: updates: #NY0S9X+ #NY0SDT (create section) + #NY0T3K + more
      18. NY0RM9: ‘{post.status.snapshot{;date20151118Wed0840pst‘;after ID ’minutes 0‘;revision ’28‘;version2.7‘;words ’9167‘;as ’Due to Chrome crash NXV6F0, on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave giving updates {#NXVSVU thru #NXVUAS + {#NOTPON thru #NXVSKT: section move #NXVSKT}+ history update NXVSB6}
        + ‘Post restored to revision from November 16, 2015 @ 01:18:28 [Autosave]’ and on quick look looked current’; do ’continue editing‘}}’
      19. NXVSB6: starting updates:
      20. NXVS9G: ‘{post.status.snapshot{;date20151115Sun1605pst‘;after ID ’minutes 0‘;revision ’27‘;version2.6‘;words ’4452‘;as ’Due to Chrome crash NXV6F0, on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave giving updates {title+#NOPO30 thru #NOPO74 + #NTMDA0 + #NWWLSC thru #NX95CI} & ‘Post restored to revision
        from November 14, 2015 @ 19:20:39 [Autosave]’and on quick look looked current’; do ’continue editing‘}}’
      21. NXK0RX: updates: #NXJZMA
      22. NXJZAF: ‘{post.status.snapshot{;date20151109Mon0706pst‘;after ID ’minutes 0‘;revision ’26‘;version2.5‘;words ’8800‘;as ’Due to OS forced restart NXGEHV, didn’t properly save so on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave’ gives updates small changes + #NXEM9V thru #NXD8O0 + #NXF5HX thru #NXF3FH + #NXEVXT thru #NXD9PO + #NXG6JJ thru #NXG920 + #NXG8XQ thru #NXGA46}
        getting ‘Post restored to revision from November 7, 2015 @ 15:11:56 [Autosave]’ expect its current though can not tell on quick look
        ‘; do ’continue editing‘}}’
      23. NXEYX5: finishing ‘‘[WordPress doc] create’
      24. NXER4S: ‘{post.status.snapshot{;date20151106Fri1122pst~(verify)‘;after ID ’minutes 0‘;revision ’25‘;version2.4‘;words ’7998‘;as ’got ‘Aw, Snap’ and on reload got ‘There is an autosave of this post that is more recent than the version below. View the autosave’; got updates {#NXEG0Y + massive reordering so diff is not concise} getting ‘Post restored to revision from November 6, 2015 @ 19:05:54 [Autosave]’ & ‘The backup of this post in your browser is different from the version below. Restore the backup.’ which gives all updates thru last word at
        #NXEQAB
        ‘; do ’now Update again then more updates as time & need‘}}’
      25. NXBB2I: updates: {full organizing & grouping} + {cut ‘NVTCFC: ‘-’’ as seemed pointless} + TBA + #NXD1IF + thru #NXD5D3 + ‘‘type’’ + ‘annex’ grouping + {‘‘[doc] create’’ –unfinished} + grouping ‘‘‘1.JotHere.com’ or similar ‘WordPress’ site’‘ + grouping ‘‘‘WordPress’ document’
      26. NWWETH: AnytimeInnovator additions in reverse start order:
        1. NXB57O: ‘{post.status.snapshot{;date20151104Wed1235pst~(verify)‘;after ID ’minutes 0‘;revision ’22‘;version2.1‘;words ’6556‘;assome todo but usable and {due spam still forcing site to limit outside contact, need to get out new means NWWLSC} ‘;do ’now Update again then more updates as time & need‘}}’
        2. NXB2AU: updates {#NXB1SF moving into there its contents} + #NXB250 + would do more but last backup is browser so last version lost for diffing; spellcheck + {update IDs to latest format: 525 replacements}
        3. NXAUNZ: ‘{post.status.snapshot{;date201511004Wed0849pst‘;after ID ’minutes 0‘;revision ’22‘;version2.1‘;words ’6392‘;as ’yesterday eve Chrome crash before actual last update, so just now reload getting ‘The backup of this post in your browser is different from the version below. Restore the backup.’ which indeed appeared much newer so kept’; do ’now finish edits here: {add #NXAWR8 and its containing group & get that working in Chrome & Firefox, last update #NXB1MP}‘}}
        4. NX967Y: –never actually performed due to next (NXAUNZ): ‘{post.status.snapshot{;date20151103Tue1102pst~(verify)‘;after ID ’minutes 0‘;revision ’22‘;version2.1‘;words ’6321‘;assome todo but usable and {due spam still forcing site to limit outside contact, need to get out new means NWWLSC} ‘;do ’now Update again‘}}
        5. NX967B: spellcheck + {update IDs to latest format: 505 replacements}
        6. NWZMRD: #NWZMX3 + {~30% more to #NVSX4L} + #NX7L8P + #NX91CQ + #NX930G + #NX93ZI + #NX94R3 + {to enable that, #NX94Q9 factor-out} + {insert most missing ‘‘-’’}
        7. NWZMQD: at & right after time of parent ID, #NWWLSC +{do /5129#NWW39J here where it could help, as #NUAFD2}
      27. NWWD9Q: ‘{post.status.snapshot{;date20151027Tue1406pst‘;after ID ’minutes 0‘;revision ’21‘;version2.0‘;words ’5324‘;asmuch todo but seemingly finished #NWU63H so good idea to save’; do ’now Update again‘}}
      28. NWUJ58: continue #NWU63H {starting new post /5929#NWUINJ}, listed in reverse order:
        1. NWV4AL: move categories, then do link updates /5129#NWV24Q
        2. NWUJ6E: move ‘NOLDef’ to new post as no obvious pick here but
          1. NWUJBQ: it wasn’t here originally per #NOLZ4H –biggest reason by far
          2. NWUJBY: the references from standard pages won’t have to be fixed, mostly only references here, though all that happens with Pretty Link updates
      29. NWUHQ7: ‘{post.status.snapshot{;date20151026Mon1347pst‘;after ID ’minutes 0‘;revision ’20‘;version1.8‘;words ’12661‘;asmuch todo but big change before & coming’; do ’now Update again‘}}’
      30. NWUGAN: {spellcheck, finding #NWUHIR} + {update IDs to latest format: 1339 replacements}
      31. NWUG92: TODO: finish completing latest entries + proofread + verify links
      32. NWU65O: prepping for #NWU63H, update post to latest format, so from http://1.jothere.com/wp-admin/edit.php?orderby=date&order=desc pick post with highest ID so /5102#NWSV6H including: {replaced ‘author(s) background (on the topic)’ of #NREHNZ with present}+{cutting ‘NOKW72: none.’}+{cutting ‘‘post name history in reverse start-order’’}
      33. NWU63H: seem to be getting too frequent ‘Aw, Snap!’, very likely because of post size getting to big, so break it up.
      34. NWU5NC: ‘{post.status.snapshot{;date20151026Mon0926pst‘;after ID ’minutes 0‘;revision ’20‘;version1.8‘;words ’12353‘;as ’Chrome gave ‘Aw, Snap!’ reload page getting ‘There is an autosave of this post that is more recent than the version below. View the autosave’; did & got ‘Post restored to revision from October 26, 2015 @ 16:15:14 [Autosave]’ and ‘The backup of this post in your browser is different from the version below. Restore the backup.’ which had 1 line more making current so kept’; do ’now continue editing‘}}’
      35. NWSRIN: ‘{post.status.snapshot{;date20151025Sun1524pst‘;after ID ’minutes 0‘;revision ’19‘;version1.7‘;words ’11733‘;as ’Chrome gave ‘Aw, Snap!’ reload page getting ‘The backup of this post in your browser is different from the version below. Restore the backup.’ which gave significant (all?) diffs so kept’; do ’now continue editing‘}}’
      36. NWCIVR: ‘{post.status.snapshot{;date20151016Fri2055pst‘;after ID ’minutes 0‘;revision ’18‘;version1.6‘;words ’11118‘;as ’need to reboot OS‘; do ’Update then return to editing when needed‘}}’
      37. NVWFEF: {‘ class=”N0QX1H”’ usage bad: cut ~7 wrong-placed instances and add 1 to special usage on #NUAAWD}
      38. NVWEKZ: ‘{post.status.snapshot{;date20151008Thu0402pst‘;after ID ’minutes 0‘;revision ’18‘;version1.6‘;words ’11089‘;as ’to move out #NUA7NJ‘;do ’opening again, got ‘There is an autosave of this post that is more recent than the version below. View the autosave’ so did it and found all my additions there so restored it getting ‘Post restored to revision from October 7, 2015 @ 00:50:46 [Autosave]’ then continue editing’; do ’continue editing‘}}’
      39. NVTDNN: several additions: {#NUAB99 improvements including detailed at #NVT60L}+{add #NVT43L}+{add #NVSWPG}
      40. NVTDKQ: ‘{post.status.snapshot{;date2015100609Tue1246pst‘;after ID ’minutes 0‘;revision ’17‘;version1.5‘;words ’11250‘;as ’~3min ago, got an ‘Aw, Snap!’ then refreshing the page gave page without any of the last edits but an option to restore from browser backup so did that which gave ‘Post restored successfully. Undo.’ and seemingly all data restored’; do ’continue editing‘}}’
      41. NVSWNZ: {additions thru #NVT00M} + {additions thru #NVT4EW}+{#NUAB99 updates for clarity especially #NVT60L}
      42. NUSWEQ: ‘{post.status.snapshot{;date20150916Wed2001pst‘;after ID ’minutes 0‘;revision ’16‘;version1.4‘;words ’10422‘;as ’>500 words added plus significant updates’; do ’Update again‘}}’
      43. NUQ69U: ‘{post.status.snapshot: date20150915Tue0842pst‘; after ID’ minutes 0~‘; revision ’16‘; version ’1.3‘; words ’9822‘; as ’new edits to do‘, do ’open then get ‘There is an autosave of this post that is more recent than the version below. View the autosave’; review & do it, getting ‘Post restored to revision from September 7, 2015 @ 23:28:00 [Autosave]’ then start editing‘}
      44. NUBKOM: just now tab went blank with ‘Aw, Snap!<br/>Something went wrong while displaying this webpage. Closing the apps and tabs that you don’t need may help by making more memory available. Learn more Send Feedback’; all other tabs by in this profile were similarly killed. Closed all other tabs & refreshed this one. Got text missing edits plus ‘There is an autosave of this post that is more recent than the version below. View the autosave ’; did it. Got ‘Post restored to revision from September 7, 2015 @ 18:27:54 [Autosave]’. Then also got ‘The backup of this post in your browser is different from the version below. Restore the backup.’ which (via diff) is just ~2 sec different, so don’t restore it.
      45. NU9XZN: ‘{post.status.snapshot: date20150906Sun1421pst‘; after ID’ minutes 0~‘; revision ’14‘; words ’8185‘; version ’1.1‘; as ’new edits to do’‘, do ’but get immediately get ‘There is an autosave of this post that is more recent than the version below. View the autosave’ so review & do get ‘Post restored to revision from July 14, 2015 @ 19:40:54 [Autosave]’ then start editing‘}’
      46. NRHH3S: NRHH3S: note the 1st published date at ‘[UTC ]May 27, 2015 @ 00:06’ when {thought did it at NREICW }+{the above record shows no reason for it to be there}+{it apparently wasn’t then else wouldn’t have had motivation of NRBUZF} +{there is no revision within 2 days of that date}{https://web.archive.org/web/http://1.jothere.com/4670 has no record of it but it also has no record of the site as of 2015}, so {I really don’t know how it got set to this date}+{set to match NREICW: UTC ‘07-Jul 13, 2015 @ 1 : 52’}
      47. NRHGYD: ‘{post.status.snapshot: date20150714Tue0813pst‘; after ID’ minutes 0~‘; revision ’11‘; words ’8334‘; version ’1.0‘; as ’need to add ‘section history additional in start order’‘, do ’start editing‘}’
      48. NREICW: NREICW: ‘{post.status.snapshot: date20150712Sun1752pst‘; after ID’ minutes 2~‘; revision ’10‘; words ’8306‘; version ’1.0‘; as ’more to do but proven quite usable as is and now basic polishing done‘, do ’Publish #1‘}’
      49. NREECG: spellcheck; add to missing categories: ~5; {update IDs to latest format: 860 replacements}
      50. NRE3AU: a few min ago got ‘He’s dead, Jim!’ so clicking Refresh now got & did ‘The backup of this post in your browser is different from the version below. Restore the backup.’: Kdiff3 revealed just 1 character added at NRE2BW.
      51. NRDXEL: check links: checked a few
      52. NRDQYE: ~20min before, start completing incomplete text which catches my eye, ending in NRDVYT then NRDX30
      53. NRBW0K: NRBW0K: do NRBX25 (replace all ​“double-quote​” to ​‘single-quote​’) on this post: replacement qty 355=315 +40+0 & 356=254+102+0 respectively.
      54. NRBUZF: NRBUZF: ‘{post.status.snapshot: date ’20150711Sat0730pst‘; after ID’ minutes 0~‘; revision ’9‘; words ’6580‘; version ’0.90~‘; asTOS phrase especially is key and all new posts reference this and I am about to promote some posts as /4812#NR4KV9, need this post to become published, so‘, do ’start polishing‘}’
      55. NRHH8O: ‘1st published date at ‘[UTC ]May 27, 2015 @ 00:06’’ corrected
      56. NOZXH9: ‘{post.status.snapshot: date ’20150526Tue2346pst‘; after ID’ minutes 0~‘; revision ’8‘; words ’6561‘; version ’0.89~‘; as ’more additions & completions‘, do ’start editing‘}’
      57. NWV5SG: updates here (diff 2015.05.25-06.22) were mislabeled as but were actually Destiny’s
      58. NOWDNQ: ‘{post.status.snapshot: date ’20150525Mon0145pst‘; after ID’ minutes 0~‘; revision ’7‘; words ’6392‘; version ’0.89~‘; as ’have to sleep then move onto other work‘, do ’save & pause editing‘}’
      59. NOVE14: ‘{post.status.snapshot: date ’20150524Sun1255pst‘; after ID’ minutes 0~‘; revision ’7‘; words ’5640‘; version ’0.88~‘; as ’have ideas have get down now‘, do ’resume editing‘}’
      60. NOVBEI: ‘{post.status.snapshot: date ’20150524Sun1158pst‘; after ID’ minutes 0~‘; revision ’6‘; words ’5601‘; version ’0.88~‘; as ’hours work >1 and need to leave with friends‘, do ’save & pause editing‘}’
      61. NOVBEI: ‘{post.status.snapshot: date ’20150524Sun1158pst‘; after ID’ minutes 0~‘; revision ’6‘; words ’5601‘; version ’0.88~‘; as ’hours work >1 and need to leave with friends‘, do ’save & pause editing‘}’
      62. OV3MG ‘{post.status.snapshot: date ’20150524Sun0911pst‘; after ID’ minutes 0~‘; revision ’6‘; words ’5161‘; version ’same‘; as ’not finished‘, do ’start editing‘}’
      63. NOUIV2: ‘{post.status.snapshot: date20150524Sun0142pst‘; after ID’ minutes 1~‘; revision ’5‘; words ’5135‘; version ’0.87~‘; as ’words >1000 more‘, do ’save & stop‘}’
      64. NWU6YK: original history
        ‘post edits overall history table, by increasing start-time’
        ‘entry ID’ ‘action’ ‘why’ ‘word cnt’ ‘ver #’ ‘s#’ ‘date (typ fr earliest ID)’
        NOLYOE: . start new content /4658#NOLXCJ 0 0 1 right after NOLY4C=20150819Tue1034~pst
        1. NOLYUG: ‘now {via ‘Copy to a new draft’, so of {then latest post template used by author, so /4658#KOLWCZ}, so of then its latest saved version, so with last entry ‘NOLY4C: stop & start per NOLXKU 493 1.1 2 now=20150819Tue1033pst’} created {this here post, so’ http://1.JotHere.com/4670 ‘} then cut {all its content not to be reused here, so the content just applying to the template, so all the posts’ fully stated points including their KCGUIDs}.’
        2. NOLYZI: import /4658#NOLXBU ; compose the basic idea & test it: works! Enter thru NOME7E
        NOMEHE: . stop need now to work on other stuff 1264 0.8 d 1 now=20150819Tue1627pst
        NONQ2S: . start finish basic work here ||? ||? d 2 now=20150820Wed0936pst
        1. NONQ66: continue where left off
        NOO83N: . stop periodic save & other stuff 2625 d 3 now=20150820Wed1605pst
        NOOL7R: . start continue work 2635 d 4 now=20150820Wed2048pst
        1. NOPPGZ: before this, various additions
        2. NOPPH7: replace ‘NOM40D: terms & other expressions and their definitions
          1. NOM41B: in order entered here

          ’ with present value at NOM41B

        3. NOTGGO: more additions
        NOTGKA: . stop+start periodic save 4023 .85 d4 now=20150823Sat1157pst
        start
        NWU70T: continues at entries chronologically after this entry NWU6YK
      65. O3QFYY: for use of this post as a template: {post.status.snapshot: date2016.03.07MonPst‘;after ID’ minutes t60*2-0 since Pst1013~‘;revision ’0‘;version0‘;words ’364~‘ ;as ’need a proper place to put this, notably to do {move TBA ‘factor out everything but that section :O3OLLY’}’; do ’following NXBIBI with {{template plus no source text} last {addition if known else history entry} /4670#O3OLLY (post 1st-latest and {related: no}), create {this ‘document’ http://1.JotHere.com/5432#O3OLQW}‘}’.
    11. NYMK00: comments: are next & elsewhere per ‘To reply & discuss’