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

@freemo @Demosthenes To be fair I’m probably slight more prickly than usual given the challenges of running an instance in a post-Trump cancellation world, in full lockdown (again) in Scotland with a four year old and wife who broke her (dominant hand) wrist yesterday! Everything is a challenge!

@freemo @Demosthenes No hostility here, but @freemo I think in total we oversee the same amount of users overall and really the last thing any of us need is aggro 😜

@freemo @Demosthenes I’ve slightly edited my post which will hopefully please the lawyers out there.

@freemo @Demosthenes Well that’s a relief, isn’t it.

@freemo @Demosthenes And honestly it’s a real kick in the butt when people try to tell you how to run an instance that you pay for and put your time into and ultimately have the final say on, which I’m sure is something you @freemo are very familiar with 😜

@freemo @Demosthenes I’ve issued a statement to my instance stating that free speech is the right to express yourself freely (safe from impediment by your government or other influences) but that if that expression is in breach of our rules then it would be moderated, As you say, it does not give you the freedom to say anything you like (and, as I said, without consequence). I’m hopeful that is in line with qoto.org’s policy.

@Demosthenes @freemo Let’s hope so, eh?

@Demosthenes Do you speak for qoto.org or are you only a user there?

@Demosthenes Did you just say that out loud? I feel qoto.org might be about to drop off our relay...

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!

@jk @kensanata ThibG's response further down this thread might be useful (the OP's replies less so): https://github.com/tootsuite/mastodon/issues/15016#issuecomment-713614579

@jk @kensanata Ah sorry I didn't see the thread! I wonder if it's related to this in v3.2.1:

https://github.com/tootsuite/mastodon/pull/14556

I know that it breaks relaying, unless you use a fork of the Pleroma Relay code (which I've started using on both the mas.to and mastodon.scot relays)

@jk @kensanata Is this by any chance regarding use of relays?

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