Chaturbate API fucked up for anyone else?
 

We make heavy use of the Chaturbate API.
Works great 99.5% of the time.
Noticed last night it wasn't working correctly, and it's still fucked.

We write the data to a sqlite db, and something is fucking it up on write.

Not sure the problem yet.
Anyone else having problems?

now i understand, why i have since 48h so low signups on cb.

i dont use api, but cb technics, but the results are really low...

also my sales are stopped since starting 16th of this month..

hmmm

errr.... CB technics?

i mean normal cb Affiliate Linking Codes

My sites grab the xml feed every 5 minutes. I only keep track of what happened on the past load and the dump file I have did not indicate any problems.

What kind of problem are you seeing? Have you isolated the write statement that is fucking up so you can see what the data you are trying to put into the database looks like?


All my numbers for this period look pretty normal from what I can see.

.

works ok here...

There's XML, JSON, and YAML versions of the API. IDK which one you're using. I can't speak for the others, but I can say YAML certainly has its quirks. You don't go into detail about what issue you're having. But if its related to irregularities in the API, read on.

One irregularity would crash my PHP at random, while the rest of the time everything would work perfectly fine. This baffled me for weeks, until I finally figured out WTF was going on.

In the YAML version, model names typically aren't encased in quotes. However, if the model's name happens to be all-numeric, they are encased in quotes. This resulted in unexpected, unneeded quotes being put in my PHP. Which of course would crash the PHP whenever an all-numeric-name model happened to be online. And then it would magically work again once all the numeric name models logged off.

I contacted their support about this, explained what was going on, and that it probably was a bug in their code and not intended. They ended up changing a few things in the YAML API a bit. But none of the changes were related to, or in any way affected, the all-numeric model names bug that I'd pointed out.

So I just let it go. I instead just coded around the irregularities. Haven't had an issue since. Good luck to you.

A models name is a "literal" -- you cannot perform arithmetic on a model's name (a string) ...

That said, if the source data (feed) is not corrupt, or there has been some change, you need to echo or print out the data parsed. Using a PHP parser I would do this in a terminal with php cli you will get better error reporting.

By experience sometimes their API has glitches or cant be reached but it never last for very long...

That's not a bug, that's just how YAML supports integers and floats. You should probably just use a real YAML parser since that's not the only weird thing it does... (see how invoice, postal, quantity, price, tax and total become ints or floats in PHP: yaml_parse - Manual)

Definitely sounds like OP has something like that going on as well.