Marie/Rose News

Still winning! just a few more updates to go and shell be done with the spam attack. The attack is still going on, but she should be ignoring the vast majority of messages now.

Rose is currently under a spam attack. Apologies for the brief downtime. Her protections have kicked in, so she currently catching up on the missed updated from all the non-spammy chats. Shell be back in a few minutes :) I'll make sure to edit the protections based on the information from this attack, to avoid this happening again.

Teeny tiny update: - Fixed a missing log channel string when importing chat data - When pinning a message, rose now links to the pinned message in the log channel message

Small Rose update: - Updated all languages. - Set "warns" to require the CanRestrict permissions. This is to avoid admins using warnings to ban users when they havent got ban rights. - Added a userid for fed creators in the /fedinfo command. Due to telegram's privacy logic, the mentions were often breaking, so this should make the data a little less useless. - When importing/exporting a backup file, forward the file to the logchannel for future reference. Behind the scenes: - Handled some leftover TODOs that I had lying about for a while. - Added some caching for some small bits and bobs of data that didnt require database accesses all the time.

Also, something else worth noting: The new admin permissions system makes it possible to whitelist users by promoting them to admin, without giving them any rights. This means youre able to select some users which you would like to be able to send blacklisted or locked messages, without lettig them ban or change your group settings. This is the main reason behind my question for the permissions needed for warnings - If we dont restrict the use of warns, those whitelisted users will suddenly be able to warn (and so possibly ban after repeat warns).

Connections should now work for group creators again :)

I found a bug which meant creators were being stuck with no rights (fuck you telegram) and have just fixed that. Sorry for the inconvenience :/ Also, removed the need for changeinfo when warning users; didnt make sense.

Rose update! - New admin rights! As detailed in this poll, rose now respects admin permissions. Only admins with promote rights can promote, etc. If you want to keep the old behaviour, read the help about admins and enable legacyadmin. This took me forever to get juuuust right - wanted it to be as easy and seamless as possible, and I think it worked! - Updated the blacklist matcher to fix some bugs people have been reporting. Should be faster than ever too, thanks to some new optimisations! - Added private notes. Enabling this will make Rose send a message with a button, which will redirect to the user's pm and send the note there. Easy! - Improved admin caching. You can now run the /admincache command to reset the cache! Of course, updated all translations too. To all those using the Russian translation, please go ahead and update your translations soon! At this rate, I'll have to remove it in a few weeks :( As usual - questions/bug reports in @RoseSupport. Enjoy!

Back up! Sorry for the downtime. WTAL at reasons later tonight.

Rose is currently down. I'm working on getting her back online. There are 104k updates to process, so I'm going to go ahead and drop them so that we dont have to wait🙃

Rose update: - Fixed a bug where Rose would complain that a message was too long to send when it wasn't actually too long. - Photo albums no longer count as multiple items in antiflood. Previously, an album with 6 photos would count as 6 separate messages. Now, it will only count as one. - Updated translations.

Rose update: - Added Persian translation. - Updated NL translation. - Added a helpful "Check fed admins" buttons on the output of the /fedinfo command, which allows you to quickly see the admins in a federation. - Fixed a bug where note links in buttons wouldn't work in connected chats. - A bunch of backend optimisations etc etc boring stuff for you but cool for rose Let us know if you find any bugs in @RoseSupport!

Updated translations - Rose now knows French!

And as a sidenote - if you want to see your language in rose, go ahead and translate it! I'll add it as soon as it reaches 90% :)

New feature time! - You can now save links to notes in your buttons. For example, to link a button called testme, you would make a button using [cool note](buttonurl://#testme). Clicking this button would then redirect to a pm with Rose, where tapping the start button will send the linked note. This helps reduce spam, as notes go straight to the user's PM, instead of polluting the chat. This can be used anywhere where buttons are supported, so you can even add notes to your welcome buttons! - Added a neat shortcut which allows for buttons which link to @chatname - Rose now automatically converts them to a t.me link. So creating a button for [this channel](buttonurl://@MarieNews) now works great! - And finally... I updated the translations. The russian language is beginning to lag behind, so if you're keen on keeping it available, please go update it on crowdin soon! :) Enjoy - and report any bugs in @RoseSupport!

Small bugfix update: - Saving new notes with {preview} sometimes required it being saved twice before the preview appeared. This has been fixed - the setting now takes effect on the first save. - Adding a fedbanned user to a chat did not ban them. This has been fixed - they will get kicked immediately. Head to @RoseSupport if you find any bugs!

Another small (but significant!) upgrade to Rose today: - Previously, fast userbots have been reported to send messages too quickly for Rose to mute them. This update improves welcomemute with some extra logic which should fix this, by getting Rose to delete those messages once they've been sent. Sounds simple enough, but damn was it frustrating to test!

Small Rose update today: - Fixed a bug with locks and telegram permission causing the wrong permissions to be applied to the chat. Will keep improving this until its perfect. - Massively improved antiflood - if someone spams your chat, rose now wont spam back with "X has been banned" messages. She should now only send one, and delete the rest silently! - Added the /pinned command which links to the current pinned message - Using /report or @admins in a private group now shows a message link in log channels, instead of the old forwarding approach Now that I've fixed the antiflood bug, I think I've figured out how to make welcomemute delete messages sent by bots too fast for rose to mute in time - that should be coming in the next few updates!

Another Rose update! - when doing /lock all, rose now uses the telegram permissions to stop users sending any messages. - added a new lock; invitelink! You can use this to stop people sending channel or group @, as well as t.me/ links. And you'll still be able to tag people, what a wonderful world! - setlang and import/export commands are now logged in the log channel - translations are updated - some new optimisations to avoid some of the load issues she's been experiencing. Lots more to come, but it's a start! I plan to add a whitelist feature to the invitelink lock which allows you to approve of certain channels/groups; such as an off topic group or a news channel. As usual, let us know in @RoseSupport if there are any odd bugs popping up, especially regarding locks!