web3.py VS websocat

you can also write your own key generator using web3.py (https://github.com/ethereum/web3.py, see this part of the docs https://web3py.readthedocs.io/en/latest/web3.eth.account.html#creating-a-private-key)

I understand from literally the only other thread about this on the internet (https://github.com/ethereum/web3.py/issues/879) that web3 removed 'KeepAliveRPCProvider' from newer versions. Is there a fix for this or is this tool obsolete now?

There's also Github where many people have posted open source projects such as this: https://github.com/ethereum/web3.py

Basically I’m trying to do what nueverest is trying to do here: https://github.com/ethereum/web3.py/issues/685

True but there is a decent amount of support for Python when it comes to Web3 (Web3.py for example). Plus, Python is a great starting language anyway

link to pull request where tests were added (issue #2056)

Another thing you might consider is web3.py. It might not be as useful as javascript libraries (web3/ethers), depending on what you plan to build, but the concepts are all the same and, again, you can leverage existing python knowledge.

It's similar to running netcat in server mode, wrapping a script. It's even closer to doing that using websocat [1], whereby one does not have to do the websocket header juggling.

The main difference is that while netcat or websocat will spawn a new process for each connecting client, ScaleSocket has a concept of rooms (channels). For a room, a process is spawned once only. All clients connecting to the same room are routed to the same process. This is not straight forward to do using the forementioned tools.

There's a small comparison page [2] where I have mentioned some alternative tools.

[1] https://github.com/vi/websocat

one combination I came to really love this year is babashka (https://github.com/babashka/babashka) + websocat (https://github.com/vi/websocat). I wrote about a method of live web programming with this pair at https://github.com/whacked/cow/blob/main/a%20technique%20for...

babashka isn't strictly necessary; you can also pipe plain text, but pushing hiccup expressions to the browser DOM from the REPL with instant feedback has opened a new world of interactive programming for me.

No... the core of it is a django instance in the cloud with a Vue front end (what you're seeing in the screen shot). To push data in, the client connects to a websocket (using https://github.com/vi/websocat) and push key/value pairs in. I'm not in the middle of gameplay at all.

There's really nothing to this. I just have to provide the bus name and an optional pattern. Now using websocat, I get output like this:

Subscriptions is real-time streaming of data from server to client through WebSocket. You will need a constantly active connection to stream such events. You cannot use curl for this and have to use a WebSocket client like websocat if you want to access it via command line. Once executed, a stream of pending transaction IDs will start flowing in.