@Fitik@fedia.io messages to/from threads has been causing some major problems with the message processing queues on fedia.io. To keep the instance running, I had to block it until I can sort out why.
Recovering CISO
May have an orchid problem
Bad photography
Worse dad jokes
The worst Infosec hot takes
Podcast: https://defensivesecurity.org/
Blog: https://infosec.engineering/
Twitter: @maliciouslink
https://infosec.exchange/ Admin
#infosec #security #cybersecurity #risk #fedi22
…and for fucks sake, be nice to each other. We are only here for a brief time. Make it enjoyable.
To help support the costs associated with running this instance, please consider donating. You can set up recurring donations here:
Patreon: https://www.patreon.com/infosecexchange
Ko-Fi: https://ko-fi.com/infosecexchange
Liberapay: https://liberapay.com/Infosec.exchange/
You can also support with a one-time donation using PayPal to “jerry@infosec.exchange”.
@Fitik@fedia.io messages to/from threads has been causing some major problems with the message processing queues on fedia.io. To keep the instance running, I had to block it until I can sort out why.
@IlliteratiDomine @DarkThoughts I found the problem - it was an error I introduced when moving fedia,io to containers recently. it works now.
@IlliteratiDomine @DarkThoughts Thanks for tagging me. I wasn’t aware there was a problem. I’ll take a look.
@Cavalarrr @ernest I did what all the cool kids are doing and disabled federation on fedia.io. The problem isn’t really the local users as much as all the content being federated in.
@shellsharks @infosecpub @lemmyworld I will look into it, but there are quite literally no options to either enable or block this in lemmy.
@shellsharks @infosecpub sadly, there are no such options in lemmy or mastodon
@Fitik@fedia.io I removed the block. I’ve been having some luck in reducing the server load today with the help of the mbin team.