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%;’

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.

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‘}’.’

NUBKGG: is ideally formatted so the latest entry is displayed and hovering over gives all the entries.

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)

O4TKBX: to alert general readers that ‘hey, we know it’s not fully polished’

O4TKD6: to assign an amount/rating (of polish) so to prioritize what needs attention as far as raising the polish to more desirable levels

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)

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.

NUQFKM: to the imprecision & differences of what constitutes a ‘word’ (so bigger variances if using different meters/counters)

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.

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.

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.

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.’

NXD2LP: until one knows the workarounds where after it’s super easy, and to get you that point…

NXD2NB: for everyone, this site documents the WordPress caveats & workarounds everyone needs to know (yes, necessarily a lot of reading, but 1 time).

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.

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.

NVT60L: broke #NTMDA0 into 2 sub-points and well-expanded on each, especially support offer of #NVT5SA.

NVT5YR: cut ‘, here listed starting with typically most preferred’ as that is handled well enough by the order and ‘else’s’;

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)

NUBFD5: so adding ‘ & discuss’, as realized from NUBEMQ this aspect covered could use appropriate announcement here.

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)

O3KR84: ‘{post.status.snapshot{;date ’2016.03.05SatPst1000~‘;after ID ’minutes 91~ since Pst0831‘;revision ’30‘;version ’3‘;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

NXER4S: ‘{post.status.snapshot{;date ’20151106Fri1122pst~(verify)‘;after ID ’minutes 0‘;revision ’25‘;version ’2.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‘}}’

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}

NWU63H: seem to be getting too frequent ‘Aw, Snap!’, very likely because of post size getting to big, so break it up.

NWU5NC: ‘{post.status.snapshot{;date ’20151026Mon0926pst‘;after ID ’minutes 0‘;revision ’20‘;version ’1.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‘}}’

NVTDKQ: ‘{post.status.snapshot{;date ’2015100609Tue1246pst‘;after ID ’minutes 0‘;revision ’17‘;version ’1.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‘}}’

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.

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’}

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.

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}.’

N0SF78 ~12hrs ago, especially as this point needs to be 1st but #N0QW6N is so seemingly-unavoidably {long an negative}, plan move this to its own article, then making the additional here short as quote(–click for details and especially to operate on other devices as via smartphone & tablet);

N0SEHV Title (q(As with most websites, this website is best viewed & used on a laptop or desktop!)) as a problems as "best viewed & used on" can be viewed as what would be best for the user (rather than the website) and also it repeats "website" and also "As with" (with perhaps grammatically correct) is less familiar & more stuffy, so replace with present.

N0SR31 instead of standard sized, placed title in q( style=";font-size: 133%;") as this is probably a big problem plus still too much attention to #N0SQ88

N0YHZH now replace q(Then be ready) with q(Then please be ready) as the politeness helps, including makes the transition to a negative less jarring

N0YI37 now replace q(unless you can help us) with q(unless say you can help) as sounds less desperate & more hopeful.

N0QXP6 per #N0P4H0 and source's new title, change from “content {use-terms including copyright}: ~“by default ~“properly-including-minimally copybut fullyrefer- especiallylink-to info..”” & why” to present, also using "reproducing" above "copying" per present Winter Olympics on MSNBC saying ~"Do not reproduce or transmit without written permission of...",

N0SGFW replace quote(–follow thisbefore & when reproducing any content-or-info here, including any printing or copying of it.) with present: adding "especially " plus "or quoting" plus making all links to instead of some external definition (as Wikipedia) links the point on the matter in the target doc (which also includes the def links) (well "reproducing" as that word is not (yet) mentioned); also cut spurious quote-mark.

N0W7PE title: updated with latest values and made entire a single quote with ".." in middle.

N0YHJW This currently right after #N0SFIK (about); and was thinking about moving to the bottom as it's standard to have a copyright; but since this is short very (plus standard) and very important (indeed needed now for an upcoming legal post where the recipients (insurance adjusters) might be tempted to copy; plus not-respecting copyright is very serious problem for movies and so their copyright notice placed in very front of all DVD & Blu-ray "Play film"), decide to move it as far up as possible, so right after #N0IDXM.

N0SFKJ now created & added to #M8K00L, even though that's on the topic of "Use" not general "about", as no other better spot (including links in tagline impossible) and a link to site "about" expected on every page of a website but otherwise missing, and added right after #M79S5K as that seemed to well introduce it as well as being at right detail; don't include slogans as those already mentioned in tagline and again at (below) #M7A5F8.

