We're aware of an issue where Rose has mistakenly been flagged for copyright infringement. Obviously, this is incorrect, and we've contacted telegram to get this rectified. Mistakes happen!

We'll keep you posted as soon as this gets fixed. Thank you for your support and patience.

Aaand were back - apologies for the scare! Maybe try out a custom clone if you'd like 👀

Small Rose update!

- Fix a bug where a notename with an &, or other html-escaped characters, couldn't be used in note buttons.
- Make sure that the default blocklist reason supports markdown, same as all other lock and blocklist reasons.
- Make sure logchannels don't try to log usernames for joinrequests in chats that don't have a username.
- The usual bugfixes and improvements.
- Update translations.
- Added new serbian-cyrilic language 🇷🇸; thank you to all who contributed!


Enjoy :) And if you'd like to customise Rose's picture to fit your community, come get your own custom instance!

Rose update!

- Added support for a new "checklist" lock, to delete checklists from telegram's latest update.
- Updated cleanservice to handle the new checklist service messages.
- Added support for a new "cashtags" lock, which deletes messages containing what telegram calls cashtags; they look like this: $CASH.
- Improved the zalgo lock to avoid some edge cases when used with emoji
- Improved blocklists to also match various similar characters, such as cyrillic letters which can be confused with latin letters. See followup post; use the lookalike blocklist prefix to match words which look like they might match, but use mixed scripts!
- Usual bugfixes and improvements.
- Updated translations.

Enjoy :) And if you'd like to customise Rose's picture to fit your community, come get your own custom instance!

Just undid the changes handling normalisation of blocklists to improve matching of lookalike characters, as this was causing issues in multiple international groups.

I do still think this is a very helpful feature for fighting spam though! So if you would like to keep using those changes, this is now possible by using the lookalike prefix. Just use:
/blocklist lookalike:bot to stop users from sending messages containing things like bot, вот, or b0t.

Enjoy, and apologies to anyone who faced any issues with this.

Telegram has been experiencing some issues for the last few hours, causing delayed responses from Rose, due to the high load of users.

We're monitoring and looking into possible solutions, but it looks like the issue is in telegrams end.
If you're running a large monetised community, I can recommend getting a custom instance; these private clones of Rose won't have any issues with load!

Rose has been running smoothly for the last hour - everything should be good to go again!

Rose update!

We're excited to add a new feature which we expect will be very helpful in fighting some common spam messages; namely, custom emoji blocklists! Similar to how you can already blocklist stickerpacks, you can now also blocklist emojipacks.
To do this, simply reply to a message containing custom emoji, and use the /addblocklist emojipack:<> syntax. This will blocklist every custom emoji pack in that message, protecting you from further spam.

Other updates:
- Also added support for allowlisting custom emoji when emojicustom has been locked. Same as for blocklists, simply use the /allowlist emojipack:<> syntax!
- Updated the /help command to have a button to the docs website at missrose.org/docs - hopefully the search function can be helpful!
- Significant performance improvements to help minimise recent telegram blips.
- Improve performance for the cleanwelcome feature.
- Improve overall performance monitoring tooling to ensure we can stay reactive to telegram issues.
- Initial steps for further performance improvements over the next few updates.
- The usual bugfixes and improvements.
- Updated translations.
- Added support for the Catalan 🇪🇸 language! Big thank you to everyone who contributed.

Enjoy :) And if you'd like to customise Rose's picture to fit your community, come get your own custom instance!

Hi all, Telegram seems to be having some issues again, showing a large spike of timeout errors.

We're investigating, but ultimately it doesn't look like there's much we can do other than wait for telegram to recover.

If you're using Rose in commercial groups, my best advice is to get a custom instance, as the dedicated bots will be much less subject to telegram's limits.

Thank you for your patience!

Telegram has recovered, everything should be fine again. I'm going to keep investigating to see what else can be done to reduce these issues.

Rose is having issues due to a network issue seems to be ongoing between telegram and hetzner, my server provider. It is unclear who is responsible between the two.

We are investigating, but rose may be responding with delays.

The issue seems to have resolved itself, but I'll keep investigating with hetzner and telegram to see what can be done.

