fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

Currently playing around with github.com/MightyShadow702/v86 which leverages github.com/copy/v86 into DeltaChat. Effectively allowing you to run a 32 bit .iso file inside DeltaChat as a webxdc application.

Right now tcp/ip is wired up with realtime communication over iroh 💥 🧠

x86 emulator for Webxdc based on Copy's v86 emulator - MightyShadow702/v86Emu-webxdc
GitHubGitHub - MightyShadow702/v86Emu-webxdc: x86 emulator for Webxdc based on Copy's v86 emulatorx86 emulator for Webxdc based on Copy's v86 emulator - MightyShadow702/v86Emu-webxdc

@rtn you have something working already?

@liaizon @rtn
Yes, networking works, we have a LAN in and can chat with netcat/telnet and ping each other

@liaizon @rtn @delta
Here is a running in v86Emu . Chatting over telnet with @hpk running netcat in @alpinelinux on the other side.

@link2xt
Do I understand it correctly that the two virtual machines that are running in a v86 webxdc app are communicating via a virtual network that's essentially a p2p pipe between two deltachat users?

Now that sounds like a good application for plan 9 (or even inferno. Did you know that inferno had an old IE Plugin to make it work in a browser?)
@liaizon @rtn @delta @hpk @alpinelinux
l

@sirjofri Here I got to boot after enabling ACPI and switching to "hdd (img)" booting mode instead of "cdrom (iso)" even though I am booting an .iso

@sirjofri
Networking works, but I don't know much about plan 9 to start any network services or mount stuff with 9p.

@link2xt
That's probably good enough for any plan 9 user out there, I guess.

Incredible work!

I think someone should work on an inferno port to webxdc, as that's more what inferno is intended to be (running apps natively), though I can imagine the following scenario:

One 9front machine as the server, which is part of the realtime message network via webxdc or some bot. This one provides services all the time.

Users can start different webxdc/inferno apps, with inferno using 9p to directly interact with the 9front server.

That is, inferno and 9front use a standard network connection tunneled through the realtime message protocol, but they don't notice it. That means, multiple users can be part of the same plan 9 network without specific VPN and router setup.

Are there limitations to that realtime message protocol? I remember people sometimes had issues with P2P connections in the browser (I don't remember the exact technology used there, but the issue was around the provider they used, not sure if that applies here, too)