trumpet@mastodon.scot @trumpet@mastodon.scot

@FediFollows @trumpet So in theory mastodon.scot, which is on the same subnet, should also have the same issue.

@privacyint@media.privacyinternational.org

Hi everyone, the issues with our object storage provider appear to be resolved and everything is back to normal (although the fix we implemented earlier seemed to work anyway).

Hello everyone! We have good news and bad news...

GOOD NEWS:

We've upgraded to Mastodon v3.3.0. More details here:

https://github.com/tootsuite/mastodon/releases

BAD NEWS:

Our object storage provider is having issues today which has broken media on this instance. Hopefully normal service will resume shortly.

https://status.wasabi.com

#mastoadmin

HELLO EVERYONE! It's the 1st of December and to celebrate we've upgraded to Mastodon v3.3.0rc1 🙂

More details here: https://github.com/tootsuite/mastodon/releases/tag/v3.3.0rc1

Those of you that caught the announcement earlier will know we were expecting a little downtime today. A faulty disk has been replaced with minimal downtime, everything is back to normal :-) Thanks for your patience folks!

Hello everyone! I hope you're having a nice day. I'm having a nice day. And the fediverse is having a nice day!

And guess what? Mastodon v3.2.1 has been released! And we've upgraded to it already!

More details here:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.1

We've not asked for donations since the first lockdowns earlier this year, as we know a lot of people will be in difficult circumstances, however we've still received several donations since then.

Thanks to everyone who's donated, it means a lot to us!

This instance is and always will be a free service, but anything that helps cover our costs is hugely appreciated. Stay well and stay safe folks! ❤️

Hello everyone! We've upgraded the instance to Mastodon v3.2.0. More details here:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.0

There's an issue with playback of audio files that was introduced in v3.2.0rc1 which does have a workaround, but which we've not successfully implemented. We'll get this fixed as soon as we can.

#mastoadmin

Hello my little friends! Today we have upgraded to Mastodon v3.2.0rc2, and that's got to be a good thing, right?

More info here:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.0rc2

Toot toot!

TOOT TOOT!

Hello there! We've upgraded to Mastodon version 3.2.0rc1. More details here:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.0rc1

Hi everyone! We've updated to Mastodon v3.1.5:

https://github.com/tootsuite/mastodon/releases/tag/v3.1.5

As always thanks to Eugen and the rest of the Mastodon development team for all their hard work 🙂

Hi everyone! We've upgraded to Mastodon v3.1.4. More details here:

https://github.com/tootsuite/mastodon/releases/tag/v3.1.4

In other news, spambots are increasing turning their attention to Mastodon instances. This instance is actively moderated and we do try and stem the flow of spam accounts, but we need your help!

If you see a spam toot, do please report it so that we can keep our instance tidy 🙂

Hi everyone! I hope that everyone's coping in these difficult times.

Usually at the start of the month we'd run a fundraiser to cover the running costs of this instance, but we're going to skip this again this month due to the hardships many of our users might be facing.

Stay safe and stay well! ❤️

We've removed the block of recent spam registrations and have blocked the offending IP addresses to try and prevent future issues. Registration is now open again.

#mastoadmin

Hi everyone, due to a recent surge in spam registrations we've temporarily moved to approval-based registrations. We'll move back to the normal registration model once we've dealt with these.

#mastoadmin

So, after carrying out some forensic investigation on what went wrong, it appears that our upgrade to a newer version of Redis didn't work. It looked like it had, but hadn't.

We've corrected the issue with Redis and everything appears to be _properly_ working now, but we'll monitor the situation.

Unfortunately because of the nature of the issue the @trumpet account didn't receive any of your messages saying there was a problem!

Apologies for any inconvenience caused folks 🙂

The issue affecting our timelines has been resolved. Thanks for your patience!

We've been made aware of an issue where the federated timeline is showing our local timeline, and are investigating.