This is unnecessary. You should use the RPC call account_history_api / get_transaction if you need the full trx. It already includes all the data you are looking for.

Nice of you to highlight this post and provide some of your thoughts! First, a bit of a correction -- Greymass is an organization with @jesta, but also myself and a few others. This article was actually

Thanks for the heads up! This issue was leftover from me updating to HF22 today. Everything should be resolved now, and anyx.io should return the same results as api.steemit.com again.

Yes, I misunderstood that hivemind supports get_content fully. It unfortunately does not. I updated it the other day to direct to the full steemd node rather than hivemind. If you try again, results should

Thanks for the heads up. It seems I misunderstood that hivemind should support get_content calls, apparently that is not the case. Issue has been resolved and the results now match api.steemit.com.

You've done something wrong in beem; likely you've assumed data in steem operations is always uft-8. It is not guaranteed to be so. I believe Jussi re-formats steem data to be uft-8. This is not a good

No, there's only the automated message. Anything further is dealing with steemcleaners, who are humans. :) I had a whitelist before but it is too cumbersome to manage. If you use Steemit's API interchangeably

There's nothing explicitly negative about a cheetah comment. You can just ignore it if you know you're not doing anything wrong, nothing will come of it. The "daily post" stuff she will figure

While it would be great to search using a transaction id, I haven’t found a way to do so using Steemit condenser api (the current functionality is simply deprecated). This is due to (the first history

Absolutely not. Plagiarists, identity thieves, or other fraudsters will mute comments from anyone calling them out on their actions. This means the @steemcleaners and @cheetah efforts would be useless,

The 2000 character limit is a seemingly arbitrary limit enforced by 'jussi', Steemit's API middleware. Most other node operators use this middleware. Since I've been building my own middleware, I'm not

custom_json ops don't affect the ram usage of consensus. These ops are simply validated and placed into the block log -- stored on disk. It's up to any second layer solution to determine what (if anything)

I don't object at all to this change, but I wanted to caution those using custom_json's for derived consensus data, that this may change how you interpret ordering. You can no longer do async/parallel

Browser extensions are pretty insecure things. I'd recommend instead just creating a bookmark and have the url be the following: javascript:(function(){location.assign(" + ((location.hostname ==

Thanks!

So, semantically you wouldn't really be "hosting an API" -- this more of a translation layer. But definitely plan on open sourcing it after I get some feedback and formalize the design, as my

Not yet, no. It's definitely still a work in progress, and I've only mapped the GET requests so far (and some I know don't work). But given some dev time I'll have POSTs working too :)

I hadn't heard of HATEOAS, but that's interesting! So far I have focused on stateless GET requests, as the majority of the interaction with steemd is actually that. The only real thing to support for POST

Boom, refreshable web query in excel. It's just that easy.

So, this layer would actually sit in-between something like steem-js (which is a library for a specific language) and the steemd API node chosen. If you're working at the library level -- you need not