ITT: people guessing what the technical details of the implementation might be and then freaking out about it as if it's true and confirmed . Such a frustrating read.

Nobody knows how they will implement this, but here's a more likely scenario:

Jolla creates a PC tool to help non-technical people flash their Sony phone with a Sailfish image. This tool may be proprietary, and may require payment before it downloads and flashes the Sailfish image.

That's it. No need to freak out.

It doesn't mean that experienced users would have to use the proprietary tool, or that once installed the images will be tied to a specific account, or that they will include a load of DRM to prevent unlicensed copying.

Jolla only has to make it easier to pay, and most people will pay. This community has enough technical know-how to dump an image from one device and share it if we want, but I think most people here recognise that it's worth paying to support the company.

Jolla will also want to make it possible for as many people as possible to try Sailfish, and not everyone knows how to flash a phone.

My theoretical scenario ^ would fit with what we know about how Jolla has handled similar issues so far. As others have mentioned, the 3rd party proprietary packages shipped with official devices (text prediction library, Microsoft exchange support, alien dalvik etc.) are contained in a separate repository. If you're using a community port it's currently possible to add the repository and install these components (although AD won't work because it needs kernel modifications IIRC). It's "not allowed" but it's not impossible either because making it impossible has implications on privacy, takes time and effort, and people would inevitably find a way around it if they wanted.