Userscripts.org

A lot of changes, a big step in the good direction.
I think some of them needs to be getting used to.
And a lot of scripts probably needs updates. :p

I've got a small suggestion; change "home" into "profile". Home means something different with what you're trying to define here.

Some other suggestion you mite consider.

As I said at the bottom of the last blog post, I'm really loving the changes Jesse.

One small suggestion on the Userscripts and Firefox page (something that hadn't even occurred to me until yesterday) -- this topic highlighted that people may download scripts before trying to install them, and Firefox wouldn't be the default program for .js files. You might want to lift some text from (or simply link to) the greasespot wiki about this.

Nice! I hope that now less people will ask in the forum how to use / install users scripts.
An idea for the install button, you can add a simple javascript that check the browser (userAgent), and if is not firefox show a confirm dialog, something like:

<a href="..." onclick="return navigator.userAgent.indexOf(\"Mozilla\")==0?true:confirm(\"To install this script you need FireFox + GreaseMonkey.\nYou are using a different browser.\nContinue?\");">Install</a>

Instead of the confirm dialog also a floating div with a link to the how-to page could be a good solution.

Jesse, regarding your post about the "dashboard".

I actually thought I was logged in with a false name.
How about the link just says "Settings"? Or what was wrong with just my username?

Also, a quote function for comments would be very nice.

// Also, I think that the amount of installed scripts is one of the most interesting facts, so why not make it a little more prominent?
I think the number 1 criteria for installing a script would be how many people installed it, and not how many Fans it has, or how many updates.

I'm not sure about it but I think some "scriptwrighters" have faked the number of installs of their scripts.

I think I opened a thread about that once, given that it's possible by simply a for() loop in PHP, but it wasn't changed, which is too bad.

It should only be counted as one install per IP in my opinion.

now, where can i find scripts i once favourited ?

bug: Editing my user profile's bio results in a 500 Internal Server Error page (this was the case yesterday, too).

As to the new "dashboard" - I only know I'm logged in by the "Logout" link, whereas before I knew I was logged in as "khopesh." I liked that. I think you can still have the dashboard but perhaps name the link "<user>'s dashboard" or just revert back to "</user><user>" instead.</user>

As somebody who works for a company that has done a lot of thinking about what "dashboard" pages should look like, I can tell you that a grand overview summarizing all the important stuff—though it should be concise (not crowded and no scrolling)—is the ideal. If there's room, the user icon would be nice (either on the dashboard, or more impressively, on the top nav bar.

I liked the favorite scripts - it let me sync up different systems with my favorites, plus it let me crawl through favorites of other users whose opinions I value.

Also - please use the <title> more constructively a good number of pages have their title as just "Userscripts.org" (which is annoying) rather than "Userscripts.org discussion - new topic" (for the page I'm on right now) or "dashboard - Userscripts.org" for the dashboard, etc.</title>

I like the changes. As for the request "to contribute text for Opera/Safari/IE", I've never used the 2 latter, but here's a quick attempt at the former:

Other Browsers

User scripts can be used in browsers other than Firefox, but the scripting APIs and browser JavaScript support vary.

• Opera userscripts: Opera has it's own UserScript API with different functionality than Greasemonkey's. However, it does recognise Greasemonkey scripts. and many scripts on this site do work in Opera. See here for a guide to installing scripts in Opera and here for details on which Greasemonkey scripts are likely to work.
• ... excerpt about GreaseKit
• ... excerpt about IEScripts. Perhaps borrow from here

and maybe add a reference to it above, something like:

"For this guide I will assume you are using Firefox, if not you should install Firefox first, or see "Other Browsers" below."

@Aquilax - on a similar note, I don't know if browser detection would be such a great idea on the Install button. What about Firefox users without Greasemonkey (Or Safari/IE users with their respective extensions, I think they respond to install links). Maybe a cookie based solution, pops up the very very first time a user clicks an Install. Although browser detection might be an idea for the Userscripts and Firefox page. Serving alternate content? All in all, I'm liking all the changes. Fair play. Something based on socialhistory.js would be nice to see, I do like sites that remind me how much they can tell (i.e. where I've been).

User scripts for IE: IE7Pro(IEscripts database & IEscripts tutorial)

Jesse the Install button appears to be borked.

Clicking it doesn't bring the name of the script up properly , nor the domains it works on (includes?).

Instead it shows a number derived from the URL used.

Eg clicking the Install button on http://userscripts.org/scripts/show/9580 install URL http://userscripts.org/scripts/source/9580.user.js brings up the install box with "9580" being the script name installed but with no includes.

Manually install the scripts work fine (ie via the New User Scripts menu item and just copying and pasting)

A suggestion, especially useful while the dashboard is empty: dashboard drop-down menu featuring all the links in the dashboard.

Update: Jesse has installed this on the site. All that remains in it is some CSS tweaks for the menu (I've commented out the redundant insertion code).

Hey thanks for the drop down menu under my username. That's pretty kickass.

Thanks for so many great changes to the site. Like the repositioning the download count and the install help. Love the username dropdown! I wish you would go back to the larger font size however.

One major thing to do would be to implement a standardized version control script which would be callable from any userscript. That would simply check back to the userscript.org hosted source code for a standardized version key the first time the script was invoked on a daily (or selectable) basis. I'm in the process of modifying a script to act on itself, but would be nice to see it standardized. Another nice feature would be the ability for authors to delete comments which no longer apply, such as for corrected bugs, etc.

Also, can we get hit counters in addition to dowload count? It would be nice to know what % found our script downloadworthy.

There are still people that post topics asking how to install a script

http://userscripts.org/forums/3/topics/9428

I think that the cookie solution is the best solution. The first time that somebody reach US instead of showing the homepage redirect them to a tutorial page which explains what are userscripts, requisites to install them and perhaps also a tutorial to install and remove an useless/sample userscript.