Well, there's always the chance that visitors do not want your services. Ever thought of that?

Not meant as an offense, but this is a triple facepalm situation.
Never ever buy any meds from unknown sources.
If something is cheap, it's cheap for a reason. Learn from it and be happy you survived.

Since Electrum is an alloy of silver and gold: ArAu.

Some of the oldest known coins are made of Electrum and were found in Lydia. They are called Stater.

It's assumed that in Egypt, Electrum was called Asem.

The obvious Net can be added to each of them too.

indiegogo.com has a global rank of 8,157 (http://www.alexa.com/siteinfo/indiegogo.com) and accepts donations at indiegogo.com/commonsense.

I assume only domains owned by whoever accepts donations or sells items count.
If not, then I have two who use twitter/reddit. And those two rank really high (9/114).

Completely dropping all caching for https sessions makes not much sense and would hurt performance because every static image or stylesheet needs to be re-fetched every time. Also, you can enforce a disk caching in Firefox with "Cache-Control: Public". As far as I know, there is no RFC prohibiting the caching of https content.

Setting up a correct caching policy is the job of the webmaster. There's no reason not to cache e.g. layout images or css when doing https. You cannot rely on browsers as a webmaster. With "Cache-Control: Public", the guy running the bad DNS in this example could enforce the disk cache, circumventing the "https is never cached" assumption.

If you want a more trustworthy reply than mine: http://code.google.com/intl/en/speed/page-speed/docs/caching.html ("HTTP/S supports local caching of static resources by the browser.")

I beg to differ: http://blogs.msdn.com/b/ieinternals/archive/2010/04/21/internet-explorer-may-bypass-cache-for-cross-domain-https-content.aspx

That's why you configure your browser to delete all cached data when you close it.

Runs fine on XP, which is good for occasional use.
Sadly still fails on W2k, which is bad for constant use.

Maybe it would make sense to add an option to pause the blockchain download. That might come in handy during the initial download, when you sometimes need all resources for something else.

You might want to check your links. Every one of those four gives me an internal server error.

Write a counter (db/flat-file backend) and when it reaches 100k, display a random icon/image via the page header.
The user can then do a screenshot and since you know what image should be on it, it cannot be faked.

For a developer, this is however a scenario that's pretty much outside his control. He could server ga.js from his server, but then always needs to keep it updated. Until DNSSEC is rolled out, cache poisoning will always be an attack vector. That aside, I wish people would null route analytics; it's annoying and often causes lags.

tl;dr: If you control the DNS, you can serve malware.

I fail to see the spectacular news.

Which requires that people actually trust this one person in the first place.

What does not change much. The captchas were put up to stop spamming, which is pretty much what jduck1987 offers.

If I would have had a really great day, I'd call you a greyhat seo. Automated captcha breaking sure is no whitehat practice.

It's all been done before: http://en.wikipedia.org/wiki/Operation_Bernhard

For now, everybody can try to cause an inflation by dropping Bitcoins to my address.

You are not interested in Bitcoin for what it is, but for the amount of dollars you can make by manipulating the price.
If you want to increase the BTC/USD rate, why aren't you trying to decrease the value of the Dollar?

My reason is that new users will consider the whole forum as a kindergarten because a tiny minority (currently two are especially active on that sector) thinks it's ok to crap all over the place.

If you go somewhere, and the first thing you see is a spoiled kid who throws a hissy fit on his soapbox while an old geezer keeps bumping your heels with his shopping cart, then there is no incentive to stay or come again.

Instead of calling it "Kindergarten", it may be better named "The Loony Bin". If it's hidden until you reach eg 50 posts, then a newbie can look around without facing nutjobs.

I stumbled across this when I was waiting for two transaction from the same sender, but to two different addresses which I used to keep both amounts separated for the sake of an overview. Let's say you do business with someone and work on two projects for that person. It still would be desireable to see that you got amount x for job 1 and amount y for job 2. Of course it doesn't make a difference balance-wise, but you can scroll back through your history and easily see which project earned you how much. It actually isn't confusing at all: I expect two transactions and the sender makes two transactions. But in the end it gets added up into one of both addresses.

It's kinda like shopping: you buy two items and pay the sum. But on the receipt, you still see how much each item cost (apples and oranges, I know). Of course you can go to the seller's website and search the prices, but it's simpler to just look at the receipt.

I just ran the following example in the testnet:

Bob has an address which holds 500BTC and he sends out a transaction to two recipient addresses (100BTC each), both of which belong to Alice. She however receives a single 200BTC transaction to the first address only and the second address isn't used.

Now, from what I know, the client sums up coins from multiple addresses to get the amount you want to send out, but shouldn't the recipient see the two transactions in his client?

Granted it's a very special case, but it's somewhat confusing, especially since the blockexplorer shows transactions to both addresses.