Ideas in Computing

This document is a sort of manifesto on my thoughts about the philosophy of computing, as well as a journal of ideas for software and hardware that I'd like to build but don't have the resources to right now. It was inspired by One Hundred Ideas for Computing and there is some overlap between samsquire's ideas and mine.

Table of Contents

Software to Write

libxmpp, an XMPP client library

XMPP is the closest thing we have to a messaging protocol that doesn't totally suck, however its ecosystem is so bad that it doesn't really stand a chance of being adopted right now. One of the main reasons for this is that there are very few clients that support enough XEPs (pretty much everyting beyond basic, IRC-like chat is implemented in extensions called XEPs) to provide a really nice experience, and only one, as of the writing of this, that does them really well (Conversations on Android).

In order to remedy this I propose we create a library, ideally implemented in C for the sake of portability, that implements all the essential functionality of a modern XMPP client including group chats (MUCs), HTTP file upload, OMEMO encryption, publish-subscribe feeds, and voice and video calls. It might be a good idea to start by adapting Profanity's source code. This library could then be used to make the creation of fast, native, and feature-rich XMPP clients much easier.

Libxmpp is just one small step in my master plan to create a truly universal and user-controlled messaging platform capable of lasting the next 30 years; a synchronous analogue to email.

Yet another graphics toolkit

The state of GUI development with free software kind of sucks right now, Unless you want to use something ancient like fltk or reinvent the wheel with X or Wayland graphic primitives, you're basically stuck with QT or GTK. QT is nice because it's relatively light and pretty portable, but it's written in object-oriented C++ which dramatically reduces which languages you can use to build applications with. GTK is written in C so there are bindings to nearly every language, however it's not very portable and it's managed by the Gnome developers who treat it like their own personal playground. Both toolkits absolutely suck at backwards compatibility. Contrast this with Win32 which, while Windows only, worked just as well 20 years ago as it does today. Themeing in QT and GTK is also a huge pain.

I'd like to create a cross-platform, easily themeable (think winamp) GUI toolkit with a focus on accessibility and future-proofing, likely written in C. I know very little about how existing GUI toolkits work so this project is pretty far in the future.

As I understand it GTK and QT use a medley if boutique protocols to load themes and interface with things like screen readers and source browsers, however I think this stuff could be made dramatically simpler and easier to work with by exposing the UI over 9p, just like Plan 9's Acme text editor.

Org as a standard format for WYSIWYG documents

Recently Karl Voit started working on a formal standard for org-mode with the aim of increasing its adoption as a markup language independent of Emacs. As an avid user of org-mode – I'm writing in an org buffer right now – I would really like to be able to simply send people org files instead of exporting them to pdf or odt first.

This meshes nicely with a problem I've noticed in the FOSS side of things: an almost complete and totally lack of lightweight word processors and note-taking applications like or on MacOS. I think that this provides an excellent opportunity to create a lightweight word processor that implements most of the functionality of org-mode in a way that normal people can take advantage of.

This will take time to become a real thing, however I've started work on the initial component, a parser library and command line tool for org files, à la cmark or discount for markdown.

Peer-to-peer collaborative editing

Building off the org-mode word processor idea, it would be great if there was a totally peer-to-peer way collaborating on a document.

I'm thinking something along the lines of Atom's Teletype, but implemented in a way that Emacs users and users of our new word processor could collaborate on an org document or project without having to create an account somewhere.

Of course, being able synchronously to edit documents stored on a central server would still be a good idea, and could perhaps be adapted to make website publishing really easy, along the lines of the activitypub-based blogging systems.

It might just be a matter of exchanging ed(1) commands through a TCP socket.

Per-document chatrooms might be useful, ideally with a way to be accessed from a bog-standard IRC client for the sake of making this all work seamlessly in Emacs, Given that Emacs runs on a single thread we'd probably use an external program and just communicate with it over a socket or dbus or whatever.

Viewable With Any Browser Join the Fediverse!!! 100% mothra-compatible Powered by FreeBSD This site made with GNU Emacs

Last Modified: 2021-12-16 Thu 16:55