rolle, to mastodon
@rolle@mementomori.social avatar

: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:

mastoadmin, to mastodon French
@mastoadmin@mastodon.tn avatar

Lancement de notre campagne de collecte de dons pour notre instance mastodon

https://blog.nizarus.tn/promesse-de-don-mastodon-tn

Ville, to random
@Ville@elytra15.com avatar

Would Mastodon generally run better on 4 shared vCPUs or 2 dedicated vCPUs?

michael, to mastodon
@michael@thms.uk avatar

Somehow I still find it funny that because my mastodon instance is hosted in Germany all the YouTube previews are in German

Revertron, to random
@Revertron@zhub.link avatar

How can I determine which instances have blocked my instance?

ai6yr, to random

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...).

jeff,
@jeff@newsie.social avatar

@ai6yr

There is a special hell that is being a or larger public instances.

It's amplified 100X for Newsie and Journa.host due to the sheer number of and

Now layer on the people that just can't help being mean to one another.

ugh.

ian, to random
@ian@phpc.social avatar

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!

paul, to random
@paul@oldfriends.live avatar

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

Anyone using Mastodon + Steampipe? Steampipe is an open-source zero-ETL engine to instantly query cloud APIs using SQL
https://hub.steampipe.io/plugins/turbot/mastodon

It has many different "recipes" to see the data on your instance/Mastodon account. https://hub.steampipe.io/plugins/turbot/mastodon/tables

Users &Admins can create access token and use it

Remittancegirl, to random
@Remittancegirl@mstdn.social avatar

Hey people. Just a reminder that our admins are working hard for us all. Won't you please chip in and help them with their costs?

mick, to random
@mick@cosocial.ca avatar

For the first time the 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.

1/?

A pair of graphs showing sidekiq queue latency and enqueued jobs. The queue latency peaked at around 6 minutes at roughly 6pm this afternoon, but was between 1-2 minutes most of the afternoon. The maximum number of messages in queue at any one time was 12000. The majority of the traffic is pull queue.

mick,
@mick@cosocial.ca avatar

This strikes me as an issue.

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.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • anitta
  • cubers
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • Durango
  • Leos
  • Youngstown
  • thenastyranch
  • slotface
  • rosin
  • kavyap
  • mdbf
  • osvaldo12
  • JUstTest
  • ethstaker
  • khanakhh
  • tacticalgear
  • provamag3
  • ngwrru68w68
  • everett
  • GTA5RPClips
  • modclub
  • normalnudes
  • megavids
  • cisconetworking
  • tester
  • lostlight
  • All magazines