All the latest news about Marie, and her little sister Rose!
Marie Support:
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:
- /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 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!
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!
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.
Hi all.
I'm sure many of you have noticed that Rose has been having some delays over the past few days, and are wondering why. The short answer is, we cannot afford to upgrade her to a larger server with the current donations. If we don't upgrade her, she will keep being slow.
The maintenance we did the other day was to extend the storage of the database. However, the new storage is too slow to handle Rose's traffic, which is what is causing this issue. There are no other companies which would allow extending the storage at fast enough speeds - I've checked.
To fix this, we need a new server, with more storage. This is expensive.
A server big enough for rose's size would cost us £200 (260 USD, 230€) per month.
Currently, we receive £120 (160 USD, 140€).
Which is why I'm turning to you - if you enjoy using Rose, and would like to see Rose keep growing, please setup a monthly donation here. You would be helping millions of users use one of telegrams largest bots, reducing spam, and making communities a safer place for everyone.
Sorry for the awkward message, and thank you in advance!
Paul
We have been receiving several inquiries regarding the recent changes from Telegram, which are causing many groups to experience issues in regards to channels and spam.
Rest assured, we are working on implementing the ability to ban channels to fight this type of abuse. However, this does require some work to implement, and also time for us to test to ensure it does not negatively impact Rose's performance - or cause any new issues.
We ask that you remain patient while we perform the necessary work and testing to get this added for you, and as soon as this feature is available for use, we will post an announcement to let everyone know.
The migration is still ongoing. Expect another 30 minutes of downtime.
Читать полностью…Reminder: The migration will begin at 7pm UTC; in 30 minutes.
Rose will be unavailable during approximately 2 hours while the maintenance is ongoing.
Following yesterday's update - we intend to go through with the database maintenance tomorrow evening at 8pm UTC.The above maintenance has been postponed to a later date.
The aim of this maintenance is to increase her available storage, allowing us to keep her working as expected.
This will cause some downtime with Rose - we expect her to be unavailable for approximately 2 hours.
Thank you for your understanding!
Will provide more updates nearer to the time.
New Rose update!
Lots of fixes and improvements today, aiming to make Rose clearer and more helpful for everyone.
- Improved log channels. Log channels now log manual admin actions as well as actions performed through Rose! This should help you manage what your admins are doing in your chat, longer than recent actions.
- New /privacy
command! Show's Rose's privacy policy, and allows you to export and delete your personal data. We don't store anything unless we absolutely need to, and we want that to be clear to everyone! Use it in PM to get more info.
- Limited the number of feds a user can be admin in to a maximum of 20
. We've been seeing some people misusing federations to ban people in hundreds of feds at the same time, which harms everyone. If you want to share your fbans, use fed subscriptions instead - that's what they're there for.
- Fixed an issue with admin titles not being set as expected when using /promote
- Fixed an issue where /antichannelpin
wouldn't work in certain chats
- Lots of bugfixes and improvements.
- Updated translations.
Thank you, and enjoy the update! As usual, join us in the support chat if you have any questions.
To make it easier to get channel IDs, the /id
command can now be used to get channel IDs from forwarded messages.
Rose update:
- Added support for admin-only notes and filters. Rose will only reply when admins use these! To create an admin-only note, add the {admin}
filling. For example:/save secret Shhh, only admins can open this note! {admin}
- You can see which notes/filters are admin only when you use the /notes
or /filters
commands.
- Improved the /blocklist
command - you can now see what the custom blocklist actions are when checking the blocklisted words.
- You can now blocklist forwards and invitelinks from specific groups or channels simply by blocklisting their id. This is helpful if you would like to stop forwards JUST from those groups, but dont mind others! But if youre looking for blocking all... then check out locks.
- Other improvements and bugfixes.
- Updated languages.
If anyone speaks Taiwanese or Polish, please update crowdin as soon as possible - translations are behind.
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:
- 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!
Small Rose update:
- Added a spoiler
lock type, to stop users from hiding their messages behind spoiler tags.
Enjoy!
Telegram seems to be experiencing some issues at the moment. This is causing delays with multiple bots across telegram.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 🎉
Rose will recover when telegram does - thank you for your patience.
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.
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 ❤️
Hi all, me again.
Thanks to the overwhelming number of donations over the past few hours (really, thank you!) and some helpful tips on server availabilities, we believe we've found somewhere reasonable to run Rose efficiently.
To make sure everyone can keep relying on Rose, we would like to get this done as soon as possible; at 7pm UTC, tonight - in one hour. We expect the maintenance to last 3 hours, like last time.
Hopefully, everyone agrees that a slow Rose is not helpful, and understands why this maintenance is so urgent!
Thank you for your patience.
Rose update:
This is a VERY small initial update to support the bot API 5.5.
Under normal circumstances, we would usually group together all the new features that the new bot API provides Rose into a single update. However, we've experienced so much spam over the last two days, that we've decided to release a small preview to handle the new anonymous channel spamming.
Features:
- Added a new locktype, anonchannel
. Use /lock anonchannel
in your groups to stop anonymous channels sending messages into your chats.
- Ensure that blocklists and locks work as expected on anonymous channels.
- Internal bugfixes to prepare for full bot API 5.5 support.
We are aware that many commands, such as /ban and /fban, are not yet ready to be used against anonymous channels. Rest assured, we are working hard to get them ready in the next update.
Thank you for your patience, and enjoy!
Migration completed. Rose should be back up and running.
There are currently no new features added yet - the latest bot API update will be added later this week.
Thank you for your patience!
Small Rose update:
Updated all translations and languages. As usual, if youre interested in helping to translate Rose, join us on crowdin!
On another note, we are planning to go through Rose's database maintenance tomorrow at 7pm UTC. As mentioned above, this should result in a downtime of approximately 2 hours. Will keep you updated nearer to the maintenance window.
Rose has just reached 200M total users, across 2.6M chats! 🎉
Very strange to look back to a year ago, when we were celebrating 60M total users - especially when we now have over 46M monthly active users!
This is no small feat, and we couldn't have done it without you all. Thank you!
Of course, nothing is perfect - with this massive growth, Rose is now, yet again, growing too big for her server. Her database has grown so large that she will soon need some maintenance to increase her storage.
This change will increase our costs, which leads me to my next point - if you enjoy using Rose, and want to support the project, please consider donating on PayPal, or even better - becoming a GitHub sponsor! This will allow us to assess exactly what we can afford for our next upgrade, and keep Rose running in peak condition somewhere nice. In turn, that should keep performance sky-high; everyones happy!
Will let you know over the next few days when our migration is planned for, and what our time estimates are like.
Thanks again to everyone using Rose, have a great day! 😄
Small Rose update:
- Fix a bug where chat imports wouldnt import all settings.
- Reduced chat import/export cooldown times. Due to recent performance improvements, this can now be used once ever 30 minutes, instead of 3 hours!
- Fix a bug where permapins sometimes wouldnt pin
- The forward
lock now allows for whitelisting of users/chats who should be able to be forwarded from. Simply allowlist their username!
The latest migration has been a great success on our side, so we're looking forward to adding lots of new features over the next few weeks :)
Small note:
Previous update introduced a small bug when saving blocklists with no custom reason. This has now been fixed - sorry for the trouble!
^ This has been resolved. Telegram has removed all the incorrect tags.
Читать полностью…