I would like to address the whole topic of the enforcement and the implementation of push notifications in RC.
We, a mid sized German university, are happily using rocket.chat on premise on our own infrastructure. Currently we are serving round about 10.000 users in our main chat, working flawlessly.
Then RC introduced the limitiation of those push notifications. To be clear, as we are used to work with open source projects we are always happy to give somthing back and get things going. So despite the price only for pushes is quite a stance (see this thread about the pricing How to buy push notifications?!) we entered the negotiations to get a licence for an educational licence which includes unlimited notifications. We are acknowledging the fact, that this is actual a cross financing for the whole project, but which was never said
Then, during our negotiation, the limit was inforced. We disabled push for our users, as we expierienced for EVERY single failed notification our logs filled up with:
I20201210-18:04:31.260(0) server.js:204 Push âž” error Error sending push to gateway (5 try) -> Error: failed [429] {"code":131,"error":"the amount of push notifications allowed for the workspace was used","requestId":"86759b8a-c7a0-4291-b183-cd6231e2d451","status":429} [....]
Which nearly brought our servers down…
This morning, the RC Bot informed us 134 times, that
“Attention You have reached your monthly mobile push limit. Check push usage for more details.”
Nice one, we disabled that! So all the admin users had to click that blue banner at the top exactly 134 times… and set the channel of rocket.cat as read…at least that worked! Note again: We disabled push!
To be clear: This is not the way to handle such things! If you want to get revenue out of your product, treat your potential customers good, do not bug them, package bundles which are affordable! For the price offered it would be cheaper to send those pushes out via SMS! We are happy to invest in OSS and projects but it has to work! And for all the little and small users and enterprises out there: You are pushing your user base out! This is dangerous stuff for an OSS project!
Sending this via mail to our contact at RC as well!