@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.
jerry
joined 8 years ago
The fallout from the malicious tj-actions/changed-files is still being investigated. It is fortuitous that this malicious commit was identified fairly quickly, as further compromise of major OSS
@hitstun@fedia.io @jerry@fedia.io @Nougat@fedia.io 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.
Jerry, I have a question why does fedia defederates Threads, but infosec.exchange doesn't? In the past fedia was federating with Threads, but recently they were suspended
Jerry, I have a question why does fedia defederates Threads, but infosec.exchange doesn't? In the past fedia was federating with Threads, but recently they were suspended
Behold the magic of the fediverse! In the Flipboard app, you can now follow these cybersecurity experts and journalists from the Mastodon community:
@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.
Hello everyone. If you care about fedia.io, please read this: https://fedia.io/m/fedia/t/350673
Note: it’s good news-ish
view more: next ›
@harrysintonen@infosec.exchange the second and third order impacts of this could get interesting