Boy, I have not gotten this many reports on people on my server in some time. (carry on folks on my server, no violations here... but everyone is reporting everyone they disagree with on Gaza and Israel left and right...). #MastoAdmin
I was looking for a project that would let me manage my Mastodon follows & followers better. Haven't found anything but did come across Mastodon+Steampipe. If you know of something, @ me
Can say that my #Cloudflare#R2 block storage for #Mastodon is massively growing. A year ago it was stable at ~80-89Gb, but lately it's heading to 200Gb+ #Mastoadmin
For the first time the #CoSocialCa Mastodon server has started to struggle just a little bit to keep up with the flow of the Fediverse.
We’ve usually been “push” heavy but we’ve started to see some spikes in “pull” queue latency. The worst of these spikes was today, where we fell behind by at least a couple minutes for most of the afternoon.
What should an Admin, or if you're an Admin, what do you do, about someone's post that contains unnecessary extreme profanities attacking a well-known person?
While my original proposal to hide images in order to highlight the importance of well-written alt text did not gain a whole lot of traction, I'm still glad there was some conversation, and grateful to everyone who is still interested in joining in.
If you do participate, I would love to hear from you!
I've received my first "report" on hugs.lgbt and I'm very confused ....
Two posts were reported ... neither were from hugs.lgbt posts ... one was a reply to one of my posts by a mutual, the other was a post by that mutual without any hugs.lgbt involvement ...
Did I receive the report because one of those was a reply to a post of mine?
But why the other one?
Also very confused as to why ... the first was a thank you reply to a post from me.
The other was a meme.
The category was "other" but no notes or any other information that I could discern 🤔 🤷♂️
Aside from relays and adding elastic search to a mastodon instance does anyone have any other things they do to enhance the user experience? #mastoadmin
Backblaze was down for me for around the last 10 minutes as of this post
Edit: It's still down. Status.backblaze.com has no issues
Sidekiq errorL Aws::S3::Errors::ServiceUnavailable: Service temporarily unavailable, please try again
Images were blank but seem back now
#Backblaze#MastoAdmin
I'm having issues they can't resolve lately. B2B doesn't play nice with Mastodon. Any good, reasonably priced alternatives? Refer-a-friend links won't insult me
Between setting up DigitalOcean Spaces [1] for uploaded media and enabling @michael's FediFetcher [2], my experience on a one-person self-hosted Mastodon instance has been greatly improved.
Ok I should really know this but can’t find the setting for the life of me. How do I get a little icon on the bottom right hand corner of my profile picture? #mastoadmin#mastodon just like below
I do not understand how I have almost 8 gb of status data in my database for gardenstate.social. in the last 7 days it grew 8k? at 8k a week my server would have to run for 973 weeks to get to 8 gb.
I often run the cli script that removes unreferenced statuses. I feel like this should be much smaller!
PSA: If you're getting Error 500 messages from mastodon when trying to upload images from mobile: You're probably trying to upload a HEIC/HEIF image and the fastimage gem errors out.
Easy fix: search for fastimage in Gemfile.lock, change version to 2.3.0 and run bundle install. Then restart mastodon services.
We just published our first Trunk & Tidbits post! This will hopefuly be a monthly update where we showcase what we worked on last month, and what's coming next.
I hope this will bring more visibility to all the efforts and love that put on Mastodon
645 days after setting up my own Mastodon instance, I finally tackled tuning my Postgres database config last wk & today setup multiple Sidekiq Processes after my queue got to 10K for the second time this wk
I read the guides multiple times over those 645 days but it never clicked in my head. I was afraid to mess with Sidekiq because I didn't want to brick my instance.
Then today, during the thunderstorm, the old grey cells clicked in and I understood.
We merged a migration yesterday and it is far too expensive to run on large servers, so we are rolling it back. If you already applied it, please check the link above to revert it before upgrading.
It is probably best to skip today's nightly build, if you did not deploy it yet.