...and then the Captcha won't work making it impossible to request coins.

Is there any way you can compile minerd so that it is run from the command line on the Android system (i.e. compile as a normal Linux binary for ARM)? This would have a few advantages for some specific use cases:
- Possibility to control and monitor the miner over SSH/any other remote shell protocol
- Would run on devices with broken screen (or broken input method)
- Android-version independent (I'm not sure)?
- Better for people who love the command line

When I asked you to make it compatible with Android 2.2, it was because I was already guessing it would only be compatible with 2.3 and up, like most Bitcoin and Litecoin apps. I guess it's some problem related to certain libraries not being present on 2.2...

I really don't want to put pressure into you doing this, but are there any updates? Don't forget to tell us when you achieve some more progress...

The orange, changed image looks better on the website. Even though it looks fine now, take care not to abuse of the orange color if you ever make more changes to the layout. Too much orange is one of the problems I find on some websites with the United theme.

Yes, I know, I'm not criticizing you. In fact, the icons on my page are in the opposite side (float: right) of the div, when compared.
They look much better now You're not so bad at web design as you say...

I like it, it reminds me of the homepage of my tnyCloud service. I think the four bigger icons in the middle of the page need to be anti-aliased because they look ugly now.

Time-based expiration of links shouldn't be too hard to implement, but only if it is independent from the hit limit (IMO these should be two different settings, anyway). I may add it this or next week, but first, I want to make sure there are no bugs in the code so far.

The advertising system would only be feasible when the "price" for a link is small, and then third-parties using tny.im as a payment gateway may not like it. I have plans for pointing people to Bitvisitor when the amount to pay is below 0.001 - there are no other faucets or similar services that I know of that pay instantly like Bitvisitor, and it's unpractical for people to wait several hours to visit a link.

Indeed, but as I said, this isn't made with content-selling in mind, but made to be part of a payment gateway, where it doesn't matter if the long URL is clicked many times, because it can only be used once. I may start using this system on another of my websites soon, as a way to provide automated system for accepting Bitcoin.

As I said on my lengthy post, you can set a value for the hit limit in order to make sure not more than X people visit it. But then, you'd have to either increase the hit limit each time you know someone is going to pay, or create a new link.

Or else, you can just hope that the people who pay for the access to the link don't share the long URL with anyone.

Unfortunately, I can't think of any better solution: you must always point people to the long URL once they pay, and that always opens the possibility of people sharing it with anyone else. The only solution for that isn't on my hands: it's to have an unique long URL for each client.

I'm the developer of the http://tny.im URL shortener, and I've gradually been adding Bitcoin-related features to it, starting with Bitcoin address shortening and now also a payment gateway service.
Today, I'm opening the "Internet toll" service (not to be confused with "Internet troll service" ) to the public for a final beta testing phase.

What's the "Internet toll"?
Basically it is a set of features that allow you to charge people for visiting your short links, and obviously get that money back later. When clicking on a short link with the payment option enabled, visitors are asked for a Bitcoin payment before they get to know and visit the long URL of the short link.

I have took special care in making sure the long URL is not available to anyone who didn't pay - however, nothing stops users from sharing the long URL with others once they pay for it. That's why this system works best as a payment gateway with unique callback URLs - I'll explain later.

Even though the system was designed for smaller amounts of Bitcoin, being adequate for micro-payments, it works with virtually any amount.

Here's an example of a short link you must pay to visit: http://tny.im/pay

How do I set up a short link with these features enabled?
On the tny.im homepage, or through the API, shorten a link. If you do it through the API, you can set the "price" and "payoutaddr" parameters directly.
If you use the website, you must create a link first, save the passcode and then edit it in order to set these options.
More information at http://tny.im/toll.php

What is this good for?
When I first talked about this on the social network CoinConnect, an user suggested this was good for selling files. I'm sure there are plenty of other uses. It can be used for charging for the access to any URL, be it a file, a page or a video. It gets much more interesting when you use it as a payment gateway and in conjunction with the "hit limit" setting.

What about the payment gateway?
You can use tny.im as a Bitcoin payment gateway - without the need to run a Bitcoin client on your server or even having a dedicated wallet for it. You only need to have a Bitcoin address.
Have your system shorten your callback URL using the API. Set the "price" (how much users pay, in Satoshi) and the "payoutaddr" (address to where what you earn will be paid). Also, set the "hitlimit" to 1 - this way, the link can only be paid for and visited once.
Then point users to the short URL returned by the API. When the user pays, it will be redirected to the URL you shortened, in this case, the callback URL.
That callback URL should be unique for each payment, and that's something you must implement on your side. When the user visits the callback URL, you'll know he/she has paid.
Even if people share the long URL with others, it will have no effect because the token (or whatever unique it may have) was used (and marked as so on your database) already. That's why it is important to have an unique long URL.

Even if this seems complicated, it isn't: after you automate the process, you can make it work as any payment gateway.

Payout and fees
You get paid once the earnings for your payout address hit the value of 0.05 BTC. The only fees I currently take are the miner fees, which are usually 0.005 BTC per transaction. The fee will be subtracted from your payout; this means that is you earn 0.07 BTC from users' payments, you'll receive 0.065 BTC.
The earnings are counted on a per-address basis, not on a per-link basis. This means that if you have 50 links with the same payout address, you'll get paid once the sum of the earnings on all these links is >= 0.05 BTC.
Currently, payouts are issued manually by me and take usually (much) less than 12 hours, but they can extend for up to 48 hours. Later, I'll implement an automated system to do payouts for me.

Don't hesitate to ask any questions or give suggestions. I know it's hard for you to trust me, since I have zero reputation on this forum. I suggest you only use this system for small BTC amounts, because I have no reputation and because the system is still Beta (even though I tested it a lot, I can never test all the possible conditions).

Any chance of making it compatible with Android 2.2? I want to burn out my cheap tablet by trying this, but it only has Froyo and can't be updated.

Even if you don't get much traffic, I believe every bit counts; furthermore, ads are loading very slowly (and may not load at all) with the old affiliate code, which means that from your not-much-traffic even fewer people will see the ads.

http://skude.se/BTC/ is listed twice. Just a minor mistake, or is there any special reason?

I have used this service since its start, not as a publisher but as an advertiser for my websites.
I recall the first ad was for my own URL shortening service (w/out ads), and it was even a bit aggressive ("tired of waiting for redirection? my shortener has no ads"); recently I have taken a more passive approach since I figured out CoinURL isn't exactly in the same market/user base as my URL shortener - no need to get more enemies
More recently, I also bought ads for another website of my own, with positive results - even though the ad I posted for it accidentally broke the iframe of the redirection page, support contacted me in a few hours and I had the problem solved in a couple more. CoinURL also implemented the feature I suggested in the emails we exchanged, the one of ad preview (exactly to prevent broken iframes).

As an advertiser, I'm quite satisfied with this service and its support system (fast reply, no annoying ticket system, and even accept users' suggestions), even though as an link-clicking user I really hate services like CoinURL, making me wait to browse to the links I clicked.

Add me too, please. I'm not going to waste this freebie opportunity

Well, the API worked right for me. I have double encryption enabled (but not two-factor authentication).

I recommend that you double-check for typos (as well as accidental spaces) on the URL you're using to access the API.

It looks like the typo isn't in the guid, because then it wouldn't return "Error Decrypting Wallet" but "GUID Invalid". So the only reason I see for it not to work on your side is that you're passing the wrong password to the API.

Joined yesterday and only deposited 0.1 BTC so far, just to make sure it doesn't run away with my money
Use one of my links to join and make my day better (isn't that enough of a reason?)!
http://pyramining.com/referral/3hcxzk7rd   still active
http://pyramining.com/referral/pm98kr26a   still active
http://pyramining.com/referral/za3fdbqc6   still active
http://pyramining.com/referral/mxygpbr9k   still active
http://pyramining.com/referral/3xcg6e4zd   still active

Yes, the identifier you should be using is something like abcaa314-6f67-6705-b384-5d47fbe9d7cc. So that's not the problem.

Even though retrieving the address for my wallet worked fine through the Blockchain API (unlike what happened to unclemantis, on his other thread), I can't seem to be able to decrypt a backup of the same wallet on my computer with openssl either. I have double-encryption enabled, may that be the problem?