Include things like github.com/foo.js or janl/github.com.js

[agnoster]

Example: suppose djsd receives a GET /github.com.js

Previously, we would only look for ~/.js/github.com.js. Now, the following would also appear (if present):

• ~/.js/github.com/pull-request-edit-button.js
• ~/.js/janl/github.com.js
• ~/.js/janl/github.com/gpl-warning.js

This should make it easier to share and fork repos of dotjs files, as well as putting features into their own "bundles" (inspired slightly by vim's pathogen).

(I also updated the chrome installation instructions - Google broke that a some point. Thanks, Google! Thgoogle.)

[johan]

While I understand how you think, randomly mixing semantically named directory levels with non-semantic ones will have lots of bad interactions; say, including a bundle from some guy named "com", "info" or "museum", for instance.

Those would both run on the domains where his dns-semantically named subdirectories match, and on google.com, blog.persistent.info and guggenheim.museum respectively.

Something like https://github.com/johan/dotjs/commit/0881164619724c550ff72e9e2e7a7148565bbeff is way safer.