Google and Mozilla are failing to support browser extension developers
> It is a regular occurrence to hear about open source developers selling their browser extensions, only for their users to be exploited later on by the new owners. ... We are witnessing the failure of browser vendors to recognize the value of our labor and the important role it plays in a healthy browser ecosystem.So this is an interesting philosophical question - the market value of the extension is the value of "monetizing" it by stuffing ads, or worse, monitoring/tracking/exfiltration, into the extension. It's the market value of the trust of the extension's userbase. Is that the value of the extension developer's labor?I would argue not really. The value of a bank, for instance, is not the amount of money in all of the vaults. That money is held in trust for customers, and it is not for the owner of the bank to dispose of. Therefore, nobody who makes a fair offer for the bank should expect those resources in the transaction, so a fair market price for the bank is much less - such as the present value of the interest earned by the bank minus the interest returned to customers.In particular, the only reason the bank has customers is they expect to get their money back, generally with interest, at some point in the future. If they didn't, they'd put their money elsewhere. So if a bank is willing to sell the contents of the customer accounts, that indicates incomplete information in the market - customers didn't know the bank wasn't trustworthy. The true market value of the bank, in a perfect-information market, would be close to zero.It seems like the problem here is that we know two ways of compensating browser extension developers: "don't" and "breach your users' trust." Those point to wildly undervalued and wildly overvalued estimates of the fair market value of the developers' work. And we should come up with some fairer way to value their work (or, more fundamentally, to compensate them; we may not need to monetize the extension, necessarily) first, and I'm not totally sure it's the fault of browsers for not having had such a clever idea - it seems like we collectively need to figure that out.