My browser / operating system: Windows NT 10.0, Chrome 124.0.0.0, No Flash version detected

Note: As far as I'm aware, this is not related to the front page bug on the projects disappearing.

What the bug is
This link to the API is the only proxy link on Scratch that uses a GET request, i.e. the only proxy link that you can view with your browser. It is supposed to show the projects currently displayed on the homepage. However, when opening up the page, it says that a start tag < is missing at the very beginning of the page. Meaning, it shows nothing. I tried this on iOS too, and it also said there was an error, but that time it said that the document was empty.

When it started
I'm not sure when it started saying this. I did try this a few days ago, and it also gave me this error. Luckily, the Wayback Machine archives this page multiple times per day, and it appears that this has been present for more than a year. Because the projects disappearing on the homepage didn't start until yesterday, this is likely not the cause for the missing projects.

Why it happens
Currently, the cause to this is unknown.

I tried providing an image, however it unfortunately does not let me. If someone else can provide an image, please do.

stop [hammer time v]

Why did nobody reply to this? I'll bump it up.

stop [hammer time v]

This will (hopefully) be my last attempt to bump this up to the top. I just want another opinion/response about this.

stop [hammer time v]

having the same issue as well and the api just shows an error

The Scratch Site seems ok and running now.
________________
FishHoue's Signature
print(“FishHoue”)

Can replicate that the API is not loading. I suspect this is connected to the disappearing projects. Why do you say it's not?

From a technical viewpoint, this error is caused by a malformed XML file. This is obvious if you view the page in question in FireFox. I assume that it tried to read the actual JSON file (which is the file sent for API) as an XML, which is also obvious in FireFox. I'm not sure why that page specifically has done this and not other API pages.