Let me address your other points in autistic detail as well since I feel like you're going to try and pick at everything:
The backend was also never touched. If you edited your /etc/hosts file throughout the whole downtime, you would have been able to use Spy.pet.
This is wrong, simply from the fact that you're using Cloudflare.
At the very least, you'd have to know the exact edge server Cloudflare assigned to your website to be able to connect to its IP address, which you're not going to know unless you figure out how to trawl through your DNS cache or ping it manually and write it down somewhere before the domain got taken down. (Or you set it to the IP address of the underlying server, which would be retarded to share with others)
Assuming you did, Cloudflare's infrastructure wouldn't have allowed it. Cloudflare is just a glorified WAF; it doesn't assign an IP address to each domain passed through it, it instead uses shared edge servers and figures out which server to forward the request to using your Host header and the DNS settings you've configured. It's why Cloudflare doesn't accept ports other than 80, or why you can't just paste the IP address from your ping tool into your browser
The moment the original domain stopped working (due to the DNS entries being wiped), Cloudflare would've started rejecting all requests for that host because those DNS entries don't exist anymore. You know they don't exist anymore because the domain wouldn't have stopped working in the first place
And even if you managed a way around that, HTTPS would've prevented the connection.
You were using a cloudflare edge certificate, meaning that HTTPS is set up to only work through Cloudflare.
The only way this would have worked is if you disabled HTTPS (retarded) and pointed the host towards your server behind cloudflare (even more retarded). If it was just that simple, Kiwifarms would've endorsed it every time a domain got taken down. I don't see you telling people to do it in your telegram channel either
Check the date on the tweet, retard.
What's wrong with the time? You announced 6 hours earlier
on Telegram that the domain was taken down:

So if you lost data at any point, it would've been right here before the tweet happened.
Plus it took you 2 days to bring the site back up, which is pretty long if all you had to do was just point the DNS entries towards the old server.
There is absolutely no way for Discord to find where I'm hosting the messages. Wrong as always, stalker.
You've fucked yourself over by using Cloudflare. The 10+ discord users who want to burn down your site and nail you to a cross have nothing compared to a $15 billion company, getting the best lawyers money can buy to subpoena Cloudflare, and doing the same to all the ISPs up until they connect to you.
I don't know why you're channelling your inner Fatrick and calling me a stalker when all I care about is the data. You scared a lot of servers when the site was made public for the first time, and a lot of people would've hidden or deleted their chats after knowing that there could be bots scraping everything they're saying. If the site's data is gone, then those messages are
permanently gone because they can't be scraped anymore. And you have the gall to fling shit after doing this