laravel-echo-server VS tinyssh

Which of these do you use for your realtime Laravel applications? Soketi seems good but documentation doesn't seem that good. Laravel Websockets is mentioned in the official Laravel docs as a Pusher alternative,and Laravel Echo Server looks good but hasn't been updated for a year.

Events are broadcast using Laravel Echo Server, Laravel Websockets, or Soketi. Say on a channel time.

Yeah, we've used https://github.com/tlaverdure/laravel-echo-server in production for years. But our version is modified, restarts in sync with the clients on a schedule, and needs...TLC.

As for the connection error, that is shown because no websocket server is setup and running for your app (also adding to my docs). By default, my messenger-ui NotifyManager.js uses laravel echo and the socketio library, along with laravel-echo-server for the socketio instance.

not websockets, but this looks like a great alternative option https://github.com/tlaverdure/laravel-echo-server

While on topic of sshd having minimal dependencies, shout-out to Jan Mojžíš and his minimalist implementation:

https://github.com/janmojzis/tinyssh/

> [after] hardening steps [...] most of the bots can't even negotiate a connection

Yep, same here, except I'm using [tinyssh], which organically does not support anything other than ed25519/curve25519, sha256, and chacha-poly.

[tinyssh] https://tinyssh.org/

djb suggested that for openssh instead of the tinydns kex, so tinydns switched also:

https://github.com/janmojzis/tinyssh/issues/50