Why are unpublished extensions still considered repetitive content?

[Don Schmitt]

I understand not wanting the store to be flooded with duplicate content.

But why would the Chrome Web Store be concerned about extensions that aren't even published?  This should be an exception to the rule.  There are many scenarios where this could be helpfull.

Here's one scenario that has no solution without an exception for unpublished extensions:

1. Enterprise customer wants to push an extension to their employees using ExtensionInstallForcelist.

2. Not all employees are on domain-enlisted machines so they HAVE TO USE THE WEB STORE! But now they're stuck with all the web store rules.

3. The customer wants to have control over their version of the extension so they aren't hit by surprise updates without doing their own testing.

We can't accomplish this scenario with the current repetitive content policy which sucks and we are facing a potential takedown that will affect us and our customers right now.

Again: Why would they give a damn about unpublished extensions?  This has to be made an exception to the policy.

Thanks!

--

Don