

So, you’re basically running the KDE infrastructure, just not using the KDE WM? Have you done a ps and counted the number of KDE services that are running, just to run KDE Connect?
Here are the (KDE) dependencies on the Arch KDE Connect package:
kcmutils
kconfig
kcoreaddons
kcrash
kdbusaddons
kdeclarative
kguiaddons
ki18n
kiconthemes
kio
kirigami
kirigami-addons kitemmodels
kjobwidgets
knotifications
kpeople
kservice
kstatusnotifieritem kwidgetsaddons
kwindowsystem
pulseaudio-qt
qqc2-desktop-style
qt6-base
qt6-connectivity
qt6-declarative
qt6-multimedia
qt6-wayland
When you run KDE Connect, you’re running most of the KDE Desktop and Qt; you’re just not using it.
Have you ever tried running it headless? I have; it doesn’t work.
Sourcehut also supports Mercurial, so you also have an option to the herd mentality.
Sourcehut also has zero, or almost zero, JavaScript in the interface, so it doesn’t suck
Sourcehut is also componentized, so you can mix and match the pieces you want or need:
Sourcehut is by far the best hosted VCS option at the moment. The Mercurial support alone puts it miles ahead of the others, which are all hobbled by tight coupling to git.