As many of you are already aware, telegram has been experiencing significant issues with their bot API over the last few hours. This is affecting all bots, and has meant significant delays on rose's responses.

There's sadly not much to be done on our side other than wait for telegram to recover - this isn't something in our control.

Thank you for your patience.

Everything should be back, thanks everyone for your patience

Hi all,
My apologies for anyone who had Rose send unwanted error messages in their groups today. A recent configuration change to improve roses handling of telegram updates and improve stability caused Rose to hit a connection limit trying to connect to its cache - which was not the goal.

I've now fixed the issue, and expect Rose to be working as usual again. I'm hopeful that these new changes will help avoid the delays that have been occurring over the last few days, and keep Rose snappy.
Thank you all for your patience, and for helping make Rose the bot she is! ❤️

Hi all,

Two weeks since my last post about working on Rose's performance. Uneventful for Rose, but very eventful for me, as I've been hard at work adding new optimisations in the background to fix any bottlenecks that had creeped in! We now have:
- a faster blocklist matcher
- improved caching logic
- tuned database/cache connections
- and more to come; still have some things I'd like to mark as done!
And all the changes have given me the opportunity to add some more performance metrics, so it'll be easier for me to spot where issues come from in the future. Really happy with the progress so far 🎉

As part of these changes, I released a small update to Rose earlier today, which now has Rose asking users to do a one-time verification of new groups via a webapp before Rose starts working. I understand this has caused some confusion - don't worry! All normal, I'm just trying out something new to help fight spam groups who add Rose but then don't use her. I've just updated the message to try and make that clearer.

Thank you, and enjoy :)

Wishing everyone Happy Holidays from the Rose team! ⛄️🎉

It's been a massive year for Rose, with the userbase growing at an unprecedented rate - we're nearing 1 billion total users!
It brought along lots of new challenges with scaling and optimisations, but I'm excited by how we've handled each one. Have some interesting new features planned for next year, so looking forward to sharing more details once they're done! 😄🎉

Rose update!

Telegram released their latest bot api version a few days ago - meaning we have some new features to play with!
- You can now save Premium Emoji in Rose's messages! 🎉
- Buttons now support different styles - "primary", "danger" and "success". These are shown as blue, red, and green buttons, respectively.
With this update, Rose now allows you to display these button styles by using the new buttonurl#<style> syntax. For example, you can set a green success button with: [A Button](buttonurl#success://example.com)
- The CleanService module has been updated to support some of the new service messages that bots receive.

On top of that, we have a few more features from Rose's side:
- Log channels can now only be set up by the group owner, to help keep crucial settings logged.
- Using the leavefed command in PM now uses the correct chat name.
- Filters will now also match on dice triggers.
- Federations no longer get enforced when an admin unbans a user - this should allow groups to remove deleted accounts if they want to clean their ban lists.
- The usual bugfixes and improvements, and as well as massive amount of internal refactors and performance improvements.
- Updated all translations.

Enjoy :) And if you'd like to customise Rose's picture to fit your community, come get your own custom instance!

Hey everyone! 👋

A quick aside from the usual Rose updates, but bear with me! I'm the solo developer behind Rose, and I'm working on making the bot even better for group admins like you.
I'd love to hear about your experience managing groups - what's working, what's frustrating, and what challenges you're facing. This will directly help me figure out what to focus on next!

It only takes 2-3 minutes: https://forms.gle/JefZQ9zSFvQPqBLs5 edit: Closed, thank you for all the feedback!

Thank you for helping me make Rose better! 🌹

Hello everyone!

One of the overwhelming pieces of feedback i got after launching custom clones was that the price was too high.

So, after a lot of behind-the-scenes action, I'm launching a new way to get your own custom Rose bot, at a significantly lower price point.

Introducing Rose Core — your own branded bot for just $10/month.
Everything you love about the free version, plus:
✓ Your own bot with custom name and picture
✓ Use across up to 5 groups
✓ Increased limits on filters, notes, and blocklists
✓ Exclusive features like broadcasts, echo, and scheduled messages

The existing custom instance option is now Rose Premium ($50/month), featuring more groups and premium support.

Check it all out on our website - or create your new bot in @RoseClone_bot now! 🎉🌹