Socket.computer

This article/section contains info about defunct content.

socket.computer is a website which similar to CollabVM. The site, in its original run, was formerly part of the many demos available on socket.io's demos.

CollabVM used the socket.computer engine for CollabVM v1.0, but there were some notable changes.

• CollabVM's design differed from socket.computer's.
• socket.computer ran Windows XP while CollabVM ran many different operating systems, which ranged from Windows 95 OSR2 to Windows 7 Ultimate.
• CollabVM did not have the laptop image present, and was scaled fully.
• CollabVM had a chatroom added
• socket.computer reset every 15 minutes. The component which made the VM reset every 15 minutes was not enabled.
• Several vulnerabilities were fixed.

CollabVM has several virtual machines, including one known as "VM 2" that runs Windows XP SP3. It has basically the same specifications as the socket.computer VM (barring more RAM and a far better CPU), but it is much faster and has many more programs preinstalled. If you are looking for a socket.computer alternative, you will want to check it out.

Original timeline

The original socket.computer ran from ~April 2014 to October 2016.

• October 9, 2016: socket.computer freezes, and the server stops responding. This outage also affected socket.io's chat, as well as weplay.io. This makes October 9, 2016 at 11:25 PM (EST) the last known time socket.computer and weplay.io were online.
• February 19, 2017: socket.io goes offline for unknown reasons.
• March 5, 2017: After socket.io was offline for several weeks, the site came back online, with the demos page missing from socket.io entirely. socket.computer and weplay.io remain in a frozen state.
• March 18, 2017: The demos page finally returns to socket.io. The socket.io chat makes a return, along with a brand new demo, a collaborative whiteboard. weplay.io and socket.computer are removed, so this can be declared the "official" shut down date for both projects.
• Sometime in August 2017: socket.computer and weplay.io's web server stops responding. Pings also fail.
• Sometime in early January 2018: weplay.io no longer belongs to an IP address, indicating the project has been permanently closed. socket.computer still belongs to an IP address at this point, although the site's IP had not responded to any pings since August 2017.
• Sometime in July 2018: socket.computer no longer belongs to any IP address.
• August 25, 2018: socket.computer's domain expires and is now up for sale, confirming the project is permanently closed.
• February 2019: socket.computer now redirects to a parked domain.
• February 2020: Parked domain is not renewed, and socket.computer is now for sale.

The return of socket.computer

• 11:11:16AM EST February 6th, 2020: Dartz purchases the socket.computer domain.

While socket.computer had effectively been sitting in limbo for about 4 years, on April Fools Day 2024, that all changed.

As an April Fools Day joke, the CollabVM site was redirected to socket.computer under the guise that CollabVM had shut down; the socket.computer domain was then running the original socket.io-computer, running in a VM running Ubuntu 16.04 (Even then, the socket.computer code didn't like that very much and had many bugs that didn't even happen on the original site).

On April 3rd, 2024 (fairly close to the 10th anniversary of socket.computer's existence), a custom from-scratch recreation of socket.computer written in TypeScript, no longer using socket.io, was put onto the site and open sourced, and the site is now perpetually running, mostly for historical sake.

The story of socket.computer

Long ago, there was a website simply known as socket.computer, which used to be a demo for socket.io. It hosted a singular virtual machine running the Operating System Windows XP.

The site was never known for being very functional. Very frequently, it would break, the resets would stop working and months would go by before Kevin Roark fixed it.

However, on one fateful dry and cool October evening, the site came to a full stop.

It still has not been explained to this day why socket.computer was permanently shut down.

Perhaps it was the owner getting tired, or maybe, it was the endless amount of exploits.

As some people may know, the site may have been... lacking in security, severely lacking in security.

An endless amount of time they know as "Turns"?

Perhaps a direct access to the main heart and core they also call "QEMU"?

The rumor has it that the old socket.computer stopped working after one of its so called "resets" was the last thing the site had ever seen.

These resets were known to happen just only 15 minutes after one had already occurred.

And after that unknowingly last reset happened, it was the end.

The end of socket.computer.

- Calub Veim