Documents shared from this docserver. Consider them all as perpetual rough drafts. As such, save a copy of any doc with info that matters to you, just in case it changes later, or is replaced, or becomes unavailable.
[ Docserver end date: 2026 Autumn ]
The length of the descriptions can be changed with the following options.
Writing with the computer medium: Typing plainly.
The computer as a tool: Write immediately and repeat workflows.
Personal: Where I am and conversational topics.
Perception: Mindset and memory management.
Docserver information: The change log, help, a guideline, and stylesheets.
Encouragement to keep plain text as plain text, even when formatting it. (HTM and CSS)
A computer will draw a letter at the press of the button for that letter. Just add spaces between words and blank lines between paragraphs, nothing more is needed. The result is a plain text doc compatible with the past, present, and future computer devices.
The intent of Hypertext Markup (HTML) is two-fold: mark regions of text (markup), and reference other content (links). HTML is simply enclosure marks (much like parentheses) written as names instead of singular symbols. It is like adding proofreader marks, just as minimal but HTM marks are more legible.
Docs marked with HTML remains readable as plain text. The alternate view implied by the HTML marks is supplementary for displaying the text.
An HTML docviewer (computer program) provides an alternate view by leaving out the marks and making adjustments to spacing (f.e. line height or indentation) and text (f.e. drawn thicker or underlined). The computer programmers of each of those HTML doc viewers had to decide the default characteristics for the spacing and drawing of the text. As such, each of those doc viewers might display the same HTML doc differently, though usually only slightly different.
The intent of Cascading Stylesheets (CSS) is for changing those default characteristics of the HTML marks (t.i. spacing and drawing) that have been decided by the computer programmers for each of the HTML doc viewers.
CSS has nothing do with the document content. CSS is only a convenient means for changing the default preferences of the computer program (t.i. doc viewer) without having to rewrite the computer program itself.
See "Section 1. Writing with the computer medium [#1]" for its list of docs.
Personalizing the computer for comfort and use: write immediately and repeat workflows.
As the tool a computer is intended to be, the computer utterly fails when it is unable to repeat what a human already did (t.i. a sequence of actions) with the computer itself. Instructions for the computer is just a recipe, and should be completely changible [ Yes, I do that. I change "eable" to "ible" (and at some other times, too) to match the sound. Yes, I am allowed to do that, and so are you; that is how a language works (otherwise that language is dead). ] by the person using the computer program.
I have personalized various custom keyboard layouts (remapping) for my use with the X Window System [x.org], I have and written why (as a reminder for at least myself) within the docs themselves. Notes about ASCII, PDF, and general binary formats. Notes about computer instruction interpreters (f.e. Lisp or shell) and their commands. Approaches for editing text with Ed [gnu.org] and Emacs [gnu.org].
Perhaps first and foremost on my mind with computers is my own personal comfort when using them, t.i. having information readily accessible from the computer medium rather than merely available. For example, writing plaintext documents, perhaps marked up with HTM [plain-htm.htm], therefore no additional software (computer programs) needed beyond what usually comes with the computer, t.i. with its OS ( operating system)). Plain text is likely the most friendly for computer programs to understand, too, and readily transferred to probably any other computer regardless of its OS.
Obviously, computer programs are "disabled" by the typical menus, pointer cursor, and overlapping views of the typical interface from the computer itself. Making the human-computer-interface (HCI) more accessible to people might also help make the interface more accessible for computer programs, too.
So far as of the year 2022:
A variety of permanent disabilities and permanent impediments have been referenced for the sake of creating a single large minority of people (by a variety of labels and categories), but inherently is too diverse to address specifically. Thus, the individual is forgotten, and certainly unmet needs or desires at any moment remains unaddressable for that individual.
The human-computer interface (HCI) has been implemented with a focus on novelty, special effects, and presumed benevolence rather than respecting the content communicated with the computer. That has been cumbersome for the "temporarily able body (TAB) majority", and predictably has been impracticable for the diverse "disability minority".
The cumbersomeness of the typical HCI has been bypassed for the sake of enabling specific minorities of the diverse "disability minority" by layering over that HCI with yet another interface (t.i. an interface for an interface) implemented with a focus on novelty, special effects, and presumed benevolence, again.
That option has been largely ignored by the "TAB majority" in favor of the former cumbersomeness, t.i. too cumbersome even for the non-disabled.
For example, consider a multi-floor building with stairs leading to each floor. Thinking of only the "stair impaired" people might inspire the installation of ramps to each floor. On the other hand, re-thinking the purpose might inspire the idea of an elevator, or having only a single floor, or eliminating the "need" of a building (or maze of walls) at all.
For HCI, it is pretty obvious the operating systems of computers (and likely their hardware) in their current forms must be abandoned in order to live beyond computers as they are currently known. Personalizable implies do-it-yourself (DIY) instead of done-for-you (DFY). DIY is the means beyond a set of options or commands decided by someone else (DFY) for no one in particular.
It is especially about time for considering the importance of the temporary moments of disability experienced by the TAB (f.e. no-sight phone call, or temporarily single-handed), as that aids in addressing similar permanent disabilities.
In other words, there must be some new curiosity, some interests beyond the stories sold by the "computerized appliance" market, f.e. an all-in-one computer or a PDA (including misnomered "smartphones").
See "Section 2. The computer as a tool [#2]" for its list of docs.
Where I am (Ka-imu-kī), who I have helped (local orgs mostly), my pursuits (computer personalization), and my interests (health, computers). Though I sometimes say I am in my second half-century of life, I have never been interested in keeping score and I have had no interest in being competitive about anything.
This docserver "l8l.info" (a.k.a. "L8L.info") and my email adresses are the only Internet services I use publicly. I never make use of other Internet services that require my contact information, as I have no interest in being nagged by computer programs and advertisements. My contact info can be determined from the docserver help doc [docserver-help.htm] when viewed with a text editor.
No name can be unique, but hopefully that clarifies that for me the "l8l.info" (or "L8L.info") computer address for this docserver is unrelated to anything else or anyone else (especially on the Internet). In fact, I have no awareness of its similarities, but because I have not sought any such awareness as I generally never browse the Internet anymore (too old, nothing new).
For me, I think of "l8l" as representing "infinite scroll" or "an inifinity scroll", the (magical) opportunity a computer display provides for viewing documents. I also consider it to denote the infinite ("8") between parallels ("pair of els"), similar to how I have often felt about myself and my own interests from our fictionalized culture. That is why I appreciate discovering overlapping interests with other persons, then I feel less parallel to everything.
I am currently outdoors in the city [words--culture.htm#] (once again) I guess until I meet new people. Hopefully someday I will gain allowance for being indoors again, and maybe personalize my own international telegramming device (t.i. computer) again.
See "Section 3. Personal [#3]" for its list of docs.
Perceiving is shaped by the mindset at the moment and by memory management.
Documents about the documents on this docserver.
Encouragement to keep plain text as plain text, even when formatting it. (HTM and CSS)
A very quick introduction (especially section 5 [plain-htm.htm#5]) to marking a plain text document with HTM (hypertext markup).
HTM is just marks, like proofreader marks, and is not instructions for the computer. That is, there is no need for computer programming knowledge.
Most of the time, the only mark used will likely be for a paragraph, which is just <p>. Other commonly useful marks are for headings or lists. A plain text doc remains as plain text even when it has HTM marks.
An excerpt from section 2 [plain-htm.htm#2]:
Sometimes the ending of a region is obvious by a mark beginning a new region after it, f.e. a paragraph after a paragraph, thereby the ending mark is conveniently optional.
<p>A paragraph of text that is followed by another paragraph.<p>The previous paragraph obviously ends when this paragraph begins, but this one has an ending mark.</p>
The prior notes I wrote as an introduction for HTM, with different details.
Quick reference of named or numbered letters in HTM, for when the letter ʻokina and letters with accents are unavailable when typing on a computer.
For example, select and copy a character, then insert the copy (t.i. "paste" it) into the text in any other computer program.
A CSS stylesheet for a stylesheet with its documentation (t.i. comments) marked with HTM. [ Made the statements too concise. Would like to rephrase the explanations someday. ]
The "style" of Cascading Style Sheet refers to expression rather than decoration, because CSS is for changing the default spacing and drawing of HTM marked regions of plain text docs. Therefore, CSS actually describes the characteristics of HTM marks rather than the doc.
The intent of the CSS stylesheet should be documented with comments embraced by /* and */. The text within a commented region can be marked up with HTM, and then the documentation for a stylesheet can have an alternate view in an HTML doc viewer.
A well-documented stylesheet inevitably links to itself for styling HTM marked examples of its CSS rules within its own documentation. Therefore, a "stylesheet stylesheet" such as this one is "the mother of all stylesheets", as it precedes and begets all thereafter.
A recipe (kitchen) and a mathematical formula (academic) and a computer program (office) are all the same thing: a set of instructions. The only significant difference is the notation.
Personalizing the computer for comfort and use: write immediately and repeat workflows.
Repeatability of tedius tasks, and discrete instability by means of external memory.
General examples for applying to whatever hardware or software is available.
Notes about the view management capabilities of StumpWM, a Lisp (t.i. LIS-t P-rocessing) interpreter for basic instructions and recipes for the computer.
StumpWM provides various prompts for typing computer instructions, or the name of a StumpWM command, or for help.
StumpWM is an SBCL [sbcl.org] Lisp interpreter with view management capibilities (t.i. a window manager) for the X Window System, providing an interactive extensible computer interface. The X Window System is often used with a UNIX-like operating system, such as GNU/Linux.
Notes about using specific software (StumpWM [stumpwm.github.io] + X11 (release 7.7) [x.org] + TinyCore Linux [tinycorelinux.net]) and one of the possible hardware options for it (Raspberry Pi 4B (4GB mem) [raspberrypi.com]), with intent of implementing my main (or former? maybe again?) pursuit towards the computer as a personalizable tool, especially by the everyday person.
[ Likely an earlier version of the Raspberry Pi would be enough, perhaps the Pi 3 or even Pi 2. Have yet to have the means to test. Also, less than 4GB of memory would probably be fine, too, especially if only used as a remote control for using other computers (f.e. with VNC), but have yet to test that firsthand either. However, I am rather interested in considering microcontrollers, which are even less hardware than that, as I want to minimize excess use of resources, f.e. no need for a triple-trailer semi-truck just to go grocery shopping for a loaf of bread and a bottle of milk. ]
See "Dual-system computing: 4. A personalizable computer" [dual-system.htm#4] for a general idea (t.i. non-specific hardware and non-specific software).
Pursuing having the computer repeat the keystrokes, pointer movements, and any other button presses for any workflow involving any computer program system-wide. Though incomplete, it could help with getting started (again).
Various opportunities would arise from having such a button-sequence recording ability, and without need for computer programming knowledge nor so-called "artificial intelligence" [words--culture.htm]. For example, the keyboard macros available in Emacs [gnu.org] (a LISP interpreter) provides this ability, which also includes text editing, email, access to Internet documents, UNIX shell interpreters, and other activities possible within Emacs. [ The abilities of Emacs are modular, so more can be added and any can be removed. ]
For example, a recorded sequence would be likely a short length of text (f.e. button names like "a" or "Control-c") that can actually perform the work [ Or, to play a difficult part of a game for someone, perhaps requiring fingers that person has lost, or that has been permanently injured. ] rather than recording a video requiring lots of computer memory and telegramming bandwidth. Or, accomplish a task so tediously repetitive that it might never have been attempted without such automation.
New opportunities are like having elevators instead of having only stairs, f.e. the package delivery services with carts that would be encumbered by stairs if there were no elevator. Think of how anyone uses an elevator instead of stairs regardless of personal physical ability, and without feeling stigmatized for not using the stairs. Convenience and with no shame, and everybody benefits without needing specialized engineering knowledge or personal ability.
Lisp is list processing (t.i. "LIS-t P-rocessing"), a means for instructing a computer for handling lists, f.e. a list of instructions.
Lisp itself is programmable, meaning its notation can be customized. In other words, Lisp is a "programmable programming language", and is partly why Lisp is said to have no syntax, unlike other computer languages.
Lisp is experienced in a interpreter program rather than with a compiler program. As such, Lisp itself can be programmed before, during, and after a computer program is written with Lisp.
As the computer is currently known to the everyday person, as a mere appliance instead of an ingredient.
A computer does what a person desires at the mere press of a button, but for most people that is only science fiction.
As aforementioned, the computer utterly fails when it is unable to repeat what a human already did (t.i. a sequence of actions) with the computer itself.
Excerpt from the document:
There are simply two sets of instructions for a computer:
Write to and read from "temporary memory".
Like scribbling on scratch paper. It disappears when the computer is turned off (no electricity).Write to and read from "permanent memory".
Usually an external storage device.All interactions with a computer comprise those two purposes: "now" and "later". The memory might be for the screen displaying drawings of text. It might be on another computer.
Use a powerbank (rechargable battery) to power both a Raspberry Pi and any USB-powered computer display.
Or, two Raspberry Pi modules and a single computer display with two display ports. Some powerbanks can power all three at once. Of course, use separate powerbanks for discrete power usage [dual-system.htm#3].
Note that the display can be detached from the Raspberry Pi and powerbank, and the keyboard and memory detached from the Raspberry Pi, all while the Raspberry Pi remains attached to the powerbank. No need to turn off the Raspberry Pi (which typically has no off button anyway). While that is one way of not having to restart the Raspbery Pi, it would be best to save all work and detach the external memory, too.
Includes the ʻokina, kahakō composition, and various accent compositions.
(xmodmap, Xserver, StumpWM)
Includes the ʻokina, kahakō composition, and various accent compositions.
(xmodmap, Xserver, StumpWM)
Establish the bottom as the consistent location for the command line by drawing enough blank lines (f.e. with echo) to fill the screen from top to bottom instead of using the clear command.
Commands for file transfer, find, and grep.
Permissions, passphrase options and use, and generating an ssh key.
Reading and writing with various text editors, such as Ed and Emacs.
Some essentials about Emacs, and some rather elaborate details. (Probably. Need to read again someday, determine relevancy.)
Very old info about installing Emacs. (Need to read again someday, determine relevancy.)
IIRC, this explains the details (t.i. eliminates the mystery) for enabling the basic email interface rmail provided in Emacs.
Very old doc [long before last (obviously minor) edit date 2024 May 01]. Seems to be a proposal for replacing the desktop file of Emacs [gnu.org] (Lisp interpreter with built-in text editor).
Some of the opportunites of using the Ed text editor within Emacs.
The elegant view management naturally occurring from using the Ed text editor [gnu.org] is reminiscent of writing computer instructions in BASIC on a home computer in the 1980s.
Experiencing that within Emacs [gnu.org] allows for repeatability of workflows with Ed, as well as "superuser" capabilities even when Emacs is started with "normal user" privileges.
The bits about the dots and dashes for ASCII (rather than Morse code) for storing info in computer memory, and for telegramming with computers across the international telegramming network (a.k.a. the Internet).
A brief summary from personal notes for adding hyperlinks within a PDF doc, and combining images into a single PDF doc.
Even thought Portable Document Format (PDF) is plain text, PDF is for describing how to layout text and images rather than for editing text. That is, for drawing.
The recommendation for PDF is to use the version that has the features needed for making the desired doc, instead of simply using the latest version. That usually means the earliest version possible, which is commonly "PDF 1.3", though "PDF 1.4" has some nice conveniences.
Ideas for inserting documentation within a binary file, and for external documentation for a binary file.
Where I am (Ka-imu-kī: Honolulu, Hawaiʻi, USA, Earth), who I have helped (local orgs mostly), my pursuits (computer personalization), and my interests (health, computers). Though I sometimes say I am in my second half-century of life, I have never been interested in keeping score and I have had no interest in being competitive about anything.
As of 2022 Jan 09, I am outdoors in the city [words--culture.htm#], and have been mostly in a neighborhood known as Ka-imu-kī (Honolulu, Hawaiʻi, USA, Earth) ever since mid-2008, though closer to the Kāhala area lately. I am without any social capital [words--culture.htm#] and I am without any resources (other than my experience with computers) to share with anyone else.
That is, I have nothing available to share with land/home owners [words--culture.htm#ownership] to help with their responsibilities of stewardship.
Without a place indoors [words--general.htm#], I have no means of storing possessions [words--culture.htm#] and so at the moment I am making a practice of collecting nothing more than I feel I can healthfully carry. As such, I am without the means to keep and care for the resources employers typically expect employees to already have.
Yet, everyone seems to be doing fine without me participating. Maybe someday [words--general.htm#] I will get lost within the busy-ness once again, participating, passing the time to my own final moment of life in that way once again.
Until then, my patience and acceptance has felt like enough for me, no anxiousness, I am at peace with myself and everything (just waiting to die, like everyone else), and most definitely without any sadness but also no bursts of energetic happiness.
Former document is much longer and was renamed to "participation-2024May31.htm" for reference, and will likely remain unedited. Perhaps later some parts will be copied into the current doc.
People and organizations who I have helped most recently (2008-2021) with the computer medium. A sort of portfolio, but also somewhat a telling of how my relationship tree [words--culture.htm#] dissipated.
I was able to help them even though I knew nothing about art, nor about being a Catholic, nor about being a woman. And, I still know nothing about any of that. Nonetheless, we had overlapping interests, t.i. my craft with the computer medium.
For the Jean Charlot Foundation, I scanned thousands of pages of docs and books, and scanned hundreds of photographs (f.e. slides) and archived artwork. Their docserver had maybe a few hundred docs and images, and I added thousands more [helped.htm#1] without needing a database or a COTS (commercial off the shelf) CMS (content management system). Using no COTS software kept it as secure as the docserver itself (t.i. no additional security concerns), and made it future compatible with any filesystem, docserver, OS, and text editor programs. I focused on accessible (t.i. beyond merely available) for both humans and computer programs, and on ease of maintenance or transitioning with the tasks lists, guidelines, and help I wrote and continuously updated.
I am also credited [helped.htm#2] in the "Preface" of the 200+ page book Writings by Jean Charlot: a bibilography (2014) by Janine M. Richardson, with its formatting, posting, and printing. Additonal credited with helping with checking of sources for the author. See its "Preface" [vault.jeancharlot.org] with the paragraph referring to the "unofficial webmaster since 2009 for the Jean Charlot Foundation website".
The former docserver of archive materials that I managed. It was slightly modified, but seems (I am mostly guessing) the same as before it was displaced for a different initial appearance for the organization.
Writings by Jean Charlot: a bibliography (PDF) [vault.jeancharlot.org] (2014) by Janine Richardson.
Writings by Jean Charlot: a bibliography (HTML) [vault.jeancharlot.org] (2014) by Janine Richardson.
For the Catholic Women's Guild Hawaii, I scanned hundreds of archive documents and created PDF documents from them [helped.htm#3] (f.e. per folder from the boxes). I later transcribed their Bylaws [helped.htm#4] for revising and reprinting, edited a few newsletters (folded 17 by 11 inches) for emailing to the members, and formatted and printed the annual report (including tabulated financial reports) for the Board members.
I tend to favor practicing "computer wizardry" (a term from the 1900's), especially exploring my curiosity along the lines of personalizing interfaces of the computer medium.
Mostly to do with personalizing the computer medium for myself and sharing what works for me with everyone else, but at the moment within the limits of the computers at the public library (my only computing resource).
Also a list of unlikely pursuits [pursuit.htm#2] such as the unwritten computer program "S.C.U.C.H." (personalizable by anyone), or maybe someday [words--general.htm#]completely giving up on life and simply passing away the rest of my living by playing nostalgic video games (NES, N64) until I die.
It seems like to me all of my pursuits (even the unlikely pursuits) are different beginnings for the same direction (not to be confused with a goal or endpoint): personalized computing. Ultimately, that means developing a text editor that can also interpret computer instructions from the person using it, including being able to write instructions to completely replace that text editor itself, t.i. full and complete customization of the computer experience.
Perhaps incredibly, the intent is to enable every person without the need for anyone to be a computer programmer. Of course, computer programmers would benefit, too, from the ease and the personal opportunities.
Some notes from reading some documentation. Maybe this will help me keep up with whatever my curiosities happen to be about these topics.
Perceiving is shaped by the mindset at the moment and by memory management.
In essence, the "you" is also "me", so no point anybody other than me (and only "now me", not "later me") taking anything personally that I wrote.
Besides, this is the computer medium, so just save-and-edit any doc [ Nope. Absolutely no copyright on anything authored by me. I give full credit to all the influences from every single thing in the Universe. ] with new phrasing for yourself, as that is what I do, too.
Emotional Freedom Technique (EFT) uses the common memory techniques for addressing memories, especially with emotion (t.i. energy for action) to do something about the memory.
Just some reminders for myself, various perspectives.
A very old document, older than the file date which is merely when it was copied to the docserver.
Words and phrases I tend to be careful about using, as for whatever reason other people have a different understanding, t.i. mean something different.
Words and phrases about our culture, as I have observed it and reflected upon it.
Words and phrases about food, as I have observed it and reflected upon it.
Documents about the documents on this docserver.
The most recent changes to docs from this docserver "L8L.info".
The modification at the top of the doc you are currently reading (t.i. "sharing.htm") is also a convenient link to the "What is different?" doc, because "Sharing" is the current default doc from the docserver.
New help document for this docserver. Still revising... Also the new stylesheet, but likely only for itself, the doc "Sharing from L8L.info" [sharing.htm], and the doc "What is different?" [different.htm].
Prior help document for older documents from this docserver.
Help for this docserver [help.htm]
Explains the visual differences for the HTM/CSS alternate view of the docs, but mostly for prior stylesheets, and some general tips.
For example, hyperlinks [help.htm#hyperlinks] have been might be decorated with dotted, dashed, and solid underlining.
It also has help for creating a personal stylesheet [help.htm#personal] for affecting docs from this docserver, or any docserver on the international telegramming network (a.k.a. the Internet).
CSS is just a list of characterstics for each HTM mark, and is not computer instructions at all, t.i. no need for computer programming knowledge.
Review the additional CSS style applied to many of these docs, and their explanations.
Former "new" stylesheet intended as replacement.
Former guideline with my approaches for writing notes with HTM.
It is a basic approach in order to keep the docs easy to read, edit, and revise. No need for computer programming.
[ Needs to be updated replaced... ]
Information that was useful to me, located at other docservers on the Internet.
convert and mogrify, or magick (as of 7.x).