←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
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. j1elo ◴[22 Oct 25 12:51 UTC] No.45668301[source]▶
> 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

Status: RESOLVED

> This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

This trend of auto-closing issues is so upsetting. Can we get rid of it already? This describes an actual issue, and it wouldn't get magically resolved through a lack of actions. I could maybe buy auto-closing bugs that have been stale for 3 years, but 30 days is just ridiculously short. It only serves as makeup for the numbers to appear as if there are not many defects in the software, and it seems to be a common practice in too many projects.

---- EDIT: Turns out this got fixed in the end [1]. Good for this particular case, but the point stands.

[1]: https://invent.kde.org/network/kdeconnect-kde/-/merge_reques...