Update on Registration Requirement to Utilize Push Gateway

Because you are consuming a service we are providing, the same way we are required to have logins with Apple and Google and pay them yearly fees to use their push notifications services. These services have polices we have to follow, and in order to do so, we need to control the usage of our gateways.

You are welcome to cut the middle man, us, and deal directly with them.

What part of that is so hard to understand?

Why odd? The instances were not storing local data about the usage of push notifications, but we were able to measured usage by counting hits form workspace IDs to the service.

This is factually incorrect. You can change the setting for the server not to send push notification on ALL MESSAGES by default, and only on mentions. User can override that per account or per channel. Are you not aware of this possibility?

1 Like

Except those settings don’t seem to be helpful considering my instance likes to send push notifications to my phone about half an hour after i had a DM conversation with someone else over the desktop client.
I don’t know if there’s just something wrong with my phone or the server but my assumption of how the feature should work is: If the user is online using the web or desktop client and hasn’t marked a message as read within a given timeframe, send a push notification to the phone. This doesn’t seem to be the case.

I wouldn’t want to get charged for such notifications.

2 Likes

Is not your instance. That’s the buggy push notifications systems they pretend to charge us.

I’ve been using RC just with the IT team during the last year, before going into production. I like to test extensively the self-hosted solutions before going into production. That team can use the 1000 limit in just one day, because all of us work from home. So that “free” account never will be free.

Privacy also matters. I’ve installed RC having in mind precisely that. Tracking cookies, RC having access to our messages, pushing themselves messages to my server… that’s completely insane.

I’m so disappointed I’m leaving rocketchat to Matrix, a true open source and enterprise chat solution. No strings attached.

Good luck to you all. I really hope someone can fork this, like Libreoffice did with Openoffice or other cool projects forked from rusted ones. If not, we can see us in Matrix.

3 Likes

Some guide for moving data from RC to Matrix would be nice.

This is definitely a bug, the system is expected to work as you described. Can you please open an issue with more details about your deployment?

UPDATE: We are changing the proposed free push notification limit from 1k/month to 5k/month. and splitting the sponsor plans into 2:

  • 5 USD/month for extra 5k push/month
  • 10 USD/month for extra 10k push/month

And let me please explain why I use the word proposed:

The reason we are asking servers to register now, and not imposing any limits, is exactly because we don’t have enough data about usage profile to be able to confidently determine what are the right ranges. I have already stated that admins will have had the reports about their usage and trends for months before we finally decide and enforce any cap.

Based on the feedback here, rather than just using just the statistics we collected by counting unique sources hitting the server, we tried to discard test and demo servers from the calculation by removing all sources with less than 100 push sent per month and sources that only hit the service for a short period.

Once we gather data from registered servers and you know how much you are really using, we can take the informed discussion about the limits.

We are also looking into adding to the sponsorship plans, the full encryption of the push notification messages, a feature that was only available for the enterprise license, but we need to figure out some technical details about how to do so.

I trust you understand at all we are doing is working hard to make rocket.chat grow better every day, and we do need your support to do it.

Regards,

Gabriel

Today, I am trying to register and it does not allow me to authorize the server so that it can sync with https://cloud.rocket.chat/
when performing the step to log in and synchronize the server with the cloud account, it shows for a very short time the authorize button which does not give an opportunity to click when it again shows the cloud login view

What version of RC are you running? The push notification queue cleaning algorithm may be faulty in this case and we’d like more info to investigate. Or, if the message was indeed older and just arrived late, the problem may be a overload on our gateway… and that’s one of the reason we want to invest more on it.

If you clicked login from inside of your workspace. It sounds like the registration portion is done. Try hitting sync on the connectivity services page. Then once it finishes try to login again. It does an oauth login and the redirect uri has to match otherwise it fails to let you login.

new user here - currently having a look at rocket and matrix - and - as i found this topic not really sure about the truth behind what the webpage (unlimited & open-source…) promotes.
So - yeah - until that is clarified thats a big minus on the checklist when i compare the two solutions.

