.meta.js

[openuserjs]

.meta.js

[cletusc]

Here is some skeleton logic for when this gets implemented, feel free to use or abuse. Ref #3 for serving installs.

// .user.js
exports.install = function (request, response) {
    if (!scriptExists) {
        response.send(404);
    }
    if (request.accepts('text/x-userscript.meta')) {
        // Forward request to meta routine.
        // ...
        return;
    }

    // Pull script source.
    // ...

    // Increase install count.
    // ...

    response.set('Content-Type', 'text/javascript');
    response.send(200, scriptSource);
}

// .meta.js
exports.meta = function (request, response) {
    if (!scriptExists) {
        response.send(404);
    }

    // Pull script source.
    // ...

    // Increase install count.
    // ...

    if (request.accepts('text/x-userscript.meta')) {
        response.set('Content-Type', 'text/x-userscript.meta');
    }
    else {
        response.set('Content-Type', 'text/plain');
    }
    response.send(200, scriptSource);
}

[sizzlemctwizzle]

We should respond with a content-type of text/javascript for both. The accept header is just for knowing what they want. Also you left in the same comments for meta as script. We only increment the install counter when accept is not text/userscript-meta. This is the only time we shouldn't increment the counter for a request of the .user.is file imo.

[cletusc]

I actually meant that to be there, but not for installs (it should have said meta install count). In short: a monthly estimated active users count in addition to the normal total installs. I'll branch that off into a separate issue/discussion though.

Edit: discussion posted here.

[sizzlemctwizzle]

An update install would still count as an install, but I think we can ignore automated update checks.

I'll branch that off into a separate issue/discussion though.

Google Groups preferably.

[sizzlemctwizzle]

Pardon the forced updates. I had to clean up after after myself.

[jerone]

This doesn't seems to work anymore... anyone can confirm?

Also; GreaseMonkey will standard have .meta.js support, greasemonkey/greasemonkey#1885

[jerone]

This doesn't seems to work anymore... anyone can confirm?

Nvm, found how it works again; is on a different path. Then greasemonkey/greasemonkey#1885 will probably not work.

[sizzlemctwizzle]

We already support greasemonkey/greasemonkey#1824 for this, and it has already been pulled and released (1.15).