There's the option of running the Android app in the official KVM-based Android emulator but that only acts as the main client rather than a secondary client like the desktop app. It honestly probably uses less memory than Signal Desktop, especially after being open a while.
Conversation
i heavily rely on desktop notifications, so if i had to resort to that i'd probably just pick a different client entirely
1
I think KDE Connect can bridge the notifications including replying to them from the desktop but I'm not sure if that requires using KDE. I just feel like trying to use an unofficially supported client is a recipe for ending up needing to do a fair bit of work to keep it working.
2
I use KDE Connect already, but the Android app -also- sucks. Sometimes I get a message on the Desktop app and five minutes later long after I read it the Android one finally sends me a notification.
1
I'm used to the non-GCM push implementation on devices without Google Play which works essentially the same way as the desktop app. GCM is efficient but it's not particularly reliable and often has delays. The efficiency is mostly from apps reusing the same connection anyway.
3
1
I don't see any fundamental reason GCM should be more efficient than a properly written application sleeping in a poll or a thread making a blocking read from the notification socket. It's more a matter of apps being idiotic or maliciously doing other stuff in the background.
1
The reason it's more efficient is that it's a single connection with highly optimized rare polling based on a good heuristics for tuning the frequency of the polling. If the apps all use the same polling interval and coordinate it with flexible alarms it wouldn't be that bad.
2
poll does not have a frequency of polling unless you misuse it by passing a timeout. It sleeps until there's data.
1
The issue is that connections often break in practice without notifying you, so you need to regularly wake up and send some data both to keep the connection from being killed and to make sure that it hasn't died yet. It's particularly bad with most mobile data connections.
2
poll should return with an exceptional condition if the socket dies. If it doesn't this is a problem the OS should solve; it's trivial to do if you can see the connection go down/up again.
1
1
Connections die pretty quickly if you aren't sending anything through them on mobile networks and you don't receive reliable notice of that. OS doesn't know about it either and the device is generally asleep when this happens. Need to decide how often to wake to keep them going.
It's a significant issue for non-mobile connections too, and you need to keep making a lot of new connections to handle all the network switches and drops, but first you need to detect that it dropped. The server will know it dropped when it tries and fails to push, client won't.
Is this NAT-hell only? In principle it shouldn't happen on a real IPv6 network, which we'll hopefully be able to assume in a few years...
1
An IPv6 network without stateful firewalls shouldn't have this issue, but stateful firewalls will still end up dropping old / inactive connections. There's also just a whole lot of broken stuff. I think there are a lot of pure IPv6 mobile networks already and it still happens.
2
Show replies