Marie/Rose News

Rose update: - Major optimisations. Rose now uses less than 20% CPU at peak times. With 15M users and 150k chats, that's no small feat! - Improved the lock whitelist. Previously, there had been a bug where one item could appear multiple times in one whitelist; this has been fixed - each item is now unique. - Updated all translations (note: Hebrew, Italian, Colombian Spanish, and Uruguayan Spanish are trailing behind - please update them if you can!) As an aside, I'd like to remind everyone that the Rose server is entirely paid for by donations. So if you enjoy using Rose and would like to donate to keep her server running, please do so on github, or paypal. Funds are getting low, so every little helps!

On the bright side - from what I can see, the maintenance achieved what I was hoping for; massive CPU improvements from the database. That is to say - CPU usage has been cut by 60-70%, which means Rose can handle even more load than she could before. I'll keep monitoring this closely over the next few days to make sure nothing is going wrong.

Rose is back up. Had some major issues with the database - no data was lost, and it should all be back up and running now. Sorry for the inconvenience!

It is now 2am and the restoration is still going. I will keep rose offline for the night and get her back online tomorrow morning. Sorry for the inconvenience.

Maintenance taking longer than expected. Sorry for the inconvenience, doing my best to get everything back up and running!

Rose is currently under maintenance - apologies for any issues!

Rose update: - Improve caching for federations. Most federation related actions should now happen a lot faster. - Add minicsv mode to the /fbanlist command. As usual, let us know in @RoseSupportChat if you find any issues with the update. Edit: Update temporarily reverted while I fix a bug that popped up :) Edit2: Re-released, with bugfixes.

Rose Update: - Bugfixes and optimisations. - Updated languages. - Added the /clearall command to clear all notes in a chat. This is an owner-only command. - Added the /stopall command to stop all filters in a chat. This is an owner-only command. - Added the /unblacklistall command to remove the entire blacklist in a chat. This is an owner only command. All three of these command require confirmation before being executed. Please be careful using these - once you have deleted your data, you cant get it back. Please not that the following languages are trailing behind and will need updating in the near future: - Hebrew - Italian - Brazilian Portuguese - Columbian Spanish - Uruguayan Spanish If you are a fluent in these languages (or would like to add new ones), please come contribute on crowdin! Enjoy :)

Small Rose update: - privatenotes now just send the note when used in a connection - Added Vietnamese to the rose list of languages!🇻🇳 Big thanks to all the translators out there that are helping make Rose international :)

Rose update: Addressed some more more markdown issues that were raised today. - Some broken buttons should now work again - Weird text in buttons should stop appearing

Bugfix update: - Fixed a markdown issue stopping people from adding buttons to new notes (did that this morning but heyho). - Fixed a markdown issue where text wasn't being added to some new notes. New parser == new issues... Luckily, that should be it now :). - Unmuting a user now fully removes them from the restricted users list. Remember that the last update added new strings, so there might be some work to do on crowdin to keep your languages up to date.

Rose update: Added support for Bot API 4.5: - You can now set admin titles through Rose! Use /promote @user sometitle to set a user admin title. - Rewrote the entire markdown logic parsers to support nested logic, and the new parse types. This means the entire parser should be more stable, and it adds support for ~strikethrough~ and __underline__ types. I also added support for ```codeblock```, since I realised that was missing! - Added some new error handling for promote/demotes. - Some small bug fixes here and there. Enjoy! :)

Can you see it? That tiny misalignment on the first command? Yeah, so can I. But no more. Rose update: - Very important formatting fix for the /connection command. - That's it. - There were no other changes.

I've also re-enabled the support chat @RoseSupportChat, as a gesture of good faith that 2020 has somehow improved telegram overnight. Hoping for the best :)

New year, new update! Here are some of the latest updates to Rose, available as of right now: - You can now add a default blacklist reason, using the /setblacklistreason command. This can be used to replace the default blacklist reason, to avoid rose mentioning any blacklisted words in her warnings/reasons. - Each log channel entry now has a message link to the command/relevant message. - The fban message is now a single message, instead of a weird send-edit that was confusing some clients. - Adding a group link, ID, or @name to the lock whitelist will now stop locks from acting on any invitelinks, or forwarded messages from channels. Note that the current chat is always whitelisted. This is done using the same /whitelist command that is currently in use. - Log channels now have categories; you can now enable/disable separate log information that you aren't interested in. Eg: disable everything except for reports, and automated bot actions (from antiflood, blacklists) - Log channels now log user joins/leaves. - Fixed a bug where the /quietfed setting wasn't being saved properly. - Multiple backend improvements to caching, networking, and general code readability :) - Updated languages. I'll also be adding some new bot API 4.5 features soon, but wanted to get these ones released ASAP! Enjoy, and happy new year! 😊

Happy new year!!! 🎉 Ps: major update coming soon... 😉

I've also changed the fed log to be sent to @RoseSupportFed, so anyone interested in who gets fedbanned from the Rose Support federation can see from there.

Due to some pretty terrible human interactions over the last few weeks, and a serious case of telegram burnout, I've decided to close the Rose Support group and move everything to a help channel instead. Introducing the @RoseSupportChannel. A basic collection of help to answer the most popular questions. I'll be adding more basic help there over the next few days. Don't PM me, or any of the other Rose Admins. You will be reported and blocked. Thanks.

Nevermind, all back now!

Telegram seems to be having some issues - hence Rose is temporarily down. I'll be analysing the situation and trying to get her back up and running ASAP.