thanks.
also. you should be able to see solo worker data at this point. there is still an anomaly floating about that i'm trying to trap but it should be healthy enough to access. right now, solo worker address can be any syntax as long as the btc address is there address, address_worker, address.worker.the logic will move up to the top level address and grab all related worker under the user. as far as i can tell, there appears to be no workers without a corresponding solo users stat, and there's no immediate benefit to just see / track a single worker under the user umbrella.
also. you should be able to see solo worker data at this point. there is still an anomaly floating about that i'm trying to trap but it should be healthy enough to access. right now, solo worker address can be any syntax as long as the btc address is there address, address_worker, address.worker.
Cool! It works!
It's kind of magic that this works without an app update. I guess you aggregate the data on your own backend, or something like that.
As per your description, when I put in my worker address for the Sidehack Compac Stick pool I see all the pool members. The way that "pool" is structured is that we all use an address provided by philipma1957, with individual workers to track shares.
It's a lot to look at, but it does work. No need to limit the view to individual workers on my account.
adjusted to go down the hierarchy but not up. this is useful feedback. appreciated since i don't see all the common use cases yet. if it's not relevant i'll chime in accordingly and punt the request.
. will find a balance.
