Marie/Rose News

Maintenance is now beginning.

Hi all, me again. Thanks to the overwhelming number of donations over the past few hours (really, thank you!) and some helpful tips on server availabilities, we believe we've found somewhere reasonable to run Rose efficiently. To make sure everyone can keep relying on Rose, we would like to get this done as soon as possible; at 7pm UTC, tonight - in one hour. We expect the maintenance to last 3 hours, like last time. Hopefully, everyone agrees that a slow Rose is not helpful, and understands why this maintenance is so urgent! Thank you for your patience.

Hi all. I'm sure many of you have noticed that Rose has been having some delays over the past few days, and are wondering why. The short answer is, we cannot afford to upgrade her to a larger server with the current donations. If we don't upgrade her, she will keep being slow. The maintenance we did the other day was to extend the storage of the database. However, the new storage is too slow to handle Rose's traffic, which is what is causing this issue. There are no other companies which would allow extending the storage at fast enough speeds - I've checked. To fix this, we need a new server, with more storage. This is expensive. A server big enough for rose's size would cost us £200 (260 USD, 230€) per month. Currently, we receive £120 (160 USD, 140€). Which is why I'm turning to you - if you enjoy using Rose, and would like to see Rose keep growing, please setup a monthly donation here. You would be helping millions of users use one of telegrams largest bots, reducing spam, and making communities a safer place for everyone. Sorry for the awkward message, and thank you in advance! Paul

Rose update: This is a VERY small initial update to support the bot API 5.5. Under normal circumstances, we would usually group together all the new features that the new bot API provides Rose into a single update. However, we've experienced so much spam over the last two days, that we've decided to release a small preview to handle the new anonymous channel spamming. Features: - Added a new locktype, anonchannel. Use /lock anonchannel in your groups to stop anonymous channels sending messages into your chats. - Ensure that blocklists and locks work as expected on anonymous channels. - Internal bugfixes to prepare for full bot API 5.5 support. We are aware that many commands, such as /ban and /fban, are not yet ready to be used against anonymous channels. Rest assured, we are working hard to get them ready in the next update. Thank you for your patience, and enjoy!

We have been receiving several inquiries regarding the recent changes from Telegram, which are causing many groups to experience issues in regards to channels and spam. Rest assured, we are working on implementing the ability to ban channels to fight this type of abuse. However, this does require some work to implement, and also time for us to test to ensure it does not negatively impact Rose's performance - or cause any new issues. We ask that you remain patient while we perform the necessary work and testing to get this added for you, and as soon as this feature is available for use, we will post an announcement to let everyone know.

Migration completed. Rose should be back up and running. There are currently no new features added yet - the latest bot API update will be added later this week. Thank you for your patience!

The migration is still ongoing. Expect another 30 minutes of downtime.

The migration has begun.

Reminder: The migration will begin at 7pm UTC; in 30 minutes. Rose will be unavailable during approximately 2 hours while the maintenance is ongoing.

Small Rose update: Updated all translations and languages. As usual, if youre interested in helping to translate Rose, join us on crowdin! On another note, we are planning to go through Rose's database maintenance tomorrow at 7pm UTC. As mentioned above, this should result in a downtime of approximately 2 hours. Will keep you updated nearer to the maintenance window.

Following yesterday's update - we intend to go through with the database maintenance tomorrow evening at 8pm UTC. The aim of this maintenance is to increase her available storage, allowing us to keep her working as expected. This will cause some downtime with Rose - we expect her to be unavailable for approximately 2 hours. Thank you for your understanding! Will provide more updates nearer to the time. The above maintenance has been postponed to a later date.

Rose has just reached 200M total users, across 2.6M chats! 🎉 Very strange to look back to a year ago, when we were celebrating 60M total users - especially when we now have over 46M monthly active users! This is no small feat, and we couldn't have done it without you all. Thank you! Of course, nothing is perfect - with this massive growth, Rose is now, yet again, growing too big for her server. Her database has grown so large that she will soon need some maintenance to increase her storage. This change will increase our costs, which leads me to my next point - if you enjoy using Rose, and want to support the project, please consider donating on PayPal, or even better - becoming a GitHub sponsor! This will allow us to assess exactly what we can afford for our next upgrade, and keep Rose running in peak condition somewhere nice. In turn, that should keep performance sky-high; everyones happy! Will let you know over the next few days when our migration is planned for, and what our time estimates are like. Thanks again to everyone using Rose, have a great day! 😄

Telegram seems to be having some issues and causing delays with Rose. Ive locked the chat until this is resolved to avoid confusion and spam. This has now stabilised, chat unlocked.

Rose bugfix update! - Manual pins are now also logged in the log channel. - Fixed a bug where filters might be unintentionally triggered when using unusual unicode. - Fix the /stopall command when connected. - Remove unnecessary delete permission for enabling cleanwelcome settings. - Fix incorrect importing of certain welcome settings. - Fix incorrectly named logchannel item. - Fix a mention parsing issue when using names with non-latin characters. - Lots more backend optimisations and fixes to improve usage and performance. - Updated translations. This update also brings two new languages - 🇧🇾 Belarusian, and 🇵🇹 Portuguese! A big thank you to everyone who contributed. Enjoy, and as usual, let us know in the support chat if you have any issues!

New Rose update! Lots of fixes and improvements today, aiming to make Rose clearer and more helpful for everyone. - Improved log channels. Log channels now log manual admin actions as well as actions performed through Rose! This should help you manage what your admins are doing in your chat, longer than recent actions. - New /privacy command! Show's Rose's privacy policy, and allows you to export and delete your personal data. We don't store anything unless we absolutely need to, and we want that to be clear to everyone! Use it in PM to get more info. - Limited the number of feds a user can be admin in to a maximum of 20. We've been seeing some people misusing federations to ban people in hundreds of feds at the same time, which harms everyone. If you want to share your fbans, use fed subscriptions instead - that's what they're there for. - Fixed an issue with admin titles not being set as expected when using /promote - Fixed an issue where /antichannelpin wouldn't work in certain chats - Lots of bugfixes and improvements. - Updated translations. Thank you, and enjoy the update! As usual, join us in the support chat if you have any questions.

Small Rose update: - Fix a bug where chat imports wouldnt import all settings. - Reduced chat import/export cooldown times. Due to recent performance improvements, this can now be used once ever 30 minutes, instead of 3 hours! - Fix a bug where permapins sometimes wouldnt pin - The forward lock now allows for whitelisting of users/chats who should be able to be forwarded from. Simply allowlist their username! The latest migration has been a great success on our side, so we're looking forward to adding lots of new features over the next few weeks :)

Fban checks on Rose have been reenabled. Everything should be back to normal now! :)

Rose has been reenabled. Fban checks have been temporarily disabled, for performance reasons - we're investigating what the cause of this is. To clarify: You can still fban, but fbanned users joining a chat will not get banned. Sorry for the inconvenience.

Hello everyone, unfortunately Rose is experiencing some issues and she is currently unresponsive. We are actively looking for a solution and we’ll keep you updated. Sorry for the inconvenience!

Rose is back. Right on time! Sorry for the delay everyone, everything is now running better than ever :) This has been quite a big update on the Rose internals - so if you find any bugs, or have any issues over the next few days, please reach out in the support chat, as usual. Thank you!