sirjofri @sirjofri@mastodon.sdf.org

peak hn

Plan9 is the only operating system that impressed me with the “text as a user interface” concept

@peregrine @cancel plan9 is the only actively developed thing that I know that can do it in an orderly manner..

> The SSH protocol allows clients to make outgoing TCP calls via the server. Sshnet establishes an SSH connection and, rather than execute a remote command, presents the remote server's TCP stack as a network stack (see the discussion of TCP in ip(3)) mounted at mtpt (default /net), optionally posting a 9P service descriptor for the new file system as /srv/service.

owo http://man.cat-v.org/plan_9/1/ssh

Been after that one for a while but I finally managed to run a #RaspberryPiOS in a virtual machine using #qemu.

Oh neat I can somewhat use drawterm from the phone #plan9

Throwing USB sticks across the boat to each other's desks is still the fastest way we found to transfer videos between devices.

builds.sr.ht completed it's 30,000th job today

3D printed a 2.5" HDD rack for my Raspberry pi Syncthing server. #theWorkshop

Spent a bit of time tonight to improve mothra compatibility of XXIIVV.
#plan9

There is not enough Glenda fan art, commissioning a friend

Vim: avoid plugins. Don't turn it into an IDE. Unix is your IDE and Vim is your editor.

Of my plugins, the only ones which don't add more language support are:

Fugitive, exclusively for :Gblame

Ctrl-P

vim-surround

editorconfig

hilinktrace, which helps with designing/modifying color schemes

@glenda I've written a sample fs that might help with figuring things out, along with careful reading of the section 5 and 9p(2): http://src.a-b.xyz/rngfs

If it feels a bit too much I suggest you look a few commits back before I added write support, it was still simpler then. Eventually I'll have both the lite and full versions, with generous comments.

There's also /sys/src/lib9p/ramfs.c but its usage of 9pfile(2) obstructs a lot of important stuff.

"Truly, we live in an era of print-worthy web design," I say, just before toggling to Reader View.

Quick reminder (or clarification) about the workflow on SourceHut

GitHub has trained you to open issues for *everything*, including support requests, asking questions, feature requests, bug reports, and so on.

On SourceHut, you should not do this. We have mailing lists, and your first stop should be a project-discuss or project-users mailing list. Only when you have confirmed that you have a new bug or accepted feature request should you file a ticket on the bug tracker. This prevents clogging up the bug tracker with duplicate or poorly thought-out tickets, and usually gets you better support for your problem too.

Thinking about changing the default permissions for trackers to prohibit public posting to re-enforce this.

Displaying fresh toots under #9front
Totally slow, unoptimized and ugly but well that's a start

Paraphrasing something I said on a GNU mailing list about SourceHut's "alpha" status:

The alpha and beta milestones are how we're driving the software well above and beyond the levels of quality typical of our domain. Today, during the alpha, sourcehut is *already* the fastest and most reliable software forge, period. But we're not impressed by the competition, which is why I set our goals even higher, and why it's still considered in alpha.

dynamic linking was a MISTAKE

So in case you didn't know there are a bunch of cool Plan 9-related projects on sr.ht

Digital audio workstation
https://sr.ht/~ft/pipewave/

Music player
https://sr.ht/~ft/zuke/

AV1 video player
https://sr.ht/~ft/treason/

git9
https://git.sr.ht/~ori/git9

Fennel port
https://git.sr.ht/~raingloom/fennel

Bunch of stuff from ~kvik
https://git.sr.ht/~kvik