And now Whitespashe is running on Mastodon 3.2.0!

We're now as up-to-date and efficient as we can reasonably be! Time for a well-earned coffee! :blobcatcoffee:

After watching the slow loading of assets via backblaze, I've now implemented an nginx cache and haproxy wizardry to try and speed stuff up somewhat!

@angristan contributed to my success via his blog post:

After following that, I then stole a load of code from the mastodon docs and

Now I've got a fairly resilient media hosting stack!

My hard drives will surely thank me! Backups too!

I've updated Whitespashe to use backblaze for its media storage! Hopefully I'll have a much less sad hard drive now!

Ugh. Had so many issues with networking yesterday. I lost internet for a fair part of the day, my VM hosts would not stay clustered or in sync, either! :REEEEsuka:

I had to completely redesign the network connectivity at home and finally for sorted at about 1am today!

Things seem stable now, but yesterday was sent to try me. πŸ˜“

Whitespashe is going offline whilst I bring us up to the most recent version. It's gonna get wild. is now running on Mastodon Master branch, as the v3.1.2 release can't be built due to a dependency being yanked.

We're bleeding edge guys!

Playing around with ansible when I should be sleeping....

My next big project: every service I host must be deployable in ansible.

New storage server is racked, the rack is pretty much built, awaiting tomorrow to migrate my existing server stuff across!

The rack has claimed blood from both myself and my wife, so it has been correctly sanctified.

Show thread

Whitespashe is getting an upgrade! One server rack being installed in my house....

Ugh, dealing with my old dovecot mail server....

I can get the maildirs and userdirs separated nicely, I can get the mysql lookups to work perfectly...

Can I fix a permissions error when I enable autoexpunge on the junk folder? Hell no I can't!


Ugh. I've had to disable full-text searching, as my VM is unable to handle the high memory requirements. Looks like a hardware upgrade is in order soon. πŸ˜₯

Show thread

Some memory issues on

Rebuilding my elasticsearch db, as it hasn't been running for a couple of months.

Whitespashe is going down for a little while whilst I add SSD caching to my ESX host. Fingers crossed!!

Oof. Generating a vanity domain is pretty CPU intensive.

Once that's done, I'll be able to link it to my mastodon node!

Until then: slowness :loading:

For anyone that's running a instance on :

Do you need an entirely separate mastodon instance for both Tor and Clearnet, or can you effectively have both addresses point to the same server?

Boosts welcome.

Just tried to upgrade the RAM on my server with a shiny new 8GB stick....

Looks like it's DOA. Now I have to send it back to amazon and wait for a new one. My poor ESX server. Looks like another 4 days wait (at least). :REEEEsuka:

So, when attempting to use git to manage my Mastodon instance...... :battery_full:

I managed to pull the branch that had none of my custom changes, and a completely different docker-compose file. :battery_ok:

I then proceeded to bring up my mastodon, screwing with all of my containers. :battery_low:

For whatever reason, it refused to revert container names and volumes, however much I tried. :battery_empty:

After eventually switching to the correct branch, and judicious use of 'docker-compose down', everything came back up!

But no luck, as my reverse proxy couldn't see the server. :loading:

One nginx restart, and logs started flowing! :battery_full:

We're all back online now, but I blame @mike for giving me well written instructions that I dutifully ignored. now fully supports 1337-character posts!

Next on the list of admin work, is to get a Gitea instance online, and start mirroring the main mastodon repo. Then, I can have custom patches for this functionality applied on each upgrade.

Extended character limit works! Now I just need to find where to add the correct customisations for Tusky to see it.

Show more
Whitespashe Mastodon

This is a mastodon instance that allows users to share ideas and participate in discussions.

Whitespashe is named after the Admins' first joint coding project, which replaced spaces within a Word document with non-printable characters.
This would preserve readability, but would fool plagiarism detection sites such as Turnitin.
This site was named after this project, as it represents a desire to create whilst simultaneously sticking it to the Man (or in this case, the hellscape that is Twitter).

We have a hidden service frontend running at: http://whtspshcehqg4nj4wqyiopjcfxradop7ujflycxum7wkfivewqt36zyd.onion

Our code of conduct and extended information can be found after the 'Learn More' link below!