Small Rose update:

- Fillings are now case-insensitive. This means that {first}, {First}, or even {FIRST} will all work as valid entries when using fillings, resolving one of the most common issues people have when using fillings; but no more! All fillings support this, whether you're looking to use user, admin, protect, nonotif... they're all there.
- The help, limits, and markdownhelp commands can now all be disabled.
- Improve fban logic when handling join requests; approving an fbanned user will now still fban that user.
- Make sure the /approved command also list approved channels, not just users.
- Make sure the filter comand gets deleted as expected when using cleancommand.
- Reports now reply to the reported message rather than the command that was used.
- Some other minor bugfixes and improvements.
- Updated translations, and added support for Columbian Spanish 🇨🇴! Big thank you to all that contributed.

Enjoy :) And as usual, if you'd like to support Rose, you can use Github Sponsors, crypto, or Tribute. Or, you can register for custom clone early access!

Small Rose update:

- Filters and blocklists now support prefix: and exact: matching syntax! This means that you can now stop users from sending lone "hi" messages in groups with the following command:
/addblocklist exact:hi Please don't send lone 'hi' messages! {warn}.
Similarly, you might want to make a custom command using filters which only triggers at the start of a message:
/filter prefix:/command You used a command!
- The /help's "back" button now links you back to the previous help section, making it much easier to navigate; it would previously always go back to the help's home.
- The admin ID of the admin that issued an action has now been added to logchannel entries.
- Bug fixes and improvements.
- Updated translations.

Enjoy :) And as usual, if you'd like to support Rose, you can use Github Sponsors, crypto, or Tribute. Or, you can register for custom clone early access!

Announcing Custom Instances!

That's right; we're proud to finally announce @RoseClone_bot, allowing admins to create their very own customised versions of @MissRose_bot.

Each bot comes with new exclusive features - including custom names and pictures to match your communities, increased blocklist and filter limits, echo and broadcast commands, repeated messages... and more to come!

So what are you waiting for? Create your own Rose at @RoseClone_bot now! More information on our website.

Enjoy!

Rose update!

- Added a new botlink locktype, which will delete any links (both t.me, or @) to bots. Paired with the invitelink lock, this should fight the referral spam that people are often facing these days!
- Renamed the story lock to forwardstory, to make it clearer that stories are a kind of forward.
- noformat now works on notes which have {private} specified.
- Improve permapin reliability on message edits with buttons.
- Added help section to mention features available in custom instances.
- The usual bugfixes and improvements.
- Updated translations.

⭐️ Custom Instances
- Custom instances now have the ability to "clean" rose's old messages, similar to how cleanwelcome works. This allows you to delete old actions, filters, or notes!

Enjoy :) And if you'd like to personalise your community, come get you own custom instance!

Rose update!

- Fixed some bugs with the botlinks locktype which caused it to also match private invitelinks. This is now fixed.
- Improved the CJK lock to correctly match the Hangul script.
- The usual bugfixes and improvements.
- Updated translations.

⭐️ Custom Instances
- Custom instances can now mark filters as custom commands using the {command} filling. That filter will then show in your group's command suggestion box ([/] in your text bar), giving you a built-in and intuitive way to easily explain which commands your users can use in your group! (docs)

Enjoy :) And if you'd like to personalise your community, come get you own custom instance!

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

To celebrate, we've cut the price of Rose Custom Instances by 40% until January 1st; now down to 1500 stars (~30$)!
It's been a wild ride finally getting these personalised Roses released, so we're looking forward to sharing them with more of you 😁

Telegram is currently experiencing some issues with their bot API, meaning Rose is currently unavailable.

Rose will recover once Telegram fix the issues on their end. Thank you all for your patience!

This has now been resolved!

Telegram seems to be having issues again.

As usual, Rose will recover once Telegram stabilises. Thank you for your patience.

Telegram seems to be back! :)

Woops, spoke too soon - still some instability going on. Should be mostly working, but with delays.

Has been fine for the last day so I'll mark this done!

Rose update:

- Add a new blocklist glob pattern, **. Where * will only block a single word, ** can be used to match any number of words. For example, follow ** x will stop follow me on X, as well as follow on X, or even follow blah blah blah blah X. Should be helpful to help fight spammers who send longer messages with a few key words in there!
- Added a new zalgo lock, to stop messages containing too many formatting characters (such as H̤̄͑ē̤͑̄l̤̄͑l̤̄͑ō̤͑̄ W̤̄͑ō̤͑̄r̤̄͑l̤̄͑d̤̄͑).
- Improve various features of the emojionly lock to make it more reliable and predictable.
- Allowlisting inline bots will now also allow those inline bots to send buttons.
- Webapp links in buttons can now also be allowlisted.
- If you set an action to use a silent warning, and hit the warning limit, then the ban/mute/kick will be silent too.
- Add more information to welcome logs for when users join through linked channels.
- Update emoji detection libraries to work with new emoji versions.
- /rules noformat will now ignore privaterule settings if used by admin.
- The 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!

Small Rose update:

- Add support for using backticks as a kind of quote when adding blocklists or filters. This should make it easier to avoid client markdown clashing with the bot's own syntax. For example, its now possible to use use /blocklist **test**
- Fix a bug where an admin note with media would sometimes still show media to the user.
- Fix a bug where the custom lock action of {nothing} wouldn't be shown in /locks. It now shows as expected.
- The usual bugfixes and improvements.
- Updated translations.

Custom clones:
- All of the above (of course!)
- Improved blocklist name matching to also trigger on join. Custom clones can now use syntax such as /blocklist name:@*bot to stop any users who have a bot username in their name from joining. This is particularly handy against the latest wave of spammers that's been plaguing telegram.
Pair it with silent actions to hide the entire process from users! /blocklist name:@*bot {sban}

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

Happy Easter everyone! 🐣

To celebrate, we're offering 40% off custom rose instances; down from 2500 to 1500 stars ($30) until the end of April.
So, are you looking to customise your group chat with your own bot? Take advantage of higher limits, broadcasts, name blocklists and more? Try out your own clone!😄

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