Sort:  

Yes, it seems to confirm what @l0k1 and I said about the api:

It's very inconsistent.

Well, the specific claim about the API responding with single-quoted JSON is false. It doesn't bear out in my experience. My tools would not parse such JSON and I've never seen that parse error.

I dunno what to tell you man.

@l0k1 and I have both encountered it and he has documented it in detail.

Are you referring to the thread, where @l0k1 says:

Followed by @xeroc's reply:

... it's not the error of the library, but an error in your code.

Yet, you said:

About the API? Well, let's start with single quotes are not valid JSON field delimiters

In other words, it wasn't the API response as you assert. And @l0k1 failed to update his post to reflect that fact.

@l0k1 and I have both encountered it and he has documented it in detail.

This is false. You have never encountered this issue in the API response.

I've seen it happen, once. Please do the faddat / JSON search here.

Additionally, l0k1's seen it happen.

Additionally-- I tried your tool. I don't think that it got everything or if it did, didn't get it in the right format.

Details, yes. Important details? Yes.

Oops-- it was a piston error. That time.

Fixing up Steems' API would have resolved that in no time. But never fear! The gRPC API is nearly here and it talks gleefully with the front end in real time. Everything else can go much more smoothly from there.

Ok, so we have you on the blockchain claiming that it was a rare situation that is impossible to recreate. And my tool also just happened missed it on those exact same occasions. Got it.

Incorrect.

Ya know what man? I won't tell you about it. I'm back off to my grpc-itude. you'll see.

Oops-- it was a piston error. That time.

How was it a piston error?

And now we're into questions I don't have the answer to.

It was a piston error, because xeroc said it was.

It was a piston error, because xeroc said it was.

No he didn't.