←back to thread

KDE Connect: Enabling communication between all your devices

(community.kde.org)
475 points snthd | 2 comments | 12 Oct 25 12:04 UTC | HN request time: 0s | source
Show context
jancsika ◴[21 Oct 25 16:24 UTC] No.45657724[source]▶
The feature set commenters here want is insane:

* fast as possible

* LAN, but also WAN when necessary

* in fact how about multi-protocol, and use the fastest protocol that's available on both devices, it's 2025 people!

* work for sending a gargantuan amount of files with possible interruptions (essentially, be rsync)

* be battery efficient, it's 2025 people!

* don't rely on a centralized cloud server, just connect the damned devices to each other

If you think you can hack this together, you should write it for Gnu Hurd because they'll release that well before you're finished

replies(1): >>45657797 #
ValdikSS ◴[21 Oct 25 16:29 UTC] No.45657797[source]▶
>* be battery efficient, it's 2025 people!

It took a long time for me to prove that what KDE does negatively impact the battery life.

https://bugs.kde.org/show_bug.cgi?id=441830

The other user even wrote a LD_PRELOAD hijacking library to not recompile the application every time

https://github.com/max0x7ba/kdeconnect-powersave-keepalive

replies(3): >>45658373 #>>45658501 #>>45668301 #
1. snthd ◴[21 Oct 25 17:19 UTC] No.45658501[source]▶
Fixed in "Remove custom keepalive intervals" merged 12 Aug 2024

https://invent.kde.org/network/kdeconnect-kde/-/merge_reques...

replies(1): >>45660783 #
2. ValdikSS ◴[21 Oct 25 19:49 UTC] No.45660783[source]▶
It improved the battery life but made the connection activity detection worse (the disconnected phone won't be detected for up to 2 hours), but I didn't complain anymore.

I initially set it to 5 minutes.