Maximum length of connector filter

Is it possible to increase the length of the connector filter used for filtering NuGet packages? We'd like to use the a filter to maintain a list of approved packages for our organisation and the current length of the filter (1000 characters) isn't sufficient for this.

Product: ProGet
Version: 3.5.8

The connector filters are designed more to include or exclude just a few packages. Because of the way the filters get translated to OData queries, longer ones are likely to just time out the server anyway.

Since you have a list of approved packages, would it be feasible to just pull those to the feed manually, then disable the connector? Or do you have any suggestions for how we could better support your workflow?

Our aim is provide a curated feed that only contains packages that we've approved for use in our products. Ideally we'd like some way of approving at a package level but without having to specify which versions are approved. This way we can leave it to individual developers or teams to use the latest version of packages as and when needed. They'd also be able to see that new versions were available.

The only alternative I can see is a process whereby we regularly check for the latest version(s) and upload to our ProGet server. This could be manual or automated (given a list of approved packages).
I'm going to look at how this can be automated as some packages, especially for web development, have a large number of dependencies which would make anything manual quite painful.

Thanks for the clarification; this is definitely a roadmap item for us. We don't have any details on it, but as we start spec'ing out, we'll be in touch.

We have exactly the same requirement. Would be nice to see this feature implemented soon.
That was one of the main reasons why we bought the enterprise version.
Thanks.

Thanks for letting us know; we're currently waiting on the NuGet v3 API to be released before spec'ing this out further. It's scheduled to ship with VS 2015 later this month, so we'll have a better idea after that.

It used to work, and it still kind of does depending on the time of day... but NuGet.org's performance has degraded significantly over the years. Now it's very hit-or-miss, and the longer the package filter list, the higher the chance your connector will time out.