Comment by karmakaze
4 months ago
I was wondering what "the network" here means:
> To achieve this, KDE Connect:
implements a secure communication protocol over the network, and allows any developer to create plugins on top of it.
Has a component that you install on your desktop.
Has a KDE Connect client app you run on your phone.
Looking further it is only for the local network (with ways to extend it e.g. VPNs).
> Has a component that you install on your desktop.
This is only if you use Windows (or MacOS, as there's also a KDE Connect compatible Mac app out there somewhere IIRC). If you're on KDE Desktop Linux, you're already good-to-go, as it's a pre-installed component of a typical KDE environment. :)
not true for all distros. and this kind of thinking is really bad imo for network services.
It has bluetooth support now as well
it also talks about using a VPN and what ports to open in a firewall.
I don't know how it handles the harder part, the "device on internet" talks to "device in my house"
most phones and apps use this "harder part" to interpose their corporate server for more than TURN/STUN and continue to "collect all the data" or "insert a subscription"
Did you get this to work with wireguard though?
As long as my phone is connected to wireguard KDEConnect does NOT see any other computer, apparently because it wont forward ICMP broadcast according to the internet.
I would really like to have a solution to this issue but since its baked in WG i don't think this is possible
5 replies →
> the "device on internet" talks to "device in my house"
It doesn't handle it well other than with bluetooth or awkward port forwarding and manual entering of IPs.
I don't see it as a problem though, I don't think I have needed a single time over my many years of use to share my clipboard with, or control the media player or mouse and keyboard, of a device that was not in the same room or on the same network as me.