Sellers can't leave negative feedback for scumbag buyers. it was changed a few years back so they could only leave positives. Leaving a positive but actually telling of the non-paying or chargeback scamming customer is a violation of their policy. This was to make the site not look like it was a complete criminal scumbag site, to be appealing to "buyers", while fucking over merchants, who have to suck it up, and provide free shipping for just about everything out of their pocket too.

This is likely the fault of the service not actually sending the payment until later, not delayed processing on the part of the Bitcoin network.

This has little use; DHT is made for BitTorrent, not money, and is searchable. http://en.wikipedia.org/wiki/BTDigg

Alt-coin talk is off-topic for the noob area.

Why not go back to the source:

        Much stupid
                         Super annoying
   Joke coin
                     Many fools

Have a look at the forum source (this one for thebutterzone's profile)


When an ICQ account is added to a user profile, the forum adds an image with user information, which is inserted below the avatar area in every post a user makes. This allows a third-party to track IP addresses every time a post by a user is viewed, and to know the ICQ number of the user who's post was viewed.

You could say the same thing about that paper money thing governments print. You would have to keep track of (a stack) of paper for years to come and if you lose it your money is gone.

You statement is actually applicable to old-fashioned paper money, but is not applicable to a bitcoin paper or offline wallet; you can make multiple copies of your money and store the copies in multiple locations or with trusted individuals. It can even be encrypted so that "found" copies can't be spent by other people.

A paper wallet is a long-term offline bitcoin address (and private key) that is secure, by not being (and never having been) stored on a computer, where it might be "hacked". Worse is an online wallet, money stored on someone else's wallet service, where the money is basically not yours anymore.

Here is a thread documenting creation of a paper wallet: https://bitcointalk.org/index.php?topic=361092.0

Windows easy transfer has previously transferred user app directories correctly, which is exactly where the wallet is located. If you manually unchecked the user profile when copying, you cause your own problems. http://technet.microsoft.com/en-us/library/cc722197%28v=ws.10%29.aspx

You will start to see Microsoft recommend that you transfer stuff with cloud skydrive with windows 8.1, so that they can hang on to the lock-in a bit more.

It's here:

Are you programming? If not, you do not need either Accelerated Parallel Processing (APP) Software development kit or Display Library (ADL) Software development kit. The standard driver already includes an OpenCL runtime.

I have had some time-consuming posts eaten by database error. It's a good idea to CTRL-C copy your entire post to the clipboard before pressing "post" or "preview", if it's something long.

SierraChart setup tips:

Set price ticks correctly per exchange:
Go into Menu -> Tools -> Chart Settings. Pick "Edit Global Symbol Settings". Choose Service "SC Historical Data", and press New. Then edit on the "General" Tab:
-Symbol: mtgoxUSD
-Price Display Format: .00001
-Tick Size: 0.0000100
-Currency Value Per Tick: 0.0000100

Now in Menu -> Tools -> Chart Settings, "Price Display Format" and "Tick Size" is auto set to  ".00001"

Fix volume display until next SierraChart Launch:
Go into Menu -> Tools -> Chart Settings. Go to "Advanced Settings 2" tab and change "Volume/Open Int. Multiplier" to "0.0001". Press Apply

See volume:
Menu -> Analysis -> Studies. select "Volume" and press "Add>>", set volume format to .0001, and OK.

Bar analysis
Go into Menu -> Tools -> Chart Settings.
Set Bar Period to "Number Of Ticks", "Range Of Ticks", set the number, and do whatever analysis you want.

ANN: New version of Sierrachartfeed and direct-download history files, working again (and fixed again Feb 10 2014)

Original post with details of what this software is, read first:




Sierrachartfeed gets data from bitcoincharts.com for multiple exchanges. Each time they change some API "feature", it seems to break other people's software. This is the fourth fifth "rebirth" of working software I've written since slush gave up maintenance of sierrachartfeed.

note: when using the single-letter option, there is no space between the option and the parameter

Download links:

• SierraChart software:
  • http://www.sierrachart.com/downloads/SierraChartSetup.exe or
  • http://we.lovebitco.in/schart/SierraChartSetup.exe
• sierrachartfeed:
  • http://we.lovebitco.in/schart/scfeed.py (Python 2.7 standalone source) or
  • http://we.lovebitco.in/schart/scfeed.exe (2.41MiB) (Windows 32 bit exe, py2exe)
    md5sum: eeaabc7edb427e1c6e419c042cad6848 *scfeed.exe

For history older than five days, before first running sierrachartfeed
The normal Bitcoincharts API only has five days of data available. If you have never run sierrachartfeed for a particular exchange ticker before, it will only get the last five days. However, if you want all trade data from the beginning of time, you can download some big files first:

• Go to this web page: http://api.bitcoincharts.com/v1/csv/
• Download the individual CSV files for exchange tickers you wish to track
• Extract the gzipped files to the SierraChart data directory (C:\SierraChart\Data)
  (a utility like 7-zip can help you with this)
• When you first run sierrachartfeed and specify a ticker with CSV, data will be imported from this file first
• The CSV file will be renamed after all data from it is imported

You will also need to re-download a new CSV if it has been over five days since you last ran sierrachartfeed.


The SCID filenames are different from previous versions, to avoid using or overwriting obsolete data. New filenames are of the format mtgoxUSD-p4.scid (where p4 indicates precision 4).



Changelog
(0.7.1 - 2014-02-10)

• CSV file synchronization impossible due to the remote files now being gzipped and unstable, abandoned,
• Import user-supplied local CSV method added,
• warn of a trade gap if last local trades are older than the 5 days available through API.

(0.7.0 - 2013-12-19)

• A local CSV is mantained and updated with trade data, resumed from nightly updates
• Fixed the only-5-days-available API
• Merged libraries into single file, fixed much library fustercluck
• Higher default precision, fixed volume rounding
• About 1/2 of .py is new code.

Yeah, that sounds like a legit offer...

http://www.101domain.com/co_in.htm  -> 7.99 USD/yr
You don't need to transfer the domain out of there to your other registrar, just set up the DNS servers and such.

Bitcoins? -> http://www.domains4bitcoins.com/

You don't need to spam up this forum with your requests. Anything that needs to be written probably already has been x100; you don't need to harvest more useless "content" for this great new forum you are developing. You can read my web link and click on the Bitcoin address right below it in my signature.

I've got it working again. Huzzah. I just need to iron out some crap data from bitcoincharts CSVs, like this:

1387430609,560.640000000000,0.356700000000
1387430826,667.500000000000,0.299600000000
1387430714,554.260000000000,0.036100000000
1387431207,692.500000000000,0.151600000000
1387431697,1000.000000000000,0.150000000000
1387431246,612.700000000000,0.100000000000
1387431516,540.290000000000,0.029000000000
1387431550,583.000000000000,0.514600000000

Those are timestamps in seconds (in this case from localbtcUSD). You can see that at least a 10 minute range of trades are all randomized, which really pisses off SierraChart. I'll need to sort them efficiently without impacting 500MB+ of exchange data that only has a minor problem (and so far, they all do to some extent).

Hint: to get it working faster once I release the code, start downloading your exchange's CSV files now, and put them in the C:\SierraChart\Data directory (don't worry, SierraChart feed will download it and keep it up to date if you don't...)  I will be ignoring previous SCIDs by using new filenames.

DONE: moving this to a new thread so OP doesn't have non-working code and links: https://bitcointalk.org/index.php?topic=377649.0

I said sane. It is nutty to allow users to shoot themselves in the foot by providing an interface to act on mistaken assumptions like these:

OP: Then I delete the address. Will money still be in the wallet? And I will be able to send money from 1st address? Without a trace?

To answer the OP's question:

The minimum fee is 0.0001 per kB of transaction size. The amount of data you send determines the minimum fee. If you send to many recipients, or you are using many payments you previously received to fund the transaction, you may be creating a transaction larger than a kilobyte. Bitcoin-Qt will calculate the appropriate fee based on the transaction size; other wallets often do not do this in strict compliance with the rules.

If you do not include the 0.0001 per kilobyte bitcoin fee when required, your gonna have a bad time. For transactions that qualify to be free, you should still add this as a voluntary fee, as it may take hours or days if your transaction includes no miner incentive for inclusion in a block.

The "stupid button" comment is separate from the pretty picture showing the layers of script; it's referring to the LMGTFY button along with the other buttons. It's like saying, "look stupid, all you had to do is Google, was that so hard??" (although that's 90% of new posts). I did just use that service when the three-word-search and "get lucky" was the exact answer, though.