WS = WebSockets
WSS = WebSockets Secured (SSL)
WebSocket is a computer communications protocol, providing full-duplex communication channels over a single TCP connection. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011, and the WebSocket API in Web IDL is being standardized by the W3C.
WebSocket is designed to be implemented in web browsers and web servers, but it can be used by any client or server application. The WebSocket Protocol is an independent TCP-based protocol. Its only relationship to HTTP is that its handshake is interpreted by HTTP servers as an Upgrade request. The WebSocket protocol enables interaction between a browser and a web server with lower overheads, facilitating real-time data transfer from and to the server. This is made possible by providing a standardized way for the server to send content to the browser without being solicited by the client, and allowing for messages to be passed back and forth while keeping the connection open. In this way, a two-way (bi-directional) ongoing conversation can take place between a browser and the server. The communications are done over TCP.
The WebSocket protocol is currently supported in most major browsers including Google Chrome, Microsoft Edge, Internet Explorer, Firefox, Safari and Opera. WebSocket also requires web applications on the server to support it.
If you do not or cannot load a telnet client like SyncTERM or mTelnet on your system to access Archaic Binary you can also get to the BBS using the website. Please note that using the official website (https://www.archaicbinary.net) to access the BBS will give you an encrypted connection. Accessing Archaic Binary using a 3rd party website or relay system will provide you with an un-encrypted connection.
Most commonly used WS (un-encrypted) sessions will come over from the fTelnet Relay system. This is a great piece of software and allows more people to access BBSes and might give unaware users access to the BBS it should be known that the traffic is not encrypted and does possibly flow through 3rd party people other then your ISP (and any ISPs between you and I).