jobangles

Foxy lady

Public Key

npub1h3x4tt35u5gedg8p2t0g6n27l7gkdnlsfc9y6ekl3udqqc79u0mqwygpg9

NIP-05 Address

jobangles_at_mastodon.world@mostr.pub

Profile Code

nprofile1qqstcn244c6w2yvk5rs49h5df400lytxelcyuzjdvm0c7xsqv0z78aspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsn3avrm

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1h3x4tt35u5gedg8p2t0g6n27l7gkdnlsfc9y6ekl3udqqc79u0mqwygpg9

Show more details

Last Notes

2023-12-16 10:32:28

- reply

@npub1w0h…uwua @npub1qml…mdus I see, thank you for explaining. To offer some context, I have experienced firsthand that Signal will use a ton of battery when not using GCM, so I can confirm that. See here as well: https://github.com/signalapp/Signal-Android/issues/9729. By comparison, in my experience Conversations has been a lot easier on my battery. So I'm genuinely trying to understand why Signal couldn't implement this as well. It would be great if it would use less battery, a lot of people seem to encounter the issue.

2023-12-16 10:08:55

- reply

@npub1ynl…873s @npub1w0h…uwua @npub1qml…mdus @npub185n…luq0
I hope you're both not still angry with eachother. I would like to understand the technical details here. If I'm not mistaken, what Daniel is saying is that conversation's persistent client-server connection is more battery efficient than signal's (when not using GCM). It does not seem to me like the connection method itself is affected by the difference in scale between both apps. I.e., could signal not use a similar approach to improve batterylife?