N1404R to present as prior name "writing conventions" doesn't other communication forms of #N0AD0Q but since that is the only exception it seemingly doesn't deserve its own section (though barely as that point is very important"

N1472X now decide to (again) place this 1st as compared to present 1st #N140QE, it's more {immediately relevant since we're reading} and (as the 1st got longer plus a bit more complex with #N143OV) shorter & sweeter

N143OV a key & simple way to achieve: for any content repeated, designate a source instance and replace all other instances with a link to this source, then on the whole resultant content (which should now be much shorter where the repeats were), repeat this process until no more replacements can be done.

N14128 from subsequent sibling changes, this now falls right after #N140QE which is okay as that & above apply to everything including this (very) important thing and are short.

N13Z7O move this (up) to 1st (in #N0BQ1C) as this feels even possibly more important than really-important top item #N0TF0C (probably so because the material IS often ready for folks to look at when they are pointed to it, but they still need to know about this reply matter); so plus is not (well not just) a #N0BQ1C"writing convention" (parent) but really a communication convention

N0SVMF some improvements, most notably replacing q(where you assume your reply will be reposted after what it replies to else within that article page (again per this site's top goal: to communicate via proper post) with just the standard redactions unless you in your reply specify something different (as the additional redactions desired for its repost).) with present as seemingly much clearer including use of {} to break up & group simultaneously-applying concepts plus adding link to the mentioned site feature and more.

N13Z3C at this history point or before, placed this right after #LG4OWH then only this morning that fell right after #N13OG4

N0ACZQ The vastly preferred method to reply is for you the replier to reply directly yourself, and via proper posting here: via a reply commenton the content being replied to else in the best matching thread (including creating a thread for your point, but only if it doesn't already exist), else via a new article which in its title-else-intro tells including links-to what it is replying to.

N0AD0Q Failing that, reply by other methods (as ideally reply in writing (as posted here except in not the best place, or posts on other sites, or via email or txt/SMS) else reply verbally (as phone calls or in-person))where you assume your reply will be reposted...

N13RU3 present version, significantly extended & clarified from q(.., typically posts here are live wiki pages -similar to Wikipedia pages- so here, frequently articles, and sometimes even comments, get updated, ideally regularly, and some have multiple authors (plus potentially owner(s) who are not the authors))

N13RNP now located as 1st item of #N0BQ1C as this indeed appears the most needing-alert-thing, as now reminded when doing removal such alert at 4250#N13QPB

N0YK11 replace q( and sometimes comments, get updated, ideally regularly, and can have multiple authors) with present more clear & accurate.

N13RJZ at creation time, since this is really important including to make the removal of #N0TG9B, wanted to place high but placed right after #M87XAJ since it's short & quick

N0TGHP now created, motivated to introduce including introduce the need for #N0TFGY, and then found this also served as an intro & parent container for #M7AUKR.

N0TFGY So among numerous benefits of a wiki, this means, on this site, creating a post including comment is lowest-stress, including since: (1) it need not be initially complete and regularly isn't, as it readily can be updated as convenient & more is known and often is, and (2) one can use additional authors to help create it, and (3) more lowest-stress reasons.

N0TFGY But this site doesn't yet automatically alert on the post itself of any additional updates to it and authors on it; so the post author(s) must maintain this info manually in the post itself and the featured (initial) date & author on a post are often just its beginning so readers must look at a post contents, generally the bottom of its text, to see how recently & frequently it's been updated & how, plus to see its additional authors & owners if any.

N0YGP6 replace q(readers must read the post, generally the bottom of it, to see how recently & frequently & how it's updated plus see any additional authors (and owners when different from the authors).) with present.

N0SI3R Replaced fr(In better posts after 2012.06~ plus a few comments & sections,) to present as much clearer plus more accurate.

M7AUTO for the version of text, see its sub-section “.. history in order:”'s last entry: the ID (at the entry's beginning) will also be the version ID, moreover if the entry ends with a date as "; pst2014.02.01Sat0806." that also tells when last edited.

M7BKAZautomatic maintenance including self-labeling {of history sub-section and version-ID & -date} is planned (for every post, comment, & section, and eventually every text snippet)

N0SHAE title fr(every post, comment, & section's history & version: ) to present (making a statement of what's done) to be in line with title of {the parent section=#N0BQ1C} and just be considerably clearer.

LG4OWHideally a special unique tiny ID on every item, as “LG4OWH” on this point. While initially a bit odd-looking so made small & tucked-to-the-side wherever possible, these are very-powerful permanent short IDs for most any item, including for any point, step, sentence, or sub-content, or function/procedure, or folder or file, or change or version, or even a physical item or a name itself, enabling it to be uniquely & permanently portably-tracked & referenced (so then also easily commented upon: just refer to it by this ID), plus creation-stamped (tellable when it was created down to the second, plus often who created and even where and in what context including sometimes why), even eventually telling the item's full history

N0SV3N replace q(this site's goal N084LL (to point & link to anything, then also enabling easy comment on it)) with present as more readable by humans.

N0YIUA until now this right after #M87XAJ(outlined) but, while an immediate curiosity of any onlooker, it's not that intrusive now that codes are IDs are typically stashed on the right and more important is point #N0TFGY so now place right after #N0TF0C.

N13O16 Every use, or at least the first recent use, of a word or phrase here which could possibly be unfamiliar to any readers (except perhaps the very rare) is to be a hyperlink, else have an adjacent link, to its definition in this context, notably to the author(s) definition else to this website's definition (web search here can usually find it) else the definition by a reputable source most notably on Wikipedia else Google Maps.

N13OPV Every reproduction and ideally derivation here should have adjacent-or-on-it a telling-of-its-source including a hyperlink-else-best-approximation to its source, including as required by copyright here.

N12O00 be sure to also read the text immediately prior to where you were pointed to, including the titles & ideally other-bold-parts of all the larger sections containing it, in order to get the context of that point.

N12NSL And to find again where you were pointed to, all you need to do is re-follow or refresh the link pointing you to here.

N0SRPB now create this as while this is definitely true for ~95% of websites, it's an extremely important feature which many seem to forget (including Lucy!) or don't yet know. Place it as 1st item of #N0SISW

N0TI8Sbest of all, dramatically better than a book or a magazine or newspaper or newsletter article or even an email or tweet --where one easily ends up saying stuff they then can't later correct, and is regularly expected well-complete plus maintain their publication even though they now may very much want and need to move to something else-- here release info & publish with the lowest possible stress:Create & save drafts (of articles) until you're ready, if ever, to share them; and even when shared, limit who can access until you're ready, if ever, to allow a wider audience. Plus, for articles AND comments: write under one or more pseudonyms , and, per wiki incremental collaborative design, eliminate the expectation it needs to be complete or all worked out on first release and, at any stage, bring in others to help you so it's not all on you; plus at all stages, even after publishing to the world, per wiki system and matching copyright controls, still have full freedom to subsequently make full even massive additions, corrections, & improvements, and in both content & who shared to!

N0SKV1The normal use of this site is ordinary folks posting their written communications here (via articles & comments) then emailing/messaging/posting to their readers the link to their post and/or having their posts found by web search.

N0SJW2On every article, click one of its categories to also see all the other articles here explicitly placed in that category or any of its sub-categories.N12VVL For every article you find here, there is a reasonable chance there are more of them on the topics listed in its categories.

N12QLV was q(The right side bar has: Search plus lists of Categories, Recent Articles/Posts, Recent Comments, top Authors & Editors (click on each to see o see his/her articles).) with improved wording including exact references to named widgets now that they've just yesterday been very-well-named plus add some more.

This right sidebar is very useful, including for browsing: see above&below its “Search” right at top plus it's many useful lists: All “..Category”N10H7P plus the sidebar's many useful content lists: “..Most Recently-Modified Articles”N10HDO & “.. Most Recently-Posted Comments”N10HID, and even “Authors..”M8AQ0E & “Editors: All & With Bio+Stats”M8AUVK plus click on each to see his/her articles! Plus more lists following those, as “Articles per Month for all History”N10VKE.

N12U7P was q(But do realize, especially as this site encourages all & every topic and by anyone, similar to say Google Docs, likewise its entry point is generally not its home page and its specialty is not random browsing, understandably per its normal use.

RSS feeds: this website offers 2 feeds (of our articles w/o comments and of our comments), but, respecting copyright here, do not use these nor share this data and/or links to it except per official written authorization from us this website's management; but dolet us know of need for this feed info and we may grant access to this.