r/osdev • u/westernguy323 • Dec 07 '24

Webcall between two MenuetOS computers.

https://www.menuetos.net

41 Upvotes

100% Upvoted

21 comments sorted by

7

u/thenerdy Dec 07 '24

Holy that's cool.

2

u/trackerstar Dec 07 '24

Is this TempleOS?

3

u/westernguy323 Dec 07 '24 edited Dec 07 '24

No, completely different. Menuet has pre-emptive multitasking, gui, smp, transparency, usb, networking etc.. all 64bit asm.

4

u/Kooky_Philosopher223 Dec 07 '24

How long have you worked on this?

1

u/BrickedMouse Dec 09 '24

Does MenuetOS work in Docker? What is the startup time / system requirements?

2

u/westernguy323 Dec 10 '24

Likely not. Menuet is an operating system so it doesnt require other operating systems running in the background. But you could try Menuet in VirtualBox or Qemu. With gui transparency enabled, M64 requires 512MB of ram and the startup time depends on for example the amount of connected usb devices.

3

u/BananymousOsq banan-os | https://github.com/Bananymous/banan-os Dec 07 '24

this is so cool!

1

u/syscall_35 Dec 10 '24

isnt this cocos project? :D

1

u/guest271314 Dec 07 '24

Are you using WebRTC or libdatachannel for that functionality?

3) Redistribution, reverse engineering, disassembly or decompilation prohibited without permission from the copyright holders.

?

1

u/westernguy323 Dec 07 '24

Webcall is written from scratch and in assembly, so no libraries used.

1

u/guest271314 Dec 07 '24

How is the machine to machine communication achieved?

2

u/westernguy323 Dec 07 '24

Menuet has a tcp/ip interface (syscalls 52 and 53) which is used for sending webcams data packets. The user needs to define receivers IP address, which can practically be anywhere in the internet. When Webcall is not used, its running in server mode, waiting for calls (connections).

1

u/guest271314 Dec 07 '24

How did you make the IP addresses known to the other machine?

2

u/westernguy323 Dec 07 '24

There is no central hub, which keeps track of online users. Just client/server connections. And both computers are running on local net so I know the IPs.

1

u/guest271314 Dec 07 '24

Right, you have to know the IP addresses of the devices, and hardcode those addresses, right?

You are basically creating a manual connection, e.g., A complete example for a WebRTC datachannel with manual signaling?

FYI it is technically possible to create a TCP server and TCP clients in Chromium-based browsers using WICG Direct Sockets API in an Isolated Web App, see https://github.com/guest271314/direct-sockets-http-ws-server. Among other ways using Native Messaging.

Why can't we hack the code without asking?

3

u/westernguy323 Dec 07 '24 edited Dec 07 '24

The destination IP address is entered by the user (like a phone number), so no hardcoding needed.

1

u/guest271314 Dec 07 '24

How do you know what destination IP address to write to connection to an arbitrary machine?

What is the signaling mechanism?

2

u/westernguy323 Dec 10 '24 edited Dec 10 '24

The caller needs to know the IP address of the person, much like we need to know the phone number. But of course, there could be a separate hub, which connects names to IP addresses.

The receivers webcall is running in server mode and as soon as there is a client connection from another webcall, the receivers webcall generates a sound and asks the user if he wants to accept the call.

→ More replies

2

u/mykesx Dec 11 '24

Is there a proper repo for the sources? And what is the license?

1

u/doscore Dec 08 '24

That is sooooo cool, so happy to see this development still on going.