![]() ![]() The gateway then sends the alert onwards to Google and Apple, for them to generate the alert on the mobile devices involved when the mobile app isn’t running or in the background. The connection is encrypted, but the content isn’t. ![]() Through that gateway all alerts from every rocket.chat instance anywhere, self-hosted or not, pass. It is generated by sending an alert to the Rocket.chat gateway. That push notification isn’t generated within your own server, or within the mobile applications after receiving the messages concerned directly from our server. When you someone, or a channel, or even share any message in any channel, the server pushes an alert by default to the mobile devices of the users involved. Especially as there is no way in Rocket.chat to finetune when/how you want to receive alerts, nor any meaningful instance wide settings, and the default is alerts get pushed always. However, something that wasn’t clear to me before, push notifications in Rocket.chat involve multiple third parties without users giving explicit consent (which is very problematic in terms of GDPR). Rocketchat desktop alerts all happen at once full#The reason we run our own instance is to be in full control of the data we share between ourselves in rocket.chat. It was a notice from Rocket.chat alerting me that from now on registration is mandatory to use the Rocket.chat gateway to enable push notifications to mobile devices. I was surprised to receive a 2am automated message from ‘rocket.cat’ in our company’s self-hosted Rocket.chat instance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |