←back to thread

KDE Connect: Enabling communication between all your devices

(community.kde.org)
475 points snthd | 1 comments | 12 Oct 25 12:04 UTC | HN request time: 0s | source
Show context
sombragris ◴[13 Oct 25 19:11 UTC] No.45572177[source]▶
At least in my use case (as link between Android devices and both Linux/Win PCs) KDE Connect is a real killer app. It enabled seamless integration and saved me lots of hassle and time. It really should get more exposure.

I see reports that it doesn't work. These are mostly for distros where Plasma is either rather old or taking a backseat after other environment (usually Gnome). I'm having great results with the latest Plasma 6 on Slackware-current and also in a standard Windows 11 environment.

replies(5): >>45654960 #>>45655713 #>>45656716 #>>45660465 #>>45666378 #
gear54rus ◴[21 Oct 25 13:42 UTC] No.45655713[source]▶
I definitely have a need for this, but I can't stomach same-network requirement.

Maybe they need self-hostable coordination server so that devices can connect to each other through it.

For now it's still 'send to telegram saved messages' for me.

replies(3): >>45656765 #>>45657330 #>>45664900 #
exdeejay_ ◴[21 Oct 25 15:08 UTC] No.45656765[source]▶
Have you considered using Tailscale to get around the same-network requirement?
replies(2): >>45659067 #>>45659958 #
1. forbiddenlake ◴[21 Oct 25 18:50 UTC] No.45659958[source]▶
Tailscale doesn't support mDNS / multicast at all, making working with KDE Connect more nebulous. I attempted to add a static peer via the Tailscale hostname, but both ends report not reachable, and the Tailscale daemon is constantly dropping multicast packets. So I'm not sure how this helps, but I also don't have a use case - if I'm on my laptop, my phone is on the same Wifi network 99% of the time.