Show newer

I have increased the number of sidekiq workers to deal with the remaining queue from yesterday. Now the sidekiq main process consumes one CPU core. Expct another hour or two of delayed toots.

We just muted, thus you might only interact with accounts from this domain if you follow them. We'll lift the ban on Friday at 14:00 UTC to check if their admins have gotten rid of the problem.

It's the grant tables again. We will reboot the host system (Xen Dom0) that runs and several other guest systems (Xen DomU) around midnight UTC to make better suited grant table settings effective Expect somewhere between 10 and 30 minutes downtime..

When do you prefer automatic cleaning jobs and the snapshots being done? Cleaning makes the server slower, snapshots maen about 2min downtime. Basically this question means: Where are most of you located?

All times UTC:

Sorry, the server is a bit slow because I manually started some cleaning jobs. This situation will continue for the next 30 minutes or so.

Another sorry for still not having updated to 4.0.2: Two sick kids, so I am drowning in work.

Sorry, people, the server is a bit slow at the moment, the btrfs_cleaner has lots of work to do.

I have a request.

Bad actors will soon figure out - if they haven't already - that setting up impersonations of important organizations now will allow them to set off an explosion of chaos and confusion at a time of their choosing.

So if you run an account for an organization (especially #LGBTQ), please set up link verification between your Mastodon account profile and your organization's website.

If not, please boost.

Instructions are here under "Link Verification":

To all mastodon admins:

Hi! I’m Evan Phoenix, the primary author of puma, the ruby webserver that powers mastodon!

Please reply or DM me if you need tuning help! I’ve got no officiation with the mastodon, just want to see you succeed!

(Quick Tip: set WEB_CONCURRENCY to core count * 1.5 and then tune MAX_THREADS. High thread values will see diminishing returns!)

Starting this instance on a server with "some space and an IPv4 address available" was a naive thing. I'll figure out how to move to the bigger machine next week. So far everything worked with zero downtime, but moving to a bigger server might mean ~15 minutes unavailable when I either have to move a subnet or change IP address – or both.

Better.Boston service announcement/postmortem 

Our server has seen record numbers today. At 1:30pm EST, our server became backlogged and couldn't keep up with the number of posts that needed to be pulled from other servers.

This was noticed at 1:53pm, and we quickly used an idling server that was on standby to catch up on the backlog of posts (as soon as I got back from lunch)

The system fully caught up by 2:09pm EST, and seems to be back to full health.

#BetterBoston #BetterBostonAdmin

Worked without downtime: xl block-attach on the Xen side and btrfs add on the toot side did the job. But expect to be a bit laggier the next few hours since filesystem balancing is on the way.

Show thread

Five minutes downtime incoming around 18:00. I am going to add another virtual disk.

BTW: The 4.0.2 update will be either done monday or friday next week. So, be prepared for another 15 minutes of downtime.

Friday evening will mean 5 minutes downtime for adding space to the root filesystem. It will also mean 30 minutes of lag (as today) when the filesystem is balancing. BTRFS fun as always (no BTRFS vs ZFS flamewar, please).

The say rules currently say "no transphobic", but it's not fear (Phobia, Angst), it's just hate. So please provide me with a better word.

Reading through the pages I have not seen anything that can be punished under german law. But still so much hate. I am so happy with the decentralized Fediverse: Large platforms can be forced to contract (nice Kontrahierungszwang), here we first can say: 1. Go, build your own Fediverse instance, protocols are open! 2. Blocking your instance does not stiffle free speech, every potential recipient can look at your local timeline!

Show thread

For transparency: I just soft blocked a TERF ("trans excluding radical feminists") shithole instance. You still can add these TERFs to lists and stuff or follow them (why should you) but boosts won't propagate and some discussions might have holes.

updated to indicate only glitch-soc is affected. There are other security updates in mastodon 4.0.x so not wasted effort to update if not running glitch-soc

This message for everyone on the fediverse:

First, please ensure you go into your account settings and enable two/multi factor authentication. No, I mean do it right now. I’ll wait till you’re done.

Ok, thank you.

Now, if you are the admin of a mastodon instance running glitch-soc, please go upgrade to 4.0.2 ASAP.


Should we show the local timeline or the federated timeline for non-members clicking ?

Show older

A Mastodon instance aimed at (but not limited to) the cycling community.