Chaturbate XML feed issues
 

I am seeing JSON coming in instead of XML on my XML feed url.

Not sure when it started but has been happening for a little while now. I moticed while doing a site check and saw way too many images missing.


Sample of what is coming back from the xml feed url: [{"username":"canbebought","spoken_languages":"engl ish","tags":[],"current_show":"public",


.

All feeds XML, JSON and YML are returning JSON, it appears.

So, if you are using the json feed then you are probably ok. If you are using the xml or yml feeds, you are screwed right now.

I have submitted a ticket to support.

.

They're not exactly the same, though. Slight differences between the three, but still just json :upsidedow

Doesn't matter if they are different, none of them are xml and my program is expecting xml :(

Giving it JSON just makes it puke.


Makes me think I might want to make it adaptive though so if it gets xml it uses it but if it is json instead then use that.

.

Oh I know, just saying it was weird.
I like the idea. Maybe the feeds going to json is why some people are saying that sales are down right now, and being adaptive would fix that. :upsidedow

I think this is something that has just happened today, not 100% sure on that but I look at my sites often enough that I think I would have caught it if it was happening very often.

Big gray "Chaturbate" images showing is always a clue that something is not quite fucking right, ya know?

.

Looks like they got it fixed.

.

Yea everything is not good in the neighborhood. Have you emailed them yet?

Ah sorry, I thought I read that it was going on for a while. Not sure why..

But, even when it is working (Looks fine now, although the first try timed out for me), I still see broken images here and there on almost every load using XML. Do you know of a good way to just filter those out?

I don't see them very often but no real good way to filter them out that I know of.

Th eonly thing I ever came up with was testing each image as youu bring in the xml (or something like that). That would mean pulling every image file onto your server so you could interrogate it to see if it is the gray chaturbate image or an actual model image.

That seems like a lot of extra load for every xml load, ya know? If you pull in 1000 recordss then you have to also pull in 1000 images to check each one.

There might be a better way to do it, I just haven't figured any other way out, so I just accept that there will sometimes be ugly gray chaturbate images pulled in from the cdn.


.

Broken images share the same md5 hash.