Dear Rocket.Chat, I do not appreciate features we’ve grown fond of using, such as Read Receipts, being seized from us and made a paid feature abruptly and without warning. This completely inappropriate and immorally manipulative sales strategy has ruled out the chance of my team ever purchasing a s…

I had not noticed that major change and that’s not going to be well received by users. Unfortunately we just upgraded to 6.0.0, so it’s too late now :frowning:

Hi! I am really sorry you feel this way. This change is stated in 6.0.0 release notes as well as some other restrictions and improvements. We have been carefully listening to our community, and bringing awaited and desired improvements and fixes, as you can also read at that release note. Here …

i agree with @steve5050 … moving a existing function to EE ist not cool. so we need to leave RC also, because Enterprise is to expencive for our team (many users, but we only need to chat).

All we use is basic Chat features with self-hosted RC. And read-receipt are basics for it. EE is pretty expensive for us.

You’re right, and as my needs and budget grow, Rocket.Chat won’t be considered after this horrible situation they’ve created for me and my team.

Sorry Duda, I can’t let this pass without comment. [image] dudanogueira: We are not taking advantage of sys admins or users This is of course total and utter nonsense. Rocket are taking advantage by removing what were previously free community features in to Enterprise only, and forcing the…

Thanks for your feedback on this item. Read Receipts have been an EE feature from since before I joined the Core team but, as noted, that restriction has not been previously enforced. Recently the team has invested time in improving the read receipts handling for threads which was not working corr…

Implementing these advanced/enterprise features in CE barely anyone will use does not justify removing Read Receipts, a straightforward but necessary component of any real-time communication system. Even the most basic, small-scale use cases require this feature. If you hadn’t caused this great inco…

I understand that it is important for the company behind Rocket.Chat to make money. When the push notifications were limited, I understood the move behind it. I even asked for a offer for the EE. Unfortunately, the prices for an enterprise edition are far from our budget. Then the extended LDAP fun…

Update 6.0.0 Read Receipts Complaint

Community Support

steve5050 March 11, 2023, 12:12am 4

It was a feature I used with all of my team members more than 20 times every day now being held for ransom. My comment is exactly right.

Topic		Replies	Views
RocketChat is no longer a suitable tool for use in organizations Feedback	21	9496	April 13, 2024
Upcoming changes to identity management integrations Announcements	104	23755	February 16, 2022
Introducing the Starter plan — free access to premium features for limited-scale use Announcements	33	5783	January 14, 2025
Final Update on Registration Requirement to Utilize Push Gateway Announcements	104	21435	April 19, 2021
Why I'm leaving Rocket Chat & Finding Alternatives Community Support	30	3999	March 15, 2023

[Secure CommsOS™ Launch] Join our next Roadmap Reveal webinar to learn more Register now ->

Update 6.0.0 Read Receipts Complaint

Related topics