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:

- 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!

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!

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.

This has now been fixed - apologies for the confusion.

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!

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 on 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!

Everything is back to normal, thank you again for your patience!

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!

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:

- /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).
- /info now shows more status fields; member, restricted and not in chat!
- Reports now also show the user id.
- 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.
- If you change log channels, Rose will now log that change to the old channel.
- Backend improvements.
- Updated translations.

As I said last time; Malayalam, Tamil and Khmer speakers, please update your translations on crowdin, or they will be removed.

Enjoy!

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!

This has now been fixed - telegram have removed the incorrect claims.
Thank you for your patience!

Note: if you still can't access the chat, try restarting your app.

New Rose update!

- You can now add and remove multiple blocklists or filters with a single command!
To do so, just wrap the list of names with (), and separate each one with commas.
For example:
/filter (one, two, three) test will add filters "one", "two", and "three".
/blocklist (hi, hey, hello) will blocklist "hi", "hey", and "hello".
Simple!
- /info now shows whether a user is approved in the current chat, as well as mute/ban durations.
- Log channels now show the full name of the user affected by an action.
- When anonadmin is enabled, log channels now show the title of the anonymous admin that performed an action instead of the chat name.
- Fixed a bug where setting the floodmode to mute 1m would mute forever.
- Fixed a bug where rose would send errors trying to reply to a deleted antiflood message.
- Allow /fstat to be used even on users rose hasn't seen yet.
- Backend improvements.
- Updated translations.

This is the last warning for Malayalam, Tamil, and Khmer languages - these will be removed in the next update if they are not updated on crowdin.

Enjoy!

Rose update:

- Added a new {nonotif} filling to notes/filters/welcomes etc, which stops the message from sending a notification in the chat. This is a feature which has often been requested for welcome messages in the past, to reduce notifications to users!
- Blocklisting filenames is now more powerful; blocklist file:*.jpg to blocklist all jpg files, while still allowing users to mention filenames! This is fully backwards compatible, so existing file blocks will still work.
- The {protect} filling to stop forwards/screenshots is now available everywhere that supports fillings.
- New locks: stickerpremium and stickeranimated. As named, they can be used to block premium and animated stickers.
- The /pinned and /donate messages now reply to the replied-to message, if available.
- Backend improvements and bugfixes.
- Updated translations.

Enjoy!
And if you'd like to help support us, please donate!

New Rose update:

- User-only filters! Limit your filters so that only users can trigger them (not admins!). This can be done simply by adding {user} to your filter text.
For example: /filter test Only users can see this {user}
If an admin wants to force rose to reply, they can use the "force" keyword; for example:test force will force rose to reply to the test note.
- The anonchannel lock now supports allowlists; you can allowlist a channel ID/username to allow them to speak, while still having other locks/blocklists/antiflood trigger on them. Much safer than approving channels completely!
- The command lock also supports allowlists! This might be useful if you want to stop all commands, except for a select few; for example, you might want to /allowlist /rules to let users check the rules.
- Allowlists have been improved for the matching to be more predictable. Let us know if you're seeing strange behaviour with the new format, and we can see how to fix your lists!
- Log channels now log join requests and join approvals.
- Fbans also work with join requests.
- Using /info on an anonymous channel will now show whether they are approved, to make it consistent with how it works on regular users.
- Lots of minor bugfixes, improvements, and updates.
- Updated translations.

Enjoy!
And remember to donate to support Rose :)

Small Rose update!

- New locktypes! emoji to stop all emoji, emojionly to stop messages which contain just emoji but no text, and emojicustom to stop Telegram's recently added custom emoji, which can be spammy, or contain NSFW content.
- The /locktypes command has been redesigned to show an explanation of each type of lock! Should make it easier for users to understand what each one does now.
- More improvements to url allowlist matching. Hopefully should be even more accurate now.
- Updated translations.

Enjoy! :)

Tiny Rose update:

Telegram recently announced that usernames can now be linked in a new way - for example, marienews.t.me would link to this channel.
Rose is now aware of this, and will consider this format to be an invitelink lock, same as t.me/MarieNews would be.

This change already works for everyone using the invitelink lock - no need to change anything.
Enjoy!

New Rose update!

This is a combination of lots of smaller improvements that people have been requesting for a while now, so it's good to get them ticked off!

- Added a new module named "Clean service", which allows you to control which service messages to delete, with much greater control. Pins, calls, joins, leaves - you choose! Check the /help for more information.
- Blocklists, locks, warns, ban, mute, and kick reasons now all support markdown, buttons, and fillings. This should make it easier to provide buttons and resources as part of your bot integrations!
- FBans now also support markdown (but no fillings/buttons, as these dont make as much sense in this context).
- You can now use the {replytag} filling in filters for Rose to reply to the user that the filter is replying to. This is very similar to what notes already do!
- Antiflood now comes with a new setting, called /clearflood. This allows you to set Rose to delete the flood messages that were sent.
- Antiflood strings have been reworked to ban when a user reaches the limit, rather than exceeds. A small, but important distinction! Also, the Nth message no longer gets deleted; only the following messages get deleted (unless you've enabled clearflood!).
- Lots of improvements to the help; fixed some typos, added new examples, and made some clarifications!
- Lots of bugfixes and improvements.
- Updated translations.

Enjoy!
And remember to donate to support Rose :)

On another note:
It is now that time of year where I'm going to need to do some server maintenance for some important infrastructure upgrades - the database is now outgrowing the server. Turns out, 360 million+ users requires a lot of storage!
This also means there will be quite an increase in cost; so if you'd like to show your support and help keep Rose alive, please donate!

My tentative date for this is Wednesday 12th of October, at 7PM GMT.
This will require some downtime, so Rose will be unavailable for a couple of hours.
More details to follow closer to the date!

We are planning on going forward with the server upgrade this Wednesday evening (October 12th) at 6pm UTC (or 7PM GMT, UK time).
There will be approximately 3 hours of downtime (depending on various factors) during which Rose will be completely unavailable.
We recommend locking your groups before the upgrade, to avoid spam during the downtime.

Apologies in advance for the inconvenience! And if you have any further questions, please ask in the support chat.

This is a reminder that the server migration will be starting in one hour.

However, I will be trying some fancy new settings, which should hopefully allow us to keep Rose online and operational for the majority of the switchover, rather than the expected 3 hours of downtime. Hooray! :D