:skull360: We have now successfully upgraded to v4.3.0-alpha.3+mementomods-2024-05-26. The server has Mastodon Bird UI 2.0.0rc37 installed with no further changes at this time in the UI.
The branch is now synced and up-to-date and 158 commits ahead from the last version 2024-05-01.
I love running the newest version so I can test ahead in production for the upcoming Mastodon Bird UI versions. I do have my local instance with the production db, but it is far more fun this way and it feels good to have new things.
This "testing in live" is also because it's the perfect way to make sure that I can help contributing to Mastodon and spot bugs before they end up in the final rc, beta or stable versions. There most probably will be some minor bugs, but the earlier we tackle them the better.
As usual, please tell me about any strange things you may encounter with this Mastodon version. We're running bleeding edge after all.
I hope you enjoy your time here. Feel free to send me a message if you have anything in mind. :bunhdheart:
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
Thanks to some sleuthing/fixing by @derickr (we were on a bugged ImageMagick version), if your phone was 500'ing on image uploads, that problem should be gone now on phpc.social. Please report 'em if you still see them! #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
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.
We have the capacity to run 40 workers (following the change I made last week, documented earlier in this thread.)
We have fairly huge backlog of pull queue jobs.
Why aren’t we running every available worker to clear this backlog? 🤔
It might be necessary to designate some threads specifically for the pull queue in order to keep up with whatever is going on here, but I am open to suggestions.