Rose was down due to a scaleway network fuckup - She's back online now, and I've forced her to ignore the 500k messages shes received over the downtime to make sure she was available as quickly as possible.
Sorry for the downtime, I'll be discussing mitigation options for future occurences.

I'm going to start migrating Rose from Scaleway to Digital Ocean in the next hour or so. Digital ocean should be a lot more reliable than scaleway, which should make Rose more stable, and avoid issues like we experienced this morning.
Rose will be put in maintenance mode while I transfer the (surprisingly large) database from one server to another - this means she wont reply to any commands other than /start.

With the new provider, comes a a more expensive server - so if anyone would like to support Rose and help keep her alive, please donate; she can do with the money!

I will send updates here when this is completed.

Maintenance has started.

And maintenance is now over! Rose is now running on Digital Ocean :)

Small rose update:

- Updated translations
- Welcome mutes no longer remove the "add user" permission
- Lots of behind the scenes cache optimisations
- Some behind the scenes work to make future updates easier to apply

Small Rose update:
- Added noformat for filters. To use, simply say the filter name and noformat in the same message, and nothing else.
EG: for a filter named test, send test noformat to get the non-formatted version of the filter reply.
- Some more backend tweaks.

Also, worth noting that the cache changes added in yesterday's update has massivesly reduced CPU usage, meaning Rose will be able to keep scaling for the foreseeable future. Hurray for caching! 🎉

Rose update:

- Updated translations
- Added the /quietfed on/off command; send this to your chat to quietly remove fedbanned users that join the chat, instead of sending a "X has been removed because he is fbanned for reason Y in federation Z" message.
- While fedbanning, Rose will now edit the "Beginning fedban..." message, to reduce clutter.

Rose language update:
Rose now speaks chinese 🇨🇳!

Feel free to join us on crowdin if you would like to add your own language!

Rose update:
Rose now speaks hindi 🇮🇳!

Also, fixed a bug in imports causing blacklists to stop deleting messages

Rose update:

- Added the /blacklistdelete command. This can be used to enable/disable any blacklisted messages being deleted. If your blacklistmode is set to "nothing", Rose will simply reply not to send any more of these messages, and provide the reason specified. More info available in the help!
- Improved some more caching regarding locks and url whitelists. Should be faster than ever!
- Fixed some minor bugs (they should'nt have had an impact on anyone, but I knew they were there and that bothered me; plus, its an optimisation, so... 🤷‍♂️)
- Updated to latest translations. Thank you to everyone helping to translate!

I've also gone ahead and updated the donations string; I've been accepted onto the github sponsors program, which allows people to donate every month for a consistent income. This is super helpful, and makes it possible for me to judge how much I can afford to pay for Rose's servers :)
If you'd like to donate, please go ahead and do so either on github, or on paypal!

As usual, head over to @RoseSupport if you have any questions, or find any new bugs. Have a nice day! :)

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.

Nevermind, all back now!

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.

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.

Happy new year!!! 🎉

Ps: major update coming soon... 😉

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! 😊

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 :)

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.

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! :)

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.