Trying to run a little experiment and want to make sure my understanding is correct.
If I post something on my fediverse server, assuming it takes some time to reach all of my followers' servers, does that post get inserted into their feeds as if posted at the original time, or rather on top of their feed, but with the original timestamp?
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.
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.
"If you help run a public-spirited Facebook group, forum, listserv, or other kind of digital space that aims to strengthen connections between people in your local neighborhood, town, or city, @wearenew_public]'d love to speak with you."
About 1.5 years of running a small mastodon server.
Running costs currently are about 1€ per active user a month.
Would probably scale to a lot more users with not much cost increase. CPU-wise the server barely has any load.
A very big chunk of the cost is just the caching of media files. about 120GB for 3 days worth of caching
Where are fellow #Mastoadmins planning what tools we need to combat the spam wave? Where are we planning features improvement to Mastodon (the software) or 3rd party tools to counteract this spam wave?
The Feb 2024 mastodon spam attack should be a learning lesson, and we should make our tools robust so this doesn't/cannot happen again.
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.
My understanding of the current #spam issues is that it is people taking advantage of open registration instances. Essentially hijacking.. which is causing small-instance admins like me to domain-block those instances for sanity.
Question: Assuming the spammers will eventually be removed from the victim instances, is there a 'whitelist’ somewhere that #MastoAdmins#SelfHost community could consult so we can unblock domains that should no longer be a problem?
someone on a Japanese hacker forum decided it was a good idea to spam the entire Fediverse because they wanted to cancel a minor that DDoSed a Discord bot which apparently made them lost millions (what?)
A Discord bot. I can't make this shit up man.
The real culprit seems to be someone who goes by mumei in the ctkpaarr.org forums, whose first post was literally a threat to ap12, that if they don't delete their "Kuroneko Server" Discord bot, they will spam every blog, forum and SNS and cancel him.
This shit is ridiculous.
The ap12 account from mastodon-japan was actually fake, and this dude impersonated a minor to get all of the Fediverse (us) to bully him.
Today's attack proved that the Fediverse is unfortunate pretty vulnerable even to just a skid (or maybe OP who warned the skid).
The cause of the attack includes:
insufficient moderation on some servers allowing mass account creation.
no good methods to filter out even just a keyword for an entire instance.
Even though most of us survived the first wave, we have to prepare for the second and future ones:
Servers should enable the equivalent feature in their software that enables moderators to check if an account is ok first before letting them post anything.
Mastodon, Misskey and major software should implement a regex filter that ignores posts from any instances.