If this works the way its says it does (which Ill assume it does), then this is great!
Will really save alot of hassle getting some of the scripts working in chrome with alot less hassle, well done!
And thanx for bringing it to our attention, I really dont watch the google extension page as much as I should.

Changelog of version 1.0.0.4

- support of script running order
- "new userscript" option
- now one storage for every script is used independet from the url its running at
- access to unsafeWindow functions (without return value)

Changelog of version 1.0.0.5

- Compatibility:
* remove wrappedJSObj calls
* emulate Obj.toSource()
- Bugs:
* it was not possible to install userscripts from http sources
* problems with multiple spaces in some header tags
* GM_getResource didn't work on pages with flash
* Tamperscript now is enabled by default
- Feature:
* userscript source url is stored and used for update check
* system script (Tamperscript) can't be deleted anymore
* chrome extensions version supports file:// uri too
(Attention: a option needs to be enabled @ "chrome://extensions/")

I'm somewhat new to Chrome, and just discovered this extension yesterday, and I absolutely love it! This solves one of the great advantages Firefox had over Chrome, as running scripts as extensions is iffy at best. Not to mention the fact that they clutter up your list of extensions, and they're very difficult to edit.

One thing I wanted ask about are Includes. They seem to assume wildcards, even when there aren't any. For example:

// @include http://twitter.com/

This has the same effect as this:

// @include http://twitter.com/*

Is that a bug? I don't think it should work like that, and doesn't in Greasemonkey, Scriptish or Chrome (when compiling as an extension).

Thanks!

This is already fixed in the beta Version of Tampermonkey.