Mar 192011

LI5ANZ:  :

  1. LI70DG: coming soon!
    Host your writings here for free!



    Got a thought?
    Jot it here! ™
    Be it something public you want to share to the world,
    or (soon) something private you want to share with a few or just for you,
    Jot it here! ™
    Get published any writings just sitting in your computer or in your email:
    Jot it here! ™LHBPCZ: SCALE9x friends, Welcome! Here’s under-construction real JotHere content.

    LHBPKA: So what’s (Features & Uniqueness)

      1. LHCNIW: In short, it’s free web publishing for much (& ideally all) of your writings –whatever the topic, Jot it here! ™, and
        also published

          1. LHD7VV: easily, including WYSIWYG and soon auto-accounts
          2. LHD7W6: with maximal flexibility, extensibility, and export & portability, including top open source open standards: all XHTML, your own CSS & JavaScript, pick from 1000s of plugins, and in WordPress,
          3. LHD8VW: with great short URLs, indeed easily a URL even to every individual point you make (my invention)
          4. LHD7WJ: collaboratively if you want: it’s a wiki with full edit differencing and without the edit wars
          5. LHD95K: with unified top blogging one seriously via WordPress
          6. LHD7WV: with versioning & differencing of changes and
          7. LHD7X6: with serious, versioned backup,
          8. LHD84F: with increasing other features (see over 20 features listed below),

        and all

          1. LHD84W: without the trouble of finding else designing & hosting your solution for this yourself (designing & hosting a blog, wiki, or CMS, which, even for the best ones, is notable work, especially when you want to do it well).

        right now a solution for you which no other leading website offers.

      1. LHCVZ0: Per its name “Jot here!”, solves, else aims to solve, the problem of “I’ve got this existing writing, or idea or thing I’d like to write about, but I don’t know where to put it.” Jot it here! ™
        As all other leading solutions don’t really work well:

        1. LHD0C3: Storing it on one’s computer or private files is certainly doable (I’ve done mostly that) but often has killer results.
          1. LHD0E0: The work ends up never getting out to the world, not even shared with anyone.
          2. LHD0EW: The work is not in a format ready for publication, and it often would take some serious work & planning to make it ready.
          3. LHD0G2: The work is not properly indexed & categorized & backed up, and so gets lost, often forever.
        2. LHCZGI: Email is always a tempting for putting most any writing but frequently causers all sorts of problems.
          1. LHCZZN: Yes one can always put it in an email message, and with full HTML email (as Gmail offers) that’s a pretty good format for just 1 draft, but then once you’ve sent it out:
          2. LHCZIT: it’s hard to update (without overloading readers, & possibly yourself, with “another update”),
          3. LHCZLQ: you can’t take it back
          4. LHCZNB: you can overload people with more details than they want in their inbox right now: “Why’d you send me this long message?!”
          5. LHCZQ0: It likely doesn’t get out to all the people who could appreciate it if they knew of it when the time was right.
          6. LHCZOQ: it’s typically hard to categorize each piece of writing sent this way, yet
          7. LHCZT5: it burdens every recipient, and typically right now, to store it, and organize it else loose it, or to delete it.
          8. LHCZS4: No one can find it via web search.
          9. LHD048: And one’s writing typically ends up just getting lost & forgotten in the inbox and eventually deleted.
        3. LHCW5X: So one may think get “get a blog or website”, and this definitely is a great direction, but even professional bloggers & web writers with several websites & blogs still have this problem (of where to put much of the writing & ideas which comes along), because
          1. LHCWMR: the writing doesn’t/wouldn’t fit the topic & sensitivity of any website one has or is set-up to use and/or would get lost there, throw off the topic there, and not get properly appreciated there.
          2. LHCWOG: and if one went to the trouble to find some website or blog where this writing would fit, then typically that’s a LOT of work, as there:
            1. LHCZ14: one have to create yet another login/handle and frequently a profile & identity (pic, bio, etc.), and
            2. LHCZ1K: learn their site and
            3. LHCZ4B: typically learn their formatting codes as frequently there’s no WYSIWYG, and
            4. LHCZ2K: store one’s writing in their probably non-standard, non-portable text format, and
            5. LHCZA1: risk one’s writing there being deleted and parts lost if it got edited
              1. LHCZBZ: so one really also should figure out how to maintain backups of it, and do backups, too,
            6. LHCZD7: all typically for just this one piece of writing or for just a few pieces (because the topics of many other things you deal with almost certainly won’t fit there!), and
            7. LHCZDQ: still almost certainly never get paid for your writing, nor for all this additional work you had to do to put it there,
          3. LHD14W: so pretty much the only thing this does guarantee is the actual web writer & reviewer is typically
            1. LHD1CO: burdened with
              1. LHD1F9: many websites to learn and many logins & profiles to maintain,
              2. LHD1DB: plus possibly several of his/her own websites/blogs to setup & maintain

              –pretty much for every different topic s/he has thoughts on

            2. LHD1GU: Or often just doesn’t get their writings & thoughts out there, due to all this trouble.
        4. LHCWLS: Well,
          1. LHCWHD: rather than find-else-create yet another website/blog else another login & profile (and really set up & maintain them), and
          2. LHD0UB: and rather than mostly loosing writing by committing it to email,
          3. LHCWHN: and rather than just writing it but then never getting it out to the world,
          4. LHCWIM: and definitely rather than just then not writing it,
          5. LHCWUR: Jot it here! ™
        5. LHCXOB: Indeed, today there’s no other leading any-topic website which offers what JotHere does:
          1. LHCYO0: today there are only a few leading websites which allow the average user to cover most any topic (Wikipedia, Facebook,, Google Docs, plus group sites (as Google Groups) IF a group thing) and
          2. LHCYRB: these ones all have notable-if-not-painful drawbacks, as none provides these many other essential features which JotHere provides.
      2. LH5PM5: Unlike most big Web 2.0 sites today (including Wikipedia), all writing (pages, posts, & comments) is in XHTML (maximally powerful & portable), plus it’s WYSIWYG, so
        1. LHCSTZ: no yucky BBCode & Wiki markup to have to learn & port & hand-code everything in.
        2. LHCSYI: It’s WYSIWYG most of the time,
          1. LHD5SL: It’s WYSIWYG for all posts & pages (main writing) and soon comments, too.
          2. LHD5XH: so you see immediately on your screen what your published content will look like (exactly else pretty close) as you create & edit it.
          3. LHCTR7: Without WYSIWYG (as on most any site which uses Wiki markup (as most wikis do) & BBCode (as most web forms & discussion boards), you have to learn & write in a bunch of codes (hand-code) which is awkward & relatively-slow even for someone who well-knows the codes.
        3. LHCTB1: All text is in XHTML
          1. LHD5W7: All text (all pages, posts, & comments) is in XHTML
          2. LHD5XZ: so your text is maximally powerful & portable as
            1. LHD5ZY: HTML is the most popular text format on the planet, and
            2. LHD61K: XHTML is the most clean & extensible version of it (as a proper subset of XML),
            3. LHD61S: all 3 have been carefully researched & designed by a scholarly & commercial world-recognized IT consortium (
          3. LHCTRG:Very unlike BBCode (used on most web forums & discussion boards) & Wiki markup (used on most wikis) which is mostly crap:
            1. LHCTSV: much-less standard (every wiki & every forum/board has a different variant & there’s no official standard for either)
            2. LHCV06: so haphazardly designed that is very hard or impossible to get WYSIWYG editors for it.
            3. LHCTSL: much-less portable, do its poor standards
              1. LHCV91: indeed, portability is so bad, the general user can’t even copy-nor-move formatted text to another location within the same site! —unless one has WYSIWYG entry (very rare) or has access to the underlying code (which usually is on the case if s/he wrote it) and wants to drop-into-code to get it, or one is willing to do one all the work to manually rebuild the formatting, which overall means it doesn’t get done.
            4. LHCTUZ: Were mostly only invented as a quick hack (as a quick way to fix the lack of WYSIWYG editors in a web browser, but now these are everywhere & free)
            5. LHCU16: are dramatically-less powerful (as no truly-rich formatting, and no CSS, and no JavaScript typically; indeed typically extensibility was never even part of their design).
        4. LHCSV6: Together, if you want to copy some web text (or any HTML) including quoting a web page, here you just copy & paste in WYSIWYG with no or minimal editing.
          1. LHCU7E: –quite unlike BBCode & Wiki markup, where one has to manually recode all the internal formatting in the question (as links, indenting, nesting, quoting, bolding, italics, etc.), which is so much work it typically means the formatting is just stripped out and one just hopes it’s still okay (including not loosing key links if one forgets to reinsert them, which often happens).
      3. LH5PO4: Format your text your way, & most powerfully: add your own CSS & JavaScript and with minimal restrictions
        1. LHD65R: CSS & JavaScript provide enormous power
        2. LHD661: Nearly impossible to find on most Web 2.0 sites unless sometimes if create & host one yourself.
      4. LH5R45: Built-in shared categories, which you can also extend, to help you get your thoughts & text really organized, plus collaborate.
        1. LHCRNZ: also in the not too-distant future, versioning & perhaps-differencing of categories & categorization.
      5. LF2FXT: Unlike Wikipedia and many Web 2.0 sites, soon support for private content so truly enabling one to put all one’s writings here, including:
        1. LHD501: changing-one-mind on access (dynamically adjust who can access),
      6. LH5PL3: It’s a wiki:
        1. LHD7PA: every post is a wiki page, with an infinite edit log and differencing between an two versions.
        2. LHD7OG: so you don’t have to write it alone AND can get the most-quality content (collective intelligence), including:
          1. LH5UBY: everyone can help edit if you want, or just a few, or just you: here, it’s up to you (you can undo any change to text), and
          2. LH5UA0: automatic versioning and a complete history of edits with differencing, telling exactly who changed what when.
      7. LH5PQT: A wiki without the edit wars:
        1. LHD8SW: Ability for any number of people to combine their efforts (collective intelligence) but still write on the same topic in each in their own way –no big deletion fights & edit wars (as because “there is only one way to write on something” (!) or because “yours is not in the right format” or “it’s not notable enough to be put here” ) as dominates Wikipedia authoring.
        2. LHD8SM: Unlike Wikipedia, in fact no other website I’ve seen has this solution.
        3. LHD8TO: How this is done? We’ll be detailing that shortly.
      8. LH5RS7: unified top blogging, too!
        1. Don’t think “just wiki” as each wiki page can also be a blog post:
        2. LHBVL1: best called “a wiki post” including
        3. LHBVLE: each wiki post can also have:
          1. LH5S3O: a publication date (for journaling)
          2. LHBVDF: categories/tags (for organizing)
          3. LH5S2K: threaded comments posted by readers & authors, plus
          4. LHBVMR: each participant can individually subscribe/follow to get notified of updates.
        4. LHD990: And serious blogging: not just a toy-blogging add-on to some wiki; no, this blogging is done via WordPress, the leading favorite among serious bloggers and also a mini-CMS.
      9. LHCQNZ: Great URLs for your writing: URLs that
        1. LHCQQC: are short URLs (good for increasingly popular Twitter & SMS & greets & status updates)
        2. LHCQYK: can be redirected to another location
        3. LHCQR0: mostly don’t ever need to be changed-on-users & resent-out-to-users (for instance, when a URL went to the wrong location or included a misspelling or the wrong category or some confidential info)
        4. LHCQS6: (my invention) can easily include permanent links to every item you write, even to your individual sentences, points, phrases, rows & columns if you want (example: “LHCQS6” links to this very point), a feature unique to us.
        5. LHDAEP: See also our doc on the well-designed URL.
      10. LHD1R4: Provides, else aims to provide, versioning & differencing of all data.
        1. LHD1SA: Unlike most every leading website site except wikis and now most of WordPress with its version 3.0.
        2. LHD4F1: full versioning & differencing of post content & title. Every version published & every draft explicitly-saved, plus the last auto-save (which happens about every minute) is kept, along with the date & user who did it when, and any two saves can be differenced.
        3. LHD4LJ: soon, versioning & differencing of comments.
        4. LHD4M8: in the not too-distant future, versioning & perhaps-differencing of categories & categorization.
      11. LHDAM6: Serious, versioned backup.
        1. LHDAPO: in case something happens which messes up the site, our administrators could hopefully recover it.
        2. LHDAY8: For the website’s code, attachments, and database.
          1. LHDAML: Currently we already do daily snapshot backups for the last 7 days. But this definitely is not enough for us.
          2. LHDAR2: We’re planning to soon start using WordPress backup service
            1. LHDAWU: provided by 3rd party (not the same storage location nor company as the where the main site is hosted) for additional insurance that the data can’t be lost.
          3. LHDATJ: And we’re planning to do infinite backup versions, plus the ability to difference any two versions, via a DVCS as Git, Bazaar or Mercurial.
        3. LHDB9L: Our upcoming doc “Backup & especially versioning of WordPress” has more.
      12. LHDEV1: A general-purpose, simple, clean universal site theme
        1. LHDE8H: Because the site can have content on any topic.
        2. LHDEXB: Similar to Wikipedia’s theme (as Wikipedia also can cover any topic) but a little less formal (since JotHere can be informal).
        3. LHDF0T: Gives maximum width for content
          1. LHDF1G: As it could, and regularly does, contain tables & diagrams which require much width.
          2. LHDEZC: So only 2 columns (the main content area plus 1 navigation bar);
          3. LHDF4J: Just 1 column (content, with ads and other content injected into it) is being considered to give the content even more width
        4. LF2GS0: Coming soon: built-in support for mobile phone display (now that increasing people are reading websites just from their smartphone)
      13. LHDA1D: Under construction now: ability to create official writing style standards and create, classify, & find all posts meeting those standards.
        1. LHDA61: For instance, one might have a Hemmingway writing standard, or an Wikipedia writing standard; and this document btw conforms to the writing style LGWEB3.
      14. LF2F2Z: Soon, a fun, addictive, live-community feeling & participation via features as News Feeds” (easy sharing of what you’re up to with your associates) & “Who’s online”, similar to Facebook, via say BuddyPress.
      15. LF2FH2: Eventually event listing & group site hosting, for functionality like, Yahoo Groups, BigTent, Facebook Groups, Google Groups, etc.

      16. LF2FAL: Especially in our early stages, the ability to find & suggest plugins (a library of 1000s) and probably get those plugins if they’re good
        1. LHD6MR: Pick from 1000s of plugins, most of them open-source, for nearly everything: ecommerce, chat, picture galleries, music players, and much more.
        2. LHD6KB: unlike say where one’s can typically on get whatever plugins they already have.
      17. LF2F4G: Coming soon: “Everyone already has a login”: to login, everyone can just reuse their OpenID, Google, Facebook, Yahoo, or other login of other leading website.
      18. LHDFV6: Coming soon: Tagging may be disabled
        1. LHDFWE: to instead insure authors use categories which appear strictly more powerful (can have a parent and can be renamed).
      19. LHDFGD: Coming as requested: Ability to search for a Boolean combination of categories.
        1. LHDFIJ: Some support for this is built-in to WordPress 3.1 I’ve read.
        2. LHDFJY: Importance? Well, since the site can have content on any topic, one of the first things a reader might do is filter for just those posts on a particular topic, to emulate the functionality s/he is used to on a normal website which covers just one particular topic. But then of course the reader may want to filter further filter (and search) that just as s/he would on a normal one-topic website.
      20. LHDE5E: Coming as requested: dynamic sub-theming
        1. LHDF7K: To spice up the universal theme which is nice but understandably plain.
        2. LHDF8W: the site theme changes where possible to match the content being displayed.
          1. LHDFAU: Example: romantic content might get a romantic purple/red & white theme.
        3. LHDFCR: Triggered by displaying post(s) in particular categories for which a special theme is defined.
      21. LHCSDN: In the not too distant future, featuring all people who really contributed to a piece of writing, indeed right-next-to the writing.
        1. LHCSJB: –unlike Wikipedia (which hides the names of all the authors: one has to know to click on the “History” tab, and still that’s nothing but a huge edit log where often it would be a lot of work to accurately decipher who the top contributors really were).
      22. LH5Q2A: And, coming eventually (when we’ve got the code to do it) you get paid for your content put here, proportionate to the revenue it brings in. One often puts hard work into one’s content, and we believe the creators & contributors should get paid for that!
        1. LHBWT4:unlike most all of the Web 2.0 sites out there today which don’t pay you a penny for your content, and don’t intend to:
          1. LHBWZO: Facebook, MySpace, thousands of forums, and many others, all keep for themselves all the revenue they earn form your content. In fact your content is typically what gets them most-if-not-all their money, but they keep it all for themselves. Is that fair?
          2. LHBWV6: Wikipedia & don’t pay you anything, either. Yes, they also don’t collect anything for your work (well at least not directly), as they give everybody’s content away for free. But, while that sounds sweet to the world, is that really right? I think not. As I like to say, “If you contribute a little to Wikipedia, you’re nice. If you contribute a lot, you’re broke.”

          LHBXN9: –Forget that! People put hard work into creating good content, so it’s our opinion & goal they should be paid for it wherever possible when others use it.

        2. LHCO97: Alert (something I didn’t know when I started out): expect very little money soon from the ads on your content, even with top notch content, as the web is now packed with content, so, like a book or a magazine or a poem or n script for a play or movie, even if well written, your content will likely need to be marketed so hundreds or thousands of people are reading it before it generates anybody (even us) significant ad revenue.
        3. LHCOJG: BUT, well before it ad revenue becomes significant, you can get your content reviewed & commented by both associates & and the general public, plus share it getting you respect plus speaking engagements & consulting contracts, which can bring very significant money.
      23. LHBPSI: Full support for you & your participants to have multiple pseudonyms & even logins when desired –one can share his/her real/legal name only when & where one desires, indeed (unless good reason) even JotHere does not require a user to tell JotHere her/his exact identity, to allow everyone the ability to feel maximally comfortable to share whatever one wishes and speak up on issues where one feels s/he needs to via the safety of pseudonyms whenever appropriate.
        1. LHBQ5I: –quite unlike Facebook who demands your real/legal name (else will encourage others to report you and will remove you); and despite all their promises of privacy controls so to let you decide to reveal your stuff to someone only if you want to, hypocritically still requires you (else will suspend or delete your account) that you to trust them with what they do with your real/legal name & with your real identity. So should you trust them? Because of this, & quite a bit more, many smart people say they are very limited in terms of what they share on Facebook, and regardless of what Facebook promises as far as privacy controls. So is that the sort of environment where you’d want to put your readers & participants?
      24. LH5Q5G: And a host of other features friendly to writers & readers.
      25. LF2G3J: Plus more features planned in the years ahead, as we move eventually beyond wikis WordPress into semantic web (Web 3.0) hosting including dynamic semantic outlines & powerful comparison table support..

      1. LH5PVC: And based on the WordPress standard. WordPress:
        1. LHD6VG: is the leading favorite among serious bloggers and also a mini-CMS
        2. LHD9CT: is well know to live up to its name and press out words.
        3. LHD6XZ: is open source, and most of its hundreds of themes and thousands of plugins are open-source, too
        4. LHD6YK: significantly insures your valuable content here doesn’t get trapped (as locked into some unknown property platform that may go out of business next year) but rather is in a very-well-proven platform for text on the web, and in one which is principally open-source, and in fact in soon the most popular open-source Web 2.0 text publishing platform on the planet! –see for instance see the latest Google Trends of “WordPress,(Blogger|Blogspot),Joomla,Drupal”: all are now declining, except WordPress, which is now 2nd only to Blogger (generally used by inexperienced bloggers who don’t know better, so just pick the one which is easiest to start and which starts with the name “Blog” –hey, I was one) and now that Blogger’s starting to decline, WordPress may soon be #1.

    1. LHBW0O: And JotHere’s no hypocrite: it’s reflexive & it eats its own dog food:
      1. LHBVSW: JotHere’s biggest first users are the site designers themselves, saying “It’s the publishing site I’ve always wanted!” In fact,
      2. LHBVUA: It’s “internal” documentation (of how the site was & is being created) is published in the site itself, and (pretty much except for passwords & similar) is entirely public.
    2. LHBVS4: So in short, the JotHere is designed to be a no-brainer choice: “Got a thought? Jot it here! ™
    LF2G24: How can we do it for free? Where we aim to make our money? Quite fairly:

    1. LF2FEB: Automatic relevant embedded ads (and where
      you will eventually get a % of the revenue share, unlike Facebook &
      MySpace & many other sites which keep everything for themselves) or
    2. LF2G2V: ad-free if you pay a small hosting fee.
    3. LH5QSP: Eventually enabling you to charge for info where you want (and we just keep a %).

    LH5SKO: Curious? Be sure to comment below with your questions & comments, or email us at .

  2. LI55MY:  Section Past+Future Table (in order)

    LIBHI1:  PREFACE. Like stenotype used in court reporting, the format used in this table is fast-to-write & compact, while still being complete, so requires some instructions to understand it.  LI5GA2:  Each row in this table is stating essentially “(an Attribute (of this section) has/had a particular Value, Starting some time-or-event) for a particular Reason, until Ended-by some event”. LI5H56:  Consequently, current values are the ones for which the “Ender” has no “Actual” doer. LIBHOS:  also see table footnotes.
    LI5D8S: LI5D90: LI5D97: LI5D9O: LI5D9B: LI5D9U:
    ID + Link(s) Attribute Value else Modification-of-value Starting When: Planned & Actual Starting Reason including inspiration & preparation Ender: Planned & Actual
    LF2E8B: LF2E8B 8B source A: “LF2E8B“= 20110115­utc124811 The WordPress of wasn’t up yet so Google sites seemed the next best thing, and could easily have ads A: F2
    LI5CPQ:  PQ source’s content updated 15x. A: Version #1 – Jan 15, 2011 4:48 AM Biggest motivator: “” was advertised by business cards on last day of SCALE9x. A: Version #15 – Mar 1, 2011 2:06 PM
    LI5K9A: title “” A: just after PQ starting; Version #5 – Jan 15, 2011 5:18 AM A: D3.
    LI5CDP:‘s destination cloaked forwarding to (source=8B) A: after v1 in PQ where content is P: 1X.
    LH5QKN: LH5QKN  KN draft source LF2E8B[JotHere_intro]_LH5QKN.htm LH5QKN“= 20110225­utc051447 Too difficult to seriously edit within Google Site’s very limited editor. A: OQ.
    LH5R8P: LH5R8P 8P draft source cut & source discussion LF2E8B[JotHere_intro_cut]_LH5R8P.htm LH5R8P“= 20110225­utc052913 For text cut but may want to use elsewhere, plus discussion of what should go here. P: 2X
    LI5KD3: D3 title “ features” A: just before OQ This is almost entirely what this section so-far is about; it does mention on attributes (as pivot tables) which may only come in say a later but only a sentence and that, too, could end into If this were an “About” page (as former title”, and which is needed), it would need to also cover other attributes, as History, financing, philosophies, possibly founders & motives, etc. P: none.
    LHHJOQ:  OQ draft source 321[1.JotHere.com_features]_LHHJOQ.htm A: now=20110303­utc141714 Too difficult & slow to seriously edit within WordPress’s editor. P: none for now.
    LI5CS9:  S9 http://2.LoveRules.Info/321 entire content of including all prior versions, done according to Method LHHO8F 1st developed for this job. A: v1: 8 March, 2011 @ 3:52 WordPress 2.LoveRules.Info to become else have most/all its content moved there A: v15: 10 March, 2011 @ 1:01
    LI5IF2: F2 source http://2.LoveRules.Info/321 A: end of S9 P: none.
    LI5Q09: source’s content repaired damage done by Google Sites to HTML anchors, notably To aself_KEP2FG -see that, created for this task. A: ~To aself_KEP2FG= 20110310­utc112735 Damage broke all links, but wasn’t so complete that with some cleverness, it was quick to fix. A: just before file of rev 855 =12:01AM, Mar 11, 2011
    LI5RH1: source’s content verified identical: that old KN, which had been posted onto Google Site’s 8B, had been effectively retrieved now in OQ. It had. But had diff XHTML which wasn’t easy with my built-in KDiff3; researched several alternatives, creating article created article diffing XML, and finally did via diff LHUFDO. A: slightly before (when diffing XML = 20110310­utc131219) Being identical simultaneously insures that the export from 8B was complete and that nothing had since been added to KN but not posted. A: diff LHUFDO (20110310­utc131300)+~5min to review.
    LI5DBS: BS this table Created (there was no formal Section History), naming it Section History Table, and creating columns which (after a few hours of testing) I resolved to name as named in v16: ID + Link(s) Attribute Value else Modification-of-value Starting When: Planned & Actual Starting Reason including inspiration & preparation Ender: Planned & Actual. A: now= 20110316­utc110216 Columns inspired mostly by sheet current_LFBLNZ of doc template spreadsheet LF7BGN (except aims to have a single table shared by multiple documents). Use of an inline table plus ID + Link(s), also inspired by post  Word wrap in XHTML which does these frequently, especially in its field Parent(s)‘s thinking of tables including similarly doing references for field “Starting” and “Ended by”. P: updating in V9
    A: new name in YZ.
    LI65AP: source’s content spell-check P: start-~1hr.
    A: now
    Had to do for Section Past+Future Table so hard not to just do all. P: none.
    A: LI65ES
    LI70YZ:  YZ this table‘s name Section Past+Future Table P: now= 20110317­utc083035
    A: now, replacing part of BS.
    See Why change from Section History Table  to Section Past+Future Table. P: none.
    A: none.
    LI5LYZ: v16 source’s content version 16 P: today (20110316)
    A: LIBICX:  (20110319)
    P: some.
    A: none.
    LI5L1X: 1X‘s destination normal redirection to http://2.LoveRules.Info/321 P: right after v16 P: QN.
    LI5LKQ: KQ’s About page being-constructed quotes In short P: soon P: none.
    LI5LQN:  QN‘s destination http://2.LoveRules.Info’s destination P: after KQ P: none.
    LI6ZV9: V9 Section Past+Future Table‘s (column) header names & other structure introduced in this table make proper links to defintions, using format created in relevant dimension attribute table
    of Word wrap in XHTML
    P: possibly after QN.
    A: none.
     Column names & table layout are to be resued so of course should be formally (and externally) defined. Originally started LI669B:    (Section Past+Future Table subsection) “Introduced column headings” to do this but that would be a temporary mesure until this was done, so just do this direct: as own post as Style LI6LOG of (Section Past+Future Table). P: none.
    A: none.
    LI70AJ: feature outline list (So what’s convert to feature table(s), probably unpivoted P: shortly after QN especially to get a clear pic of what to work on.
    A: none.
    Putting it into a table should make it more accessible & better-looking, and perhaps eventually automatable (as “just show me features working now”).  Unpivoted seems key as for any given feature, we’ll only compare it’s presence on a small subset of alternates (to JotHere). P: none.
    A: none.
    LI5Y2X: 2X draft source cut & source discussion some better location for 8P & future content P: sometime after QN 8P is unpublished in its location so a better location should be found as and/or: this table (Section Past+Future Table), a subsection, and/or as a separate post. P: none.
    source’s content (template row; copy & paste it then edit to suit) P:
    P: none.
    A: none.
    1. LI728N:  Why change from Section History Table  to Section Past+Future Table (for this table):
      1. LI72CW:  Because, as demonstrated here in this table, it doesn’t just describe the past/history, it also is capable and does describe the future plans, so the name Section History Table isn’t sufficient.
      2. LI72DH:  Replacing History with Past as Past  , not  History, is the dual of Future and I need Future and I can think of no alternative for  Future which has a dual which is History.
      3. LI72KR:  I do not mention  Present here (with Past+Future), even though it’s often mentioned with Past and Future, as the Present mostly isn’t here (though can be computed from here and sometimes needs to be to avoid restatement, as accessors of this document). But for the most part the rest of the document (not here) is Present.
      4. LI72RM:  I have Past come before Future because that’s the way it’s listed here ((in order)) because that’s also the order in which it happens.
      5. LI72VD:  I write Past+Future instead of say Past & Future or Past and Future, because it’s shortest & intresting looking (stands out, an interesting combo of the two) & looks cool.
    2. LI5TC5:  Re a universal ID, All dates computed from a universal ID in UTC format “YYYYMMDD5­utcHHmmSS”:
      1. LI5UIY:  Example: “now=20110316 164805” if taking the ID used here “LI5TC5“.
      2. LI5UEQ:  specifically computed by JavaScript “LI5TC5”.UTC70s36_date_KCSRMT().UTC2113().
      3. LI5UF9:  Why?
        1. LI5U7S:  To be universal and avoid time zone confusion & computation, indeed the hour offset changes just in the a universal IDs here:.
          >>> “LHHJOQ”.UTC70s36_date_KCSRMT()
          >>> “LI5DBS”.UTC70s36_date_KCSRMT()
        2. LI5U7J:  To save space.
        3. LI5UPD:  starting now (until NW): separate date & time with ” ”
          1. LI65LD:  I am not happy with ” ” but there are almost no other characters that will generally cause a line-wrap and don’t want a date column to get widened more than it already is.
        4. LI65NW:  NW: separate date & time with ­utc (HTML ­utc)
          1. LI65RT:  Pro: adds “utc” (time zone)
          2. LI65SF:  Pro: no-spaces but when needed, breaks neatly (rectangularly) across the line, as here for NW‘s creation.
          3. LI662P:  Con: Tricky to quickly insert the ­ use copy & paste off an existing one.
  3. .
    Copyright © 2011 by with all rights reserved.
  4. LI5AIR:  Section features end