Nikhil Kothari

Makes sense. So let's say every user gets a total score of 1 and they can split it across options (or not). Percentages should be based on the scores rather...

> Percentage should be based in total votes for each option IMO. Can you elaborate this? As of now, percentage for an option is calculated as `total number of votes...

> % of each vote = total number of votes for that option / total # of users who voted. Makes sense. The total would be higher than 100% overall...

Nope. Can't do this because Apple punishes silent notifications. https://dev.to/progressier/how-to-fix-ios-push-subscriptions-being-terminated-after-3-notifications-39a7 https://meta.discourse.org/t/ios-notifications-can-lose-permission-to-push-if-the-user-is-currently-active/290225/7 https://github.com/firebase/firebase-js-sdk/issues/8010

So, now the "fix" is: 1. Show the notification. If the push is sent from the current user, then add a "silent" property to the notification. 2. After the notification...

This might still cause issues if getting the data from IndexedDB takes too much time. iOS wants devs to fire a notification immediately. Possible solution: fire notification immediately and then...

Looks like the only solution is to not use topic based notifications and send notifications to each user individually.

Kinda difficult to implement, but understandable why it's needed. We have the last visit timestamp, so maybe try to find the first message after that? Only problem is if the...

@TITANiumRox is working on the mobile app now. We'll ship this feature soon since it's half ready, but performance upgrades took precedence.

> Also, double tap to like please (👍) #811