trayscale VS Centrifugo

There's something like this. I try but my internet stop working when I use that. https://github.com/DeedleFake/trayscale

I've actually just recently used this with both pointer and value reveivers in one of my own projects.

I've got a project that depends on Libadwaita 1.2. The ubuntu-latest runner is 22.04 which only has Libadwaita 1.1 available in its repos, causing all of my CI runs to fail. I don't use Ubuntu personally so maybe this is something I can fix via APT and I just don't know how, but what's the recommended procedure for handling a situation where the runner's version of a dependency of a project is out-of-date? I couldn't seem to find anything in the official documentation or anywhere else via Google.

Source: I deal with this myself quite a bit with the Gtk4 bindings I use for one of my projects.

Here's an actual module that I work on as an example.

I've tried a number of them over the years but my latest attempt at a GUI project uses Gtk4.

#1: Introducing Tailscale SSH | 13 comments #2: Tailscale devs sometimes contribute to Headscale #3: I got annoyed at the lack of a Linux GUI, so I built one myself. It's not finished by any means, but it can at least list peers and their IPs. | 1 comment

Yep. I was using manual WireGuard tunnels for that, but everytime I added a machine I had to configurations from both sides with manual key swaps, plus the fact that it I wanted direct connections between each machine the configuration would literally have increased exponentially. Tailscale handles all of that for me. Literally. It's primarily an automatic WireGuard tunnel coordinator. I just have to install it and log in and voila, it just works. I like it so much that I've actually got a project that wraps a GUI around Tailscale for Linux.

This is very likely. I've been writing a GUI wrapper for the Linux Tailscale client, and part of what I interact with from their libraries uses generics. In particular, they've got a views package that implements immutable containers.

Hello, I am author of https://github.com/centrifugal/centrifugo. Our users can choose from WebSocket, EventSource, WebTransport (experimental stabilize in the future). WebRTC is out of scope as the main purpose is central server based real-time json/binary messaging, and WebRTC makes things much more complex since it shines for peer-to-peer and rich media communications.

What I'd like to add is that Centrifugo also supports HTTP-streaming – not mentioned by the OP – but this is a transport which has advantages over Eventsource - like possibility to send POST body on initial request from web browser (with SSE you can not), it supports binary, and with Readable Streams browser API it's widely supported by modern browsers.

Another thing I'd like to mention about Centrifugo - it supports bidirectional WebSocket fallbacks with EventSource and HTTP-streaming, and does this without sticky sessions requirement. I guess nobody else have this at this point. See https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-releas.... Which solves one more practical concern. Sticky sessions is an optimization in Centrifugo case, not a requirement.

If you are interested in topic, we also have a post about WebSocket scalability - https://centrifugal.dev/blog/2020/11/12/scaling-websocket - it covers some design decisions made in Centrifugo.

Check out https://github.com/centrifugal/centrifugo - it was initially designed to be a standalone language-agnostic real-time messaging server. So it may be used with Django without radical change in the existing application and using ASGI. It can also provide a much better performance if you care about it.

https://github.com/centrifugal/centrifugo

It's a complete solution, including server, admin panel and client library.

We're an European company and use OVH, Hetzner and others.

Hello! Theoretically you can take a look at https://github.com/centrifugal/centrifugo - which is a standalone self-hosted real-time messaging server. It does not have native support for Laravel and not compatible with Pusher protocol, though integrating with any backend system, including Laravel: see the blog post https://centrifugal.dev/blog/2021/12/14/laravel-multi-room-chat-tutorial, also has some helper packages:

Hello, it's also possible to design an app in a way that its core will be built with Python, but WebSocket part delegated to something external and efficient like https://github.com/centrifugal/centrifugo – the benefit of the approach is that application business logic is completely decoupled from the real-time transport layer. This may lead to a scalable design with graceful degradation. I think this is especially useful when you already have backend built with Django and need to handle millions of concurrent connections.

Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo