Hi everyone! We've updated to Mastodon v3.1.5:
As always thanks to Eugen and the rest of the Mastodon development team for all their hard work 🙂
@DinDudeNuffin Usually advertising something!
Hi everyone! We've upgraded to Mastodon v3.1.4. More details here:
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.
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.
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 🙂
HELLO EVERYONE. We've just upgraded to Mastodon v3.1.3!
NOW WASH YOUR HANDS.
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!
@Jkp I could have sat and fiddled with it but since I didn’t want to delay getting the instances back online I went for the simple (but slightly slower) option and used uncompressed backups.
@Jkp Not sure! I’ve done lots of similar compressed backups and restores, even between different machines, so just one of those things!
@Jkp We run the instance in a virtual machine on a Proxmox host, so just use Proxmox’s internal backup/restore tools,
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.