May 122011
 

N48P2Q: KCGUID ‘‘especially what I need to know’™’’ :http://1.JotHere.com/401#N48P2Q

  1. ‘section’
    1. MO3B4H:  ‘‘‘Pretty Link’ entry’ ‘anew’’ http://1.JotHere.com/6mp
    2. M31R7R: ‘history in reverse order’
      1. OSWKF8:   ‘op’ resume editing after {;date 2017.07.10MonPst1839 ;polish .6 ;version TBA ;words 6355 ;revision 15?}

        1. OSE2EP:  OSE2EP: convert to {format latest: that of /6067#OS8EK1} (start now) cutting in textual order quote:
          1. document wrapper ‘<div class=”N2V8R4″><section><header>..’
          2. subsections: WHAT TO DO, WHAT, WHY, WHEN, WHERE, COST, WHO’S PARTICIPATING, ADDITIONAL DETAILS, ADDITIONAL HISTORY, POST TODO, CREATORS, CATEGORIES, ADDITIONAL DETAILS FOR ORGANIZERS/DEVELOPERS, FOOTNOTES, POST HISTORY.
          3. N20A33: section history in REVERSE order:
            1. .
          4. MEG922What to do
            1. N48PEX: To understand: glance at WHO’S PARTICIPATING especially since use is highly novel, then read WHAT to the degree interested.
            2. N48PH1: Ideally reply with constructive feedback.
            3. N21JED:  ‘‘section history additional’ ‘in reverse start order’:’
              1. .

            -end of WHAT TO DO

          5. MNLART: WHAT

            -end of WHAT

          6. MNYDBT: WHY

            1. .

            -end of WHY

            MAX1LQ: WHEN

            1. .

            -end of WHEN

            MAX1N4: WHERE

            1. .

            -end of WHERE

            MAX1VD: COST

            1. MNLAB7: See WHAT

            -end of COST

          7. -end of WHO’S PARTICIPATING
          8. M33M3R: ADDITIONAL FUTURE PLANS

            1. .

            -end of FUTURE PLANS

            MO37MD: ADDITIONAL HISTORY

            1. .

            -end of ADDITIONAL HISTORY

            MAX22R: ADDITIONAL DETAILS

            1. .

            -end of ADDITIONAL DETAILS

            MDE167: POST ADDITIONAL TODO, roughly in order:

            1. .

            -end of POST TODO

            MAYJ80: CREATORS

            1. MEMPEO: The author

            2. MEMPF1: No one else unless attributed.

            -end of CREATORS


            N1X3EQ: CATEGORIES

            -end of CATEGORIES

          9. MDAIRC ADDITIONIONAL DETAILS FOR ORGANIZERS/DEVELOPERS/HELPERS … -end of ADDITIONAL DETAILS FOR ORGANIZERS/DEVELOPERS
          10. MDAIRC: FOOTNOTES -end of FOOTNOTES
          11.  POST HISTORY, in order: -end of POST HISTORY

        2. OSE26N:  after date 2017.06.30PstFri1848 after words 5770
        3. after entry template is /5812#ON705D
        4. want to add text of OSCDIM
      2. OSF3WF:  starting 2017.03.30FriPst17~, plan to pseudo-name the key inventor(s)
      3. O6JJDH: added points #O6JJ8V thru #O6JJ9H,
      4. O67GQQ: ‘op’{resume editing after {;date 2016.05.02MonPst ;polish .65 ;version 1 ;words 7010t} after {NY0WO6 with replacement qty {{1st do source code regex ‘| ’ to ‘|&nbsp;’, then 155}}+21+358} after {as would be expected, none of this: update {determined by wikiEd} {} 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 5622 ;revision 12} after {‘Post restored to revision from January 27, 2016 @ 04:30:38 [Autosave].’ after updates {determined by WP} {#N1S3YC #NX7HSX thru #NX7IDI+#N21JED moved + #LL45YV thru #O1LGEX + #N14EKP thru #N14ELC moved +  #N49D7Y thru #N49D5Z moved + #NWZ1EI  thru #NWZ4JV + #NWZ13Z thru #NWZ1DI + #N14GNR + #N14H37 + #N49D7Y thru #N49D5Z + #NWYGXL thru #O1KPRR} after ‘There is an autosave of this post that is more recent than the version below. View the autosave’ after reload now} {;date 2016.04.25MonPst1257; months ago, unknown Chrome crash}}
      5. O1IUGW: ‘{post.status.snapshot{;date2016.01.25Mon1039pst‘;after ID ’minutes ~‘;revision ’1‘;version1tba‘;words ’TBA‘;as ’due to power cycle O196U6, now on reload get ‘There is an autosave of this post that is more recent than the version below. View the autosave’ + updates {{appear on left column not right, for reason I know not} and are {#N1S3YC + #NX7HSX thru #NX7I8O + #NX7IDI + #N14GIY + #NWZ1EI thru #NWZ4JV + #N14HJ2 + #NWZ13Z thru #NWZ1DI + history #NWYGXL}} + ‘Post restored to revision from December 15, 2015 @ 19:40:43 [Autosave].’ ; this appears a regression for most but seemingly not all portions! Probably caused for a 2nd version saved over another So … ‘;do ’sibling points‘}}’
        1. O1KNZQ: the version ‘3 months ago (2 Nov @ 21:35)’ , and not ‘1 month ago (15 Dec @ 19:40)’, has all changes, so using MSExWeb column select, fully restore it.
        2. O1KPN3: cannot diff {the prior revision, ‘2 years ago (26 Apr @ 00:02)’} and the latest revision ‘1 month ago (15 Dec @ 19:40)’ which I suspect is identical, including since the latter isn’t listed but instead is listed ‘24 hours ago (25 Jan @ 18:51)’ and diffing that produces ‘Sorry, something went wrong. The requested comparison could not be loaded.’ –all for reasons I don’t know.
        3. O1KPRR: NY0WO6 with 339 replacements, then continue editing
      6. NWYGXL: edits: #NWZ1EI + #N1S3YC + #NX7HSX + #NX7IDI
      7. N4MLV7: image qty: 0 to 1(N4MK38); again publish -pst2014.04.25Fri1156.
      8. N48XWV: New title #N48VNM (and while still sub-featuring the original short title) including 1st Name; notable reorganization & rewriting of WHAT; several important additions including factoring out a WHO’S PARTICIPATING section and new pros-thru-cons section Aesthetics and N49HCD; the 1st pro -work on; add Generating an ID & #N4AV3M & thru #N48N4F, & #N4B8BV and all it links to here; spellcheck;
      9. N48OUN: Reformat into latest http://JotHere.com format so post: prepend into start copy of latest(=pst2014.04.06Sun1811) 4375.N3ML92.htm (N3MLXO) then update & replace that with latest content of this article; spellcheck including MJRef to MJHref; publish now pst2014.04.18Fri1217.
      10. N48O4P: this latest version (after accidental months delay) publish now pst2014.04.18Fri1118.
      11. N14KRK: add some history notes plus #N14G06
      12. N14HUO: do 401#N14GGJ: 125 replacements; save.
      13. N14HN8: do #N14HB9: good as all IDs not found are in a strange non-standard format (I recall without sup-tag)
      14. N14ECL: 401.N14ECL.htm -created now; draft file for editing this in say MSExWeb.
      15. MJO9IB: added Linking text which is labeled with an ID most notably the MJHref solution; pst2013.03.14Thu1537.
      16. MJO8XZ: added this history section
      17. MJO39P: 1st editing this with WP3.5+ which corrupts & keeps corrupt <a id=”..”>-tags until WP fixes this.
      18. MJO383: prior history needs reconstruction
    3. N1S3YC:  TOU(Terms Of Use) including {copyright © and info’s {confidentiality/privacy & allowed use}} is JotHere.com’s default TOU except: none.
    4. NX7IDI:  To reply & discuss, please use JotHere.com’s default methods (click) except: none.
    5. MAZBWQ‘remaining sections’ (manually maintained so may be out-of-date):
    6. ‘additional’
      1. M33YGV:  ‘name anew’

        1. OSF35I:  (starting now) the-present-one per ‘OSE2EP: convert to {format latest..}’ moving content elsewhere here per OSF28X
        2. N48VNM: KCGUID: an IDentifier (of just a 6-character(short) all-caps alphanumeric, yet a typically & remarkably Globally Unique ID IFF limited-use as has-been) invented & heavily-used-by-a-few starting 2009 (per “KC”) to both (1) ID most anything especially every asset, record, & even written-point, plus (2) tell & track When (so timestamp) and often Who & Where done, all easily including quickly, globally, very portably & compactly, and aesthetically-as-possible” :N48VNM
        3. LL40IP: formerlyWhat are these 6-digit codes before every point & item?” per the most frequent need “to explain the use of them in a document
      2. NX7HSX: ‘post category’
        1. NX7I45: ‘a linkable GUID for every point LXJZ15’
          1. NX7I4S: started probably at time of ID ‘LXJZ15’
          2. N48QMM: quote(a linkable GUID for every point LXJZ15) –add to years ago
        2. NX7I87: ‘this site’s documentation for its users NQBFBL’
          1. NX7I8O: started probably days after ID ‘NQBFBL’
        3. N48QNI: quote(admin of this site LFNIZ6) –add to years ago
      3. image and caption or

        sample table
        col heading
        row heading linked value

        ‘success’

      4. ‘advertising/lessening additional’
      5. ‘motivation’
      6. ‘contributors including their {contributions & relevant background}’
      7. {to be put elsewhere} so ‘annex’
      8. ‘‘section history additional’ ‘in reverse start order’:’
        1. .
  2. OSF2H4:  ‘(‘KCGUID‘) introduction
    1. OSF244:  more technically :OSF244
      1. OSF29Z:  is ‘an IDentifier (of just a 6-character(short) all-caps alphanumeric, yet a typically & remarkably Globally Unique ID IFF limited-use as has-been)’
      2. OSF2FJ:  is ‘to both (1) ID most anything especially every asset, record, & even written-point, plus (2) tell & track When (so timestamp) and often Who & Where done, all easily including quickly, globally, very portably & compactly, and aesthetically-as-possible’
      3. OSF2DX:  is ‘invented & heavily-used-by-a-few starting 2009 (per “KC”)
      4. OSF3HC:  is {one: ‘this version :N48YVF’} in a series-else-graph of improving globally-unique ID designs :OSF3HC
      5. ‘‘section history additional’ ‘in reverse start order’:’
        1. OSF28X:  so far is {all definition/description of N48VNM}+ OSF3HC :OSF28X
  3. LL40MC: To explain the use of them in a document

    1. N48YHE: –especially per the very deep (maybe even life-form instinctual) apparent social custom ~“one should not be very especially unpleasantly unusual without explaining it, ideally very-quickly including un-prompted plus well”
      1. N49DNC: –also explaining why this subsection is listed first.
      2. N4AV3M: –indeed, while the system is pretty technically clever, it’s actually far more socially pioneering.
    2. N48Y5Y: in the doc, from most preferred, say one of:
      1. N48M88: What are these codes as “N48M88” on this paragraph? They’re short IDs under-development to uniquely-reference, date-stamp, and portably-track most any point, item, or content
        1. N498K3: –created by taking version MWPJAT (used in email) then per Lucy‘s suggestion adding “under-development “.
        2. N498T5: –1st used here
      2. N4AL9M: The ID intro used in JotHere’s right-sidebar –glance at that
        1. N14EQT: –based on and extending the then email version.
      3. N4ALF2: The intro once used in email signature

        LL3YGR: What are these 6-digit codes before every paragraph & point? They’re IDs to date-stamp & uniquely-reference most anything –see that link for more details.

      4. LL40KY: [outdated: ]IDs to date-stamp & uniquely-reference most anythingthat gives some explanation
      5. N48YBS: or similar, giving link the full explanation.
    3. N48Y6Z: placing the explanation as an aside in the document, as from most preferred:
      1. N48YD5: in a side-bar, ideally on right
      2. N48Y9H: an “Aside” of the email/message signature.
      3. N48Y84: in the preface or other document prefix
        1. N48Y8Y: the original solution
  4. N48UQ3: Name

    1. N48UR7: KCGUID
      1. N48US9: where
        1. N48VAO: The 1st 2 characters (“KC”) is from (same as) the 1st function generating these codes (UTC70s36_KCSJ8B created 2009010111280)
        2. N48VBN: The last 4 characters (“GUID”) is for Globally Unique Identifier generally so meaning NOT “typically refers to various implementations of the universally unique identifier (UUID) standard”.
      2. N49C1M: at time of parent ID (2014.04.18), I coined as the 1st name.
    2. N48UQI: Prior (to 2014.04.18), had no real name, official nor common, just this document describing them.
  5. N48Z04: Pros thru cons:

    1. N4AMRG: Outstanding: Short (so compact)
      1. N4AMSD: enables them to be used nearly everywhere, then getting all sorts of additional benefits from that
    2. N4ANZ7: Outstanding: Easy to find (an item) by (thanks to increasing automation)
      1. N4AO1J: by design, its short single-case all-alphanumeric
        1. N4AO3R: serves as an HTML element ID
        2. N4AO6G: serves as word for web search & desktop/personal-storage search in including by Google.
        3. N4AO4C: serves as a variable and function name in virtually every programming language (provided it begins with a letter which it does)
        4. N4AOH7: and for human recall and input (mostly the exception, but sometimes important)
          1. N4AOLB: short enough to easily spell out & type.
          2. N4AOFR: can be fabricated to spell certain words yet still capture almost-as-much global uniqueness plus date of creation; example: its name “LCGUID”
          3. N4AOEP: not easily memorized but can be -about as hard as remembering a phone number.
    3. N4990X: Excellent: typically globally unique
      1. N4AMPQ: Specifically: despite even today (despite increasing: publication even automatically plus web-search), long enough to assure roughly 99% of the time another ID by any other generation method won’t be in use.
    4. N49H4U: the 1st pro=Huge pro IMHO: having a short + typically globally unique & easy-to-find-by ID on every item including every written point
      1. N4AKF3: Pros thru Cons:
        1. N4AKFO: Most benefits of a top identifier
        2. N4AKPI: great references to the item
          1. N4ANSW: as then an item’s ID becomes a universal including easy-permanent reference to any item.
          2. N4AKS1: -specifically references which are short plus exact indeed can super-locate the item (can identify so track down the item no matter where it’s moved or copied to (as by web search) as are typically globally unique)
          3. N4AKTM: so enable “minimal repeating” detailed in right sidebar which itself means less: reading & storage & processing (including synchronization & maintenance) and other un-regulated copying.
        3. N4AL19: enables proper attribution & crediting & combats plagiarism
          1. N4ALQY: as each creation’s ID
            1. N4ALR9: can track back to its authors & owners where they desire that
            2. N4ALTV: are tricky to remove (so defeat) as
              1. N4ALV3: they are everywhere:
                1. N4AM1O: including, within writing, on every line
                2. N4AM2O: but yes, at least for writing, some program could “simply” be written to remove them all, but…
              2. N4ALUR: worse, unless references “fixed”, too, (hard), then references to the item break (so it may no longer have its popularity, or even work at all)
                1. N4AMDN: and “fixing” references (as to update to point to plagiarized copy) is then hard here since:
                  1. N4AM4A: the more popular the item, the more references to it (so use of its ID to refer to it) it generally has
                  2. N4AM66: regularly not all references can be found else modified to be “fixed”.
                2. N4ALXZ: For example, think programming code where every function & variable has an ID in its name —what we pioneers write. So then for every function or variable a person plagiarized, s/he would not only have to change its name to something new to hide its origin, so the program would continue to work, she would also have to track down and replace likely every reference within the program to the function/variable to the new name as well, and as well as being tricky in itself, as code increasingly becomes open-source and software-as-a-service, this may simply be impossible.
            3. N4ANIA: is made so easy to reference & link to it, the desire & clearly the need to copy at all is reduced.
          2. N4AVI8: so would well-support overt-use surveying by very important CoComp.Co(website may not be public yet).
    5. N49IRI: Mostly very good: an ID can tell Who, When, & Where other details (but possibly When), of it and/or what it was assigned to, only where & how its owners want to reveal this info,
      1. N4AMW9: including they do NOT inherently reveal, nor even contain, this info.
      2. N49IUG: Pros thru cons:
        1. N49IV0: Allows being very compact
        2. N49IVY: Allows one to get this info wrong and/or need to correct or augment or otherwise change it, which regularly happens here.
        3. N49IX8: Avoids unjust-discrimination or privacy compromises by revealing this info without forcing it to be lost;
          1. N49J2G: rather requires a database/authority to be queried for this info which then can blur and deny it as needed including depending on the requestor.
        4. N49J5Z: Allows the additional meta data properties system (as who, where, how, etc.) to be quite large plus evolve and be different including incomplete-answers in each individual instance.
        5. N49J3L: Allows for a simple & easy (so then also more stable) encoding
        6. N49J42: Notable Con:: requires additional substantial complexities to save & get this info.
    6. N49IGI: Mostly good: IDs inherently reveal the time of ID creation –well for those who know how the encoding works.
      1. N49IL3: This is mostly good but seemingly potentially bad for privacy & unjust discrimination:
      2. N49IMH: This may not be entirely or at all the case in the next version.
    7. LL41HJ: useful in numerous situations:
      1. LL41JR: as in general
        1. LL41ML: gives an ID to an item which is often fairly-globally unique.
        2. LL418E: =benefits of always & immediately doing: If placed on an item when it is created/entered whenever an ID might be necessary has notable benefits:
          1. LL41A5: it time-stamps when the item is created, including soon an ID-to-date converter web page will be offered so one can get, from the ID, the exact time down to the second.
          2. LL41BC: in the item one say a relative time (as “now” or “2 hours ago”) and still specify exactly –for the time-stamp of the ID gives the exact time being referred to.
          3. LL4CJJ: it insures all references to the will have the ID embedded so then
            1. LL4CNH: the link can be found & fixed if ever broken.
            2. LL4CNU: all references to the item can found (usually automatically) by searching on the ID.
          4. LL4CRA: it creates a uniform & short ID/serial-# for all items.
        3. LL41D9: A future version will allow one to get, from the ID, the exact user who created it.
      2. LL41ML as on text (as and ID on every paragraph, or document, or sentence, or heading, or table or column or row or table-cell)
        1. LL40ZW: any text which has an ID attached offers several benefits:
          1. LL41S8: all the general benefits mentioned above, including time-stamping & time-referencing, plus
          2. LL4131: Instead of having to quote arbitrary spans of text (and then have those quotes go out-of-date if the text changes or one got the quote wrong), one can much more compactly refer to some text by just quoting its ID (and only-optionally quoting the text, which might change anyway), and find it just by searching (as Google-searching or desktop-searching for that ID) and find it even if it’s moved to a new website or even if the text has changed.
          3. LL42VG: And then by making it easier to reference text, it then
            1. LL42YT: it then makes it easier to avoid repeating but rather encourages reuse of writings
            2. LL431D: which then cuts down on textual clutter and enables standards which are more consistent & developed faster.
          4. LL41XT: Helps track & credit authorship plus cut-down on plagiarism (as when the text is copied, the IDs are generally copied as well). The better tracking (of where words came from & went to) then also enables better authorship tracking & crediting.
        2. LL41XT Great for any documents which go thru revisions (as wikis, instructions, rules, & increasingly blog-posts) , as references to IDs will still be findable even if the text is moved or rewritten.
        3. LL45FY: Especially great for any sort of rules & laws & guidelines, including military doc, as every point & sub-point of a rule/law instantly gets ID/code so one can easily write “In (accordance- with|violation of (rule|point) x”.
        4. LL45L5: Great for manuals & instructions, as each point instantly gets an ID so one can say “See/follow/do step x”.
        5. LL421W: Good for messages, especially email, as then:
          1. LL424S: One wanting to refer to a portion of a message need not quote all the text there , just the ID (and optionally the text, but just a little bit).
          2. LL426S: since messaging is a snapshot of dialog and dialog is where a lot of (indeed possibly most) good ideas & sayings get invented, allows better tracking of where these good sayings & ideas came from (by just referring to the ID) and where they got used to (by the copying of an ID). And again since many/most good things start from dialog, this could lead to significantly better crediting where credit is due (per IDs helping credit & track, explained above). The paragraph’s ID allow one to refer to exactly where that “good saying” or “good idea” or “pearl of wisdom” came from and by whom.
      3. LL4C3M: On ID each file & folder and global-function and global-variable, using say the syntax “<name/>_<id/>” where the <name/> may change but <id/> remains constant. This allows these all (files, folders, variables, and functions) to be freely renamed & moved while still being able to restore broken links, sometimes automatically.
      4. LL4CGT: On each address book contact (as most electronic address books hide the internal ID) to track the contact
      5. LL4CXY: On each http://eTag.JotHere.com (JotHere’s standard for a email address used for portably categorizing/tagging instead of emailing, often given to each address book contact)
      6. LL4BXL: On physical items (as a phone or device) as a kind of serial #, including it’s shorter than most serial #s, and being universal, works well with other uses.
      7. LL4CBJ: Note to make use of IDs, one does NOT need to put an ID on everything (which one may not want to because that takes time & they are unsightly) but note benefits of always & immediately doing.
    8. N49AUP: improvements possible (so under construction) from least to most:
      1. LL45YV: ID-insert macros
        1. O1LF9K: goals from top first :O1LF9K
          1. O1LF9V: can insert at cursor-selection not just replace-whole-field :O1LF9V
          2. O1LFDE: can insert WYSIWYG HTML not just raw text :O1LFDE
          3. O1LF9O: robust
          4. O1LFAR: cross-platform (else it has to be rewritten for each platform) :O1LFAR
          5. O1LFC5: coded in JavaScript :O1LFC5
        2. O1LF7L: via AutoHotkey
          1. O1LFCK: achieves ‘goals from top first :O1LF9K’ except
            1. O1LFCZ: so far seems to fail ‘can insert WYSIWYG HTML not just raw text :O1LFDE
            2. O1LFH5: fails {O1LFAR & ‘coded in JavaScript :O1LFC5’}
        3. O1LFTL: via Bookmarklet
          1. O1LFWG: achieves ‘goals from top first :O1LF9K’ except
            1. O1LFXL: unsure if ‘can insert at cursor-selection not just replace-whole-field :O1LF9V
              1. O1LGEX: https://www.google.com/search?q=javascript+insert+at+cursor has answer possibilities
      2. LL45WH: the ID generator noting who created each ID where & how
        1. N49JCA: a 1st pass solution is in use: MVGADL=the Other.ID sheet of a Google Drive Spreadsheet
      3. LL463I: Better ways to display & hide the IDs so they are not so unsightly.
        1. N49JJZ: always being worked on per the motivation.
    9. N48Z4C: Very bad: with more than say 100 people simultaneously generating them, IDs will notably not be unique and start colliding (same different items wrongly having same ID)
    10. N48Z29: Killer: in a few years will run out of IDs or else IDs will have to become longer, with no prep in this design for that.
      1. N49IE7: So replacement system in the works.
  6. N49CHW: Aesthetics

    1. N49CM1: of IDed items
      1. N49GTP: is done as much as possible, but NOT so much to where (as many/most people would do) killing the other benefits notably the 1st pro
        1. N48NB9: Specifically every know effort is made to make these IDs hidden for when they are in the way,
      2. N49CMX: of IDed text
        1. N4B0HF: Here the highest & enormous effort go into aesthetics ID hiding
          1. N48NBQ: The limit is almost always the writing format options.
            1. N4AZHF: On one end of the spectrum, full HTML allows the codes to floated to the right (out of the way), plus made small, plus even be a hyperlink to itself (great for bookmarking), and of course supports arbitrary depth outlines –as this article is presently formatted.
            2. N4AZMJ: on the other end of the spectrum, Meetup event listings after ~2013 have had a serious downgrade (to be displayable on mobile phones: honest need but seemingly a terrible fix) so cannot do any floating, indenting, sizing, or even coloring, so in this case, codes & sectioning look like {N4AZQQ=body} as the official description in this real example: ugly enough that the group owner would not allow them –so then per standard we simply did no more free writing of events for him.
          2. N48NFU: But this is not enough for some maybe most folks, especially& ironically often programmers
        2. N49ERU: naturally a huge concern, indeed the #1 by far and for-most killer criticism of this solution, as both:
          1. N49EUA: most text doesn’t have any unique markers in it and when it does it’s almost-always just very-locally unique (as “(1)” or “(a)”) so very short.
          2. N49EXC: humans apparently have a low tolerance of having their natural-language text altered with new unrecognized words and especially codes.
            1. N49F0V: at least virtually all Americans I’ve seen
              1. N49F31: but in other countries where the mixing of natural languages is common, I hypothesize may be more tolerance, though maybe just a little.
              2. N49F47: especially by typical programmers
                1. N49F64: IMHO, ironically & tragically & hypocritically
                2. N49FK9: IMHO, apparently because of the combo:
                  1. N49FAV: they are very sensitive to symbolism –good
                  2. N49FNG: languages for computers can be varied & experimented with in all sorts of ways to find something better –excellent
                  3. N49FO6: languages for humans cannot be touched –bad!
                    1. N49G1Q: Why?
                      1. N49G2Y: Because they hated English class, so writing it is bad enough, so the idea of further developing it is abhorrent –?
                      2. N49G4E: Overall I’m pretty clueless
                  4. N49FBG: they are all about learning & using and even inventing languages that are
                    1. N49FD4: more precise than English for a lot of useful things –excellent
                    2. N49FE0: are as close as possible to English even when English has problems –bad, they are excessive here
                      1. N49FZJ: notably including problems they passionately hate in computer code: needless ambiguity & repetition, and where there’s no apparent chance of any program automatically fixing this.
                      2. N49GHA: –it’s as they think English is “God” aka righteous perfection itself (so which should not be questioned, so any variation is blasphemy), even though (in other mindsets) they typically know that’s not true.
                      3. N49G5I: Why?
                        1. N49G68: Currently I’m still pretty clueless.
                      4. N49GF2: especially ironic & tragic when
                        1. N49GC3: they want computers understand the ideas in our heads of English –excellent
        3. LXJXH1=(making IDs & outlining nearly-disappear into the background, as humans much prefer it displayed, while still enabling it to be found when-needed by humans & machine-search) is
          1. LXJY8A=still under regular development (see Could the presentation of this info be improved?)
          2. LXJY8U=very-difficult or impossible on nearly all Web 2.0 sites due their stripping of formatting by HTML & CSS & JavaScript.
  7. MJO3C1: Making a reference to text which is labeled with an ID

    1. MJO3D8: Does the text have an <a id=”..”> tag?
      1. MJO3EM: Yes
        1. MJO3FB: –the typical & ideal case.
        2. MJO3FG: Use href form “<url/>#<id/>”
          1. MJO8YY: Real example: http://1.JotHere.com/401#MJO8YY to link to this point –though it can be improved, read on:
          2. N4B8BV: the “&N46Ref=” URL variable setting
            1. N4B8MG: especially useful to track what links people click on, especially in advertisements.
            2. N4B8D2: Ideally include this in links to IDs and in all important URLs.
            3. N4B8F8: is set the unique point in the text which contains the link.
              1. N4B8HF: For example, /401?&N46Ref=N4B8HF#N4B8BV is a link from this line (thus the N46Ref setting) to the start of this section on N46Ref.
              2. N4B9C9: Real example: all the URLs in list of pages & sites using these IDs.
            4. N4B8NM: First use is in this OCPython member email (note from the source code all 3 of its links are with N46Ref: so one can tell if the person clicked on the text description(s) or on the picture, both are linked to similar stuff) and then in the group post it links to, as its internal docs detail starting at its point N46KV0.
      2. MJO3GH: No
        1. MJO3HS: –as were sites trip out the <a id=”..”> as with user-text on Meetup.com
        2. MJO3I2: the MJHref solution
          1. MJO3LR: Usage: http://1.JotHere.com/MJHref?q=”<id/>”(+<keyword/>)*
            1. MJO88I: MJO89Y: (+<keyword/>)*
              1. MJO8CJ: needed when <id/> naturally occurs elsewhere for something which is not the intended target
                1. MJO8CU: which happens fairly routinely as IDs are fairly short (currently just 6 characters).
              2. MJO8CX: each should be a word that occurs within the target text:
                1. MJO8GH: within say 50 characters of <id/>
                2. MJO8HE: always and literally, except a variance the search engine would correct for as possibly word ending as “attending” vs. “attendance”.
            2. MJO6HU: Originally: http://1.JotHere.com/MJHref?q=<id/>(+<keyword/>)*
              1. MJO6JO: but now found http://1.JotHere.com/MJHref?q=LTDSHF+Meetup returning quote(Showing results for LTD SF Meetup<br/>Search instead for LTDSHF Meetup); but http://1.JotHere.com/MJHref?q=”LTDSHF”+Meetup works, as used in real example.
          2. MJO41Q: Pros thru cons:
            1. MJO3V0: HUGE PRO: will not break even if the text is moved onto another of a different website.
            2. MJO92O: Very notable PRO: allows click tracking.
            3. MJO94F: Very notable Pro: could be used to do ad display on every click
            4. MJO3WV: Notable PRO: Supports multiple copies of the destination text: finds all instances provided only the text is found via public Google Search.
            5. MJO6TR: Tiny con: should be tested in an Incognito Window to simulate what other will see as Google search guesses what you the author want so will be more accurate
              1. MJO6W0: Example case: for LTDSHF+Meetup it will guess you mean “LTDSHF”+Meetup
            6. MJO406: Usually tiny CON: Seems to require ~1 day for newly appearing text (be it copied or moved or created again) to get indexed so found.
            7. MJO69Q: Small con: often requires including a keyword which won’t change.
            8. MJO3TK: CON: Initially & currently works just for IDs on the public web.
            9. MJO62Z: BIG CON: often the most recent version is not obvious & not returned first
              1. MJO664: For text on repeating event listings, indeed they have multiple versions.
            10. MJO987: Fairly Huge Con: user may find the indirection (1 or 2 additional page displays and time wait for that) very annoying
              1. MJO98I: Most especially for any link to a target on the same page: now instead of taking ~1/4 sec to scroll the page it now could take maybe ~20 seconds for 2 page loads, just to bring him/her back to the same page just in a different spot, and the user will likely be somewhat disoriented as not realizing (and not to easy to quickly tell) that indeed this is the same page.
            11. MJO62F: HUGE CON: getting to the particular text/tagged-item is tricky as while the search engine usually lists the start of the matching text, the user still needs to know to & copy (into clipboard) the ID then click on the link then page-search for it on that page, which many/most will not know to do.
          3. MJGPXPL: first implemented by this Pretty-link redirecting to https://www.google.com/search for 1st use at use on http://meetup.com/OCAndroid/events/106978332
          4. MJO8KY: Pretty-link “Parameter Forwarding Enabled” must be turned on.
          5. MJO8OU: via https://www.google.com/search
            1. MJO8PL: the “https” rather than http seems to be what the browser’s address bar web search seems to prefer & indeed add security for at little cost for this small amount of encryption.
            2. MJO8RQ: the “www.” is optional but what the query redirects to so saves the time of doing this replacement.
          6. MJO8T4: searching for the “:” in the target, as “<id/>:”
            1. MJO8UJ: via Google Search
              1. MJO8US: so far has seemed impossible from my tests.
    2. N14EKP: section history in REVERSE order:
      1. N49CDG: title: renamed from q(MJO3C1 Linking text which is labeled with an ID) to present for noted clarity plus general coverage.
      2. N14EL2: other prior exists
      3. N14ELC: q((14 March, 2013 @ 15:45:48) [Autosave] ) has this section deleted; but GS for the section ID doesn’t find it elsewhere; so restored it.
  8. N14G06: Assigning the ID of something, so including: adding an ID to an item aka augmenting the item with an ID

    1. N49CXN: by definition this only applies to ID authors which for this version are very few & restricted, so I list it last.
    2. N4AT8C: Generating an ID
      1. N4AT8S: The algorithm
        1. N4ATMY: is only very mildly clever; others could come up with it.
          1. N4ATSG: rather the real cleverness here to do the honorable task, specifically to think of & even do the logical even doing so would at be considered taboo for as long as one can see: yes generating unique short portable IDs is clever, but real clever (or insane) is using them everywhere despite the enormous social backlash.
        2. N4AU60: is very easy to code & highly portable.
        3. N4AT9V: is NOT scalable and indeed per that if used by more than a few would apparently increasingly fail for everyone (who puts their IDs public which seems like most every user)
        4. N4ATMI: so, notably due to #N4AT9V, is not to be disclosed until the replacement system is established.
      2. N4AU8O: I have built generators:
        1. N4AUC2: currently all non-publically accessible per #N4ATMI.
        2. N4AU9Y: A web page full of text templates for authoring points such as the points on this page plus computer code with IDs.
        3. N4AUUJ: a generator in AutoHotkey.
        4. N4AUU6: 1 or 2 generators in Bash shell script.
        5. N4AUIS: a spreadsheet-template spreadsheet MDRIB0 (used to make 10s of other spreadsheets) which automatically generates a creation & last-mod ID for every cell’s row & column.
        6. N4AUEU: a spreadsheet where the ID’s author & other background detail can also be recorded.
        7. N4AUSZ: more planned.
    3. N14G86: Assigning the ID of every (else a) portion of text
      1. LXJXTT=to build the tools (the software) to generally enable such augmented text is inherently very hard!
        1. LXJYCD=may appear easy (just insert IDs into text) but is much more complex
        2. LXJYD7=involves
          1. LXJYDR=balancing the needs for machine & human parsing & understanding, something only recently being done with microformats.
          2. LXJYDI=subtle, comprehensive, & integrated modifications of the whole text-processing process: in editing, display, storage, linking, & indexing
          3. LXJYKG=testing & supporting a variety of existing popular publishing platforms, notably Web 2.0 sites, so to be generally useful.
          4. LXJYEL=selling humans on a notably different way of writing & composing & authoring.
      2. N14GEP: with HTML text
        1. N4AUYZ: This section so far written just for internal use so may be hard to understand.
        2. N14G10: formats class=”aself_KEP2FG” & class=”aself_KENC7Z”
          1. N14GFD: Highest use of any; probably 100K instances.
          2. N14G91: Example: <sup><a id=”N14G91″ class=”aself_KEP2FG”>N14G91</a>:</sup> &nbsp;
          3. N14G9Y: Example: <sup><a id=”N14G9Y” class=”aself_KENC7Z” href=”#N14G9Y”>N14G9Y</a>:</sup> &nbsp;
          4. N14G2X: repair
            1. N14G3U: Several WYSWYG editors via JavaScript, including the one used by WordPress, corrupt these
            2. N14GD6: in MS Expression Web
              1. N14GGJ: regex N14GGJ: Recent regular expression to fix ID:
                1. N14GH3: Works exceptionally well. Initial use 4250#N0T6VV; subsequent uses in the articles referenced by the sources here.
                2. N14GHK: Required options: Match case, Regular Expressions, Find in source code
                3. N14GIY: from ‘(:b|\n| |&nbsp;)*<sup>(~(<sup)(KENC7Z|KEP2FG|[^0-9A-Z]))@{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}(~(<sup)(KENC7Z|KEP2FG|//[A-Za-z0-9.\-/]+/KM37RH/KEUBLL\(html_\)/templates_with_Ids_LJKDDO\.htm|\1|[^0-9A-Z]))@</sup>((:b|\n| |&nbsp;)|\:+(:b|\n| |&nbsp;))*’ –hidden characters lost so best to use #NWZ4JV

                  N14GKL: section history in REVERSE order:

                  1. NWZ1EI: present value
                    1. NWZ1RL: better whitespace matching with :b
                    2. NWZ1RY: fix #NWZ13Z: wider matching including could falsely match ‘ :blah’ but that seems rare.
                    3. NWZ2Z0: character of #NWZ1DI is not preserved so
                      1. NWZ30L: save query as file NWZ30L.fpq
                        1. NWZ394: loading fails with ‘Microsoft Expression Web<br/>Failed to load query from: <path/>. Either the file doesn’t exist or it contains invalid content.<br/>OK’
                          1. NWZ3CO: moving file to & loading from Downloads\ doesn’t change.
                          2. NWZ3DE: conclude its an ExWeb bug perhaps due to the special character.
                            1. NWZ4JC: but the character is saved as “&nbsp;” and replacing it with the representation doesn’t fix this problem.
                      2. NWZ4JV: save the from pattern as NWZ4JV.txt –restorable
                  2. N14HJ2: from 87#N10WEX: update to handle new WP-editor-corruption forms here as q(..M7A5Z2</a></sup> : Seemingly): ‘( | |&nbsp;)*<sup>(~(<sup)(KENC7Z|KEP2FG|[^0-9A-Z]))@{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}(~(<sup)(KENC7Z|KEP2FG|//[A-Za-z0-9.\-/]+/KM37RH/KEUBLL\(html_\)/templates_with_Ids_LJKDDO\.htm|\1|[^0-9A-Z]))@</sup>( | |&nbsp;|\:+( | |&nbsp;))*
                    1. NWZ13Z: the new ending ‘( | |&nbsp;|\:+( | |&nbsp;))*’ has not been matching
                    2. NWZ1DI: note the ending character in ‘’ is not a space.
                  3. N14GTN: from 4250#N0W1HQ: was Update to also handle q( class=”aself_KEP2FG”): q(( | |&nbsp;)*<sup>(~(<sup)(KENC7Z|KEP2FG|[^0-9A-Z]))@{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}(~(<sup)(KENC7Z|KEP2FG|//[A-Za-z0-9.\-/]+/KM37RH/KEUBLL\(html_\)/templates_with_Ids_LJKDDO\.htm|\1|[^0-9A-Z]))@</sup>( | |&nbsp;)*)
                  4. N14GQJ: from 4250#N0W1M5: [updated in child] from(( | |&nbsp;)*<sup>(~(<sup)(KENC7Z|[^0-9A-Z]))@{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}(~(<sup)(KENC7Z|//[A-Za-z0-9.\-/]+/KM37RH/KEUBLL\(html_\)/templates_with_Ids_LJKDDO\.htm|\1|[^0-9A-Z]))@</sup>( | |&nbsp;)*)
                4. O6JJ8V: To, anew::
                  1. O6JJ9H: ‘<sup><a class=”KENC7Z” id=”\1″ href=”#\1″>\1</a>: </sup>’
                  2. N14GJ8: ‘<sup><a class=”aself_KENC7Z” id=”\1″ href=”#\1″>\1</a></sup> ’(includes attributes sorted into WordPress preferred order)
                  3. N14GNR: section history in REVERSE order:

                    1. N14GXJ: moved here from 4250#N0W1ML
              2. N14H2O: bad ID marking, based on regex N0T3FD

                N14H37: section history in REVERSE order:

                1. N14H3H: moved here from 4250#N0W1ML
                1. N0WA0U: from({<sup>((KENC7Z|KEP2FG|[^0-9A-Z]))@{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}}{(~(<sup)(KENC7Z|KEP2FG|//[A-Za-z0-9.\-/]+/KM37RH/KEUBLL\(html_\)/templates_with_Ids_LJKDDO\.htm|~(\2)[0-9A-Z]|[^0-9A-Z]))@</sup>}) BUT
                  1. N0WAXT: q(~(\2)) seems to be ignored}
                    1. N0WB15: undocumented but not surprising since \2 represents a dynamic pattern
                    2. N0WB1C: so some(seemingly all) valid patterns are matched
                  2. N0WB2E: can think (so probably aren’t) any valid From patterns: conclude will require a more powerful Regex environment as JavaScript.
                2. N14HB9: (formerly at 3374#N0WBUQ) Workaround (which works but very slow): manually step thru (“Find Next”) regex N0T3FD on a big screen spotting for any skipped.
              3. N1ZZ1G: Regex replace N1ZZ1G: to convert a non-standard pattern
                1. N1ZZ36: same as regex N14GGJ except as noted
                2. N1ZZ3Z: from q(( | |&nbsp;)*{[0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z][0-9A-Z]}(\:|=)( | |&nbsp;)*)
                3. N1ZZ4J: Must be manually applied
    4. N49D7Y: section history in REVERSE order:
      1. N49D6Q: title: renamed from q(N14G06 Declaring something has an ID) to present more precision
      2. N49D5Z: other prior exists
  9. MAXDSI: WHO’S PARTICIPATING

    1. N48YUV: by version in reverse chronological order
      1. N48ZAK: next version (compared to this one)
        1. N49BFZ: entirely my invention so far
        2. N49AO8: based-on and taking-all-that-can-be-learned-from the prior version.
        3. N49ANR: identical goals (except as noted) but higher, notably fixing the biggest shortcomings (are found in pros-thru-cons/a>), including:
          1. LXJX8Q=to be released ASAP for general public use (so anyone can make & include their own IDs)
            1. LL45S7: So everyone can author with these IDs, The web page & macros I’ve built to generate & insert IDs I plan to release to the general public,
              1. LL45VM: –after refinement is complete, including
                1. LL45X2: a code system which is more scale-able (current system would only support a thousand people w/o ID conflicts).
                2. N49AZ9: fixes to the previous system
      2. N48YVF:  this version :N48YVF
        1. LL41TX: entirely my invention, based on my prior versions which started around 2004..
        2. LL47QH: I and only a few other alpha-testers have been heavily using them on most everything, including most all our writings per the 1st pro, since invented 2009.01.01
          1. N49HCD: Very honorably IMHO, I and most of these other alpha-testers insist on using these IDs throughout all their writings (both natural language (as English) and computer code, per the 1st pro) even despite the huge backlash –at least for any writing which they do unpaid (as all their internal writings of course; plus their writings to friends & associates plus even community & professional groups, yes despite the huge backlash) as that then is the “price” of getting this writing work for free: ironically that the authors are allowed to pioneer an ideally much better systems of communication for everybody.
          2. N4B79W: Used throughout this website 1.JotHere.com (about) -hundreds pages including of course this page; and used heavily for event listings & discussions on many community groups including Meetup.com/OCAndroid (event example)+see “About us” , Meetup.com/OCPython (event example)+(discussion example), some Meetup.com/Node-JS-OC (event example), Meetup.com/OC-Polyamory (event example)+see “About us”, parts of Meetup.com/AsianFriendster (event example); plus used on 100% of website http://LoveRules-Info.Blogspot.com; and used to id & mod-stamp rows & columns & cells on a 10s of spreadsheets including fun one Show & Food ratings.
          3. N48N14: Writes one alpha-testers, “I use IDs very powerfully in most all my writings include despite the social backlash, including since, just as it’s designed, it dramatically helps writing be precise & compact including with potentially near zero repetition. Hopefully eventually others will catch on and see beyond the superficial immediate bad to the much greater long-term good.”
          4. N48N4F: Those fortunate enough to be able to work with one of our alpha-testers and recommended by him/her might then be lucky enough to join us as an alpha-tester, too.
        3. LXJXBY=in alpha-test of the 1st release, including
          1. LXJXOH=This stage will & is taking up to 10 years, due to (my part-time effort on it from no funding) and the inherent difficulty LXJXTT..
        4. N48YX6: not ever to be released to over ~100 people due to #N48Z4C
        5. N48Z8I: due to other bads especially N48Z29, to replaced by a better system as soon as that is available & reliable and so phased out..
      3. N499WK: prior versions (compared to this one)
        1. LL41UX: entirely my invention, starting around 2004, with similar goals
          1. N49AGD: I used each myself mildly & mostly internally.
          2. N49AGX: As I recall, I never publicized them nor documented-them-for others as I wasn’t doing much publishing and they were long & bulky.
        2. N49A45: all less-compact formats
          1. N499YV: last was a longer form of ~13-characters
    2. OSF453:  key inventor/designer(s) :OSF453
      1. OSF8B4:  identity
        1. OSF875:  is so far being kept private per OSF59C, including
          1. OSF8IB:  don’t assume the ‘key inventor/designer(s) :OSF453’ are any of the author(s) of {this document or the code which generates & processes the IDs}
        2. OSF4JB:  (their identity) they properly desire to keep private until their system is in notably wider use :OSF4JB
          1. OSF58K:  …especially to keep their identity withheld from at least {content which is has reasonable potential to be widely available such this and other web posts}
          2. OSF7CD:  Why? The need…
            1. OSF7D9:  is complex to explain & appreciate :OSF7D9
            2. OSF4JM:  is: as otherwise content using these IDs reasonably suggests, possibly strongly, it be created and/or edited by the IDs’ ‘key inventor/designer(s) :OSF453’ even though suggesting/saying that is improper if 1 or more, from most common 1st:
              1. OSF4U3:  they appropriately should not have their identity revealed there –a very common need when we need to hear something we’re not, so when we need the content to be honest when that’s hard
                1. OSF6EC:  notably honest even when there is fair chance the viewer will act inappropriately to it, as say when 1 or more: {viewers may act vindictively or at least not impartially} and/or {the sentiment is so off-putting it clouds good judgement, often because over ~85% of the species instinctively dislike it} and/or {the sentiment is culturally considered improper express this directly})
                2. OSF727:  as fortunately inventor(s) value {righting the wrongs in our word including even the controversial ones and where they have to do it} above {their own fame from inventing even something great as this}
              2. OSF4U9:   the content is actually not by them but notably by someone trying to pretend-to-be/impersonate them  –this situation hasn’t come up yet that we’ve seen; but as the IDs are easily faked especially by a coder, it’s still quite possible.
          3. OSF59C:  so this privacy request has always been done, as it should be :OSF59C
            1. OSF6XG:  including by those closely involved by….
              1. OSF5CE:  until now by not-saying and/or mislead since ‘the need is complex to explain & appreciate :OSF7D9
              2. OSF47A:  now by {this explicit statement OSF4JB including its trying to explain it} despite that ‘the need is complex to explain & appreciate :OSF7D9