#devportal

This week, I had two new pull request for Steemit, Inc. to merge: PR#432 - SMT API Definitions (already merged!) PR#433 - Blockchain Include: Mira performance tuning (article by @gerbino) SMT API Definitions

No documentation pull requests this week. Some work is ready but I thought I'd hold off until I had more to submit at once. I spent most of my time continuing to researching SMTs, thanks this week's testnet

For once i have to start coming out. It is the least i can do. It is one option to exhaust. I have to relegate reservations and exercise more freedom. I have to do this especially since i cater to my dad

Preface My name is @surpassinggoogle. I have been on steem for more than 3 years and i have been part of its stories and histories. I have also been part of its growth. I love steem. (Here is some evidence

This week, I have two new pull request for Steemit, Inc. to merge: PR#430 - Small change to page header so that the canonical_url points to the original article. PR#431 - Link back to API Pagination Recipe

That's a wrap for Proposal #10. Thanks, @roadscape for merging everything. Here are links to all of the final changes on the live production devportal site: PR#420 - Again as I mentioned before, 95% was

Synopsis I will continue to provide documentation intended for application and tool developers who work on the Steem blockchain. To review the documentation I'm improving, go to steem.com, click Developers,

All of my pull requests got merged. Yay. Full disclosure, I worked on 95% of PR#420 before this proposal, but I also never wrote a blog entry about it. My plan was to write about it after it got merged

This week, I have only two new pull request for Steemit, Inc. to merge: PR#426 - Add Steem Keychain to resources PR#427 - Services Section Update Future PR - New Recipe: About config.ini That last one

This week, I only have one new pull request for Steemit, Inc. to merge: PR#425 - New Recipe: API Pagination This one was particularly time consuming, partially due to the amount of reverse engineering

This week, I have four new pull request for Steemit, Inc. to merge: PR#421 - Glossary Changes PR#422 - API Definitions Update PR#423 - Plugin / API List Update PR#424 - New Recipe: Setting Up a Testnet

I am very pleased that my proposal has been approved. While the Steem.DAO is ramping up, the funds have yet to fully match the approved proposals. But that's fine. I believe I have my mandate and this

I will provide documentation intended for application and tool developers who work on the Steem blockchain.

Last month we published an article telling you about some of the upcoming changes to the public API that we host at api.steemit.com. Today we would like to announce one additional item to those set of

Hello Steemians. We’re kicking 2019 off with a whole bunch of devportal updates! Below you will find summaries for some of the updates, but for a complete list be sure to go to: Issue 384 A tutorial was

Repository Site Issue What was the issue(s)? As a node operator and/or witness, I would like to know exactly which plugins are required by which API, so I can fine-tune my node's resource requirements.

Repository Issue Details On a node that is running the reputation_api plugin, execute the scrape rake task to capture the methods and signatures as yaml and add them to the repo. $ TEST_NODE= rake

Repository Issue Details Related page: Current diagram: I think this could be improved. The basic structure is correct, but it looks like a ruby developer just slapped it together in a hurry. Github

Repository Site Issue What was the issue(s)? As an application developer using the Steem blockchain, I'd like to know how (and why) I can compute a transaction id or get the transaction id some other way,

Repository Site Issue What was the issue(s)? As an application developer using the Steem blockchain, I want to know the status of transactions I broadcast, so that I can determine if/when my transactions