TL;DR My intention is not to bash the coin, I am holding a few HUSH myself and wanted to see what these "superb developments" are. I went ahead and checked it, and there really is not much to write home about (at least on github)
Uh-huh, and what exactly they must be changing in the node code?
Hush messenger is not a node, web-wallet is not a node, next-gen light wallet is not a node, and you never see any changes in any repos that have not been published yet.
I am not here for an extended argument or to annotate the repos, line by line. But for an example "hush messenger" is an electron boiler plate code started and left there.
Aside of the fact that the master branch is the thing people relying on when installing a new node, etc. Not a place to put the current work and untested changes, mister fairly technical.
apologies did not want to link all branches, go check the "dev" branch and tell me about all brand new readme updates. on the other hand master is still the bleeding edge code, strictly speaking "tags" or "releases" are
supposed to be the stable code.
We are working diligently on many things. TBH I think we are the only coin that offers a full restful http-api that interacts with the coin daemon. I'm sure once some others read this it will not be the case, but for the time being we are.
Just so you understand what this does, in a nut shell allows you to simply integrate the hush wallet with a web front/back end. You could take hush as payments and not need a 3rd party like most coins do. Further once we finish the counterparty and evm integrations this will allow instant access for devs to use them without needing libraries or code to impersonate the coin daemon.
Every coin daemon offers the api and it is rpc. the rest api in github is a 10 line(sorry, could be 15 i've been known to exaggerate) node.js wrapper. every language including node.js can interact with RPC, no `3rd party` is needed. your wrapper gets the command and passes it to bitcoin client.
To answer the "I don't see any commits" do you expect us to publish unfinished or thoroughly tested code to a public repo where people will just clone, build, and use it? The branding stuff is only due to people asking for it, tbh I could care less what the code running in the background is branded.
I completely understand and respect the reluctance to open your code. What I don't understand is how other random people posting in this thread has access to your private repositories and keep banging on about "how good the development" of this fork is. I was just curious, went to github checked a few repos and could not see anything. Yes, they might be in private repos but
I did not see much.