tungstenite-rs VS Warp

You can start by following tungstenite-rs client example. And since you are connecting to an tls enabled endpoint you should enable tls features. And according to your API's doc it requires you to send serialized json string for requesting message response and you can use serde ande serde_json for serialization. This is a complete example where a hardcode string request:

staticpi, is a websocket forwarding service. Basically, it enables one to keep a Raspberry pi, or any computer, “connected”, in order to send and receive messages to and from any client, without having to deal with a static IP address, open ports on your router, or similar. Built in Rust, using axum, which in turn uses tungestine-rs for the websocket connections, tokio, sqlx, redis-rs and others.

There is a client module and client examples. If using tokio, there is tokio-tungstenite on top, which has various client functions.

tungstenite: "Lightweight stream-based WebSocket implementation. It's formerly WS2, the 2nd implementation of WS. WS2 is the chemical formula of tungsten disulfide, the tungstenite mineral."

tungstenite-rs

If you just want to connect to an existing api, async-tungstenite has a connect function. It should work with wss. See some discussion of this issue here.

I'm trying out Warp for the first time, and an immediate accessibility issue for me is that the text is simply too small to read for a lot of the UI elements (context menu, side bar, tab bar…). The size should be configurable for all of the elements, not just the terminal view. I think I would also be fine with a setting that just scales the whole UI.

I did notice there is an issue for it already: https://github.com/warpdotdev/Warp/issues/1443

Warp is a Rust-based terminal with AI built in. I like it because it has things like autocompletions, history search, click-to-edit, and theming out-of-the-box. Feels super modern. And if you do want to try it out, use my referral link & get a free theme!)

Unless you want to type this every day, I’d recommend creating an alias. In my case, I’m using Warp, so I’ll right-click the command and choose Save as Workflow to save my script as a workflow. Warp AI will even help me autofill the title and description and detect variables.

This makes me wonder about newer terminal emulators on maccOS like Warp[1], and if they're for example taking all input locally, and then sending it over the remote host in a single blob or not? I imagine doing so would possibly break any sort of raw-mode input being done on remote host but I'd also imagine that is a detectable situation in which you could switch into a raw keystroke feed as well.

[1]: https://warp.dev

Warp - GPT in the terminal - very helpful for debugging

You're right, I just found the discussion there (and it's the longest one currently). For now, I just run tmux inside the emulator.