Marie/Rose News

Rose is currently offline while upgrade her server. During this time we have locked the support chat. Once the upgrade is complete and we confirm all is working normally, we will re-open the chat. Thank you for your patience! :)

Maintenance has now started.

Reminder: Server maintenance will be beginning in 5 minutes, and is expected to last between 1 to 2 hours.

The server migration is planned for 5pm GMT, on Saturday the 9th. It is expected to last between one and two hours, during which Rose will be completely unavailable. Rest assured that if the migration completes faster than expected, then Rose will of course be brought back up sooner. I will post here again when the migration is about to begin, and when it ends. Thank you for your patience!

When Rose was first announced in 2018, I made it clear that she was built for speed. My previous bot, Marie, had made it to one million users the month before, and was beginning to show the telltale signs of slowing down when usage was high. I didn't like that, at all - so I chose to start from scratch, in a new language, and see how far I could push the telegram bot API. Now, 2 and a half years later, Rose has over 63 million users, and has been used in over 800k chats. That's a lot of chats for one bot to handle. To make sure that Rose has space for more growth and keeps pushing limits, it is now time to upgrade to a better server. However, server upgrades are expensive; if you use Rose, and appreciate her help in moderating your chats, please consider donating as much (or as little) as you're comfortable with; either on PayPal, or GitHub Sponsors. I really cannot stress just how important these donations are - without them, Rose simply would not exist. The server upgrade will be scheduled over the next few days; more details will be provided in this channel. Thank you! :)

Happy new year everyone :)

A year and a half ago, Rose hit 6M users. This was big news for me; I created Rose to be fast, and I felt that this was a big milestone to prove I had (at least partially) succeeded. Today, Rose has grown to 10x that; she now has 60M users, across 760k chats. She receives over 300 messages per second, for a total of over 27M messages every day. Those are no small numbers! In fact, it makes Rose (one of?) the biggest fully free bots on telegram. Thank you to everyone using Rose, everyone who's helped translate, and everyone that has come and contributed to the support chat with new feature ideas to make her even better at managing groups. Most importantly - a BIG thank you to everyone that has donated to help pay for server costs. You are what keeps Rose running for everyone. Couldn't have done it without you! Here's to having many more years of Rose, and keeping her free for everyone to use. Happy holidays!

Telegram is currently experiencing datacentre issues. Several users and bots, including Rose, are having problems sending and receiving messages. We're aware of the issue and will continue to monitor it. Unfortunately, there is nothing we can do on our end, so please just be patient. We'll provide an update once the issue is resolved. Update: This has now been resolved. Telegram is back online, and the bot api is stable again. Sorry for the downtime!

Telegram is currently having issues. For that reason, Rose is replying slowly. We are aware of this, and monitoring the situation in case theres something we need to change. Until then - please just wait. I will update this post when things have fixed themselves. Edit: Telegram is back, and so is Rose. No messages have been missed :)

Rose update! Just a few small features today, nothing too big. - Added the new /fedreason command, which allows a fed owner to force whether or not fbans should have reasons. Enabling this will reject all fbans that are made without specifying a reason. - Fixed a bug where @admin was sometimes matched incorrectly. - /newfed no longer renames your fed if you already have one. Instead, use /renamefed. - Using /connect in a chat now shows a deeplink to connect to Rose instead of sending a message in PM. This should help reduce errors, which in turn will reduce some rate limits from telegram. Also means that anonymous admins can easily connect to chats again! - Anonymous admins removing warnings will no longer be exposed as anonymous. - Various improved error messages. - Updated translations. If any Polish, Dutch, or Taiwanese speakers would like to help with Rose, the translations on crowdin are getting old - a lot of strings are missing. If you would like Rose to keep speaking those languages, please update them :) Enjoy!

