websocat
websocketd
Our great sponsors
websocat | websocketd | |
---|---|---|
10 | 14 | |
6,491 | 17,080 | |
- | - | |
6.6 | 0.0 | |
16 days ago | 6 months ago | |
Rust | Go | |
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
websocat
-
Show HN: ScaleSocket – Turn any script into a multiplayer WebSocket server
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
-
Ask HN: What was the best software that you used during 2022?
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.
- GoLogin and python/selenium
- WebSockets in Curl
- Vi/websocat: Command-line client for WebSocket like netcat or curl
-
Realtime web-based MUD monitoring and control in tintin++ and mudlet
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.
- One Liner for streaming events from one relay to another
-
Testing the Async Cloud with AWS CDK
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:
- Netcat – All you need to know
-
Exploring the methods of looking into Ethereum’s transaction pool
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.
websocketd
- Ask HN: Tips to get started on my own server
-
Pipexec – Handling pipe of commands like a single command
Somewhat related: https://github.com/joewalnes/websocketd
> websocketd is a small command-line tool that will wrap an existing command-line interface program, and allow it to be accessed via a WebSocket.
-
Structured Logging with Slog
I hadn't even considered collecting traces/spans in this way yet, and have taken the approach of "stuff outputting logs in JSON format to stderr/local file". I usually end up writing a (temporary, structured) log message with the relevant span tags, but wouldn't it would be much better to run the actual trace/span code and be able to verify it locally without the ad-hoc log message?
The prototype I built is a web application that creates websocket connections, and if those connections receive messages that are JSON, log lines are added. Columns are built dynamically as log messages arrive, and then you can pick which columns to render in the table. If you're curious here's the code, including a screenshot: https://github.com/corytheboyd-smartsheet/json-log-explorer
With websockets, it's very easy to use websocketd (http://websocketd.com), which will watch input files for new lines, and write them verbatim as websocket messages to listeners (the web app).
To make the idea real, would want to figure out how to not require the user to run websocketd out of band, but watching good ol' files is dead simple, and very easy to add to most code (add a new log sink, use existing log file, etc.)
-
Ask HN: WebSocket server transforming channel subscriptions to gRPC streams
* Additionally, client can stream data to the backend server (if bidirectional GRPC streams are used). I.e. client sends WebSocket messages, those will be transformed to GRPC messages by WebSocket server and delivered to the application backend.
As a result we have a system which allows to quickly create individual streams by using strict GRPC contract but terminating connections over WebSocket transport. So it works well in web browsers. After that no need to write WebSocket protocol, client implementation, handle WebSocket connection. This all will be solved by a suggested WebSocket server and its client SDKs.
The mechanics is similar to Websocketd (https://github.com/joewalnes/websocketd), but instead of creating OS processes we create GRPC streams. The difference from grpc-web (https://github.com/grpc/grpc-web) is that we provide streaming capabilities but not exposing GRPC contract to the client - just allowing to stream any data as payload (both binary and text) with some wrappers from our client SDKs side for managing subscriptions. I.e. it's not native GRPC streams on the client side - we expose just Connection/Subscription object to stream in both directions. GRPC streams used only for communication between WebSocket server and backend. To mention - grpc-web does not support all kinds of streaming now (https://github.com/grpc/grpc-web#streaming-support) while proposed solution can. This all should provide a cross-platform way to quickly write streaming apps due to client SDKs and language-agnostic nature of GRPC.
I personally see both pros and cons in this scheme (without concentrating on both too much here to keep the question short). I spent some time thinking about this myself, already have some working prototypes – but turned out need more opinions before moving forward with the idea and releasing this, kinda lost in doubts.
My main question - whether this seems interesting for someone here? Do you find this useful and see practical value?
-
WebSocket to TCP bridge for game servers? Alternative to websockify?
I also used to use this (http://websocketd.com/) along with netcat(1) before just biting the bullet and writing my own websocket library for our server as we needed to scale up slightly.
-
A library for exposing simple scripts? (Scripts As A Service)
Another option if you’re ready to implement the frontend part is https://github.com/joewalnes/websocketd which has the advantage of streaming the output of your script
- websocketd
-
Show HN: How did I live without Pipe Watch?
Wanted to add websocketd [1]. It's an amazing tool to stream debugging logs to another system where you can build your webapps that accumulate alerts.
Use it only for debugging builds and not for production (obviously).
[1] https://github.com/joewalnes/websocketd
- Websocketd – It's like CGI, twenty years later, for WebSockets
What are some alternatives?
hurl - Hurl, run and test HTTP requests with plain text.
Crow - A Fast and Easy to use microframework for the web.
web3.py - A python interface for interacting with the Ethereum blockchain and ecosystem.
quickserv - Dangerously user-friendly web server for quick prototyping and hackathons
cdk-eventbridge-socket - CDK construct that creates a WebSocket endpoint for you for any EventBridge rule you are interested in. (Built for debugging + testing )
ArduinoWebsockets - A library for writing modern websockets applications with Arduino (ESP8266 and ESP32)
warp-cors - warp-cors is a proxy server which enables CORS for the proxied request
IncludeOS - A minimal, resource efficient unikernel for cloud services
sls-test-tools - Custom Jest Assertions for Serverless integration testing.
sish - HTTP(S)/WS(S)/TCP Tunnels to localhost using only SSH.
go-ethereum - Go implementation of the Ethereum protocol
lithium - Easy to use C++17 HTTP Server with no compromise on performances. https://matt-42.github.io/lithium