sec-api VS ws

Doesn't that mean that developers were profiting from a free API before? That may be fair play, but doesn't it raise ethical concerns in terms of business practices? (This guy is the GOAT of that, got rich off SEC public data)

Using this API: https://sec-api.io/ , you could get and act on new report numbers faster than any human could.

The SEC has set up 'data.sec.gov' to host RESTful APIs that deliver JSON-formatted data to external clients and to websites on SEC.gov. No authentication or API keys are required to access these APIs. Unfortunately, 'data.sec.gov' currently only provides access to Form 10-Q, 10-K, 8-K, 20-F, 40-F, and 6-K filings, but does not (yet?) provide access to Form 13F filings. However, SEC API (https://sec-api.io/) provides a relatively user-friendly query API that also includes Form 13F filings and kindly converts EDGAR filings from XML/XBRL to JSON (it does however require a key).

Before setting up a WebSocket server in Node.js, we need to install the necessary dependencies. Fortunately, Node.js has a vibrant ecosystem with various WebSocket libraries available. In this article, we will focus on using the popular ws library, which provides a simple and efficient WebSocket implementation for Node.js.

WS has a user base of 17.7 million people and over 20,000 forks. It also has clear and concise documentation, with examples and API references, to help developers understand how to integrate it into their projects.

In order to implement websockets, you can use a nodejs library named ws. It provides a fast and simple way to establish a websocket connection.

Next, you can use a library like chokidar to listen for changes in your source directory. Create a ws server, and whenever a file changes, send a message.

I use redis, sequelize and PG Listen/Notify via Robust Listeners with a websocket server coded in ws

With over 19k stars on GitHub and about 60 million weekly downloads on npm, ws is one of the most popular open-source libraries for real-time web application development

Nest supports 2 websocket platforms - socket.io and ws. We're going to be using socket.io.

I'm trying out Render.com as a potential replacement for Heroku to host and run my code, which uses Node, Express, and the ws package to connect a game made on Godot Engine and the webapp, using a Websocket connection. However, when I migrated the code over, I've noticed that the game lasts barely a quarter of the way before the server aborts the Websocket connection for literally no reason. I'm serious, it's what the log says:

If you want to learn more about WebSockets, check out the official documentation.

Making use of Web Sockets to improve server communication.