Rose update! Nothing big today, but a lot of small, helpful changes: - The /reports command (with no argument) now shows the current setting. - The /report and @admin commands now work without needing to reply to a message to report. - The /warnings command now shows the amount of time the warnings will last for. - Anonymous chat creators can now use creator commands again (such as /import, /clearall, /stopall, etc). - The usual bugfixes and backend improvements. - Update translations. Rose now speaks 🇺🇦 Ukrainian! Big thank you to all those that have contributed :) Another note: Some people have been waiting for Rose to allow anonymous users to fban. However, this causes issues, since it would de-anonymise the user. I believe that anonymous users should have their privacy respected, but also believe that federation commands should log the person who did the ban. For that reason, anonymous fbans will not be coming to Rose (at least for now). If you have more questions, feel free to ask in the support chat. Enjoy!

Rose update! Telegram have updated the bot API - and of course, that means updates for Rose too! - Fix antichannelpin issues caused by the new multipin logic - Stop /adminlist from showing anonymous users - Add the /unpinall command to unpin all messages - Replying /unpin to a message will attempt to unpin that message And of course... - Support for anonymous admins to run commands. When an anonymous admin runs a command, Rose will now send a message asking for that admin to press a button. This will allow Rose to know who that admin is without leaking their identity to others - which means that she can confirm that they have the necessary permissions to use that command. If you don't care about security, you can also use the /anonadmin command to simply give full admin permissions to any anonymous admins. This means they won't need to press any buttons, but also means that there is no way of knowing if they're allowed to use those commands. Also: - Various bug fixes and optimisations - Updated all languages Enjoy - and let us know in the support chat if you have any issues.

New Rose update: Introducing random filter/notes/greeting contents. Having the same filter EVERY time can be a bit boring sometimes. So now, you can have Rose pick a reply to a word at random! Simply separate the two contents by %%%, on a newline. For example, the following will set a filter on rose as usual, but Rose will randomly alternate between Heya, that's me!, or You called?. Cool, right?

/filter rose
Heya, that's me!
%%%
You called?

You can add as many random filters as you'd like, so enjoy! These can be used on notes, filters, and greetings. And, as usual: - Bugfixes - Updated translations

The bot api seems to be having issues with Rose at the moment. Messages are failing to send because of it. Hopefully, this fixes itself soon! edit: Seems to have fixed itself now.

Small Rose update to handle the latest telegram version: - the anonymous group bot (@GroupAnonymousBot) is approved by default; locks, blacklists and antiflood won't take action on it. - minor bugfixes. Going to keep investigating to make sure there aren't any other surprises caused by telegrams update. Let us know!

Telegram have quietly released a new update which has changed how linked channels send messages to your chats. Instead of channel messages being sent by "telegram" (userid 777000), theyre now being sent by a bot (@GroupAnonymousBot). This causes some issues with Rose, such as: - linked channels being affected by antiflood, locks, blocklists. - "cleanlinked" and "antichannelpin" may act weirdly. If you dont use linked channels, then dont worry - this shouldn't be a problem for you! I'll release a new update later tonight where ill fix this - in the meantime, sorry for the inconvenience. Edit: Looks like telegram have undone the change on their side, so everything is back to normal.

Telegram has been having issues for the past 2 hours, which caused Rose to have issues sending/receiving messages. Telegram is now back, and so Rose is too. I've cleared all pending updates, since I figured that messages sent 2 hours ago are no longer relevant, and that we would rather have Rose taking care of new messages :)

Rose update: - Hopefully fixed a bug causing Rose to hit rate limits on pinning. If you've been using antichannelpin and have seen Rose occasionally fail to re-pin, this should now be solved. - Fixed a bug causing /dkick not to work. - Improved error handling in purges - this should help debug in the rare event some messages fail to get deleted. - Other minor bugfixes and improvements. - Updated languages.

Rose update: - You can now set warn times with the /setwarntime command to decide how long a warn should last before it expires. - Added lots of alternative ban/mute/kick/warn commands to delete the replied to message, or be totally silent. Simply add a`d` or s in front of the command delete the replied to message, or to make the command silent. eg: /dban, /dmute, etc. d commands will Delete and ban the replied to message, and s commands will delete your command AND the replied to message; make it Silent. Check the /help on bans or warnings for more information. - Bug fixes - Updated languages Enjoy! :)

In other news - Rose now has 40M users, across nearly 500k chats! 🎉🥳 Big thank you to everyone for helping the project grow this big. You're all a part of this!