https://beta.devuan.org/os/documentation/install-guides/beowulf/upgrade-to-beowulf.html beowulf devuan

https://debian-facile.org/projets/lescahiersdudebutant/ debian documentation

https://tldr.sh/ documentation manpages

https://pwmt.org/projects/zathura/documentation/ zathura

https://git-scm.com/book/fr/v2 documentation git

http://www.sqlfacile.com/ DB documentation sqlite

https://calmcode.io/ code documentation python

https://pythonspot.com/ documentation python

https://www.youtube.com/watch?v=IgUAiUs4tC0&feature=youtu.be documentation flask python

https://cheatsheets.tutorials24x7.com/programming/python documentation python

/twtxt.html, at 12.9KB, is now the largest HTML document on https://mckinley.cc/.

Live.js is neat, but I don’t know why you would include it in the document. I just put it in a userscript for 127.0.0.1. https://livejs.com/

@(frogorbits.com) @niplav@niplav.github.io “I sign a lot less stuff these days now that my phone can pretend to be a credit card. Also: an impostor with a quantum computer can’t pretend to sign documents on my behalf…” -> It’s good that pen signatures are completely unfakeable. They’re unbelievably reliable. We can’t just copy & photoshop around the edges. Better worry about those definitely-soon-to-exist quantum computers that might crack cryptography.

Documentation on i2c devices is so-so. Lots of good documentation on higher-level APIs, but not a lot of “this register does this” stuff.

finally finished all the initial ugen documentation. everything now has a sentence or two. the generated page can be accessed from the ugen wiki page [[/proj/monolith/wiki/ugens]] #updates #monolith

been adopting a document-as-you go approach to the !monolith wiki. as I dogfood my software to make pieces an etudes like !breathing_cards, I write about it in a wiki stub. #workflow #documentation

PeerTube documentation ⌘ https://docs.joinpeertube.org/#/maintain-tools?id=remote-tools

microblog.pub documentation | hexa.ninja ⌘ https://docs.microblog.pub/

The master plan is to export the !worgle bits of !monolith to a !weewiki, then begin adding user-level documentation that is able to dynamically reference bits of source code as another wiki page.

while eventually I hope to get all of literate org parts of !monolith posted online as a self contained !weewiki, I’ve decided to post little pieces as self-contained documents. here is a copy of !trigvm, the toy VM used to power a rhythmic computer-sequencer controlled entirely from the !monome_grid

I really want !btprnt to be integrated into !weewiki somehow. Both can speak !janet, and I already figured how to embed PNG images inside of an HTML document. In small doses, it could be fun. #halfbakedideas

documenting my experiments with twtxt/weewiki integration at the !twtxt_playground

Thinking about getting a document camera: Any suggestions? ⌘

How do you do URLs or hyperlinks in a groff or troff document? ⌘

Don’t document software! (If you want to avoid pain!) ⌘

I finally made a script to add my twtxt messages in the 3 necessary documents. It isn’t pretty, but at least it gets the job done.

Cryptee | Private, Secure, Encrypted Photos and Encrypted Documents ⌘ https://crypt.ee/

I mean, ‘quietly’ is a bit misleading since this has been in the news every few years for more than a decade, but you all might need a reminder: https://qz.com/1002927/computer-printers-have-been-quietly-embedding-tracking-codes-in-documents-for-decades/

Poor documentation is overrated as an attribute of jokes. (Some of my favorite jokes are literally humorous attempts at explaining other jokes.) The difference between standup comedy & UI design is even bad comics know this.

I love books about the history of tech, but no matter how well-researched, they’re typically mostly a documentation of tech’s mythology (or some countermythology). I prefer the countermythographies.

I documented what I’m trying to do with MfoM, so that I can write a proper postmortem later: https://medium.com/@/mfom-pre-postmortem-92683b15ff2c

Parallel documents! Interview, August 2018 - YouTube https://www.youtube.com/watch?v=PPBeHDxcVSA

GXemul - Documentation (0.6.1) http://gavare.se/gxemul/gxemul-stable/doc/guestoses.html#sprite

Heads up, apparently there are gonna be export restrictions on neural net, reinforcement learning, computer vision, NLP, & similar research done in the US: https://www.federalregister.gov/documents/2018/11/19/2018-25221/review-of-controls-for-certain-emerging-technologies

Just created my first proper document in Scribus. It worked better than I expected.

Document Moved https://sway.com/b1pRwmzuGjqB30On

Xanadu Basics 1b– INDIRECT DOCUMENT DELIVERY - YouTube https://www.youtube.com/watch?v=1gPM3GqjMR4

inferno@interstice.com and inferno@artnet.com.br list archives http://doc.cat-v.org/inferno/historical_documents/mailing_lists/interstice/

Technical Documentation For The Canon Cat Editor : David Alzofon, Lori Chavez, Jim Winter, David Caulkins, Terry Holmes, Minoru Taoyama, Jonathan Sand, John Bumgarner, Scott Kim. : Free Download, Borro… https://archive.org/details/TechnicalDocumentationForTheCanonCatEditorSep88

Genode - Sculpt with Visual Composition (VC) https://genode.org/documentation/articles/sculpt-vc

Morphic documentation http://wiki.squeak.org/squeak/6514

Untitled Document: 1. “Introduction” http://www.unlambda.com/lmman/lmman_1.html

rebooting-the-web-of-trust-spring2018/making-dids-invisible-with-petnames.md at petnames · cwebber/rebooting-the-web-of-trust-spring2018 · GitHub https://github.com/cwebber/rebooting-the-web-of-trust-spring2018/blob/petnames/draft-documents/making-dids-invisible-with-petnames.md

In one sense, ‘the computer revolution is over’ because the period of exponential growth behind the tech ended 10 years ago. In another sense, it hasn’t begun: we have sheltered ourselves from the social and intellectual ramifications of computing. Documents are still simulations of paper, & capitalism still exists. So it’s like that period where printing presses existed but everybody used a faux-calligraphic font.

Hot take: any command that a user might want to use regularly should be short, memorable, and built-in; any command that a user might really NEED to use should be documented & included in the examples in built-in documentation.

Javascript is a just-OK language saddled with the world’s worst graphics toolkit: three distinct languages, each with specs so large that nobody has written a new implementation in 20 years, for live-editing a rich tech document to make it resemble a canvas, in ways that are not portable between the 3 implementations or minor revisions of the same implementation.

Have you tried documenting the problem so that future implementations need to reproduce it?

The existential paranoia fueling Elon Musk’s fear of AI | Document Journal http://www.documentjournal.com/2018/04/the-existential-paranoia-fueling-elon-musks-fear-of-ai/

Xanadu Basics 1b– INDIRECT DOCUMENT DELIVERY - YouTube https://www.youtube.com/watch?v=1gPM3GqjMR4

If you want to snarf up the Project Stargate documents, now is the time: https://www.cia.gov/library/readingroom/collection/crest-25-year-program-archive