Desktop client cannot connect to self-hosted instances

(#641) Feature Under consideration desktop self-hosting

Thread

Comment by Hampus
HampusStaff 1 vote originally by @hampus-fluxer on GitHub
any progress on this yet?
Yes, there's quite some progress on my local dev build. It's possible to switch between accounts in real-time (it maintains an open WebSocket connection in the background across all accounts across any backend, making switching instant, you can receive push notifications across instances seamlessly, and it won't keep caches for an account that's not currently active in live RAM, but batch writes against a SQLite DB file on disk for each account when receiving events in the background, and load this into RAM only as needed, or query the disk cache as needed when another account is in focus to power rendering of unread channels in the Quick Switcher across instances, and more). This will be quite the upgrade! It also defaults to asking you which instance to use during initial setup now too of the desktop client. I'm working on finalising this and the voice update (most recently, I've managed to remove WebRTC entirely in favour of QUIC – see https://doc.moq.dev/ for reference, so while I'm not using MoQ directly, I'm simplifying my new entirely custom voice SFU, which is written to be largely API-compatible with that of Discord to make migrating bots and integrations easier, but now with a significant reduction in complexity and boost in performance since I'm switching entirely to QUIC across all platforms, removing the need for the overhead that WebRTC brings – so I'm finalising my testing on this across web, Windows, Linux, and macOS before calling it usable), and then when it's fully tested out locally, I'll land it in here, and deploy a separate staging environment for early testing amongst the people who are currently in the Canary Testers community on Fluxer.app. And when that's all done, I'll be able to schedule maintenance to do the backend upgrade needed for the new voice architecture, as well as synchronising the Canary and Stable clients to the very latest code here on Git. After that, we'll be able to move much faster without delays. Thanks for your patience with me. image image image image
  • 620559356-c9bb2851-2155-4a42-b8d7-9aa70c19aa29.png

    620559356-c9bb2851-2155-4a42-b8d7-9aa70c19aa29.png

    3740×2818 | 1.6 MB

  • 620559376-ef2dce5f-7aec-4dff-9b4d-61150ccd447b.png

    620559376-ef2dce5f-7aec-4dff-9b4d-61150ccd447b.png

    3742×2792 | 1.3 MB

  • 620559384-c8be49ff-a1b7-4570-94bb-0b4256d36f45.png

    620559384-c8be49ff-a1b7-4570-94bb-0b4256d36f45.png

    3748×2818 | 1.3 MB

  • 620559401-91b4acd8-5335-46e3-916d-9bbe2578d99d.png

    620559401-91b4acd8-5335-46e3-916d-9bbe2578d99d.png

    1176×552 | 85 kB