trumpet@mastodon.scot @trumpet@mastodon.scot

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.

HELLO EVERYONE. We've just upgraded to Mastodon v3.1.3!

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

NOW WASH YOUR HANDS.

As it's the start of the month we'd usually do a fundraiser to help cover the costs of running this instance.

This month, due to the global situation with Covid-19, we'll skip the fundraiser and simply ask our users to stay safe and stay well 🙂

Take care folks!

Hello everyone! We run mastodon.scot as a free service because we love Mastodon and the fediverse, but it costs us money! Once a month we reach out with an appeal to our users for donations to help with our running costs. Even small donations are a great help, and all donations are very much appreciated!

PayPal: https://www.paypal.me/mysteryvortex
Bitcoin: 1mG9mvpTnx2gv281mELaQu3tjC2dUM8RR
Ethereum: 0x4cFf1Af8A322507E2ef8ac1b8Cb9a539aD8671fB

The migration process shouldn't have caused any problems but do let me know if anything is misbehaving. We did move to a new IP address but our DNS was changed before the move and so should have already taken effect for most people.

Hi everyone! Our migration went reasonably smoothly but not perfectly.

Our first attempt to backup and restore the (compressed) 24GB* of core Mastodon files and databases failed. We tried again with uncompressed data and the migration worked perfectly.

The whole process took just over an hour.

The instance should now be more responsive, and we have plenty of room for future growth.

* Our media is stored in external object storage totalling around 600GB, but didn't have to be moved.

Okay, we'll be going offline in 5 minutes. Back soon...

To answer the question that precisely zero people have asked so far, we don't _need_ to upgrade at the moment and have plenty of capacity to spare, but we have the opportunity to do it now.

It seems a better idea to upgrade when we want to rather than when we need to!