Marie/Rose News

We are receiving questions and complaints about the support group being unavailable for "copyright infringement". We are aware of this issue, it isn't the first time that something similar happens, and we're actively trying to solve this issue, once again. Obviously, the chat has been flagged incorrectly, and Telegram will hopefully revert the mistake as quickly as possible. We will keep you posted as soon as news and informations are available. In the meanwhile, thank you for your support and your patience!

Rose update: -/fstat now shows who fbanned the user when used by an admin of the same fed. If the fban was an import, it will show as imported. This only shows for admin of the same fed to avoid personal attacks. - /fedimport now allows you to choose between two different modes; overwrite, or keep. This decides what to do with any duplicate fbans; whether to overwrite them (use the reason from the import) or to keep them (keep the existing reason). - Fixed a bug where Rose would try to reply with filters to a deleted sban/smute/skick command and throw an error. - Fixed a bug where Rose couldn't update fban reasons when the new fban command was deleted. - Log channels now log to the old channel that a new channel is now in use. - Updated translations. As I said last time; Malayalam, Tamil and Khmer speakers, please update your translations on crowdin, or they will be removed. Enjoy!

Small Rose update: - All Antiraid commands now work through connections! - When an admin uses the /info command, Rose now shows if the selected user is admin, banned, or muted in that chat. - /raid now no longer works; use /antiraid instead. - Fix a small bug where the lock reason would HTML escape some characters, causing weird output. - More backend improvements and fixes. - Updated translations. Note: Malayalam, Tamil, and Khmer speakers - please update crowdin soon, or your language could be removed! Enjoy!

Rose update! This is a big one, and has been a while in the making - we're very excited to share it with you! - Introducing custom lock actions and reasons. Up until now, locks have only been able to delete messages; with this new feature, it is now possible to specify custom actions for different locks! To use them, simply use the normal lock command with the categories as usual, followed by ###, and then your reason or custom action. For example, to ban anyone promoting their chat, simply use: /lock invitelink ### No promoting other chats! {ban} With this set, anyone sharing their group link will get banned with the reason "No promoting other chats". You can check your existing lock settings with /locks. - Introducing silent automated actions. Custom lock actions are great, but some actions should just be quiet. This new feature makes it possible to use silent actions in both locks, blocklists, and antiflood. Check the help for how to enable these in your chat! - Show whether a note is {private} or {noprivate} in the output of /notes. - Reworked the output of /locks to be more readable. If you still want the full list that was shown before, use /locks list instead. - Updated the /donate string. - Lots of bugfixes and performance improvements. - Updated translations. Enjoy! And if you'd like to show your support, please consider donating with /donate!

Rose is currently experiencing some issues with the Telegram servers, and we’re actively working on it (and waiting for Telegram to fix what’s broken in their side). As a result Rose is unresponsive at the moment. We’re sorry for the inconvenience and we’ll keep you posted when new updates are available. Thanks for your patience!

Small Rose update: - Rose now speaks Malay 🇲🇾! A big thank you to everyone that has contributed to this translation. - Small backend bugfixes and improvements. - Updated translations. Enjoy!

We are aware of an issue where Rose has been mistakenly marked as a scam. Of course, this is incorrect . We are working with telegram to get this fixed. Please be patient while we get things back to normal.

New Rose update! - Added a new option to automatically enable AntiRaid. If hundreds of users join your group very quickly, it can be worrying and stressful, and it can take some time to react. To keep your group protected, you can enable /autoantiraid, which automatically enables antiraid if too many people join in a short period of time. Read more about it in the /help! For example, /autoantiraid 15 will automatically enable antiraid if more than 15 people join in under a minute. - Renamed the /raid command to /antiraid. /raid will keep working for a few weeks, but will be renamed completely in the future. - Lots of small usage improvements. - @admin tags no longer trigger reports if sent in code font. - Use full names in log channels and fed logs. - Updated translations. Enjoy!

