So you started with a 5870, what happens if you put the 5850 in by itself?
|
|
|
Which SDK? Stock bioses on the gpus?
|
|
|
Open-source is not an easy concept to grasp. I'm sorry, but it's also not my fault.
Wow. Just when I thought it couldn't get any worse. Why you gotta be trolling this highly enlightened conversation?
|
|
|
No that there's much happening at the moment, but I will be unable to update the list for about a week. If anyone would like to keep a running list of updates that would be much appreciated.
I'll do it.
|
|
|
Frankly, I think Nefario's claim is a joke at best with nothing to back it up other than a coincidence.
While on the topic though, would it be possible to have the option to LOCK one's GPUMAX payout address in their control panel so that it can not be changed ?
My BTCGuild account has permanent payout addresses and people can login to it all they want, as the worst they can do is mine for me and make me more BTC...LOL
Until someone changes the backup pool and then sets your clients to mine offline only. Then you're mining for them.
|
|
|
At this point, this thread is a waste of time. I wish I could stop getting it to show up in my 'Show new replies to your posts." link.
|
|
|
How many of those users had bitcoinica accounts?
|
|
|
In the last 24 hours there have been two GLBSE accounts (that I know of) that have been cleared out.
The common theme between them is that both users had GPUMax accounts, with passwords that were either the same (as the GLBSE accounts password) or similar.
I emailed the GPUMax website yesterday (the email in their whois records as there isn't anything on the site) to inform them of this.
Since I've not seen any notice regarding GPUMax I feel that it is my responsibility to bring this to public attention.
If you have a GPUMax account it is highly likely that it's password has somehow been compromised.
If you use the same or a similar password elsewhere (GLBSE, MtGox, Email whatever) please change them now.
If you are a GLBSE user I would encourage you to use two-factor authentication, there have already been over 3 accounts which have been protected by this.
Nefario.
If the people used the same or similar password on 2 sites, isn't it reasonable to expect that they used it on other sites as well?
|
|
|
I am not sure 3 dual GPU cards can run on Windows.
you can run up to 8 GPU cores, so 4 dual cards. Really?? I always had trouble with more than 5 GPUs. Could never get three 5970s working together. The 8 gpu cores is a driver limit put in place by AMD. Some people have had limited success in linux using virtualization to bypass, but yes, it is possible.
|
|
|
I did sign up for ripple a while back when someone mentioned it, but its mainly sat idle. I was curious as to how you were thinking a person or persons would set it up as an insurance. Could you give some more details?
|
|
|
The OTC WOT is essential a p2p trust system. It allows you to see passive/level 2 trust between parties with no direct trust connection, very similar to ripple. Have you seen that?
OTC isn't p2p, all the information is held in a central server, ripple is a client/node to be true p2p service They are actually working on a distributed version now. Are there any links to any for that? or it is just irc talk? Cause that sounds interesting You'd have to talk to nanotube from irc for more details because I've not been active in there for a bit, but the topic link is http://privwiki.dreamhosters.com/wiki/Distributed_Web_of_Trust_Proposal_2
|
|
|
The OTC WOT is essential a p2p trust system. It allows you to see passive/level 2 trust between parties with no direct trust connection, very similar to ripple. Have you seen that?
OTC isn't p2p, all the information is held in a central server, ripple is a client/node to be true p2p service They are actually working on a distributed version now.
|
|
|
The OTC WOT is essential a p2p trust system. It allows you to see passive/level 2 trust between parties with no direct trust connection, very similar to ripple. Have you seen that?
|
|
|
Updated opportunity and availability. This isn't a Pirate Passthrough. See my PPT offering on GLBSE if you're interested in passthrough.
|
|
|
It feels as though you've flipflopped on the arguments.. What exactly is your point again?
|
|
|
I am not sure 3 dual GPU cards can run on Windows.
you can run up to 8 GPU cores, so 4 dual cards.
|
|
|
My approach for a long time has been to diversify my portfolio (a point Colbee seems to think is a stupid approach in another thread), so I have lots of different investments (active and passive) around bitcoin-land. Current BS&T exposure is 20%.
You misunderstood me. I don't think diversifying is stupid. I actually fully diversify mine also. I was just saying that your exposure to PPT is the same as your exposure to BS&T, because the risk scenario is the same. If pirate defaults, you lose both your BS&T deposits and your PPT insurance fund. So if for example your exposure to PPT is also 20%, effectively 40% of your portfolio is at risk of pirate defaulting. Assuming, of course, that PPT is equal in size to his other investments.
|
|
|
As a related side note...
At some point it will really not be very truthful to refer to Bitcoin as a 'p2p' solution. It is on a trajectory which makes Bitcoin not much more 'peer to peer' than Visa, PayPal, etc (assuming they have some amount of clustering and redundancy.)
I'm begining to suspect that you do not understand how bitcoin actually works, what decentralization means in the context of economic science, nor what it means to be a 'peer'. When I log on to my Wells-Fargo account to transfer funds, is my computer a 'peer' to Wells's machines? Until recently I did all my work on a machine which contained an up-to-date block chain and which I owned and controlled fully. At that time I considered my presence in relationship to other participants in the economy as one of a 'peer', and I interacted with other participants directly (the '2' part) though I did rely on global network infrastructure which I pay a third party to provide. _This_ is the archietecture which was described in most of the documentation related to Bitcoin, at least at the time I studied it significant. As importantly, _this_ is one the aspect of Bitcoin which appealed to me the most about the solution. and that's how it continues to be. The people running lightweight clients CHOSE to run them. Nobody forced them to run the lightweight clients.
|
|
|
I tried to quote you, but all that came up was: BLAH BLAH BLAH
|
|
|
There's also a #bitcoin-escrow channel on Freenode IRC with well established users providing escrow for anyone requiring said services.
|
|
|
|