The "Audio Messaging System" is described here: https://www.we-teve.com/watch/lPHnZn7P

Better microphone from 32:16 onwards.

0:00 Origin and background of the "Audio Messaging System"
3:23 Origin of the reply-tree, and that a visual indicator for recording in progress is needed
5:34 Handling of device access permissions in the browser
9:28 Update: Can't request permanent device access permission in the browser, recording indicator
14:15 Progressive Web App (PWA) for mobile
17:14 Notifications
18:45 Asynchronous audio messaging as generalized capability
22:04 Audio for/with Augmented Reality
24:54 Potential of asynchronous discussions and conversation
32:16 Hypermedia and annotations in/with/on audio
35:03 User management, grouping messages into "rooms"
38:41 Origin of the tree navigation: tooling attempt for media/content curation
42:06 Tree vs. graph for navigation and curation
47:46 Flat room list instead of an ever-branching tree to hold messages
51:20 Deletion of recordings
53:41 Playback issues with mobile browser: custom audio player needed for playback on mobile
59:52 Audio (speaking/listening: passive) more convenient than text (writing/reading: active)
1:05:08 Phone box, answering machines, voicemail
1:06:34 Re-use of recordings (clips, snippets)
1:09:12 Provisional replacement of the tree with a flat list of rooms
1:12:16 Audio annotations on computer program source code?

Browsergame technology.

Browsergame-Techniken.

First steps of 2D graphics + animation programming with JavaFX and HTML5 canvas for graph visualization and editing.

Code: https://gitlab.com/publishing-systems/experimental/-/tree/master/graph/

Booting MINIX 3.1.2a.

Pixel graphics for Microsoft Excel in VBA (implementing Bresenham’s line raster algorithm).

Pixel graphics for Microsoft Excel in VBA (implementing Bresenham’s line raster algorithm).

Shutdown Button.

Parsing and interpreting tokens from the input for semantical analysis in order to affect and drive control flow.

Small example of ViewSpecs as found in Douglas Engelbart’s NLS and Augment.

This XML file does not appear to have any style information associated with it. The document tree is shown below.

“Interactive Tero” ist ein interaktiver Parsergrammatik-“Debugger”, aber bisher noch nicht zu einem Editor ausgebaut.

Mock-up of hypertext tool/capability use.

Ein einfacher, kleiner Web-“Browser” (eigentlich besser: Viewer).

https://gitlab.com/skreutzer/geoar

Loading (deserializing) structured input data into computer memory as an implicit chain of tokens in order to prepare subsequent processing, syntactical/semantical analysis, conversion, parsing, translation or execution.

Choices for the design of data or text structuring inline by reserving regular or special characters or sequences of such to act as a separator/delimiter/marker.

Basic model, concept and technique to read symbols (might be characters, numbers, signals, any kind of pattern/symbol) from an input source, which might be a database, a file on the disk, a data packet incoming from the network, a measure by a sensor, or a key typed by the user. Focus is on how to organize loop iterations and handling, processing, reaction to the sequence of input data arriving within or requested by your own software application code.

This shows a very simple experiment exploring 2D drawing. Rendered with code in Java.

https://gitlab.com/publishing-systems/digital_publishing_workflow_tools/-/tree/master/htx/gui/hyperdex/hyperdex_1

Welcome to the BAC Language, which isn’t a programming language yet, or
might never be. The syntax and concept is not my invention, but stolen
from somebody who didn’t want to be remembered in history and is also
not alive any more. All the books about it are long out of print, so I
simply try to implement one limited description of a bunch of its
features, therefore BAC may show differences in comparison to the
original inspiration. The implementation is even more off, caused by
lazy repurposing of other code I happened to have. As I’m writing
parsers for some domain-specific languages (text-oriented formats)
anyway, it turned out to be a relatively small step to advance into
developing an interpreter potentially for an interactive programming
environment. Maybe a little bit like LISP or Smalltalk? Not crazy enough
to consider writing a compiler.

This recording hopefully offers an overview about what “application programming interfaces” are, what role they play in the system architecture of computer software, as well as discussing the question if APIs should be copyrightable, as there’s a long legal battle going on of Oracle suing Google for their re-implementation of the Java “API”, and what the implications might be for the profession of computer software programmers, the field, industry and our digital future.

https://www.youtube.com/watch?v=R2Qh0O3Dt10 (in “VCF West XIII -- Time Paterson -- Original DOS and the old days”, Tim Paterson mentions a range of more or less different types of interfaces)

Processing workflow of the Peeragogy Monthly Wrap. Content: https://github.com/Peeragogy/Peeragogy.github.io/wiki/Wrap, Code: https://gitlab.com/skreutzer/peeragogy-monthly-wrap-experimental

An online forms generator for data entry which also handles the semantics. Code: https://gitlab.com/groupware-systems/pattern-server