Rose update: - Added a new {protect} filling for both notes and filters, which allows you to mark them as "protected content" on telegram. This will stop people from forwarding, or screenshotting, those messages. Great to stop people sharing your content! Eg: /save example This note cannot be forwarded {protect} - Added a new confirmation button for fedban reason updates. Rose will now ask you to confirm if you would like to update the fban reason when you attempt to fban an already-fbanned user. - The /import and /export commands now show which modules were imported (if they were explicitly specified). - Backend improvements. - Updated translations. If anyone speaks Malayalam or Khmer, please update crowdin as soon as possible - translations are running behind, and could be removed if not updated soon! Enjoy!

Rose update: - Blocklists now trigger on weird characters. For example, if you blocklist money, and a user sends "𝐦𝐨𝐧𝐞𝐲", Rose will now try her best to recognise these weird characters and delete the message as expected. This should help lots against spammers using weird fonts to avoid blocklists! - Backend improvements - Updated translations Enjoy!

Rose update: - /adminerror can now be used to enable/disable the errors sent by Rose when a non-admin sends an admin command. This can be useful to reduce command spam in larger groups, where users might try commands that theyre not allowed to use. Could also help for chats which use other bots that clash with Rose's admin commands! To enable it, simply use /adminerror off. Rose will then stop replying to users sending admin commands. - Updated translations. Enjoy!

Rose update: - Added a new raid mode! This allows you to defend your chats from telegram raids. A "raid" is when hundreds (or thousands!) of users join your chat at the same time to spam. When you enable raid mode, Rose will temp ban all new users who join for the next couple of hours, keeping your chat protected, and allowing conversation to continue as usual. To enable raidmode, simply use the /raid command. You can then disable it by running the same command again. Raid mode durations can be customised to suit your needs - check the /help on raids for more info. - Improvements to the display of warning settings. - Bugfixes and big performance improvements. - Updated languages. As usual, join us in the support chat if you have any questions. Enjoy!

Happy new year everyone! :) 🎊

Small Rose update: - Added a spoiler lock type, to stop users from hiding their messages behind spoiler tags. Enjoy!

Rose upgrade: Telegram have updated to the Bot API 5.6, adding a brand new formatting type; spoilers! And if telegram supports something, then so must Rose. To use spoilers, simply save a message with a spoiler tag as you usually would. That is, use /save test ||these are spoilers||. Note: older apps may not support this yet. Make sure to upgrade your telegram client to the latest version if this doesn't work for you. Enjoy!

Telegram seems to be experiencing some issues at the moment. This is causing delays with multiple bots across telegram. Rose will recover when telegram does - thank you for your patience. Telegram is back. I've dropped a lot of pending messages to get Rose back online as fast as possible. Should be all good now 🎉

Can confirm, it looks like our server provider is undergoing network maintenance. We're leaving rose online, and hopefully she'll be able to catch-up when the maintenance eventually finishes. With a bit of luck, it'll finish earlier than Hetzner have estimated. Sorry for yet another section of downtime - this is completely out of control, and sucks just as much for us as it does for you. Thank you for your understanding! Looks like Rose is back to normal for now. Hopefully the network won't degrade any further for the next couple of hours, and we can all enjoy some stability. Thank you!

Telegram seems to be experiencing issues, which is causing rose to have delayed responses. Update: our server provider is currently experiencing network issues, which means rose can't receive or send messages. Please bear with us while we look to solve this. We are still investigating.

Rose Update: Rose now fully supports the bot API 5.5! 🎉 This means that you should now be fully equipped to fight spammers posting as anonymous channels. In particular: - Full support for anonymous channels. - You can now /ban and /fban channels (and of course, unban them!). - Antiflood, blocklists, and locks now all work as expected against channels. Note: Due to limitations of the bot API, bots cannot "kick" or "mute" channels. Therefore, Rose will ban channels instead, even if youve configured Rose to do otherwise. - You can now /approve channels to allow them to speak in your group. This might be helpful for group admins who would like to speak as channels, but still want the anonchannel lock to be enabled! Finally, Rose now knows Taiwanese 🇹🇼! A big thank you to everyone who contributed. Also updated all the existing strings. Enjoy the update, and as usual, report any bugs in the support chat.

Migration completed. Looks like a big success, things seem much faster than they were before. Enjoy the speedy Rose everyone! And a big thank you to everyone donating to make this possible ❤️