The problem is that when you close the main window, there is no other way of re-opening it than exiting the app (Cmd+Q) and relaunching it, i.e. reloading all the database just to have the main interface window open again.
Should I consider it as a bug/regression and report it? Are there other Mac users here who can confirm that I'm not the only one having this problem?
It doesn't happen a lot of for me, but sometimes, the developers aren't mac friendly so you kinda have to live with it. |
|
|
|
|
Mr. Real Bot
I never reveal my trade secrets.
|
|
|
|
@gweedo, @Wolf0, @paraipan
Do you actually fully understand seriousness of this situation ? Because I don't think you do.
Gavin and other devs either are or will be under enormous pressure when they manage a code that manages **1 billion of USD worth**. And it will only get worse as the market grows.
I surely know that i wouldn't merge just any code into the main branch if i was in his situation. Do you think anybody wants to be responsible for people losing hundered millions $$$ ? Nope, one does not.
Do you know that banks and large corporations, even today, use code that has been written 10, 20, 30 and MORE years ago ? Do you know why ? Because it just works.
So not only is the "slow way" the good way, but the ONLY ACCEPTABLE way. Keep all the new cool and funky stuff out of the mainline client, until there is absolute certanity that it is stable.
You didn't read my post or even understand it clearly. First off if they released better documentation then I think most companies would roll there own bitcoind, but today it is very hard to do that. So then Gavin is forcing us to use bitcoind and have code that is managing $1billion USD of worth. Why not put some of the pressure off to other developers. I mean bitcoin's core value is decentralized so this would only farther help it. Second I think you are wrong about the banks, I seen some bank backends and they are fairly modern to keep up with security breaches and combat cyber-attacks. So again another lie. Also when do we blame the core development team for issues? Never? I mean come on a Berkley configuration issue, and we blame the Berkley db? Come on WHEN DOES THE BLAME GO TO THE DEVELOPMENT TEAM? This is why issues will never be solved or have head way. |
|
|
|
Honestly the core developers view's are so different from real bitcoiners Please, explain the views of "real bitcoiners" Or at least tell me who real bitcoiners are if it's not the people that have been maintaining the code base for longer than most have even known of the existence of bitcoin. Or by "real bitcoiners" did you mean you? If that's the case, I can breathe a sigh of relief that the devs views differ. I define real bitcoiners as people who everyday are trying to push bitcoins, trying their hardest to make it stand out in the outside world. Just power users in the sense that everyday they are head deep in bitcoin 24/7. The core developers don't have time for that, or they say they don't. Views of those people are keeping these core values of bitcoin which I think each day, the core development team is moving farther and farther from some of them. With certain aspects of the where the client is going, you can see that views are changing to something that I find not what I would consider the official bitcoin client. Now I know everyone is going to say build your own then, I have tried and let me tell you it takes more time then I can spend doing it. There is no documentation and the little documentation is out dated. I recently tried again and I got some blocks to download when just connecting to my own bitcoind node, and no one else. They need to real start looking more like an open source team then a team that is hiding behind the foundation. I honestly can't believe the lead developer is head of the foundation, and 2 business that complement each other are together. So the views will never align with real bitcoiners, and I don't count newbies views, cause they are learning and sucking in information. When I was a newbie I didn't really form my opinion about things I just took the information researched it for validity and accepted it. Now I am very well informed and can my own opinions and know how everything works in the community. |
|
|
|
you could try wget -O - http://bitcoin-otc.com/otps/46ED38A2A668A578 | gpg -u "yourname" --decrypt
keep quotes and that is your where your name that you use to register on gribble Cause your the only one that is suppose to decrypt that it is encrypted using your public key. Thanks for your response. No luck unfortunately. Still the same error. gpg: decryption failed: No secret key I'm pretty sure hair-loss problem is in direct correlation with this here problem. Help me with this, cure my hairloss. PLEASE - It's cold. I don't want to be bald  - Thanks  Well then that means you gave a public key, that you don't have access too, and in that case, you can't be helped. |
|
|
|
...
Definately.
I personally, like the slower way better. I don't want to lose money because of a serious bug in the code. Do you, paraipan ?
I think this whole thread is therefore pointless. There are and there will be forks. There is armory. If the code is good enough, it will be merged into mainline. OR a lot of people will use it instead of the mainline client.
You can have either more features faster OR more stability faster. You can't have both at the same time.
I wont call names and keep calm. That's the whole point of this thread! We don't have stability because Gavin and team are focused on implementing stuff that breaks things, like continuously modifying the underlying protocol, instead of properly documenting it and improving the client on the user side. Who do you think it got the smart idea of increasing block size in the first place? Yeah you guessed it, it was Gaving. He told pool owners they can try raising the limits. What happened after that? You probably know, the blockchain split a few days ago. 1. The blockchain split was only mildly serious bug. AFAIK nobody lost their money. 2. The increase of block size was done to ensure scalability of the network ! So it is stability we are getting. 3. The problem existed not because of bug in Bitcoin, but because of bug in BerkeleyDB. Which was used by Satoshi himself, not by Gavin. 1) Actually some miners lost coins, and Gavin being the such the nice guy :/ gave them the coins to cover up his mistake (He should just done more testing) 2) Actually we aren't even hitting the current limit so they are just arbitrary upping the limit. 3) No, they didn't configure it correctly in bitcoin program, so cause Satoshi didn't see the limit getting hit by bitcoin blocks we should blame him LMAO. Gavin is maintaining it he should have seen it being hit WITH TEST. No test was performed. So that is completely 1000000000% Gavin's fault. Honestly the core developers view's are so different from real bitcoiners. It is impossible to run a full node with out aligning your views with them, thank god for armory for allowing me to continue to help the bitcoin network and be trust-less. |
|
|
|
OMG !
How to feed all these nerd-mules starving
in our backyard ?!
Maybe we'd shoot them down?
In the sake of humanity...
...From Bite_Happy's diary.
It is ok to be jealous of people that actually have skills that pay the bills, and you don't LMAO |
|
|
|
I have this site and domain that I am willing to sell, it is http://www.mapbin.org find your own hosting and I will help move everything. It was a college project last semester. I take any offer above 3 BTC Please PM |
|
|
|
Very nicely done! how to use cold storage.
If you do the cold storage make sure you talk about how powerful armory is and really explore those features cause some of the times the other amazing features get looked over. |
|
|
|
Bitcoin Foundation: The biggest future issue with bitcoin
It is already an issue... |
|
|
|
|
So now the gem game has evolved into a full on ponzi scheme LOL
|
|
|
|
|
There is a whitelisting sticky post in the newbie forum you need to write in that, but that doesn't mean it will happen...
|
|
|
|
http://techcrunch.com/2013/03/28/bitcoin-how-an-unregulated-decentralized-virtual-currency-just-became-a-billion-dollar-market/Hang around in the tech industry long enough and you or someone you know will be heard saying, “that’s so crazy it just might work.” Two years ago, if you’d told me that an open-source, P2P currency would soon be a thriving, billion-dollar market, I would’ve told you that you were on a lonely bus headed to CrazyTown, U.S.A. But today, Bitcoin officially became a crazy idea that’s actually working.
Today, all the Bitcoin in circulation — some 10.9 million of them — have collectively crossed the billion-dollar mark. As it is wont to do, the value of Bitcoin (and its exchange rate) has fluctuated wildly today. At one point, it hit a dollar value around $78, then pushed into the mid-nineties. As of this minute, it’s hovering around $90.
|
|
|
|
|
I already withdrew all my funds from Mt Gox, cause the trading lag was much that most the time my bot would just turn off. So what exchange is the most friendly for trading bots?
|
|
|
|
And no. After May 15 v0.6.2 is not safe to use.
But can I install the 8 version while still having the 6 version? Will there be any conflicts? shouldn't be since 0.6.2 and 8 use two different db to hold the blockchain. |
|
|
|
His friends know [gbg] as an aficionado of just about anything with a 6502 processor in it. He’s also interested in bitcoins. A while back, a friend asked if it would be possible to mine bitcoins with an old Nintendo Entertainment System. While this suggestion was made in jest, it’s not one of those ideas anyone can let go of easily. Yes, it is possible to mine bitcoins with an NES, and [gbg] is here to show us how.
http://hackaday.com/2013/03/25/mining-bitcoins-on-a-nintendo/ |
|
|
|
|
Show Posts
