Hi,
just checked out the link on sourceforge but the mac version seems to be still 0.3.23 , right?
Or is just the file named wrongly?
Thanks!
Topic: Bitcoin version 0.3.24 released - page 4. (Read 23283 times)
Can we have an option to change the language on the fly please? I am on a Chinese language windows7 system, so all my Chinese software would work flawlessly, but I prefer my English software to be actually in English, because the translation is often horrid(and the Chinese translation for bitcoin client is really confusing). Right now, I delete the zh_cn folder, each time the program updates, and it's a chore.
Have you considered submitting better translations?
Can we have an option to change the language on the fly please? I am on a Chinese language windows7 system, so all my Chinese software would work flawlessly, but I prefer my English software to be actually in English, because the translation is often horrid(and the Chinese translation for bitcoin client is really confusing). Right now, I delete the zh_cn folder, each time the program updates, and it's a chore.
There's nobody to whom "the greed" could "get".
Certainly there is. Mining pools currently get 50 BTC for every block plus total transaction fees for that same block. For many of them transaction fees are the only revenue source. The minimum transaction fee effectively is a mining pool 'tax' for all network users. I understand the need to protect against DoS attacks. However, what is the point of protecting against an attack if there is no attack? If you're not flexible, always keeping your shield charged to the maximum, it is just a waste of resources!The minimum transaction fee should be a dynamically defined variable by the system. Its value must depend on
I dont know where bugreports is collected, so i post it here
We use github, put in a bug at https://github.com/bitcoin/bitcoin/issues/395. If someone can translate to russian, that is what would be needed here.I'm not on github so will post translation here
Open Bitcoin - Открыть Bitcoin (Биткоин), this one is right
Send Bitcoins - Отправить Bitcoins (Биткоины)
In parenthesis singular and plural word Bitcoin in case it's needed
I dont know where bugreports is collected, so i post it here
We use github, put in a bug at https://github.com/bitcoin/bitcoin/issues/395. If someone can translate to russian, that is what would be needed here. Is there some gpg signature to verify the integrity of the files?
Yes. See the original post in this thread.
Is there some gpg signature to verify the integrity of the files?
Please make this thread sticky until the next version and keep repeating that
There is so much traffic now many people might not see this thread.
There is so much traffic now many people might not see this thread.
I dont know where bugreports is collected, so i post it here
#: ../../../src/ui.cpp:2681
msgid "&Open Bitcoin"
msgstr "&Открыть Bitcoin"
#: ../../../src/ui.cpp:2682
msgid "&Send Bitcoins"
msgstr "&Открыть Bitcoin" <-- error
#: ../../../src/ui.cpp:2681
msgid "&Open Bitcoin"
msgstr "&Открыть Bitcoin"
#: ../../../src/ui.cpp:2682
msgid "&Send Bitcoins"
msgstr "&Открыть Bitcoin" <-- error
Basically this screen shows "Open Bitcoin" two times where it should be Open Bitcoin and Send Bitcoins in RU
I dont know where bugreports is collected, so i post it here
#: ../../../src/ui.cpp:2681
msgid "&Open Bitcoin"
msgstr "&Открыть Bitcoin"
#: ../../../src/ui.cpp:2682
msgid "&Send Bitcoins"
msgstr "&Открыть Bitcoin" <-- error
#: ../../../src/ui.cpp:2681
msgid "&Open Bitcoin"
msgstr "&Открыть Bitcoin"
#: ../../../src/ui.cpp:2682
msgid "&Send Bitcoins"
msgstr "&Открыть Bitcoin" <-- error
These installs seem to be getting more complex. I'll stick with 0.3.21. 
WTF? Does it still ask you for ridiculous fees?
When I got into bitcoin, a major selling point was "no fees". I guess the greed got to them.
LOL, I know it shouldn't be necessary to understand all the inner workings of the Bitcoin concept in order to use it, but this statement is pretty hilarious in light of the facts. There's nobody to whom "the greed" could "get". The fees are an optional feature (i.e. you can still send transactions without them) with three related functions:
- DoS prevention
- incentivizing mining
- transaction priority management
The fees get paid to the miners who process your transaction, not "the man".
For those of you who (1) can't wait for a Mac build, (2) trust a random stranger on the Internet to provide you with their copy of Bitcoin, (3) want the changes I've made to Bitcoin (Which I hope is setting required transaction fee to 0 for creating transactions and relaying), and (4) use a 64-bit Snow Leopard system, I've posted my build up at http://dl.dropbox.com/u/16187822/Bitcoin-0.3.24-pc.dmg. I highly suspect that I'm the only person who wants this, but who knows?
MD5(Bitcoin-0.3.24-pc.dmg)= 6a55039636266301b445638c55fcacb3
SHA1(Bitcoin-0.3.24-pc.dmg)= 288493d1986f50cd0be7b0bbb1377dc103a8ca18
SHA256(Bitcoin-0.3.24-pc.dmg)= 89462c2889b76627e143caa974d13bffaf5c8bb59995d700538852ed430548cd
MD5(Bitcoin-0.3.24-pc.dmg)= 6a55039636266301b445638c55fcacb3
SHA1(Bitcoin-0.3.24-pc.dmg)= 288493d1986f50cd0be7b0bbb1377dc103a8ca18
SHA256(Bitcoin-0.3.24-pc.dmg)= 89462c2889b76627e143caa974d13bffaf5c8bb59995d700538852ed430548cd
While I appreciate the effort... I'm afraid I don't qualify for #1 or #2.
Thanks for posting it for others though
For those of you who (1) can't wait for a Mac build, (2) trust a random stranger on the Internet to provide you with their copy of Bitcoin, (3) want the changes I've made to Bitcoin (Which I hope is setting required transaction fee to 0 for creating transactions and relaying), and (4) use a 64-bit Snow Leopard system, I've posted my build up at http://dl.dropbox.com/u/16187822/Bitcoin-0.3.24-pc.dmg. I highly suspect that I'm the only person who wants this, but who knows?
MD5(Bitcoin-0.3.24-pc.dmg)= 6a55039636266301b445638c55fcacb3
SHA1(Bitcoin-0.3.24-pc.dmg)= 288493d1986f50cd0be7b0bbb1377dc103a8ca18
SHA256(Bitcoin-0.3.24-pc.dmg)= 89462c2889b76627e143caa974d13bffaf5c8bb59995d700538852ed430548cd
MD5(Bitcoin-0.3.24-pc.dmg)= 6a55039636266301b445638c55fcacb3
SHA1(Bitcoin-0.3.24-pc.dmg)= 288493d1986f50cd0be7b0bbb1377dc103a8ca18
SHA256(Bitcoin-0.3.24-pc.dmg)= 89462c2889b76627e143caa974d13bffaf5c8bb59995d700538852ed430548cd
I won't demand a release just for that I'm well aware that it's EOL, but well, it's running on that one machine just fine. It's just on to run a bunch of services 24/7; nobody really uses it for browsing. It looked like a pretty simple fix, that's why I suggested adding it.
Well, I tried, Ill try again with 0.4, if you are willing, PM me and Ill churn out a couple more builds for you to test so that its for sure fixed in 0.4. I'm well aware that it's EOL, but well, it's running on that one machine just fine. It's just on to run a bunch of services 24/7; nobody really uses it for browsing. It looked like a pretty simple fix, that's why I suggested adding it.What kind of error message?
The one here: http://forum.bitcoin.org/index.php?topic=24841.msg323892#msg323892Very, very odd. I guess I'll stop including that file and see if 0.4 works. I really don't get why including that file does not work, but not including it does, but only on RC1 and I really dont feel like digging through MinGW headers to find out. I don't think its nearly worth a 0.3.24.1 just to support Windows 2000, as you shouldn't be using a EOL OS ever (if you even remotely care about security).
I won't demand a release just for that I'm well aware that it's EOL, but well, it's running on that one machine just fine. It's just on to run a bunch of services 24/7; nobody really uses it for browsing. It looked like a pretty simple fix, that's why I suggested adding it.Wait, it worked in RC1 but not RC3? RC1 did not have the fix applied. RC3 (which is the same build as final, aside from some translations) did.
Well, I tested RC1 and it started without any problems.Now I tried the final and I got the error message.
Out of curiosity, I also tried RC3 which failed too.
Wait, it worked in RC1 but not RC3? RC1 did not have the fix applied. RC3 (which is the same build as final, aside from some translations) did.
Well, I tested RC1 and it started without any problems.Now I tried the final and I got the error message.
Out of curiosity, I also tried RC3 which failed too.
What kind of error message?
Wait, it worked in RC1 but not RC3? RC1 did not have the fix applied. RC3 (which is the same build as final, aside from some translations) did.
Well, I tested RC1 and it started without any problems.Now I tried the final and I got the error message.
Out of curiosity, I also tried RC3 which failed too.
Smooth install, noticeable improvements. Great work!
Patiently anticipating the wallet encryption patch, if its implemented right it will be a excellent addition.
Patiently anticipating the wallet encryption patch, if its implemented right it will be a excellent addition.
Jump to: