- Or reduce the chance of malware submissions
- Or improve the signal to noise ratio to reduce overhead in manual checking
- Or cover some of the overhead in approving manual submissions
Then the way Google worded this might be of interest.
We designed security into the extensions system from day 1 but we’re always looking for more ways to protect users. So, today, we are introducing two significant changes in the Google Chrome Extensions Gallery: a developer signup fee and a domain verification system.
The developer signup fee is a one-time payment of $5. It is intended to create better safeguards against fraudulent extensions in the gallery and limit the activity of malicious developer accounts. Starting today, this fee will be required to publish extensions, themes and soon apps in the gallery. We are waiving the fee for developers who already registered with the gallery (specifically before 11am PST today), so that they can continue to update their extensions and publish new items without paying the fee.
This isn’t something I would directly advocate, though I have strongly thought about providing a way for content/announcements to be submitted in the past, and I think it would be wise to have some barrier of entry/trust for those submissions, along with thorough editorial control.
I doubt whether the Google site passes any link juice to Chrome plugin authors but I bet they get tons of links in other ways. I think I would avoid PageRank passing links though I know a number of sites that charge for press release submissions, and many sites have community submissions that do pass PageRank.