So, most of you may be wondering why Bluesky went down. I've made some checks across channels and it seems it is indeed not working as intended. Not Enough Resources seems to be the common issue here. However, there have also been some regression indicators with the Age Verification reappearing after force closing the Bluesky App in a logged in state. There's also this for the website version of Bluesky App (bsky.app). I even saw an error about the usage of HTST instead of HTTPS when accessing bsky.app. Which highlights a possible Certificate based or Firehose MIM/MITM attack but I cannot be certain this is the case and may be how ATProtocol is entered into a safe mode state to deal with the issues currently experienced. A MIM/MITM attack is a Man-in-the-middle attack where communication is intercepted and altered within the relay stopping the correct responses from occurring on either side. Meaning that the firehose that ATProtocol and all ATProtocol apps rely on is in a manipulated state. But I'm not the expert. It could also be possible that the current issue is a DDoS (Distributed Denial of Service) attack on the main ATProtocol servers leading to outright failure to maintain the service when it is a requirement. I also checked status.bluesky.app the official Status Page for Bluesky. The API servers were in a state of RED, downtime when I visited. At the bottom of the page was a telling indicator and notice stating an issue published, what seems to be rapid speed by the devs *without* spellchecking. We are…