Small Rose update:

- Revamp of /help command. Updated the look, and reworked the internals to improve future feature flexibility.
- Bugfixes.

Second Rose update of the day:

- Added the /antichannelpin command. This unpins channel messages that telegram automatically pins in any chats that have been linked to a channel (because of the 'discuss' feature). Rose will automatically re-pin the previous pinned message.
- Added the {private} and {noprivate} fillings to notes. These allow you to choose whether this note gets sent to private chat or not. Similar to how blacklists allow you to specify individual modes with {warn} or {ban}, you can now individually set whether a note should go to PM, regardless of the group's /privatenotes setting.
- Updated translations.
- Other minor changes.

Remember to contribute your language translations on crowdin!

Rose update:

- Added the /resetallwarns command, which allows the chat creator to reset the warns of every user in the chat.
- Various backend fixes and optimisations.
- Updated translations.

Rose update:

- Added the /feddemoteme <fedid> command. This allows you to demote yourself from a federation. Can be used when you've been added to a federation against your will.
- The /fedpromote command now requires confirmation from the admin being added to avoid people adding others to random feds without their knowledge.
- The /myfeds command can be used to list all federations you are admin in.
- Updated translations.

Rose update:

- Backend cleaning, optimisations, improved caching.
- When antichannelpin is enabled, Rose now deletes any new "Rose has pinned..." messages that occur because of her re-pinning after a channel message.
- Minor bugfixes.
- Updated translations.

Small Rose update:

- Add an option to lock the new telegram type, darts. Use /lock dart to stop people using the random 🎯 sticker!

Rose update:

- Blacklists now also look at file names. This means you can blacklist file extensions! For example, use /addblacklist *.zip No zip files here!" to stop people sharing zip files.
- Blacklisting an emoji will also delete any sticker tied to that emoji.
- Updated translations.

Rose update:

- /fedinfo now also shows the fedsubscriptions for a given fed.
- To mirror this, /fedsubs can now be used by all users.
- Various backend improvements.
- Updated translations.

Minor Rose update:

Since telegram seems to keep wanting to add new emoji games, such as 🎲, 🎯, and the recently added 🏀, I've grouped all three of these (as well as any future types) into one lock category - emojigames.
While it was nice to have individual locks, it's also super annoying for me (and admins in general) to have to update Rose's locks every time a new emojigame gets added. And since we don't know how many more emojigames telegram intends to add, better to merge them all into one lock now.

But if you do still reaaally want to stop individual emojigames, you can now use blacklists on an emoji to stop the corresponding game 😊

eg: /addblacklist 🏀 You're not allowed to have fun will stop any 🏀 emojigames.

As a sidenote:

If you want to teach Rose to speak your language, or recently found mistakes in the translation, please head to crowdin to help improve her! If your language isnt in that list, let us know in the support chat, and we'll add it ASAP :)

Minor Rose update:

- A few bug fixes; notably, bots that are added by admins no longer get muted.
- Lots of backend improvements/fixes.
- Updated translations.

Minor Rose update:

- Bug fixes and improvements.
- Improve markdown engine to reduce some issues caused when using the built-in telegram markdown parser.
- Updated translations.

Minor Rose update:

Since telegram have updated their bot API to allow detecting inline bots, I've added it as a locktype.

Use /lock inline to stop users from using any kind of inline bot!

OUTAGE:

Hi everyone,
Telegram's DC4 is currently offline. This is affecting several users, and unfortunately, also Rose since she uses DC4. Because this is a Telegram problem itself, nothing on our end can fix the issue, but it should be resolved once Telegram's DC4 comes back on line.

Thanks for your understanding and patience!

Cool, telegram seems to have fixed itself.
And of course, Rose has been back for a while now too - so nothing to worry about there.

In other, more uplifting news....
Rose update!

Today's update adds "approval" functionality.
Chat members can now be marked as "approved" by chat admins. Approved users will no longer be affected by locks, blacklists, antiflood, and fbans in that chat. This can help you mark certain members as "trusted", and allow them to post pictures, links, etc in your chat that you might not want regular, untrusted users to be posting. (Basically... This is a user whitelist!)
Check the /help on approvals for more info!

And as usual:
- Bugfixes.
- Updated translations.

As a side note: some of Rose's languages are lagging behind. If you're interested in keeping your language in Rose, keep it up to date on crowdin!
The following languages need attention:
- Albanian
- Arabic
- Hindi
- Persian/Farsi
- Spanish (Colombia)
- Spanish (Uruguay)
- Tamil

I've created a tool for those of you who have difficulty understanding the button syntax. The tool is a simple form you can access in your browser, where you enter all the button information and it will generate the code for you.

Please give it a try and let us know if there are any issues! :)

https://missrose.org/tools/buttons/

Rose update:

Introducing a new feature:
Welcome kicks!
Enable welcome kicks to kick any users that haven't unmuted themselves using the welcome mute button. You can even change the time before they get kicked to fit your group needs!

By default, this is disabled - check the help on greetings for information about how to enable, and how to set the desired time.

Note: welcome kicks will not apply to users that joined before this update.

Also:
- Minor bugfixes
- Updated translations

Minor Rose update:

/mute 1h and /smute 1h now tmutes a user, same as /tmute 1h would.
This is because I've noticed a lot of people mistakenly writing /mute 1h when they want to tmute - this should fix that.

Edit: found a small bug so reverted this - will re-enable later

This has been re-enabled! Should work as expected again.