Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Use "free software" terminology consistently #249
Conversation
luke-jr
added some commits
Sep 18, 2013
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This one is too short. How about adding:
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I'd say let's not change this one for now. I generally try to avoid using "miners" except when required because it does not translate well and refers too much to "money issuance", which is not relevant on this context. Fraud detection isn't only required for high-value transactions, and I think the "no PCI" subject should be treated seperately. |
|
Fraud detection is often necessary for low-value transactions which are being accepted without confirmation. |
saivann
replied
Sep 20, 2013
|
OK I see what you mean. How about:
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Actually, I think this one should be rewritten. How about:
|
saivann
replied
Sep 20, 2013
|
This one puts a bit less emphasis on addresses.
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This one is hidden because the website is down since quite a while and maintaining the app seems to be their lowest priority. I'd say let's not change this one. I will simply drop it in a seperate commit. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Shouldn't it actually be "no web wallet service provides" ? |
|
Probably valid either way, but this sounds more natural IMO. |
saivann
replied
Sep 20, 2013
|
Fine then. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Not mentionning Bitcoin addresses makes the explanation incomplete. How about:
|
|
I don't think it does. Consider that users might use Bitcoin without ever seeing an address (payment protocol, QR codes, URIs, etc). |
saivann
replied
Sep 20, 2013
|
ACK on your version. I didn't think we were close to "obfuscate" the addresses anytime soon. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
A bit too long for the available space. However, if you just remove "their half of", it fits correctly. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
The "no PCI" subject could be treated seperately. |
|
Even if unnecessary, I don't think PCI compliance is on-topic here as a risk? |
saivann
replied
Sep 20, 2013
|
Well, I think it is. PCI compliance is a complex standard to manage that risk, so it's closely related. Let's handle this seperately so we can push other improvements. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Did you mean "Bitcoin programs"? |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
A bit too long for the available space, how about:
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I think we shouldn't say "specifically" there. Some legislation could indirectly make Bitcoin illegal (not by name) and yet there doesn't seem to be such case so far. |
|
A ban on all foreign currency would seem to indirectly make Bitcoin illegal? |
saivann
replied
Sep 20, 2013
|
The case of Argentina (as stated) is uncertain, indeed. But no new law have been passed against Bitcoin, virtual currencies, or some properties of virtual currencies. So, jurisprudence is missing there and could emerge over time. This text was reviewed and fixed by a law student so I would retain myself to change it except under the advise of someone in the fields. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Your version is better. Shouldn't we keep a mention about the requirement of a strong majority? How about:
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
An uppercase B is used in "Bitcoin mining" everywhere, but to me it seems that both a lowercase or uppercase b are possible (correct me if I'm wrong). So if this one needs to be fixed, it could be better to fix them all at once in a seperate commit. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I would prefer to stick to the language used by most Bitcoin clients here (6 confirmations and not 6 blocks). |
|
This kind of language leads to confusion when people assume it actually means confirmation. |
saivann
replied
Sep 20, 2013
|
I understand what you mean but I don't think this one is as much a problem, or that the suggested replacement is better. Better explaining the "6 or more confirmation" idea is enough IMO. Users already see multiple confirmations in their Bitcoin-Qt / BW4A UI with a friendly red-yellow-green or pizza circle for the first 6 confirmations. "Block" is a technical term that isn't found in the apps UI, so I think it's going to be confusing. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
A bit too long for the available space, just using "known as ASICs" instead of "known as Bitcoin mining ASICs" would do the trick. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
With the new FAQ and getting started page, I think this one should be shortened. How about:
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I'd prefer to keep "Balances" here. "Coins" don't translate well and it lets people think they have a coin in their computer. It is more accurate for them to think their wallet just show balances. |
|
But this isn't talking about their wallet, it's talking about the blockchain, which doesn't have balances. |
saivann
replied
Sep 20, 2013
|
Perhaps the associated text indeed isn't relevant enough with the title. We could say something like:
Bitcoins are transaction outputs stored in the block chain. The closest understandable word I see for this system is "Balances". The idea is to help people to understand that Bitcoin balances are stored remotely ( something anyone using online banking will understand ), and bitcoins are not like physical coins stored as files in a computer ( you cannot copy a coin, make safe offline transactions, etc ). The technical details about how these balances are named and managed in the block chain are better explained on the Wiki and Satoshi paper. |
|
But they're not stored as balances. If an analogy is needed, it would be coins in a safe deposit box. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Since you change this one, I would suggest to replace "shared public transaction log" by "shared public ledger". It seems the later is more used. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I think we should keep mentionning addresses here. Also perhaps we should be more specific and say "is usually confirmed by the network in the following ten minutes on average" rather than "in the following hour". |
|
All 3 mentions of addresses here are incorrect. It's an hour on average before the transaction is actually confirmed. |
saivann
replied
Sep 20, 2013
|
OK, let's hide addresses to the user here. However, let's use "usually start to receive confirmations by the network in the following minutes", otherwise there is many other places where this should be changed as well and as you pointed out earlier, it's up to each individual to define when they consider a transaction confirmed.
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This page is being rewritten, I will include your changes in the new version. Meanwhile, it's better not to ask translators to uselessly re-translate these strings if they are going to change a few weeks afterwhile. |
|
Translators don't need to re-translate this if they already got it right the first time... |
saivann
replied
Sep 20, 2013
|
ACK |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This page is being rewritten, I will include your changes in the new version. Meanwhile, it's better not to ask translators to uselessly re-translate these strings if they are going to change a few weeks afterwhile. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This page is being rewritten, I will include your changes in the new version. Meanwhile, it's better not to ask translators to uselessly re-translate these strings if they are going to change a few weeks afterwhile. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This advice is out of reach for many users. I suggest taking the best parts of both texts:
|
|
Out of reach or not, humans simply cannot generate strong passwords. Future wallet software should include passphrase generators (BIP 39). |
saivann
replied
Sep 20, 2013
|
Great. But until then, let's help all kind of users to choose stronger passwords and recommend password generators as the best solution. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
Little typo here I think. Similar to a physical address. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This one should be split in two paragraphs. I can take care of this once everything else is fixed. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I think we should not use the word block without explanation. How about:
|
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I think we should actually remove insistance on Bitcoin address but still mention them otherwise the text isn't very clear. How about:
|
|
Private keys have nothing to do with addresses, so any mention of them here is wrong. |
saivann
replied
Sep 20, 2013
|
ACK on your version |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I think we shouldn't change this one. |
|
It's not correct as-is. |
saivann
replied
Sep 20, 2013
|
Two fixes: matches the bitcoins being spent Otherwise, ACK on your version |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I'd say let's replace "coins" by "bitcoins" in this one, easier to translate and more consistent with the rest of the website. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
This page is being rewritten with the "Protect your privacy" page, I will include your changes in the new version. Meanwhile, it's better not to ask translators to uselessly re-translate these strings when they are going to change a few weeks afterwhile. |
saivann
commented on _translations/en.yml in 45f220b
Sep 19, 2013
|
I would prefer to stick to the language used by most Bitcoin clients here (6 confirmations and not 6 blocks). |
saivann
closed this
in
15e75cb
Sep 27, 2013
|
I think that your proposition makes sense. Though when it's unclear if we speak about the protocol or the software, I would use open-source by default. In most cases, the argument is that it's open (and auditable) and I think we should be careful with the word "free" (people shouldn't be left thinking that Bitcoin has anything to do with "free money" as in "free beer"). I just pushed a commit to fix this, please re-open the issue if you see anything else you think is worth additional changes. |
luke-jr commentedSep 18, 2013
Right now, there's a mix of open-source and free software.
I'm not sure this is a good solution as-is. Maybe we should use "open" for Bitcoin itself (protocols, etc), and "free software" when specifically talking about Bitcoin-Qt etc?