|
Please post once the Farsi bounties have been paid. If it worked well, I will contribute more to other languages.
|
|
|
|
And another bet that can be closed  No seriously, this is bad news for bitcoin  Had hoped to raise some funds there myself. No explanations and some nameless "GLBSE treasurer" … doesn't mean they pull a "we got robbed" like so many before. Either way sad story. |
|
|
|
Jim how do you treat the questions of quality and word length? I could easily contribute by picking all the one word "phrases" and auto-translate by google. Actually I have a project where I got community help and me doing google-translations in an attempt to help my contributors lead to my (=maintainer) translations overruling the native speaker's correction on getlocalization having me to up-vote their correction manually. Anyway, as long as contributors don't complain about to much work or unfair rules I highly welcome Jim's attempt to reach for the white spots and hope for other projects to follow (or be more aggressive about their localisation attempts)  |
|
|
|
|
I'm slightly disappointed of the speech.
The gun-print-example is not intriguing for this audience. Printing nutrition is maybe the last thing people will want and 3d-printers will be used to do. The ship cities hosting country-size populations are a far fetched utopia.
I don't want to argue about this all being available some day in the future and it all to be very cool stuff but bitcoin is now and very real already but this story at least for me you spoiled by claiming all you have to do in order to sell flutes around the world is accept bitcoins with no costs involved. What's the price of such a flute? Assume people would pay 20x that price in other countries. Would that cover for the shipping overhead? I doubt that.
|
|
|
|
Ƀ really doesn't look like a bad choice. I never liked the color scheme people advertise with it, but the symbol seems perfect.
I'm not against Ƀ neither. It's my preference. I'm just saying that even the $ sign would be fine with me if the majority here wishes to use it. I just don't like to not have an agreement that I can push on Wikipedia or other pages. I'm pretty sure that a consensus would rule out … I like it too, and about the criticism that it looks almost like the number 8, maybe serifs should be added, like:
… custom solutions and symbols that just render badly on 50% of all computers. |
|
|
|
Hi There! I was wondering if anyone could point me in the right direction so I may once again trade Bitcoins in Chile. I was regular user of the now defunct TradeHill and like many others I was left without a reliable exchange to have some bitcoin fun.  Perhaps some chilean user has Bitcoins for sale? Or an easy way to transfer money from Chile to MtGox? thanks everyone Yo tengo BTC para vender en Chile... Si te interesa, x MP S2 Are you in the Santiago/Viña corner of Chile? Registered on bitcoinary and localbitcoins? If BTC drops further I might contact you. Else I might be interested in selling in 2 weeks again. |
|
|
|
Is the "TC" supposed to actually be invisible? I see it as "B⃦TC"
Sounds like your browser is ignoring parts of my webfont, likely in violation of standards. Anyone know how to fix this? Hey don't tell me there are browsers that violate standards!!!!1!! I guess using Ƀ could fix that issue. Ok, you made that font with T and C having 0pt/px/cm width. Can you try 1px instead? My guess is that konqueror tries to fix missing letters and a 1px letter would most likely not trigger such a "fix" but with the letter being invisible it would still yield almost the same result. And please while you are at it, un-bold it |
|
|
|
This is a bad idea, because the browser isn't guaranteed to copy the invisible TC.
Are you sure? The characters are "visible", but the font defines them to have zero width. Is the "TC" supposed to actually be invisible? I see it as "B⃦TC" (Ok, seriously, are you talking about this: BTC? So either it should load the Webfont resulting in BTC being displayed as "B with decoration", "invisible T", "invisible C" or your w3c/lynx on a non-unicode console should just display BTC … or your smart browser decides that there is something wrong with letters that have zero width so it defaults to another font. Which browser are you using?) "B⃦TC" is shown by Konqueror/KHTML, Rekonq, and QupZilla. "B⃦" alone is shown by Chromium and Firefox. Konqueror displays ฿ and Ƀ right but I have the same problem with BTC. Interesting. For me, it's really narrowing down to either ฿ or Ƀ then. |
|
|
|
This is a bad idea, because the browser isn't guaranteed to copy the invisible TC.
Are you sure? The characters are "visible", but the font defines them to have zero width. Is the "TC" supposed to actually be invisible? I see it as "B⃦TC" Then there is something wrong with your system. Here on my standard Windows 7 64bit with 8GB RAM it displays just fine. (Ok, seriously, are you talking about this: BTC? So either it should load the Webfont resulting in BTC being displayed as "B with decoration", "invisible T", "invisible C" or your w3c/lynx on a non-unicode console should just display BTC … or your smart browser decides that there is something wrong with letters that have zero width so it defaults to another font. Which browser are you using?) |
|
|
|
Anyways, we generally use the Thai Baht for Bitcoins, right?
฿ <- that right there
Please, whatever the heck you use as a symbol for Bitcoin, DON'T PICK SOMETHING ALREADY IN USE FOR A CURRENCY. Such an ambiguous symbol is a horrible choice! Please come to your senses and STOP USING IT.There's no value in a consensus that's reached with brains off. Use the @ for all I care, BTC is fine, so are Unicode hacks, just not something that's asking for trouble! I'm going to put this in my sig for a bit, just to make a point. Wow! Calm down! There are many contracts done in Dollar, Peso, Brazilian real, Nicaraguan córdoba, Tongan paʻanga, Cape Verdean escudo, Portuguese escudo and none of the involved countries ever got any of the others into legal trouble about the $ sign. $ (disambiguation) |
|
|
|
Ok, so what happened? I saw a 5kɃ wall at $13. According to this, not all got bought up. 5kɃ are now waiting at $13.09. The market depth looked more or less symmetric. Now the Ƀ-side is more or less unchanged. It barely moved down but the $-side vanished. I'm not a day-trader and do one buy/sell every 2 months but I'd like to know what the majority of the market depth consists of. Are those people continuously changing their offers? Bots doing this for them speculating on the chart history/market depth? Arbitrage bots? Or is the majority people like me that buy when they want Ƀ and sell when they want $ for the days/weeks to come? With the huge gap now I feel like it's not speculation bots quickly deciding on a new price but people that wait to see where the journey is going. Are there any insights on transactions per user on Gox? Like a chart listing the activity of the 5% most active, … users? |
|
|
|
Ok, sent 1BTC. I'm curious why do you send to "the first non-bounty output" rather than "the first input"? The inputs are save to use while the outputs (you even acknowledge that there could be more than 2 outputs) could be some other bills paid aka not in the senders possession.
Thanks! I think it is a matter of "one transaction's output is the next ones input" so perhaps I was not clear enough. What I mean is: Person X sends 5 BTC to the donation address. Say the transaction that does this consumes the following existing transaction outputs to make up the 5 BTC. Transaction T1, outpoint 1, that was sent to address A1, value 1 BTC Transaction T2, outpoint 2, that was sent to address A2, value 2 BTC Transaction T3, outpoint 1, that was sent to address A3, value 3 BTC (There will be change of 1 BTC going somewhere but that is unimportant here.). By the "small print" rule, the first output consumed by the sending transaction is "Transaction T1, outpoint 1". This is controlled by the key to address A1 which the user should have as long as it is not a green address. They should have it as they signed the transaction to send the value to the donation address. The change will go there. Edit: to give a concrete example, the transaction that you just sent to the donation address is as follows: 04ec2eb732050e792b081bb7977038a13c5e3242b67ef158cc80dadc2192d6b8:
from 127dvNfYuQa8xLYco8d8zZ62a8uGiYVuM8 / outpoint 5d4131d4ec4da2409b3e29640a723303b8684144e1efaaec973350e40f9e53a2:0
to 1DBjxbagbuy6tyV8rH9mqM5UGepGVhjn9a 4.29 BTC
to 1K6EJJYftWNyhre3codjT4jWyczrdRVG1n 1.00 BTC Any refund would go to 127dvNfYuQa8xLYco8d8zZ62a8uGiYVuM8 Ok, so while I still have difficulties understanding your wording, this example definitely is clearer. The other example apparently was a bitcoin spinner with the only input address also being the return address. |
|
|
|
Hi giszmo, I have added a 'Small print' section to the bounty as follows: ---------------------------------------------------- Small print: 1) If the bounty is not claimed, BTC will be returned within 7 days of the bounty end to the address of the first transaction output consumed by the sending transaction. (This means you should send it from an address you definitely control i.e. no green addresses). 2) Any BTC sent to the bounty address after the end of the bounty will be transferred to the general MultiBit donation address. ---------------------------------------------------- What I mean by this is, if you look at the very first transaction sent to that address it is: 1865474a418491fdc903f1934e2c93a30bfcaf572f462e2b9120ac6de3b009ae:
from 12F8uztWoQQRPuZ7XPSnYDkKJ5MnvQZuwC / outpoint 251b28ab6ab8035bb02e846297594fc31272544f110c49ec351a2f4468346ca4:1
to 1K6EJJYftWNyhre3codjT4jWyczrdRVG1n 0.10 BTC
to 12F8uztWoQQRPuZ7XPSnYDkKJ5MnvQZuwC 0.24 BTC A refund would be sent to: 12F8uztWoQQRPuZ7XPSnYDkKJ5MnvQZuwC Ok, sent 1BTC. I'm curious why do you send to "the first non-bounty output" rather than "the first input"? The inputs are save to use while the outputs (you even acknowledge that there could be more than 2 outputs) could be some other bills paid aka not in the senders possession. |
|
|
|
I have set up a bounty address for anyone who would like to contribute to the Farsi/ Persian translation of MultiBit. The bounty address is: 1K6EJJYftWNyhre3codjT4jWyczrdRVG1n Or, as a QR code:  The terms of the bounty I have added to: http://multibit.org/ (below the screenshots) Could you please state what will happen if the bounty does not get claimed? I will send my Ƀ if I get it back rather than it being sent to your wallet for simplicity. Also please blockchaininfofy your Ƀ address above. |
|
|
|
2) Probably among the very first handful of users on a freshly born service would be someone doing something naughty. I've read of the cops kicking in the doors of people for not setting a password on their wi-fi. The chief difference between some careless and clueless user like this and someone selling network connectivity and not being able to produce a 'customer list' would probably be a stay in jail.
Maybe over in the USA. Running a TOR exit node gets you the same kind of attention without actually ending up in jail but you will have to explain TOR to many people over and over again. At least that's how things work in Germany and with an open wifi you can also stay out of jail but might get some stress along the way. |
|
|
|
The B double vertical strokes is a Unicode symbol? What is its code? I can't find it on any list of Unicode symbols (maybe I'm not looking in the right place?). Yep. Unicode defines symbols like this using "combining" characters (the "already combined" characters exist only for compatibility with legacy encodings such as Latin-1), so for B⃦ you do: This works to some extent for all possible combinations (apparently some people are getting blocks, though?). From there, fonts can specialize with "ligatures" (renderings that represent a sequence of characters) - which is where things can definitely use improvement. Ok, so now I know why it looks shitty on my and many other systems. The vertical strokes are in different places depending on the program I use. In my chromium browser they are too far right and in gedit they are in addition to far right too short. Knowing it is actually a double-symbol makes me all the more favor any of the single-symbols that at least should look consistent on all systems that manage to display something: ฿ or Ƀ. The $ symbol being used for many many currencies should be reason enough to not have a problem recycling the Baht symbol for Bitcoin. Here in Chile they also use $ for Chilean Pesos. |
|
|
|
what about daily "bumping up my post" posts?
No more than once daily. You shouldn't bump a post too many times in a row. Bumping shouldn't be annoying. Delete old "bump" posts so they don't clutter up the topic. Interesting policy. I consider pure bump posts very very rude. If I can't make up any """news""", I don't bump my threads. If bumping is all fine with the mods, could you please introduce a checkbox "bump up once per day" so I can bump it without cluttering it with "/bump" posts? Aka I don't agree with pure bumping being all fine as it is the opposite of the often requested feature of rating posts and threads. |
|
|
|
Why not just use "BTC" in text and BTC in images? A symbol in text isn't really required.
It's not the first time we are discussing this and although "no authority in bitcoin" Atlas vs. "we always used ❏" Luke might most likely not be resolved ever, I'd love to see some definite preference of the bitcointalk.org users so at least we can silence this repetitive discussion here. |
|
|
|
|
Nice to see that now my 2 fav trolls keep each other entertained in a wiki-edit-war.
|
|
|
|
|
Oh this article was written by a kid or what? I found it very low quality.
Anyway, we are still at a "there is no bad news" (in main stream media) stage.
|
|
|
|
|
Show Posts
