4·
11 months ago@IlliteratiDomine @DarkThoughts I found the problem - it was an error I introduced when moving fedia,io to containers recently. it works now.
Merry 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
- 5 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.
@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
@[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.