Socket.computer

From Computernewb Wiki
Revision as of 03:19, 17 May 2022 by Dartz (talk | contribs) (1 revision imported: Old Computernewb Wiki Archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
This article/section contains info about defunct content.

socket.computer was a website which was similar to CollabVM. The site was part of the many demos available on socket.io.

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.
  • socket.computer reset every 15 minutes. The component which made the VM reset every 15 minutes was not enabled.
  • socket.computer does not have a chat box.
  • Several vulnerabilities were fixed.

Shutdown

  • October 9, 2016: Socket.computer stopped responding after the initial 15 minute reset, and did not return. This also affected socket.io's chat and weplay.io. This makes October 9, 2016 at 11:25 PM (EST) the last known time socket.computer was online.
  • March 5, 2017: After socket.io was offline for several weeks, the site finally came back up, but with the demos page missing from socket.io entirely. This can be presumed as the official "shut down" date.
  • March 18, 2017: The demos page returned to socket.io. The socket.io chat made a return, and a brand new demo, a "collaborative whiteboard", was added. Weplay.io and Socket.computer did not make a return.
  • August 2017: Socket.computer and Weplay.io stopped responding entirely, which indicates that both projects were shut down and will probably not make a return.
  • January 2018: Weplay.io no longer belongs to any IP addresses. This strongly indicates that the Weplay.io project has permanently been closed. Socket.computer, however, still belongs to an IP address although the site has not responded since March 5, 2017. Whether it officially returns or not has yet to be seen.
  • July 2018: Socket.computer no longer belongs to any IP address, which strongly indicates that the project has been closed permanently.
  • August 25, 2018: Socket.computer's domain expires and is now up for sale, which confirms that the project will not return.
  • February 2019: Socket.computer now redirects to a parked domain.
  • February 2020: Parked domain is not renewed, and socket.computer is now for sale

CollabVM has several virtual machines, including one known as "VM 2" that runs Windows XP SP3. It has almost the same specifications as the socket.computer VM (has more RAM and a better CPU), but it is much faster and has several things like Microsoft Office, Firefox, Chrome, all Windows XP Themes, a patched MSN Messenger, and more all pre-installed. If you are looking for a socket.computer alternative, you will want to check it out.

Revival?

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

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