mstdn.io admin @[email protected]

@t131t1 no worries!

@t131t1 yes?

@andreyka ok, I disabled the firewall rule, it should be better

@andreyka can you try again?

@kura The user that made the report had the choice to include specific posts, but didn't. Can't do anything about that.

Also, mstdn.io has a no-instance-wide-block-of-other-instances policy so I wasn't planning to blocking fedi.z0ne.moe :)

@kura reports coming "from mstdn.io" are reports made by users here, they are not made by the admin. If you see a report where the entire account has been reported, I see the same thing :)

We are now running Mastodon 3.4.

Changelog: https://github.com/tootsuite/mastodon/releases/tag/v3.4.0

This morning downtime was due to the server's disk being full. Sadly, I was hit by a pretty bad bug in journalbeat: https://github.com/elastic/beats/issues/23627

Last night's latency spikes were unrelated and probably due to https://status.scaleway.com/incidents/zty0ybqzxw57 (we use a HA databse)

The instance was down this morning for a few hours. I misconfigured the monitoring alert and didn't receive a notification

Thanks for your support in the last 4 years

should be good!

Looks like thare are some issues with images due to our provider

@dpreacher

@Matthieu Weird! I opened an issue: https://github.com/tootsuite/mastodon/issues/15946

@cevenolle3 bienvenue !

hello

@anon97945 I haven't touched the rules in years