you said it right there solo pool.   second time today.  i'm half reading posts for some reason.   it's on its way.

That would be correct, at this time.    Data collection for solo workers is not enabled (noted in 1st post).    Ironing out kano.is side in this first go around.   Check the post in 48 hours to see if there's any status on that.    There's a good chance there might be.

i am truly shooting to keep everyone happy.  not everyone will win, but you do get priority .  will find a balance.

so after a bit of pondering i will leave data found behind passwords authentication alone.   
even though i can secure it with a point to point node and a single password guarded from the world.

my stance on screen scraping though:

i'm not against it to pick up public data so long as the site owner doesn't say go away.
screen scraping will continue to occur to pick up tidbits of neat data (aggregator/normalizer node - no change to code) from various places until the corresponding api data is available.

given that i will keep a sharp eye out for api updates as it is the better way to go.

user requests will be sorted into versions and wish-lists (todos) accordingly to not be forgotten about.

Good Job to TheJesterOne for getting that one out, and for setting the bar for the ideas for this.
https://bitcointalk.org/index.php?topic=789369.msg11091187#msg11091187

I've fiddled with java, but not that great at it honestly. 

it should be displayed.   put your worker name at the end of this url string, browse it and see if there's data.

https://www.kano.is/worker.php?a=

fix it first to get data and pm me the worker address if there's a mismatch.

API has a implied contract with those of us who use it.    
Web scraping will definitely be unstable.   And more work for me, bad experience for end user.   Adding to wish list, and leaving at that until i ponder it more.

i summarize most stats via an aggregator for notification and the new https only requirements in xcode.   the app won't be requesting user passwords.    i would likely have to use my own and broadcast global values without others needed to do so.

If you do, i'll look into adding a QR scanner.   looks pretty basic.

Glad to see it's getting some activity use and holding up so far.

re: tagging on block solver's name
- adding to todo.   not in api but doable and it will add to the excitement   i suspect kano is not displaying it on the home screen because of privacy respect.   if i get a request to not display, i'll end up removing it.

re: direct btc address.   yes it takes address_worker syntax.

re: donation.   cool.   appreciated and thanks.

stay with testflight.    the donation address [1CKaPP1wSBBfqhJB5uE7QBqyvEf2EBSjQe] is in my signature on on the first post of the forum topic (edit: apple has policies against donation button - easy rejected - i'll tack it in at some point once i figured it out).   big shout out to all those who sent me test api addresses and beta users.

Hot off the press:   The status for your app, CKPool Stats, is now Ready for Sale.

This is the first build in the wild [so be patient as I tune it].

https://itunes.apple.com/us/app/ckpool-stats/id1076177533?ls=1&mt=8

https://bitcointalk.org/index.php?topic=1344360.0

I've attempted to include a small element of each of the original wish list:

Pool/User speed
Last Block Found Time.
Block/Block Statistics
Payouts.
Page to show a list of worker/s

no problem.   i only bring that up because the two lowest values for 7 day average on your monitor home page happens to be thursdays.   i've guestimated out what sunday looks like now.

that is interesting.   using thursday as an end of week creates pretty decent weekly variance.    possibly the worst day for the week to end.   try sunday as end of week.

Visit : https://ckpoolmonitor.zachmonroe.com/  

to see off site computed numbers on actual payouts.

Reference: 1TH computes to 0.00418972 btc/day at current difficulty.   (0.0044 last diff)

if 90% earning over a full week is your targets, the numbers there should help you with more info for making your decision.

"The pool hash rate for the last day is roughly 12.94PHs which means the 5Nd 'ramp' is roughly 2days 7hrs."
after 2.5 day, 90% looks very stable over a week period (from this angle).

variance is such a fancy term.   are we talking change in payout frequency over a time range?  variance over a month is pretty low.  variance over a week is pretty low.  if you are speaking lower variance over a day, 2PH will go a long way to lower that.   if you are talking variance hourly, you will likely be waiting a long while. 

Apple iPhone version for CKPool Stats is now available

This is the main thread to provide status and QA.  

Related Threads:
https://bitcointalk.org/index.php?topic=789369.0 kano.is
https://bitcointalk.org/index.php?topic=763510.0 solo.ckpool.org

CKPool Stats provides a portable view of key statistics from kano.is and solo.ckpool.org.

Current Release v1.2 adds:
- Worker transition to idle notification.
- Worker sorting by name / hash tapping.
- Badge notification for idle workers.
- api key QR reader.  

Release v1.1 included support for:
- Block solve / found notification.
- Payout notification (kano.is).
- Apple watch notification when paired.
- Pool statistics.
- API based worker statistics (kano.is).
- BTC address worker statistics.

https://itunes.apple.com/us/app/ckpool-stats/id1076177533?ls=1&mt=8



Troubleshooting steps:
1. Make sure you have internet access.
2. Make sure you allow notifications (do it right the first time).
3. Kano.is username(s) are case sensitive.

FAQ:
Q. There's a red badge on my icon with a number in it.  What is it and how do i clear it?
A. The number represents the count of idle workers seen in your watch list.   It will clear itself out when idle workers clear out.

Q.  How do I sort my workers by hashrate?
A.  Tap the hashrate of any worker.   It will sort ascending (yellow).  A second tap on the hashrate will sort descending (green).  Same applies to worker name.

Q. What is Direct Addresses?
A. That plus sign in configuration is for adding BTC based worker monitoring addresses.   It will be listed under Direct Addresses.
        1. use address.worker syntax (address only might work)
        2. swipe the added item to the left to get the option to delete typos.

Q.  What is the criteria for Trending Down?
A.  Subject to change: Trending Down is currently set to show worker where its 5 min hash is less than 85% of it's 24h hash.

Q.  The app link is reporting not available in my country.
A.  Try again in later.

Q.  Can I join beta to get a sneak peek at the next build.
A.  PM me an email.   You'll get added to apple's beta list for new build notification and early install.  


Known Bugs:
- Two stats pool mode covers up marquee on iPad mini.
  + Cleaned up in next build.    Workaround: Use four stats mode.


What's next in v1.3:
1.  Worker detail modal.
2.  More on/off buttons in the configuration section to customize.
3.  One or more misc todo.


Misc Todos:
1.  Summary group for DA
2.  iPad friendly(er)
3.  Multiple account support.
4.  Add worker name which found block.  (best effort)

Disclaimer:
The app is free, as such you can expect at a minimum you will get free quality support.
If you like the app and want to root for it's survival, support the dev license fee, or to just send a thanks,
    send donations to : 1CKaPP1wSBBfqhJB5uE7QBqyvEf2EBSjQe

yep (technically, a small few of us beta do see it).  but there will be lots more to show.   

i've been tacking updates in my signature, but have been quiet on posting.   just finished up a quick beta with a few pool volunteers.   tried to keep it pretty basic to get something useful cleared through apple.   sitting on apple to review one last time.   target has been end-of-month.   it might take them that long given the last review time.   right on track at the moment to meet the target.

hotstreak.  wtg.

double congratz.