That's an easy one, of course. By identifying a "commonly-used installer" (say, some installer stored by some IT team) you could then do things like say with more certainty "no, we do need older installers to keep working". Or reach out to mirrors that have decided to stop updating installers.
From an Ops perspective, having an idea of how your install base is installing your browser can have a lot of implications. And not having the information could easily lead you to accidentally breaking installations for large subsets of your users.
There's also content-market-y stuff involved, of course.
From an Ops perspective, having an idea of how your install base is installing your browser can have a lot of implications. And not having the information could easily lead you to accidentally breaking installations for large subsets of your users.
There's also content-market-y stuff involved, of course.