@[email protected] @[email protected] why would you think that’s AI generated?
Wary Jerry
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 “[email protected]”.
- 0 Posts
- 15 Comments
Joined 8 years ago
Cake day: April 6th, 2017
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
@[email protected] the second and third order impacts of this could get interesting
@melroy @jwr1 @arotrios @vaguerant I cannot express how awesome the mbin team has been. I have no idea how kbin.social was able to operate with that many users while running kbin. I can definitely see mbin working for that large of a user base, though.
@[email protected] @[email protected] @[email protected] I had to remove /m/test too, and now the delivery queues are holding at zero, as they should be.
@[email protected] @[email protected] @[email protected] hopefully you’ve seen my other messages on Fedia. I think I’ve fixed the problem by deleting /m/fediverse and purging the backlog of deliveries. The threads mentioned above were delivered but due to the issues with /m/fediverse (and possibly /m/random) the server was running way behind because it was spending all its time retrying deliveries that would never be accepted by other instances. Sadly I think I’m going to have to leave /m/fediverse deleted till the underlying mbin bug gets fixed.
@[email protected] @[email protected] @[email protected] it got here. I will go check.
@[email protected] I removed the block. I’ve been having some luck in reducing the server load today with the help of the mbin team.
@[email protected] 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.
Being mentioned in the same breath as the others in the post above is wholly inappropriate. Those are the MVPs. I just pretend to know what I’m doing.
4·1 year ago@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.
@konsi where does that view come from?
Hello everyone. If you care about fedia.io, please read this: https://fedia.io/m/fedia/t/350673
Note: it’s good news-ish
@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.
@Chozo @Novamdomum can you DM me your IP address? The site has been under a heavy ddos by scrapers and I think my script to identify those scrapers got a little carried away.