Ya know, most of that could have been done in PM... .. .

-- Smoov

My utilization was based on other traffic I generate too... like when I'm streaming audio/video streams...

-- Smoov

However, if you have your fee set to 100%, then 100% of the shares mined, by everybody, gets credited to the default bitcoin address p2pool is using for yourself. You have to leave your fee set to 0%, for your guest miners to get their full payout of bitcoin they have mined.

Set it to 1%, and 1 out of 100 of the shares they find, will be credited to you instead, randomly.

-- Smoov

Nah, they have to notify the customers of a change in the contract, which caps would be... otherwise, we'd be able to take them to court.

Even just having a note on one of the bills that they were going to change the terms, would suffice, but we got nothing.

Soo... we'll see...

-- Smoov

We haven't received any kind of notice of such a cap, and with the speed plan we have here, I'd hit that 250GB very very quickly.

Maybe, tho, because you're more rural than I...

-- Smoov

Maybe check on the # of connections you guys are allowing, both in p2pool, and in your daemons, and cut them down more.

That should drop the cumulative bandwidth used.

-- Smoov

ps: You have a data cap? ... Does the data cap only count on traffic that goes outside of our network? Do you get free in-network traffic?

When the coin comes in, would you mind posting that you received them, and that the balance you received, covers the balance of the outstanding accounts you have to be paid out?

I don't see where we need the number, but just an assurance that you have the full amount, so those of us who joined late, are reassured, that we're ok?

-- Smoov

He'd blame it on Bush anyways...

-- Smoov

You're showing something a little bit lower than your backbone.

Close tho...

-- Smoov

and you chose, not to include that tidbit of information during your ranting about this, for reasons that are kind of obvious now.

sorry, man, but you're just not high on the priority list. this isn't just a simple matter of you closing your account and he's late.

he threw you off of his service, and you'll get no special treatment to get the front of the line.

like I said in btc-e's chat, spite is a very powerful motivator, and it his time to give back what you've been giving him.

thanks for finally putting this whole thing into context.

-- Smoov

Why was the account closed?

-- Smoov

Sooooo, all we gotta do is round up everyone in that pic and waterboard them then... sounds doable...

-- Smoov

I would suggest sending one to forrestv (P2Pool developer) as well, since P2P<->ASIC/FPGA has their own issues as well, tho I suppose that concern could overlap with luke-jr's testing.

-- Smoov

Mine should be paid first. My name has more vowels than consonants in it.

-- Smoovious

Perhaps you should just put your foot down and not honor the so-called purchases which you cannot verify in the first place.

Whoever is on record with the account, is who they coin will go to, no exceptions. Otherwise? You're going to be in for a real hassle, especially if you end up being wrong and honor a 'purchase' that turned out to be false.

After all, you weren't a party of the so-called 'purchase' of the account, you are not bound by it.

-- Smoov

Just because pirate is shutting down doesn't mean he defaulted.

He announced the shut down, and if everyone gets back the coin they are owed, then it is a clean shutdown. No default.

-- Smoov

Well, IMHO, the overwhelming majority would be people who weren't early adopters when bitcoin came out in the first place, and so already have a negative attitude towards early adopters in general. It isn't based on any specific thing, but just the impression I get.

My choice is just to do FIFO, of whatever size. Picking 1/3 at random just doesn't seem right, but that wasn't your question.

As for small quantity vs large quantity, I suppose that would all depend on what you mean by small vs large to begin with. What you consider small, could be what I consider large, ya see... it doesn't mean anything because there is no frame of reference to what those terms are supposed to end up being.

If by small, you mean, the first week's worth of orders in the first 2/3 of your plan, then yeah, I'm cool with a small shipment... if by large, you mean, only the first 24 hours, then I hardly see what it matters.

If we had some idea of the first 1/3 would be the first week, or the first 4 days, or the first 8 hours, then we have something to work with. Even if it is only the roughest of estimates, it would give us an idea of what you're shooting for, and that's all I'm asking for.

Something like: We're shooting towards having all of the orders from the first 4 days going out at once, but we may end up only being able to send out the first day once we have an idea of how long assembly of each unit will ultimately take... etc

This would be something we can work with.

We know you're limited in what you can say, but please try and get someone to let you say enough of something to give a rough idea of what the goal is?

-- Smoov

edit: and I've firmed up what my issue with the random 1/3 is... if the first shipment amounts to roughly the first 24 hours of orders, or less, then the random third should still favor early orders. by early, I mean the first week, not the first month. the range of the random pick just seems too great, since it was sounding like the other 2/3 won't even exhaust the first day's worth of orders.

Alright...

the problem I'm having right now is the use of vague terms and applying numbers to them...  like...

If you ordered early then you have a good chance of being in the first 1/3, and if you ordered late, probably not, and having a 66% chance of being in the first part and blah blah blah

Ya gotta define what is "early" and what isn't, and when we're talking about chances and percentages, what are they based on? The first 100 confirmed/paid orders? The first 48 hours worth of orders?

What range are we talking about here, because as long as vague terms keep being thrown out there, yer not telling us anything, and we're left being just as uncertain as before, and talking about it did no good whatsoever.

I understand there is a certain amount of uncertainty about how many will actually be ready to go out, so, what is being projected to be the amount so far? And are we talking, for the 1/3, is that all orders, or is that a portion of Jalapenos, a portion of Singles, a portion of Minis?

Like... is the first shipment planned to be X Jalapenos, Y Singles, and Z Minis, and that first 1/3 would be taken from the earliest orders of each type until you fill up those numbers?

I put off ordering other hardware, and chose to put it into ordering a Jalapeno instead (which was literally, all of the bitcoin I had been able to mine with my very weak hashrate, for half a year), expecting that being so early in the pre-order, I would be among the first to get mine, giving me my first opportunity to do more than mine for dust. My order is on day #2... are you guys considering day #2 to be "late"?

What are you guys considering "early" and "late"? And, say I don't end up making it into the first shipment... how long until you start shipping more?

We're getting all the vagueness we can stand with our elections coming up in a few months... just be straight with us please.

-- Smoov

The API's capabilities expanded to full trading within the past week or two The page even shows how many bots/users are using the API.

They're working on notifications too... no email notifications yet, but judging from the labels in the options screen, it is coming.

And, Vircurex sends email notifications when your deposit hits, so, that's a plus for them also.

-- Smoov

BTC-e trades BTC/NMC and has an API

I believe Vircurex does as well.

-- Smoov