My company has no problem paying for software - beeing a patreon, participating in bucket lists to implent wanted features, cashing in a yearly support subscription etc. - but the planned implention is one of the worst solutions i can imagine.
If i understand right currently the open source version differs from the enterprise in terms of some additional features. But now another limitation - that of messages per time is planned/already pushed through?

Guess you have to change the comparison/pricing page - as the big fat free that is listed under the community edition (according to the provided comparision “recommended up to 1k users”…) isnt exactly the truth.
This is the same bullshit definition as with free games - where there is ingame payment needed to progress or flatrates for mobiles - that are limited to whatever GB you pay… A flatrate is either unlimited - or not a flatrate.
If you dont want to support a community edition without getting some payback for the time involved just say it out loud - because that is how this reads to a new user. There is nothing wrong with that. But it should be communicated openly.

About Rocketchat vs Matrix
The main thing i could not yet find out about matrix is, if there is a possibility for a guest to write into a specific room (support chat) - a live chat feature embedable into a website.

Does any of you use this feature?

about moving date - i havent tried - but i found matterbridge as possibility to link the two. not sure about existing data though.

1 Like

Hi,

Sorry if this is written somwhere already.

But if we use our RC only inhouse, with no external connections except smtp pushes.
Do we still have to register, or how does this work. (we have registerd our installation at the beginning of time :slight_smile: )

Or is this “only” for using your aws pushgateway to other services?


Regards Falk

For using the push gateway and the internal apps marketplace.

@gabriel.engel Since RC is a web application couldn’t the Google/Apple push notification API and the need for your AWS gateway be eliminated by using websockets (e.g. socketcluster)?

I envisage the mobile application could start a background service which connects/disconnects when a user is logged into/out of any RC server.

Such a solution like this has been looked at many times. The problem with these sort of solutions are endless. The only platform its likely to really work for is Android. iOS for example now kills off background connections pretty aggressively.

I suspect even Android in some cases does.

Not to mention when you move to keeping your own socket open… battery becomes a big concern.

Personally would love it if a project like ownpush would come along stabilize and be a good alternative for both platforms.

The short of it… Much, much easier said than done. :frowning_face:

1 Like

Hi,

I’ve been looking at this thread as my RC instance was reminding me to sort this out.

Would it be correct that not registering would eventually be the same as setting “Enable” or “Enable Gateway” in admin/Push to disabled?

What is the difference between those two anyway? Are there push features which don’t use the gateway?

Re: the 5k limit. Will it be possible to simply stop the notifications on hitting the limit rather than incurring charges?

Thanks,
Phil.

1 Like

Only mobile app notifications use the push gateway.

I’m curious about this too.
I looked for the documentation but couldn’t find…

1 Like

@aaron.ogle I’ve now looked into firebase cloud messaging, FCM, and I cannot see why the existing mobile apps cannot register for message notification from multiple servers without needing your AWS gateway. There is also no need to expose the secret key from your own FCM account.

My understanding is that each RC web host can open a FCM account (which is free) and create their own RocketChat project, so that they obtain a SENDER_ID and API_KEY for their server/domain. Both keys can be provided to the RocketChat server application at runtime via environment variables.

Then the Android/ios apps can connect to multiple servers by requesting a SENDER_ID, when they login (possibly via a secure websocket), fetch the corresponding FCM registration token and share it with the server.
https://firebase.google.com/docs/cloud-messaging/concept-options#receiving-messages-from-multiple-senders
A node.js server can multicast messages to a maximum of 500 token IDs per send invocation.
https://firebase.google.com/docs/cloud-messaging/send-message

1 Like

What if someone buys a 10k push and exceeds this number in a month?

Push will be automatically turned off or will you charge additional fees in some way?

Can I buy 5 packs of 10k push?
I learned from another source that it will not be possible and the only option is to buy the enterprise version.

1 Like

No response? @gabriel.engel

Can anyone explain why adding a handshake to the RC server and mobile apps for exchanging the sender_id and client token isn’t feasible?