Should be better now - the issue seems to be a mix of very odd timeouts (and poor error handling) from telegram, paired with some network delays from scaleway (that I have reported to them) resulting in a bot which receives all messages but can't reply to any of them.
I've done my best to avoid these issues by removing some calls which I believe aren't necessary, thus reducing the number of requests and hopefully reducing the timeout rates, and by changing some of the timeout limits.

Also; sorry for the late fix - I'm currently on a road trip holiday in the US without a laptop, so had to wait for a quiet moment to debug through my phone. Not fun!

Alright. I've just landed in Hong Kong after a 14 hour plane trip.
Last thing I saw was a report that rose was having issues. So I rebooted rose.
Scaleway has shit the bed and been "rebooting" the server for the last 14 hours, and it can't be force shutdown because it technically doesn't count as "on" when it's rebooting (great logic there scaleway). (schrodingers server anyone?)

So basically, I'm in an airport in a foreign country with no WiFi and no laptop, and I have another plane to catch in 3 hours.
I'm talking to scaleway now to get them to force reboot it on their side, and hopefully that'll fix things. Honestly no clue what happened, my best bet is genuinely some freak hardware fuck up on scaleway side given the logs I got when I sshed in, but had no time to debug.

Sorry for the troubles, I'll be fixing it as soon as I can (if I can - i reckon scaleway need to do stuff first). In the meantime, find a backup bot to use? Sorry!

Hey, at least scaleway are admitting their stuff is broken 🤷‍♂️

Rose should be back!

Going to leave the groups chats muted for a bit longer while I make sure everything is stable, but will unmute when I'm sure.

Post-Mortem:
Scaleway is bad and their hardware is bad and everything about them is bad (except their prices). I'll be moving to a more expensive and better reputed provider when I'm back from holiday. Thanks to all the generous souls that have offered more donations for switching providers! Will let you all know what the price increases are when I've switched.

I've taken some precautions to back up all the data just in case this happens again, but from what I can tell we should be all safe. I'm not sure what caused the issue with the database connection spam, but I'm still looking at it.

Sorry for the downtime, and enjoy Rose being back :)

Chats have been unmuted!

Rose has been under some major spam attacks over the last few days; if you feel like she's slowing down, that'll be why.
I'm still on holiday, so can't do anything to analyse the spam and defend against it - only option is to wait it out 🤷‍♂️ I've got a list of defences to implement when I make it home, so don't worry; I've got a plan to counter these downtimes!

Spamming commands at her won't make her reply sooner - so please don't! And please don't pm me or any other admins :)

To the spammers behind the attack:
You've clearly got lots of spare time, why not spend it doing something constructive, instead of being an inconvenience? Rose is a free product for everyone to enjoy - why not let them?

Rose has been under another spam attack. As I've said before, I'll be back from holiday soon and will be working to improve protections.

The only thing I can do is drop the missed uodates and restart her, which is what I'm about to do now.
Sorry for the downtime.

I've made a small initial set of changes to rose to begin my mega bugfix spree that will be happening over the next few days.
Currently, the progress is:

- updated all translations. I've scraped all the latest changes from crowdin, and added some new strings.
- saving a message with buttons also saves the buttons
- fixed some bugs in my markdown parsing causing some issues with escaping formatting
- automatically leave chats which have been connected to and are now unavailable; previously just errored with chat not found.
- rose doesn't report herself anymore
- the warn action string has been updated to reflect the action that is taken; ban/kick/mute/tban/tmute
- /mute should now also remove poll and add user permissions

There are a few other bugs/protections that I'm planning on fixing but haven't finished testing on my side and so haven't released yet. More to come :p

As usual, let us know in @RoseSupport if you find any bugs.

If you vote no, please go ahead and explain why in @RoseSupport :)

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!

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

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!

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

Updated translations - Rose now knows French!

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!

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 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🙃