Hacker News new | ask | show | jobs
by g-b-r 978 days ago
Not surprised in the least about Element unfortunately, it really screamed for a rewrite (one of the biggest problems was the horrible choice of database, which unfortunately was very hard to replace)
2 comments

Sounds like the old Element app that was being used was using an always on notification to poll for push notifications instead of using a push service.

Element X only supports FCM cloud push notifications right now I think

I think it used push on play store and polling on f-droid
Correct, the novel thing Element X does different is sliding sync which allows for much faster partial syncs when the app is opened. The classic apps would have to do a much more substantial (and energy intensive) sync each time it was brought up to foreground.

The big drawback are the X versions are still very far from feature complete.

It can use (and I think it's the default) UnifiedPush on F-Droid
Default is pull, but if you have ntfy installed it shows a popup and lets you decide between pull or unifiedpush(ntfy).
What was the poor choice of database on Element (Android or Electron), and how does it increase power usage?
Presumably realm in Element for Android. https://realm.io/ "Realm by MongoDB"

See also https://github.com/vector-im/element-android/issues/1025

Yes