Molly and ntfy both on unrestricted?

yeehawk

Hey there,
I just want to ask whether it's normal to have Molly and ntfy both on unrestricted to see the incoming message content? If I put Molly on optimised it'll just tell me: "its very like that new messages arrived". Even when molly is on unrestricted, ntfy will just be listed as an "active app". I just want to be sure I'm doing things correctly. Aside from that you could tell me how efficient this configuration is in regards to Molly's WebSocket?

Thanks in advance.

n3t_admin

yeehawk yes, that's correct. Ntfy/UnifiedPush is only providing the notification banner. The content (message) is fetched by Molly itself to be shown as a preview in the notification banner. For this to work, obviously both have to be running on unrestricted settings.

yeehawk

n3t_admin It seems to me that Molly's Websocket are a whole lot better optimised in terms of battery consumption than the one the original Signal app provides. Furthermore, I've come to the realization that if you have to run both Molly and ntfy on unrestricted, it doesn't really seem to make a big difference compared to just having Molly on unrestricted with their WebSocket-System when it comes down to battery consumption.

I might be wrong about this, I don't have any recorded statistics, thats why I'm writing in order to maybe get any experienced user to share their knowledge.

n3t_admin

yeehawk well, a websocket is a websocket. It doesn't really matter whether ntfy is keeping up a constant connection or Molly. The real benefit of UnifiedPush is either
a) providing push notifications to multiple apps, thus "unifying" their websockets into one or
b) in the case of Molly, UnifiedPush is the only way (besides FCM) to get notified with an at-rest encrypted db.

If your goal is to save battery and Molly is the only app utilizing UnifiedPush, there's not gonna be any difference compared to plain old websocket.