So here’s the thing with this @sing.li, in your quote above you are obfuscating very specific issues by generalizing them under the blanket of “your specific preference” and “will continue to evolve the solution” as though there are a lot of different issues related to regulating the number of push notifications and that they are all of equal importance and being methodically addressed over time.
That might all make sense under a scenario where you are NOT CHARGING PEOPLE for sending push notifications.
Under the scenario that begins on November 16, where you ARE CHARGING PEOPLE for sending push notifications, there are a couple of very specific requirements that I and others in this thread have mentioned that seem like hard requirements to implement and fully test BEFORE you start charging people and/or cutting off their server’s ability to send push notifications.
To recap, these are:
-
RC should not be sending mobile push notifications for messages that have already been marked as read / seen via web or desktop app. This is a bug that could result in you either cutting people’s push notifications off or charging them for more monthly notifications than they would otherwise need. Fix the bug before implementing the cutoff.
-
There are users who may have set their default notification preferences in RC to send mobile notifications for everything everywhere and then may be managing those notifications at the device level. Or just ignoring notifications they don’t really need. RC admins need to have the ability to override the notification preferences of users on their server. Again, this inability to modify these preferences could cause people to use many more push notifications than they need, so you should fix this before implementing the cutoff.
Not making these changes (so that admins continue not to be able to really control the number of push notifications their servers are using) before implementing the cutoff is an ethically poor choice.