Using an AI Assistant to Read Tool Documentation
Explore how to use Docker and LLMs to streamline workflows for command-line tools to enhance the process of reading docs, troubleshooting errors, and running commands. ⌘ Read more

Okay folks, I’ve spent all day on this today, and I think its in “good enough”™ shape to share:

Twtxt v2:

• Specification: https://docs.mills.io/uJXuisaYTRWYDrl8A2jADg?both
  
• implementation: https://gist.mills.io/prologic/afdec15443da4d7aa898f383f171ec1b
  

LOl 😂 Not only have a tried to write up a full Twtxt v2 specification, I’ve also written a Bash shell script that implements the new spec 😅

@quark@ferengi.one It looks like the part about traditional topics has been removed from that page. Here is an old version that mentions it: https://web.archive.org/web/20221211165458/https://dev.twtxt.net/doc/twtsubjectextension.html . Still, I don’t see any description of what is actually allowed between the parentheses. May be worth noting that twtxt.net is displaying the twts with the subject stripped, so some piece of code is recognizing it as a subject (or, at least, something to be removed).

@falsifian@www.falsifian.org based on Twt Subject Extension, your subject is invalid. You can have custom subjects, that is, not a valid hash, but you simply can’t put anything, and expect it to be treated as a TwtSubject, me thinks.

@mckinley@twtxt.net

HTTPS is supposed to do [verification] anyway.

TLS provides verification that nobody is tampering with or snooping on your connection to a server. It doesn’t, for example, verify that a file downloaded from server A is from the same entity as the one from server B.

I was confused by this response for a while, but now I think I understand what you’re getting at. You are pointing out that with signed feeds, I can verify the authenticity of a feed without accessing the original server, whereas with HTTPS I can’t verify a feed unless I download it myself from the origin server. Is that right?

I.e. if the HTTPS origin server is online and I don’t mind taking the time and bandwidth to contact it, then perhaps signed feeds offer no advantage, but if the origin server might not be online, or I want to download a big archive of lots of feeds at once without contacting each server individually, then I need signed feeds.

feed locations [being] URLs gives some flexibility

It does give flexibility, but perhaps we should have made them URIs instead for even more flexibility. Then, you could use a tag URI, urn:uuid:*, or a regular old URL if you wanted to. The spec seems to indicate that the url tag should be a working URL that clients can use to find a copy of the feed, optionally at multiple locations. I’m not very familiar with IP{F,N}S but if it ensures you own an identifier forever and that identifier points to a current copy of your feed, it could be a great way to fix it on an individual basis without breaking any specs :)

I’m also not very familiar with IPFS or IPNS.

I haven’t been following the other twts about signatures carefully. I just hope whatever you smart people come up with will be backwards-compatible so it still works if I’m too lazy to change how I publish my feed :-)

Apple Loses Major Tax Dispute in Europe, Must Pay Ireland €13 Billion
The European Union’s Court of Justice today said it has confirmed the European Commission’s 2016 decision that Ireland had given illegal tax benefits worth €13 billion to Apple from 1991 to 2014. This is a final ruling, so Ireland is now required to recove … ⌘ Read more

@bender@twtxt.net Yes, they do 🤣 Implicitly, or threading would never work at all 😅 Nor lookups 🤣 They are used as keys. Think of them like a primary key in a database or index. I totally get where you’re coming from, but there are trade-offs with using Message/Thread Ids as opposed to Content Addressing (like we do) and I believe we would just encounter other problems by doing so.

My money is on extending the Twt Subject extension to support more (optional) advanced “subjects”; i.e: indicating you edited a Twt you already published in your feed as @falsifian@www.falsifian.org indicated 👌

Then we have a secondary (bure much rarer) problem of the “identity” of a feed in the first place. Using the URL you fetch the feed from as @lyse@lyse.isobeef.org ’s client tt seems to do or using the # url = metadata field as every other client does (according to the spec) is problematic when you decide to change where you host your feed. In fact the spec says:

Users are advised to not change the first one of their urls. If they move their feed to a new URL, they should add this new URL as a new url field.

