Quote from: gradinkov on April 05, 2018, 12:42:00 PM

Quote from: Just_a_miner on April 05, 2018, 08:03:18 AM

Quote from: gradinkov on April 03, 2018, 10:16:03 PM

To begin with, hsrminer does have an API.

You mean ccminer had an API, but palgin disabled it by changing default port, removed all API-related cmdline options and changed api output format so no monitoring software can use it.

So please, dude - if you like to use crippled original hsrminer, feel free to do so, but don't spread misinformation.

It's not me spreading the misinformation.

1. Changing the port does not mean the API is disabled.

2. Not documenting the default port does not mean the API does not exist.

3. Removing command line options that adjust API behavior does not mean the API does not exist either.

4. Changing API output format does not mean monitoring software can't use it. That's utter bullcrap. It's not like miner API output has a standard. ccminer, dstm, ethminer, excavator, zecminer, ... - they ALL use different API output formats. The monitoring software needs to handle that. In fact, the ONLY difference between hsrminer's and ccminer's output is that you need to find the SPEED key instead of KHS for hashrate, and the POWER_CONSUMPTION key instead of POWER for power usage. The API call, the key separator, the value separator, the line separator, the terminating symbol, pretty much EVERYTHING else is the same. If your "monitoring software" can't figure this out, then it's your monitoring software that's crippled, not hsrminer. If you can't realize this on your own, then I sure as hell don't want YOU to touch any of my miner executables, because that's incompetency beyond repair.

5. You even sent me a private message that you "added" an API to your "fork". I already addressed that you can't "add" something that already exists. But now let's address the fork bullcrap too. Forking means you alter the code. But hsrminer's code is not published. I pointed this out in PM already, to which you responded you "reverse engineered it". Except reverse engineering means "patching" at best, not "forking". You just mess around in the binary and pretend you're some crazy genius, while in fact you just changed some existing parameters. Like "if I change intensity, hashrate increases :O". No shit. And so does stability decrease, but never mind that. And you changed the devfee address, of course.

All I see is you spreading CONSTANT fud because you're butthurt about hsrminer. But I have no idea how anyone here can take you seriously when you have so many factual errors all the time.

Friend, you have some problems with reading. I repeat for you again - ccminer HAD an api and palgin DISABLED it. You can play with words in 1),2),3) but you wasn't able to use original hsrminer "api" and asked palgin to ADD it, what an irony Cheesy

After some dude hinted you that there is hidden port, you all of the sudden become original hsrminer api expert Grin

I've sent you pm to hint you about my fork when I've read that you were asking to add api to hsrminer. As for reverse engineering - you can try to "mess around" with original hsrminer.exe and "change some parameters" to see if it will add all that I've added to my fork (and fix some palgin's bugs too) Grin

You are also wrong about devfee - it was added after 2 months of work, when 95% of features were already implemented. Devfee coded from scratch, optimized to reduce pool switching lag, backup pools added so miner doesn't stuck forever (like original hsrminer) if devfee pool(s) doesn't available, and devfee time is reduced by 10 seconds.

I understand that you are a troll, but please continue to write (especially enlight me more about reverse engineering Cheesy

) to my topic to keep it on 1st page of the forum so more people will read about my fork, thank you friend Grin