Was there a question in there somewhere?
No......
bobR == TROLL
Future posts from you will be ignored.

Forgive me for not being able to see your question behind all that bitching and moaning.
Their is something called punctuation. You might want to look into that. 
End you questions with a "?" when you ask them...it let's the skimming eyes note that their is a question being asked.

Now if you can properly form a question, and state it plainly without all the bitching surrounding it, then my mental "trolling" filters will not trigger and I might actually to read it.

Thanks for clearing that up.
We'll keep the code in place then.

I am real. Slush's pool sees the same thing....
http://mining.bitcoin.cz/stats/?history=1000

Besides, your 74330 getworks and 135 submitted shares isn't worth crying over like you're doing.
The amount of resources you used is enough to support 10+ more efficient miners.
There is no lose to me with you leaving the pool, in fact, it's a gain for me and everyone else because a inefficient CPU miner just bogs down the server.

That's all you needed to do.  That wasn't so hard was it?
We'll make the change later tonight to the code to allow this miner on your pool.
Likewise, I'd like to apologize for any previous rude tones or comments previously made (even if it was 20 minutes ago).

I'm glad you finally realize that a higher level of efficiency reduces the cost of running your pool.

This is really simple slush.... Apologize for 1) calling us trolls when we were trying to help your pool's efficiency, 2) trolling on our thread after calling us trolls, and 3) trying to put words in my mouth I didn't say.

That's all you have to do....APOLOGIZE.
If you can man up and do that, I'll put this all behind us and remove the code that forbids your pool.

That certainly is one way to do it!  Not bad...

Fine, you charge a "fee".  We don't.  Who's screwing who?

Because our pool is at a slower speed, it takes longer to get that many shares....like 2 days.
More users == more speed

And if 200,000 shares per unit is crap....
1966   2011-03-13 13:24:55   2:35:54   266129
1955   2011-03-13 04:15:49   3:34:04   330211
1930   2011-03-12 09:12:41   2:15:59   203318
1919   2011-03-12 00:07:20   2:39:24   233007

We're not the only ones seeing that high number of shares.
In any case, bye bye CPU miner.  

It works with any other pool but his, and I'll explain why.

When we first proposed our modified miner to help reduce the load and resources used on slush's pool, he argued with us and said that it was pointless and useless, while at the same time switching over to a forced donations (which technically isn't donating, it's taxing) because of the excess load on his VPS server, or so he claimed.

When we kept debating him about the role of efficiency on a server's load, he kept going back to the excuse that you must have a lower askrate to make sure that you're getwork doesn't go stale.  We proposed other ways of solving this problem (which is now in the modified miner), but slush didn't want to hear it, and insisted people keep pounding his server with a lower askrate.  Then, he called us trolls, and started to really give us a bunch of shit....for trying to help him reduce the amount of resources his server was using.  That was the breaking point for me.

There we were (Geebus and I) working away on m0mchill's miner to try and help slush, and then he turned around and called us Trolls.  So, fuck him, we started our own pool.  Then, after we start our own pool, slush's begins trolling and attempting to put words in our mouth, words we never said, and expects us to play well with his pool?!

So let me put this as simply as possible: Fuck slush.  He is not selfless, he's selfish.

If he wants to force donations because his pool is inefficient and uses more resources than necessary, that's his decision.  If he wants to apologize for calling us trolls on his thread, then coming over and trolling on ours, I'll consider taking that part of the code out.  But don't hold your breath that it'll ever happen...I'm not.

Yes. We have not committed to a date as to when this change will take affect, but it will be going  back to current block only.

We will let you know before we make the change.

***** ATTENTION CPU USERS  *****

I know someone at some point told you a lower askrate is better...they were wrong.  We are asking you to please increase your askrate from 1 to at least 10 seconds, we'd prefer 60 seconds, or we will ban your accounts in 24 hours.

The two accounts I'm watching closely are:

cd311 - Requesting 3 getworks/sec FROM 3 different IP's total.
Getwork Efficiency -
# Requested:    54081
# Submitted:    111

RobertRibbeck - Requesting 3-5 getworks/sec FROM 4 different IP's total.
Getwork Efficiency -
# Requested:    17893
# Submitted:    35


     I understand what is going on here, as I too at one point got as many CPU's as I possibly could (18 total) running on a pool.  Boy that sure was a waste, cause 1 GPU was waaaaay faster and far more efficient.  Another thing you must consider as a CPU user using a low askrate, you are not even getting 0.10% through the entire getwork before get another and try again.  I've been logging my getwork's, and out of the 18,500 getworks I have logged on my GPU, only 22 of those have an shares found in the first 1% of the getwork.  What this tells me is that you CPU miner's would find more shares if you tried to raise you ask rate from 1 to 20 or more seconds. 

Failure to do this on your part will result in your accounts being banned (you will still be paid though).  If you come back and have not fixed this problem, your IP's will be banned next.  Please fix this ASAP.  You have 24 hours to comply.

Thank you for your understanding and help with this matter,

Fairuser

ABOUT THE ATTACK ON THE SERVER...

It was a simple SYN flood and used about 1.4MB/s of traffic.  I'm not sure if it was a DDoS or just a simple DoS.  The logging I had was not sufficient to detect where this was coming from, but if it happens again, it'll be logged and *it will dealt with accordingly*.  I'm on a 100Mbps/50Mbps connection, burstable to 200Mbps, and they didn't even come close to maxing us out, but the sheer number of small SYN packet's was enough to mess with shit.  All I know is I was about to go to sleep, noticed shit was @ 0 Ghash/s, fixed it, posted here really quick, then went to sleep.  I just glad I woke up and it's still running.

Pool is back online.  We had an unusual number of SYN packets being received (3000+) to the server, and we only have about 45 active users.  It's possible we're experiencing a SYN flood, so I've enabled more detailed logging to help identify where the problem is.

You may also want to add a "-v" option to use vectors on the graphics card. 
With vectors you can see results like this from time to time.

03/10/2011 19:58:46, 899a911a, accepted at 45% of getwork[15595]
03/10/2011 19:58:46, 70bb3b4e, accepted at 45% of getwork[15595]
03/10/2011 19:58:56, a53d4081, accepted at 95% of getwork[15595]

Notice the TWO answers found in the same percentage....that's because vectors is enabled.

Don't forget, a "-h" will show all the command line options.

We do not force donations on bitcoinpool.com.  That's a big 0%. 

Yeah, the paging is broken right now and we're working on that. 
Thank you for reporting it though.

I would love to help you.  Private Message me so we can get started.

YES, we found another block.  Found by user "xxx" (which seems to have a lot of GPU power...thank you xxx).
We're just waiting for the block to be confirmed 120 times, then we'll be paying people on the 121st confirmation (which also shows the block as being "Confirmed" on the stats page).

We're still a few hours away from that though...

Perhaps our modified version will work for you.  It's got an EXE and sources.

http://www.bitcoinpool.com/poclbm-mod.zip