Closed Northernn closed 9 months ago
For the first one, when the device is online, it will send heartbeat data at very short intervals, so if a device's last update time exceeds a certain duration, it should be marked as offline and deleted. This is a small feature that will be added in a future version.
As for the second one, it seems that RustDesk's official client does not appear to have opened up group sending and requesting related information. I haven't tracked it, so it seems that the group functionality may be temporarily unavailable.
For the first one, yeah i figured thats how it works, but what I am saying is I have 13 machines connected at the moment (to test with), say about 3 of them have been off for 4 days now (powered off) yet all of the update times are today 05/02/2024 but surely the ones that are powered off should be showing as 4 days ago? not today? as in last seen, because surely it wouldn't be able to update anything if it was offline? or am I not getting that right?
Also I have noticed in the address book, if you set force relay on, on most of the machines, when I log into the account on another computer I have to turn some of them on again, but not all, it doesn't seem to be consistant.
So some of these machines I registered on 2nd / 3rd and haven't turned them on since? not sure why most are saying 5th? and registered yesterday?
我想它应该是时区的原因导致的。 请注意是否他们的更新(注册)时间与你的本地时间都差了N个小时?(N取决于你的时区与0时区的差距)。
因为我在中国用,所以强制设定了一些。
What happened?
The Updated Time of peers seems to always update even if the Peer is turned off (not online) ?
Also, would be nice to be able to use groups, so we can organise peers into groups.
Operation System
Linux
Python Version
python3
Run type Python/Docker
Python