See Choosing the Feed URL – This is one of our longest debates and challenges, and I think (_I suspect along with @xuu@txt.sour.is _) that the right way to solve this is to use public/private key(s) where you actually have a public key fingerprint as your feed’s unique identity that never changes.

I just manually followed the steps at https://dev.twtxt.net/doc/twthashextension.html and got 6mdqxrq. I wonder what happened. Did @cuaxolo@sunshinegardens.org edit the twt in some subtle way after twtxt.net downloaded it? I couldn’t spot a diff, other than ‘ appearing as ’ on yarn.social, which I assume is a transformation done by twtxt.net.

@prologic@twtxt.net Yes, fetching the twt by hash from some service could be a good alternative, in case the twt I have does not @-mention the source. (Besides yarnd, maybe this should be part of the registry API? I don’t see fetch-by-hash in the registry API docs.)

Ignite Realtime Blog: Openfire 4.8.2 Release
Openfire 4.8.2 has landed!

This release addresses a number of issues in the real time collaboration server created by the Ignite Realtime Community that aim to reduce bugs and increase stability and performance.

Interested in getting started? You can [download installers of Openfire here](https://igniterealtime.org/downloads/#op … ⌘ Read more

Docker Documentation Gets an AI-Powered Assistant
Learn about the Docker Docs AI, a documentation assistant designed to provide instant, accurate answers directly from the Docker docs pages. ⌘ Read more

ProcessOne: ejabberd Docs now using MkDocs

Image

The ejabberd Docs website did just get a major rework: new content management system, reorganized navigation, improved markdown, and several improvements!

ejabberd started in November 2002 (see a timeline in the ejabberd turns 20 bl … ⌘ Read more

ProcessOne: ejabberd Docs now using MkDocs
The ejabberd Docs website did just get a major rework: new content management system, reorganized navigation, improved markdown, and several improvements!

ejabberd started in November 2002 (see a timeline in the ejabberd turns 20 blog post). And the first documentation was published in January 2003, using LaTeX, see [Ejabberd Installation and Op … ⌘ Read more

Empower Your Development: Dive into Docker’s Comprehensive Learning Ecosystem
Find out about Docker’s multifaceted approach to developer education, including partnerships with platforms like Udemy and LinkedIn Learning, official docs and use-cases, and content created by Docker Captains and the developer community. ⌘ Read more

Hey @sorenpeter@darch.dk, I’m sorry to tell you, but the prev field in your feed’s headers is invalid. 😅

First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.

For reference, the prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html

Thanks @prologic@twtxt.net, I also just manage to get my own version of webmentions working. Please have a read at Webmentions vs. Custom Mentions Spec for Twtxt/Yarn - HedgeDoc and User Lookup for Twtxt/Yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc for how it sorta works

Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc

I’ve gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads

Ignite Realtime Blog: Openfire 4.8.1 Release
The Ignite Realtime Community is pleased to announce the release of Openfire 4.8.1. This release addresses a number of issues found with the major 4.8.0 release a few months back.

Interested in getting started? You can download installers of Openfire here. Our documentation contains an [upgrade guide](https://download.igniterealtime … ⌘ Read more

ProcessOne: Automatic schema update in ejabberd
ejabberd 23.10 has a new feature that is currently in beta testing:

Automatic relational schema creation and update.

Previously, if you were using ejabberd with an external relational database, you might have to manually apply some schema changes that come with new features when you upgrade to a new ejabberd release. ejabberd can now handle this schema upgrade automat … ⌘ Read more

ProcessOne: Automatic schema update in ejabberd
ejabberd 23.10 has a new feature that is currently in beta testing:

Automatic relational schema creation and update.

Previously, if you were using ejabberd with an external relational database, you might have to manually apply some schema changes that come with new features when you upgrade to a new ejabberd release. ejabberd can now handle this schema upgrade automat … ⌘ Read more

@eapl.me@eapl.me I have many fond memories of Turbo pascal and Turbo C(++). They really did have a great help system. And debug tools! Its rare for language docs to be as approachable. QBasic was great. As was PHP docs when I first came into web.

@eapl.me@eapl.me I have many fond memories of Turbo pascal and Turbo C(++). They really did have a great help system. And debug tools! Its rare for language docs to be as approachable. QBasic was great. As was PHP docs when I first came into web.

ProcessOne: Automatic schema update in ejabberd
ejabberd 23.10 has a new feature that is currently in beta testing:

Automatic relational schema creation and update.

Previously, if you were using ejabberd with an external relational database, you might have to manually apply some schema changes that come with new features when you upgrade to a new ejabberd release. ejabberd can now handle this schema upgrade automat … ⌘ Read more

Docker Desktop 4.23: New Configuration Integrity Check, Plus Updates to Docker Init, Compose, Watch, Quick Search, and More
Docker Desktop 4.23 is now available and includes numerous enhancements, including ASP.NET support in Docker Init, Configuration Integrity Check to alert on any configuration changes that require attention, and cross-domain identity management. This release also improves Quick Search, allowing for searching across containers, apps, Docker Hub, Docs, and any volume, and performing quick actions (st … ⌘ Read more

Docker Hub Registry IPv6 Support Now Generally Available
Docker announces the general availability of IPv6 support for the Docker Hub Registry, Docker Docs, and Docker Scout endpoints. ⌘ Read more

Erlang Solutions: Unleashing the Power of SNMP: Exposing Your Embedded Elixir/Erlang (Nerves, GRiSP) Apps to the World
Did you know that Erlang/OTP ships with built-in SNMP  (Simple Network Management Protocol) support? Using SNMP is a great way to integrate your Elixir or Erlang application into an industrial environment. This will be of particular interest for those working with embedded … ⌘ Read more

Ignite Realtime Blog: Openfire 4.7.5 Release
The Ignite Realtime Community is happy to announce the 4.7.5 release of Openfire!

This release primarily addresses the issue that is subject of security advisory CVE-2023-32315, but also pulls in a number of improvements and bugfixes

You can find download artifacts [available here](https://ignit … ⌘ Read more

Still undecided between TiddlyWiki, DokuWiki, Bear, Benotes, Memos, my blog software, standardnotes, apple notes and more. I like them all quite a bit, but standardnotes, the only one that has reall multiplatform is so fucking complicated to host on your own and then they have this stupid offline subscription thing that allows rich text or the block editor that works like notion. I also found codex docs which is really really nice. Unfortunately they lack proper authentication. 1 / 2

@lyse@lyse.isobeef.org @prologic@twtxt.net it seems like the ssl verification works now, I enabled it - but also added another option as well that I now saw in the docs, and now it did not fail on my end (which it did before). I will add a ‘enable ssl verification’ checkbox (checked by default) so that those who do not need or want it for testing and such can disable it if they want.

💭 While some people like to jump between blogging software all the time, or go back to Hugo from a custom one, I don’t really miss Hugo after switching to GoBlog in 2020, but enjoy having my own system quite a bit. Not that Hugo, WordPress, etc. are bad blogging systems, but I really enjoy being able to quickly code a fix without having to research docs, StackOverflow, or the source on GitHub. And when I have an idea for a new feature, it would often not be easy to implement in the existing systems. ⌘ Read more

Ignite Realtime Blog: Spark 3.0.2 Released
The Ignite Realtime community is happy to announce the availability of Spark version 3.0.2

The release contains bug fixes and updates two plugins Translator and Roar.

Many Spark translations are incomplete. Please help us translate Spark

Full list of changes can be found in the changelog.

We encourage users and developers to get invo … ⌘ Read more

GitHub Copilot X: The AI-powered developer experience
GitHub Copilot is evolving to bring chat and voice interfaces, support pull requests, answer questions on docs, and adopt OpenAI’s GPT-4 for a more personalized developer experience. ⌘ Read more

Just finished writing my doc on how I’m using Parabola to export LJ to Plume https://ouvaton.link/F0KxT5

Soooo… Fltk uses @ symbol in strings to apply effects to text, now wonder I’ve been having issues with the timeline.. https://www.fltk.org/doc-2.0/html/group__symbols.html
@ is used for mentions and all that stuff, so well - it just breaks the strings in the labels.

How GitHub Docs’ new search works
GitHub Docs recently changed its site-search to Elasticsearch. Here’s how it was implemented. ⌘ Read more

How the GitHub Docs team uses GitHub Projects
Explore how the GitHub Docs team uses GitHub Projects for content coordination, reviews, and publishing. ⌘ Read more

RT by @mind_booster: Incompreensível. E a protecção de dados é uma falácia: a info sensível, como nomes, seriam omitidos antes dos docs chegarem à leitura, tal como acontece com o arquivo da PIDE, na Torre do Tombo. É simplesmente impedir acesso aos docs e dificultar o debate. https://www.publico.pt/2036491
Incompreensível. E a protecção de dados é uma falácia: a info sensível, como nomes, seriam omitidos antes dos docs chegarem à leitura, tal como acontece com o arquivo da PIDE, na Torre do Tombo. É simpl … ⌘ Read more

@abucci@anthony.buc.ci see here in the okta docs: https://developer.okta.com/docs/reference/api/webfinger/ they are adding a prefix to the acct

@abucci@anthony.buc.ci see here in the okta docs: https://developer.okta.com/docs/reference/api/webfinger/ they are adding a prefix to the acct

Tutorial: Getting started with generics - The Go Programming Language – Okay @xuu@txt.sour.is I quite like Go’s generics now 🤣 After going through this myself I like the semantics and the syntax. I’m glad they did a lot of work on this to keep it simple to both understand and use (just like the rest of Go) 👌 #GoLang #Generics

Bunny AI
Bunny.net joined the AI hype and created “Bunny AI” (docs), AI images created on the edge. I tried it out, because it’s currently free during the preview, but somehow I don’t find the generated images aesthetic or I’m just to stupid to write better prompts. I guess the Bunny developers also need some distraction from time to time, because they are working hard on S3 support for Bunny Storage for years already. 🐰 ⌘ Read more

Prosodical Thoughts: Bringing FASTer authentication to Prosody and XMPP
As our work continues on modernizing XMPP authentication,
we have some more new milestones to share with you. Until now our work has
mostly been focused on internal Prosody improvements, such as the new roles\
and permissions framework. Now we are starting to extend our
work to the actual client-to-server protocol in XMPP.

Prosody and [Snikket](https://snik … ⌘ Read more

ahh this is useful https://go.dev/doc/modules/managing-dependencies. the go culture doesn’t typically have large dependency graphs like Ruby or JS.

ahh this is useful https://go.dev/doc/modules/managing-dependencies. the go culture doesn’t typically have large dependency graphs like Ruby or JS.

Ah git-bug! Ive chatted with the creator when he was working on the graphql parts. Its working with git objects directly sorta like how git-repo does code reviews. Its a pretty neat idea for storing data along side the branches. I believe they don’t add a disconnected branch to avoid data getting corrupted by merging branches or something like that.

Ah git-bug! Ive chatted with the creator when he was working on the graphql parts. Its working with git objects directly sorta like how git-repo does code reviews. Its a pretty neat idea for storing data along side the branches. I believe they don’t add a disconnected branch to avoid data getting corrupted by merging branches or something like that.

What is NATS - NATS Docs

Might play with this at work next week.

@mckinley@twtxt.net Thank you! I didn’t even know about signing and encrypting XML documents. Right, RSS is a little bit messy.

Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.

Also, never found a good explanation why I should add <link rel="self" … /> to my feeds. I just do, but I don’t understand why. The W3C Feed Validation Service says:

[…] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.

This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn’t make sense to me.

Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/ namespace, but don’t use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I’m doing.

Your article made me reread the Atom spec and I found out, that I can omit the <author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.

Ignite Realtime Blog: Openfire 4.7.4 release
The Ignite Realtime Community is happy to announce the 4.7.4 release of Openfire. This release fixes a number of bugs and represents our effort to provide a stable 4.7.x series while work continues on the next feature release of Openfire.

Notable fixes include enhancements to cluster-specific implementation of Multi-User Chat functionality, improved websocket handling and improv … ⌘ Read more

Unboxing fork improvements and unwrapping fork docs
We’re always trying to improve the GitHub developer experience in meaningful ways, and we love learning from our customers. In the last several months we released several new fork capabilities, and we’re publishing revised fork documentation that gives more details with clearer explanations to make fork concepts easier to understand. ⌘ Read more

** uxn exit **
This evening I sat down on the couch sleepy. We’d just gotten the kids into bed. I hadn’t planned on writing any code but figured I’d round the evening out with some reading.

First I read through the docs and glossary of uf, a forth system for uxn. Then I read through an example program provided by uf.

…with my palette whetted I [re-visited some other forth documentation](https://eli.li/_assets/bin/P … ⌘ Read more

Today I found on HackerNews a federated ‘Reddit’ 🤔
https://join-lemmy.org/docs/en/index.html

Ignite Realtime Blog: Openfire 4.7.3 released
The Ignite Realtime Community is pleased to announce the release of Openfire version 4.7.3. This version brings a number of bug fixes and other improvements and signifies our efforts to produce a stable 4.7 series of Openfire whilst work continues on the next feature release 4.8.0.

You can find download artifacts on our website with the fol … ⌘ Read more

Ignite Realtime Blog: Openfire 4.7.2 released
The Ignite Realtime Community is pleased to announce the release of Openfire version 4.7.2. This version fixes a number of bugs and signifies our efforts to produce a stable 4.7 series of Openfire whilst work continues on the next feature release 4.8.0.

A major highlight of this release is fixing of BOSH bugs found under load testing.

You can find [download artifacts](https://ign … ⌘ Read more

Hmm, @prologic@twtxt.net / @lyse@lyse.isobeef.org: Should we remove the section “Traditional Human-Readable Topics” from the spec? Or mark is as deprecated? I haven’t seen this being used in the wild for years. 🤔

@chronolink@chrono.tilde.cafe Replies are not part of the original twtxt format. They were added later as an extension by Yarn.social: https://dev.twtxt.net/doc/twtsubjectextension.html (only the section “Machine-Parsable Conversation Grouping” is used these days)

Look at the twtxt.net api: https://dev.twtxt.net/doc/api.html

https://book.keybase.io/docs/chat/crypto

https://book.keybase.io/docs/chat/crypto

Ignite Realtime Blog: Openfire 4.7.1 Released!
The Ignite Realtime Community is happy to announce the 4.7.1 release of Openfire. This release fixes a number of bugs and represents our effort to provide a stable 4.7.x series while work continues on the next feature release of Openfire.

Notable fixes include security updates to bundled database drivers, logging configuration fixes, and an important fix for users experiencin … ⌘ Read more

so I may have farked up twtxt on oh.mg when I started moving docs, if you can see this the new version is at https://txt.om.gay/twtxt.txt

Go 模糊测试

• 原文地址： https://tip.golang.org/doc/fuzz/
  
• 原文作者：Go Team
  
• 本文永久链接：https:/github.com/gocn/translator/blob/master/2022/w01_Go_Fuzzing.md
  
• 译者： fivezh
  
• 校对： zxmfke
  

从 Go 1.18 版本开始，标准工具集开始支持模糊测试。

模糊测试（Fuzzing）是一种自动化测试方法，通过不断地控制程序输入来发现程序错误�� … ⌘ Read more

Ignite Realtime Blog: Openfire 4.5.6 is released
Openfire 4.5.6 has been released, that addresses an annoying issue that was affecting the earlier 4.5.5 release. We’ve updated the bundled log4j library to version 2.17.1 for good measure.

The changelog denotes the two Jira issues closed by this release. You can find Openfire build artifacts available for download [here](https://github.com/igniterealtime/Openfire/rel … ⌘ Read more

教程：如何开始使用泛型

• 原文地址： https://go.dev/doc/tutorial/generics
  
• 原文作者：go.dev
  
• 本文永久链接： https://github.com/gocn/translator/blob/master/2021/w49_Tutorial_Getting_started_with_generics.md
  
• 译者： zxmfke
  
• 校对： cvley
  

目�� … ⌘ Read more

Ignite Realtime Blog: Openfire 4.7.0 beta & Hazelcast plugin 2.6.0 releases!
After a long few months full of hard work, we are happy to tell you that we are close to a 4.7.0 release for Openfire!

This next version of our real time communications server has received a lot of improvements and bug fixes.

A key area of the code that has received updates is the Multi-User Chat (MUC) impl … ⌘ Read more

Looking for a Docker Alternative? Consider This.
Docker recently announced updates and extensions to our product subscriptions. Docker CEO Scott Johnston also posted a blog about the changes. Much of the discussion centered on what the licensing changes mean for users of Docker Desktop, which remains free for small businesses and several other user types, but now requires a paid subscription — starting […]

The post [Looking for a Docker Alternative? Consider This.](https://www.doc … ⌘ Read more

Did we ever address code snippes in doc as “here-code” ?

Chatcontrol, searching messages for illegal content
On July 6 the EU parliament voted yes to a proposal from the EU\
commission (PDF) on a temporary law to allow services to automatically
search messages for suspicious content with a focus on child
exploitation.

We have quite strict confidentiality laws within EU even when it comes
to electronic communication. Its current basis is the … ⌘ Read more

How we use GitHub Actions to manage GitHub Docs ⌘ Read more…

Go 1.16 is released ⌘ Read more…

Really looking forward to the release of Go 1.16

Want to run my own instance of twtd. (Gets head down in docs.) In other news, I got a raise and a bonus today!

Want to run my own instance of twtd. (Gets head down in docs.) In other news, I got a raise and a bonus today!

Did some work on WKD handling. Can update keys with HKP posts :) Ugh need to work on docs and unit tests. Boooorrring.

Did some work on WKD handling. Can update keys with HKP posts :) Ugh need to work on docs and unit tests. Boooorrring.

can someone ELI5 how to set up hugo with drone CI? i tried the docs but i couldn’t get it to work. drop me an email or find me on irc. details on my website

i like hugo a whole bunch, i just wish the docs didn’t make me go UGH sometimes

How we open sourced docs.github.com ⌘ https://github.blog/2020-10-14-how-we-open-sourced-docs-github-com/

initial ugens page added to !monolith wiki, with link to woven ugens scheme file. the first non-C woven file in monolith. [[/proj/monolith/wiki/ugens]]. #docs #updates

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

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

Launching docs.github.com ⌘ https://github.blog/2020-07-01-launching-docs-github-com/

How we launched docs.github.com ⌘ https://github.blog/2020-07-02-how-we-launched-docs-github-com/

https://t2bot.io/docs/2020-matrix-org-lag/ Some confirmation why I prefer the good ‘ol (actually it’s improving to current demands all the time) #XMPP and don’t switch to the fancy new kids in town like, currently, #MATRIX.

Parapsychology in the PRC 1979-1989 https://www.cia.gov/library/readingroom/docs/CIA-RDP96-00789R002600290003-0.pdf

Dr. Alan Kay on the Meaning of “Object-Oriented Programming” http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay_oop_en

OFFICIAL TRAILER - IN SEARCH OF DARKNESS - THE DEFINITIVE ‘80s HORROR DOC - YouTube https://www.youtube.com/watch?v=9AKnO2hr7b0

Systems Software Research is Irrelevant (aka utah2000 or utah2k) http://doc.cat-v.org/bell_labs/utah2000/utah2000.html

Cyberfeminist Index (~1990s-present) - Google Sheets https://docs.google.com/spreadsheets/d/1q_ZlbZhstBTfnZL4QP11ebivXgsvrf8shuG-QX146nw/edit#gid=1949020646

riptide/guide.adoc at master · sagebind/riptide · GitHub https://github.com/sagebind/riptide/blob/master/docs/guide.adoc

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

From Satori to Silicon Valley https://web.stanford.edu/dept/SUL/sites/mac/primary/docs/satori/machines.html

From Satori to Silicon Valley https://web.stanford.edu/dept/SUL/sites/mac/primary/docs/satori/taste.html

From Satori to Silicon Valley https://web.stanford.edu/dept/SUL/sites/mac/primary/docs/satori/organic.html

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

Acid: A Debugger Built From A Language http://doc.cat-v.org/plan_9/4th_edition/papers/acidpaper

Native Kernel Debugging with Acid http://doc.cat-v.org/inferno/4th_edition/kernel_debugging/

Acid Manual http://doc.cat-v.org/plan_9/4th_edition/papers/acid