Installation Questions

It's installed separately, so you can have 1.0 and 2.0 installed simultaneously.

No 64-bit plugin support yet.

Yes, owners of FF 1.0 (both paying and contributors) still need to request the beta key.

I installed the v2.001 beta and at least in one respect it steps on v1.018's toes: version 2 decides it is the default FilterForge and intercepts the "filterforge://"
links in the filter pages on this site, which was quite surprising since the beta test announcement clearly states that the published filters are still for FilterForge v1.

Resetting Firefox's protocol association (Tools>Applications>filterforge) to v1's "filterforge.exe" works fine, but I don't think it would be obvious for all users.

Since the setup program already detects the existing v1 installation to import filters and settings, asking the user (at the end of the installation) which FF version they want to use for links would be nicer than changing it silently.

It isn't strictly an installation question, but it is relevant to file associations: do you plan to fork the .ffxml file format and/or the protocol (perhaps filterforge2://) to support both FilterForge v1 and v2 users? Will the current library of v1 filters coexist with the future library of v2 filters or be merged and migrated?

Quote
What's the problem with this?

The problem is that filterforge:// link handling is silently switched to FF version 2 after installing it, disrupting the use of the web filter library with FF version 1.

Automatically setting the association is appropriate for updates, not for an entirely new beta version that is meant to be installed alongside the stable version 1; letting the user choose would mitigate the browser limitation of handling protocols with one application at a time.