|
If he gets a coffee mug, can I have a mousemat?
Wait.. which will sell for more on Ebay? hmmm..
|
|
|
|
|
Paid with TXD b08e2ac6ff33bd6e076f7eb3755c7b4b2415ff200bb4a8cd7462f0c7353e0b6d
|
|
|
|
|
I would be next in line for those two units but I have to agree, it wasn't against any explicitly set rules, no matter what we may think of it.
|
|
|
|
|
huh there was a winners table there before I posted that, I'm seeing things :/
|
|
|
|
that feeling when you bid 50 early Thanks so much John, really well run auction. I'll send you a tip  |
|
|
|
I was post #735 btw if it helps you any John  |
|
|
|
awaiting official confirmation table 3 is accurate (damn I was close..) |
|
|
|
|
If working from the end please take care about bid order - earlier bids of the same value beat later ones, right?
|
|
|
|
|
Adrenaline, you can stop now :/
|
|
|
|
|
I literally don't even know if I won or not.
|
|
|
|
|
PM sent, probably longer than you wanted :p
|
|
|
|
"Last received block was generated 54 second(s) ago".
This may be a minor point, but "second(s)" looks SO ugly. It's a real pet peeve of mine about sites and programs that can't be bothered to clean this up. Is it really so hard to do "%d second%s", x, (x != 1 ? "s" : "") |
|
|
|
|
Yes, sorry, it has just been done.
Apologies for the delay, I didn't want to rush it and get it wrong - transaction id is f89de013f710f07b89e09901ed86815ebe8f115c50579fda5d2d370af06779dd
Emails were sent out if you had email confirmations on.
|
|
|
|
|
Closing down the pool (yes, again).
Two main reasons:
a) I believe bitcoin is dying a slow protracted death, with falling hashrates and falling values it's only a matter of time before it's gone entirely.
b) we had server issues which led to the outage earlier on today, but believed them to be fixed - sadly not and we're now at a state where the pool server won't boot properly, and given my position on a) I'm not willing to invest any more time in fixing this and carrying on running it just to have it all for nothing in what I suspect may be a matter of weeks.
There was one block which hadn't confirmed yet, once it has I'll get it paid out. All remaining balances will be paid out.
It ain't coming back this time, thanks for the hashes over the past few months.
|
|
|
|
|
Yep, sorry, fairly major issues overnight and this morning, sorry about this. Our first serious downtime since we started though.
I'm aware of blocks #45 and #46 showing incorrect payouts, I'll fix this shortly.
|
|
|
|
Three blocks isn't much to go on statistically. One thing I need to do is make it easier to work out our luck over any defineable timeframe but I'm not sure how to implement it yet. If someone gives me a decent idea on how to represent it then I'll code it up Those graphs which show a moving line of luck on recent blocks aren't bad, but I kind of want a number rather than a graph, IYSWIM |
|
|
|
Then you are pretty weak sysadmin because DNS server change can easily take over 24 hours for busy server.. it usually takes much less time with small web sites.
I don't think you have the faintest idea of what you are talking about. Are you suggesting a busy website makes DNS take longer to propogate? Really? Tell me how the webserver affects DNS. |
|
|
|
|
Considering it. I want to see if MM has some staying power before I invest man-hours into it.
Also we're looking at migrating to poolserverj and shadders is currently in the middle of implementing it in that; so once proven stable it shouldn't be too difficult to do anyway.
|
|
|
|
|
Show Posts
