If you have an idea you'd like to see implemented here, no matter how crazy it may seem, feel free to make a new post describing it in detail. I can't guarantee it'll get done but if it's interesting enough I'll give it a shot!

How about making a script for "I Heart Radio". It's like Pandora but has as many albums as Pandora has songs. Plus you can listen to local radio stations that participate and there are a lot. I would do it myself but don't really have the time.

link is
www.iheart.com

Idea 1: Polls

As a developer, I am interested in writing scripts for one of 3 reasons:

1. I have a vested interested in the site (I watch the content myself)
2. I am getting paid to do it
3. It would make a lot of people happy

Number 1 is a no brainer and the bounty section adequately covers number 2. Have you considered a "poll" for users to vote on which site they would like to see done. I am much more likely to work on a site that has a lot of people interested than just one lone person.


Idea 2: Limited term licenses and protection from users who would attempt to get scripts for free

Using the Update meta block seems like it would be part of the solution. Also, the user would need to provide the email address they used to purchase the script in addition to the download key to get the script. Finally, the site would embed the email address in obfuscated/encrypted form into the script before download. The author would then have the ability to go in and check to see if the email address being used to access the site matches the one that purchased it. Additionally, for those seeking a refund the author could mark email addresses as being void. For the limited time, they could mark it as active until. An added bonus would be to automatically detect when the same email is accessing the site from more than N IP addresses in X period of time ("I paid for it so you might as well use it" prevention).

I know that anyone with some programming expertise could probably eliminate the Update block. I also know that doing things like making other portions of the code not work if a response from the server during the update is also not a perfect solution. I just think this would be an improvement.


Idea 3: Have an automated test suite report on the state of each script (broken/working)

I know there is a link to "report this script as broken" link but I don't see a corresponding link for "report this script as fixed". As a developer that won't always use scripts he develops - it would be nice to be notified near real time when something I write breaks. The theory is that it is a lot easier to make a minor tweak to fix something that just worked yesterday then it is to fix something that may have been broken for months and a lot has changed since then.

Idea 4:

Also, I know you had to handicap the wiki due to security reasons but figuring out how to enable or something equivalent would be really nice. I would like to write some step by step "how to" guides as I figure each thing out so the next person can benefit from my pitfalls.

Cheers,
Joshua