WHY would they want to understand that? Either they are very interested and put some of their brain capacity into learning it (geek out), or they don't. Either way, they're not hurt right? Specialization is a good thing in this complex world. I wouldn't know where to start implanting organs, and if I spent my time learning that (if I could at all) then I cannot spend that time into learning to write better software. So we have this thing called trade... and hey, we're on the bitcoin forums, our aim is to make that easier  John, reading through the wiki is not easy. You read an article which mentions say 30 geeky terms like ''JSON-RPC API''. Shit, then you spend 2 hours understanding these terms. But to understand these terms you have to dig deeper. I can understand wiki should work this way, but at least there should be an easy to understand Bitcoin-Qt documentation for grandmas / surgeons / movie makers / non-geeks written in easy English. |
|
|
|
... yeah I'm pretty sure a surgeon doesn't need to know about rawtransactions unless he's had a change of heart and is looking for a career change ... what's your real point here?
My point is: not everybody who doesn't understand intricacies of Bitcoin and / or is unwilling to learn this not-easy-stuff should be labelled ''stupid''. |
|
|
|
When a developer feels like implementing it and has time to do it. There is not really a timeline as we're working on this on our spare time. All help is appreciated. I write song lyrics, movie dialogues, etc. Using Excel overwhelms my circuits. I can't help  Maybe we could have an auction of feature requests in which Bitcoin-Qt user would commit to pay and pay the developers for speeding up certain features? - Just an idea. The feature requests that get the most funding would be considered the most desired. Market decides. |
|
|
|
... they do not want to learn then?
I have a colleague who is a surgeon + researcher on 3D printed organs. He makes magical stuff and is definitely not stupid. He works 16h a day. He could devote 1 hour a week to learn bitcoin. Imagine him trying to understand what raw transactions are: https://en.bitcoin.it/wiki/Raw_TransactionsPeople want to learn, but the stuff is described in a way too hard for non-geeks to understand within their lifetime. |
|
|
|
It will support "sweep", ie, "send me all coins from this private key", without adding the key to the wallet. This ''sweep'' feature is nice. Do you have an idea when it might be implemented? This is superior for all cases that involve paper wallets, as unlike a naive "add to wallet" it does not encourage keys to exist in multiple places, potentially leading to all kinds of problems for the unaware. My guess is that a natively supported import of private keys in Armory also potentially leads to existing private keys in multiple places? |
|
|
|
Solution: if you need paper wallets, use a client that supports this natively, such as Armory.
Do not tell non-technical people to mess around with individual private/public keys in Bitcoin-Qt. NEVER. I do not need it. Importing private key was just an example of how ''grandmas'' or ''the stupid'' will think. BTW, is there a reason why Bitcoin-Qt would not support (in future) a native feature of private key importing? |
|
|
|
No, grandma must understand public key and private key, there is no way to jump over this fundamental mechanism of cryptography  Grandmas will have no problem with understanding a public key, a private key and a wallet. Grandmas will have problem understanding ''importing a private key'', ''dumping private key''. Imagine the following situation: Grandson: Dear, this is a paper wallet for you. Factually a paper wallet is a piece of paper with toner on it. Grandma: Fantastic. I can pay for my new jaw now. Grandson: But before you pay you must first import the key printed on this piece of paper into Bitcoin-Qt Grandma: But I am not in an import-export business, I do not want to import anything. Besides I already have the private key. It would make a better sense if I export what I already have rather than import what I already have, right? Grandson: You stupid woman. Just type your private key into Bitcoin-Qt. Grandma: Why didn't you simply say I need to type it. Why so sophisticated words for an action that even stone age people could perform? BTW, wouldn't it be much more convenient for me in 21. century to tell Bitcoin-Qt what I want to do, e.g. if I want to make a payment I simply click ''make the payment'', then Bitcoin-Qt asks ''from available funds or from a paper wallet?'', if I click ''from a paper wallet'', then Bitcoin-Qt just prompts me to type the private key? On the other hand, must I remember all these bad grammar phrases like ''importprivkey''? Grandson: It's for your own good that you learn new stuff, you silly. Be more geeky. |
|
|
|
pretty much all of my friends have no desire to use bitcoin when I try to explain it to them and they tend to just have a blank stare on their face.
... consider that maybe you are hanging out with stupid people? Come on... being IT-not-gifted does not equal being stupid. His friends may very well be great musicians, dancers, writers. How would you react when labelled stupid for your potential poor musical, dancing or writing skills? |
|
|
|
|
1. Is it xls, txt, other file type?
2. Can you post first line of the tick data? - I just need to know
a) if it is just separated by a coma (as CSV would imply) or by e.g. tabs.
b) the date and time format
Thanks
|
|
|
|
One of the big barriers with Bitcoin is that the majority of its users and developers are, to put it bluntly, ignorant computer nerds. They are extremely smart, yet completely ignorant to what the average person is capable of (no offense, its an impairment of social interaction and nothing to be ashamed of!) .
I believe if you can make it simple enough that even Grandma can use it, then you are opening up some pretty big fucking doors for Bitcoin.
So what's next in the simplification of Bitcoin?
What is next simplification? Simplify the use of Bitcoin-Qt. Translate DOS-like commands in Console into idiot-proof dialogue windows for grandmas and non-geeks so that they could too make benefit of Bitcoin-Qt's capabilities: https://bitcointalk.org/index.php?topic=198389.0 |
|
|
|
Also, you're going to need a better example than "listreceivedbyaddress" because all of its functionality is already provided in the transactions tab.
importprivkey <bitcoinprivkey> [label] [rescan=true] Is this one okay? |
|
|
|
Sure, and more will be added in the future— but _just_ putting a dialog on something doesn't make it user-friendly, sometimes it gives the appearance of friendliness and safety even when it isn't. gmaxwell, just think how much peoples' money would have been saved if there had been an ''Action'' tab with a command e.g. ''Show all addresses that have money''. Newbies wouldn't have thought they were robbed (change addresses). Wouldn't you consider it a safety improvement? Part of the reason the gui-console exists is so that we can expose functionality for developers and power-users for things like debugging/troubleshooting and emergency recovery ... as well as things that aren't quite ready for primetime or are dangerous if you don't understand them. People will understand, if there is easy-to-understand non-techie documentation. They are smart creatures My hope is Bitcoin will go mainstream one day and majority of users will be non-geeks. Non-geeks need an easy-to-operate interface. I have zero knowledge of computers - I write song lyrics for living (not in English) and I find it very hard to make use of even basic operations of Bitcoin-Qt (Shit I am even afraid to use it - there are valuable functionalities, but I am afraid to make a typo in command and blow up the computer). Very soon the forum will be flooded with non-techies like me asking tons of unnecessary questions that noone will have time to answer. When something doesn't have a GUI it's not because anyone is unaware that a GUI interface is useful, it's because the feature not ready for the general public, not intended for normal users, or because someone hasn't gotten around to it. I wasn't aware of this. Thank you. |
|
|
|
however, the debug console is meant for developers, not non-technical users Yes. It is definitely not for non-technical users. So making it more user friendly is not really a priority If there ever comes time that developers have nothing to do (in two or three years from now) maybe they could consider it, I hope. and can even be contra-productive, as we'll get more reports of clueless users messing up by entering random commands. John, I disagree. How many times did you mistake ''Warn me when closing multiple tabs'' with ''Block Pop-up Windows'' in your Firefox? Never. Now, how many times did you make a typo in your command or put space instead of a bracket or a comma? I would argue that dialogue windows lower the risk of using commands (compared to using them from console). Implementing dialogue windows for commands and their inputs would add-value Bitcoin-Qt. There are already dialogue windows for some actions like interface language change or transaction fee amount setting. Why not extending this practical approach to other aspects of using Bitcoin-Qt in the future? |
|
|
|
The weak link is the browser. You're being sent javascript and having the browser execute it - sight unseen.
Is biaddress.org service of generating keys and addresses safe then? You are using their java app that uses a browser, aren't you? |
|
|
|
Now I understand. Many thanks. |
|
|
|
From what I understand to get into ripple trading business I first need to buy 100 Ripples from someone. According to this http://www.bitcoincharts.com/charts/rippleUSD#rg30zig6-hourztgSzm1g10zm2g25zi1gVol 1 ripple = $120. So first I need to find someone who owns ripples and pay him $12,000 to be able to open a wallet at ripple.com, correct? I then after I am accepted (with my 100 ripples currently worth $12,000) I can start trading ripples internally within the peer network? I am sorry my English is not very good. Can someone confirm I am correct on this please? Thank you. |
|
|
|
1. There is a website https://github.com/bitcoin/bitcoin/issues?milestone=11&state=open where people submit: a) information on bugs (for fixing), and b) feature requests (for increasing efficiency and expanding user experience). 2. I am not sure, but I seems only a few and experienced experts can post there. They have the necessary technical knowledge and jargon to describe what they want. 3. How about a thread for non-techies in which feature requests might be submitted? 4. My feature request is: PLEASE move / duplicate the commands that are available after typing in ''help'' (in Help tab -> Debug window) to a new tab called e.g. ''Action''. The commands should be available in this tab in a scroll down like fashion. The rationale for this feature request is this: why should one type long commands like ''listreceivedbyaddress'' or remember to use a square brackets or know where to put a comma, if one can simply click the command name and insert the necessary values in a dialogue window? It would be much simpler and time-and-nerve-saving for non-technical users. For easier use (because the number of commands is considerable and will probably grow) the commands can be grouped somehow, e.g. a) into the ones requiring and not requiring a wallet opening, or b) into the ones that are for wallet management / transaction management, etc. 5. I do realize that I request for bells and whistles, especially given the early stage of Bitcoin-Qt's development (I know developers have other important stuff to code), so please do not rant about my post. I am just a newbie who would like this client to be more user friendly. What do you think about this feature request? Thanks |
|
|
|
|
Nancarrow, Justusranvier, Itchthyo,
Just to clarify, I wasn't ranting, nor was I taking the opposite position to anybody. I just asked a few questions.
I think asking questions while being a newbie is better than being ignorant.
|
|
|
|
2. Couldn't devs spend their valuable time on providing upgrades with non-controvertial features?
Who determines what is non-controversial? You just make an observation: - if you there are zero people ranting about a certain modification then the issue is non-controversial; - if there are people ranting, then it's controversial. |
|
|
|
|
Show Posts
