Thanks for adding this information inertia. In your next radiator release can you make this the default? We will be doing the same with steem-js and steem-python, and I'm sure @almost-digital will be updating dsteem also.
EDIT: I see that that is a bundle update so you must have already done so, great :)
dsteem doesn't have default nodes, but I'll make sure to change the examples to show
api.steemit.com😁I am currently implementing a HTTP Client for SteemJ - The next version will support it ;)
Good news, glad to hear it!
Yep, it's been the default for almost two weeks. :D
But of course, people have to at least do
bundle update. There are additional steps if they aren't using the defaults, which is likely. But most of that can be picked up by recloning the app and installing from scratch, which I go over in How to Update Radiator Apps.Interesting - I believe we weren't quite production ready on that two weeks ago. It's usually best to wait for a formal announcement to update such things. But thank you for being on top of it anyway, much appreciated.
Hay @justinw - I would totally agree with you, but as a third party developer myself I have to say that this is quite impossible. - I need to implement the stuff at the same time you do it, because you do not provide a lot of information to us. From my point of view this is more or less the first time I hear about a change early enough.
If we talk about Steem Updates its quite a nightmare - You release a new Steem Version, everyone updates the nodes, and depending on the changes, a lot of third party tools are no longer usable (at least parts of them).
I've talked to timcliff some time ago that it would be really great to have a changelog for third party devs some weeks before you release changes.
That would be really really nice <3
This IS the advance notification and is why we're not discontinuing hosting a websockets enabled cluster of steemd's (
wss://steemd.steemit.com) - at least not yet. We want to give everyone fair warning and a chance to update their libraries before discontinuing this service. It's never our intention to leave behind 3rd party developers. If you need help updating your applications orsteem library feel free to reach out to me directly on steemit.chat and I'll do my best to answer any questions you may have. This will be a transport change, not an API change - anything that worked over websockets to steemd will work over http/jsonrpc, generally with fairly minimal adjustments. We made a commitment earlier this year to communicate as much as and as far in advance as possible for any API changes or anything else that could effect third party developers. We will continue to notify everyone about any upcoming changes in advance. Steem on.
Thanks for taking the time @justinw - Yeah, as I said, this is the first time I see an announcement early enough and I love it. If you keep doing this for the future and especially for API changes I am more than glad to hear that <3
Regarding the switch to HTTP I also agree that it is not the most complex task :D
Steem on! :)
Will there be documentation/tutorials if we want to add Jussi in front of our own full nodes? Are their drawbacks? Was the transaction broadcast errors, account not found, and all the other issues the result of Jussi?
As we have availability to do so we will expand the existing documentation for jussi as well as any other services that are lacking full documentation.