Hm. I wonder if I can get any fediverse admins onboard to disable all images on their instance on the World Sight Day in October, so that only alt text shows up.
I've updated my #mastoadmin SQL and cron scripts a bit today to better keep my server clean.
It's getting pretty good after roughly a year of iterating on them, today in particular was a massive refactor and improvement to both query performance and capabilities.
Cleaned +70 spam accounts I had missed, thanks to the new tweaks.
Hallo alle Fedi-Admins die Probleme mit Spam haben!
Die Mute-Liste 2.2.2
Ich habe die Spam-Liste aktualisiert und ~104 zusätzliche Instanzen gefunden, die weiterhin spammen! Ich habe, mit viel Hilfe von anderen Fedi Admins, die Instanzen in einer Liste zusammengestellt, die sie stumm schaltet und nicht von ihnen deföderiert!
Ich würde mich sehr über eine kleine Spende hier freuen, da Ich wirklich hart und lange an der Erstellung dieser Liste gearbeitet habe, was Ich angesichts meines aktuellen Zeitplans kaum rechtfertigen kann! Dankeschön!
Es gibt eine neue Art von Spam, die gleichen Instanzen sind betroffen wie vorher. Die Verantwortlichen in Japan sollen verhaftet worden sein.
Ist diese Liste importiert ist ein Großteil des Spams vorbei. Das ganze ist für euch leicht, geht mit einem klick! Zudem wird keinerlei Instanz für immer geblockt, keinerlei Follower etc. zerstört oder deföderiert, sondern nur stummgeschaltet. Das ist sehr leicht umkehrbar.
Ihr könnet diese Liste einfach importieren, indem ihr auf https://yourinstance.tld/admin/export_domain_blocks/new geht und yourinstance.tld durch die Domain derer Instanz ersetzt, von der ihr der Administrator seid!
Alternativ könnt ihr auch auf Einstellungen => Moderation => Föderation => Importieren drücken, um diese Liste zu importieren.
Beachtet, dass zwar alle Instanzen mit einem Klick importiert werden können, dass aber diese Instanzen einzeln entfernt werden müssen, wenn der Spam vorbei ist.
Beachtet auch, dass es nur Sinn ergibt, diese Liste zu importieren und die Spam-Instanzen stumm zu schalten, wenn ihr euren Spam lokal und nachhaltig blockiert habt, wie hier beschrieben.
FediFetcher is a simple Python script that can help you pull missing responses from other #Fediverse instances into your own #Mastodon instance. It can also backfill profiles of new followers and followings.
It can be run as cron job, container, or even a GitHub action, meaning you don't need any infrastructure at all.
Ok, question for #mastoadmins or anyone else out there with knowledge on the subject:
Adding pgbouncer on top of the postgres database seems to have at least reduced the problem with the sidekiq queues backing up. However, the push queue is still getting backed up to a few thousand jobs occasionally. This doesn't seem like it should be that big of a problem because I've added more sidekiq processes for that queue and they should be able to get through a few thousand jobs with minimal latency. The real problem, however, is that if the push queue starts showing as little as 1 minute of latency, all remote media previews break (they just show the fuzzy gradient with the "Not Available" caption), and all media uploads break. The only way to fix it, even after the latency drops back to zero is to do a hard reboot of the server.
It feels like I'm running up against some kind of timeout setting that's set too low. I could see a latency of 10 or even 5 minutes being a problem, but expecting that latency will never hit 1 minute seems unreasonable. Any ideas on what I might be doing wrong here? It seems to be tied to the database because if I reboot the web server without also rebooting the db server, the images stay broken.
So I was going to make a small update to my tool for analyzing fediverse export files to celebrate having made my 5,000th post last night, and also to better understand how I got to that number, and I am having trouble understanding how Mastodon counts your posts.
If I count private mentions, my total is higher, but if I exclude them, I get a number below 5,000.
What's the best way to tidy up the public/system/cache folder in a #Mastodon instance?
My public/system/media_attachments is on 3.3GB.
However, public/system/cache/media_attachments is 22GB!
Similarly, public/system/accounts is 97MB, whereas cache/accounts is 22GB
How should I clear down this massive cache?
I've tried tootctl cache clear but nothing seems to change in the cache folder.
In total the cache folder is 55GB, everything outwith cache consumes only 6GB. It's making my backups massive and long to run.
Hey #MastoAdmins or #Mastodon devs! I'm building a PHP listener to receive Web Push notifications from Mastodon.
I'm receiving the notification in the listener, but it is encrypted. I've been hurting my head to find a way to decrypt it, and the docs do not mention anything about how to decrypt a notification. Any help and boosts are appreciated.
Something I don't understand is how one of the biggest fund raising #mastoadmins out there is straight running out of cash.
Maybe dude needs to learn to optimize hardware usage better, or something, but 2300/month is ridiculously expensive unless you're driving some SERIOUS traffic.
we must be due a Mastodon code update soon? It's been almost two months since the last one. It looks like there have been several good fixes and update to code, as yet unpublished.