The situation isn't that situaion, it's in fact:
- Fuz: I want to give you money to write an app for this cool new blockchain!
- Jake: OK, let me talk with Brenn
- Brenn: Yeah, we can do that
- Jake: Hey fuz, yeah we can do that
- Brenn: tries to write wp plugin, declares the situation fucked (and surely, wasn't wrong.)
- Jake: So.... Brenn's off to Ukraine, but I will keep working at this. Let me check with the folks who made the blockchain. I'm learning go for this, la-de-da..... I'm going to make a thing that reads the whole chain, doodleydoodley doo. I will do analytics on the chain, doodleydoodleydoo.... (and it was super-cool that fuz knew this and was OK with the fact that I was learning and doing his project)
- Stinc: Our shit is PERFECT! You should smell it-- mmmmmm roses!
- Jake: Okay, I'll just try to spec it around "Roses formatted JSON"
Time Passes
- Jake: Dudes, I uses roses formatted JSON and it still doesn't work!
- Stinc: yeah, fuck off. Why didn't you use the js lib?
- Jake: Because it can't do ___, _____, ______, ______
- Fuz: jake you know at one point I heard that the interfaces had been deliberately made crazy-mode.
- Jake: WTF!?
- Fuz: "Jake's a scammer"
the scam is graphene
I don't understand that scenario. I wrote a tool to replay the blockchain from RPC and save it to a database. In 7 months, it has never encountered anything weird in the JSON responses.
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:
Yet, you said:
In other words, it wasn't the API response as you assert. And @l0k1 failed to update his post to reflect that fact.
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.
How was it a piston error?