In this videotape recorded in 1986 Frank Halasz demonstrates hypertext browsers and other types of cards of NoteCards, the hypermedia system he co-developed in Interlisp at Xerox PARC.
https://archive.org/details/Notecards_Examples_Frank_Halasz_LSL
In this videotape recorded in 1986 Frank Halasz demonstrates hypertext browsers and other types of cards of NoteCards, the hypermedia system he co-developed in Interlisp at Xerox PARC.
https://archive.org/details/Notecards_Examples_Frank_Halasz_LSL
Exciting news! The Call for Papers #CfP for the #HUMAN25 Workshop on Human Factors in #Hypertext is now open. We invite researchers to submit their work to this event, part of the ACM Hypertext Conference #HT2025 @ht in Chicago. Looking forward to your contributions. Spread the word!
→ https://human.iisys.de/human25/call-for-papers/
"Real-Time History: Engaging with #LivingArchives and Temporal Multiplicities." After a great start yesterday, the conference resumes with a workshop on web archives and the Archives Research Compute Hub by Karl Blumenthal.
Thrilled that I will be able to present my paper "Weaving Time: Hypertextual Historiography in the Age of Living Archives" later in the afternoon.
Check out the conference program: https://www.ghi-dc.org/events/event/date/real-time-history-engaging-with-living-archives-and-temporal-multiplicities
#DigitalHistory #DH #Hypertext
Hyperland, by Douglas Adams, with Tom Baker as the computer!
https://archive.org/details/DouglasAdams-Hyperland
#hypertext #hyperland #hhgttg
The NoteCards hypermedia system was developed in Interlisp at Xerox PARC by @fghalasz Frank Halasz, Tom Moran, and Randy Trigg. In this 1985 videotape Moran introduced the main concepts of NoteCards, and Halasz demonstrated how to use the system to organize notes and sources for writing a research paper.
https://archive.org/details/Xerox_PARC_Notecards_Tom_Moran_and_Frank_Halasz_1985-01-08
In einem internationalen #Horizon -Projekt sollen wertvolle Kulturerbe-Stätten als „digitale Zwillinge“ bewahrt, in 3DWelten erfahrbar gemacht und mit Hilfe von Simulationen besser erhalten werden können.#HochschuleHof #Weltkulturerbe #Hypertext #Science
https://nachrichten.idw-online.de/2025/03/03/digitale-werkzeuge-zum-schutz-des-globalen-kulturerbes
Anyone knows why the HTML versions of IETF RFCs are insisting on replicating the (unnecessary) page breaks from the plain text version? Also apart from being able to jump to bibliography and to document sections from the TOC, why aren't the HTML versions making proper use of internal hyperlinking? Feels like a grand missed opportunity to make these specs a lot more usable? Especially hard to use when trying to implement vs just using an RFC for a quick consult/check...
Thinking Annotated Bibliography in Author.
by Frode Hegland
@doriantaylor Intertwingler
For those who came in late:
“Intertwingler was designed primarily as a substrate for communicating complex topics. It’s made to maximize linking between small pieces of information, in a style called dense hypermedia. This helps you gain comprehension while only having to read the parts you need to.
To achieve this effect… links managed by Intertwingler never break.”
#hypertext
https://intertwingler.net
And (Aug 2023 video)
https://youtu.be/d5-lcvKfBM4
Douglas Engelbart
Born 100 Years Ago Today
30 Jan 1925
“By ‘augmenting human intellect’ we mean increasing the capability of a man to approach a complex problem situation, to gain comprehension to suit his particular needs, and to derive solutions to problems.” — Douglas Engelbart (1962)
An essay on Engelbart’s motivation, with links to video and other historical sources on his life and work.
#Engelbart #hypertext #botd
https://tractionsoftware.com/traction/permalink/Blog2386
Bluesky links are obfuscated?! (No indication of user or anything.) Is this a security measure? Genuinely curious.
(Back in the day, we *liked* it when a URL said something about what you were about to click on. Avoids getting rick-rolled and such like.)
One of the yet-unexplored features of XTXT is its potential to multiplex multiple HTTP connections over a single serial link—without relying on TCP/IP.
In the past, we had solutions like PPP (and later PPPoE), which allowed network-layer communication over point-to-point connections. But those were fundamentally data link layer protocols, operating at a lower level in the OSI model.
XTXT, on the other hand, can be thought of as an application-layer alternative for achieving similar multiplexing, but with much lighter networking demands. It’s designed to work seamlessly on smaller systems by simply exchanging text streams—no need for OSI compliance or the overhead of traditional networking stacks.
With XTXT, all you need is the ability to send and receive structured text. And most computers, even very old ones can do that. The simplicity is the beauty.
XTXT update: fixes minor ROM and RAM problems with bank handling in ZX Spectrum +3
https://github.com/ha1tch/xtxt/tree/main/code/asm/zxspectrum
XTXT: count-frames: A very simple routine that counts the number of frames in a multiplexed text file.
Implemented for:
ZX Spectrum +3 - Zilog Z80
https://github.com/ha1tch/xtxt/blob/main/code/asm/count-frames-zxspectrumplus3.z80.asm
Commodore Amiga - Motorola 68000
https://github.com/ha1tch/xtxt/blob/main/code/asm/count-frames.amiga.68k.asm
IBM PC/MS-DOS - Intel 8086
https://github.com/ha1tch/xtxt/blob/main/code/asm/count-frames.ibmpc.8086.asm
Atari 800XL - MOS 6502
https://github.com/ha1tch/xtxt/blob/main/code/asm/count-frames.atari800xl.6502.asm
Atari ST/TOS - Motorola 68000
https://github.com/ha1tch/xtxt/blob/main/code/asm/count-frames.atarist.68k.asm
XTXT slides that show the basic elements of it visually:
https://github.com/ha1tch/xtxt/tree/main/slides
I also started work on muxcat.c but it doesn't really work yet and it's buggy as hell.
https://github.com/ha1tch/xtxt/blob/main/code/c/muxcat.c
XTXT Update: I added the utility muxcat (like unix 'cat', but for multiplexed, extended text files)
Three different implementations (Ruby, Python, Go). Still very much work in progress, they almost work.
ruby
https://github.com/ha1tch/xtxt/blob/main/code/rb/muxcat.rb
python
https://github.com/ha1tch/xtxt/blob/main/code/py/muxcat.py
go
https://github.com/ha1tch/xtxt/blob/main/code/go/muxcat.go
Another XTXT update: I added some initial support for various retro platforms. Let me know if you find any errors in the code for your platform of choice! I'm mostly testing against a couple of emulators and the hardware I have.
https://github.com/ha1tch/xtxt/tree/main/code/asm
I did more work on XTXT, adding some very simple code examples in other languages: C, Assembler (Z80 and 8086), Pascal, Go, Python, Ruby, Swift.
https://github.com/ha1tch/xtxt/tree/main/code
(the old and dirty Ruby samples are still available under the ruby.old directory, until we have newer and better ones)
Notably, the Z80 Assembler version of the most basic example compiles to a binary of just under 70 bytes. I used PASMO to assemble it. (if you need to compile Pasmo itself from source like I did on Apple M1/arm64, ensure that you add -std=c++17 to the CXXFLAGS variable in the generated Makefile)
XTXT update: Added a new article explaining the benefits of using it.
https://github.com/ha1tch/xtxt/blob/main/intro/xtxt-why-use-it.md