This has been fixed, you can provide USE_UPNP=XXX to the qmake script (see the qt readme).

It's just a wiki page, not a standard. In my (and Gavin's and many others) opionion URLs should be as simple as possible. The 1243X45 exponent stuff is simply arcane.

I do agree more standardization should happen, an "official" Bitcoin URL format would be an interesting subject for a BEP. When that standard format is determined, it will of course be integrated into the client.

Until then, we chose the most simple format possible, which can be described in one line: bitcoin:?label=&amount=   (label and amount are optional)

Quote from: Alex Zee on September 20, 2011, 10:32:04 PM

I can think of a lot of disadvantages, such as slower interface response times, exposing your interface to anyone who connects to a port, debugging it in all the browsers and their different versions, interfering browser plugins and adblocks, phishing, etc. The GUI is very simple, you won't get much advantage by using a browser as your GUI, it will probably be more difficult.

+1 It is a security nightmare. Suddenly everyone developing on the UI has to worry about CSRF, XSS, and so on. The browser has such a large attack surface, you'd probably make some "security researchers" very happy. .

Also, most users of any OS still expect an application to have a desktop UI not a "website in a program".

There is a web UI, though I don't know how stable or mature it is: https://github.com/zamgo/bitcoin-webskin

Quote

I am all in favor of UI / backend split, but see no advantage in making main UI browser-based.

A network UI/backend split would "only" be a matter of extending the RPC enough to make a full-functional UI (it especially needs async notifications/callbacks).

Quote from: Luke-Jr on September 21, 2011, 12:16:12 AM

You can already run bitcoind+Spesmilo

Yes, I recommended Spesmilo to the people that want RPC client support in bitcoin-qt.