Updated my from Mastodon v3.5.1 to Mastodon v3.5.3

Also updated my patch to increase the character limit: gist.github.com/tassaron/22291

The patch just needed a small update to change line numbers (due to the addition of the language selector)

As a user who DMs myself all the time, I start all my DMs with "Dear Digital Ocean,..."

Show thread

a moderation system for single user instances 

I understand why people don't like a (they are by nature not responsive to moderation) but I wish there were some way to get a hint that someone self-hosting isn't doing so for malicious reasons. Like, if there were an index of known (and submitted) single user instances, and if an instance has rules defined and no reports (and was submitted to the list manually), then it is green. If it has no rules or few unverifiable reports (or is unknown) then it's yellow. Otherwise it's red.

This would take a time commitment from multiple people and probably not solve the problem very much if at all. If anyone thinks it's a good idea, then maybe we can work together to try it out. Otherwise I'm not gonna push this boulder up the mountain.

And uh, I guess if you wanted to indiscriminately ban all single user instances, then having a list would help too. I'd rather you didn't, but it's fine 🤷‍♀️

Updated my from 3.0.0 to 3.4.5 ... It was actually super easy. I just created a new VM, installed Mastodon 3.4.5 fresh, imported the database and did the migrations, and changed my DNS to point to the new IP

Eventually I want to extract all my posts from Mastodon and host them in a new, leaner ActivityPub blog. Something more designed for a

Turns out I was getting 500 errors because my instance didn't have permission to upload to the S3 bucket, due to it being a cross-origin request. This was accumulating in the background along with some pre-existing issues caused by relays. Both have now been fixed so my is finally using an appropriate amount of RAM again! 🔧 🐜

Show thread

My instance is back online and shouldn't go offline again for a long time now that I've moved all the resources to object storage :kirby_happy:

Show thread

I'm gonna try to move my instance's media to object storage today... this is the only newish writeup I've found about it: github.com/cybrespace/cybrespa It looks thorough and simple but Mastodon is never as easy as it seems 🙄😬😛🤷‍♀️ I'll stop the Mastodon services in 15 minutes so wish me luck while you can 🤞 ...Bye! :tassmuffin:

I haven't been using Mastodon much lately because I'm trying to avoid fixing my technical debt 😒 I have to transfer to object storage because it's cheaper (and update by quite a few versions too) 😛

*looks at federated* guess I have some more gabs to block after work this evening 😑 where's the much-needed regex domain block for mastodon?

Sidekiq is suddenly using way less memory?? that's cool I guess ?_? I hope it stays this way because I dislike using 1.5gb all the time... now it's back to 1.

I'd heard about Mastodon and GNU Social quite a bit by the time I actually bothered checking out the fediverse in August 2018... I regret not looking into it sooner. I wrote it off as a "ghost town" but it turns out this ghost town is perfect for me because it's full of like-minded ghosts who care about free software and the evolution of social media 😁👍 I love this place!

My is on a $10/month Digital Ocean VPS which has 2gb of RAM and 50gb of storage... It's one year old now and is using about 38gb. I try to have a lively federated timeline but I also do extreme pruning of remote media so I can probably get most of another year out of the remaining 12gb... My instance typically uses 1.2gb of RAM

Show thread

I had followers from dead instances which my Sidekiq was continuously retrying to push my statuses to, and there's also a "development and testing" instance which is in the mastodon.host relay which I've suspended for giving weird errors repeatedly. My RAM usage is down significantly so I'm satisfied now. Some errors are probably inevitable with this many relays 🤷‍♀️

Show thread

My has been using a bit more RAM than usual lately. The thing using most memory according to top is , which flickers between having 1 busy job and 0. I see there are a bunch of jobs that were retried 20-30 times each (some caused by a relay I think?)... Should I delete these? Is this even a problem? The Sidekiq dashboard is not very informative to someone who barely knows what it's doing 😅

cron uses tootctl but I have the 'unofficial' Masto-cleaning commands in a shell script called 'do_sometimes' which I do sometimes, because I'm afraid to automate_this 🙃

I started sending the output of my daily Mastodon-cleaning cronjob to a log file. So far it looks like tootctl deletes about 1337 remote media per night :mario:

Show older
tassaron dot com

This is Brianna's federated microblog homepage! To follow my posts, find another Mastodon instance and join the fediverse.