In my opinion, as a maintainer and user of Chromium (as distinct from Chrome), 
we absolutely need to ship this with the code removed / disabled.  This is a 
deliberate attempt to lock out the open Web, to force the use of a 
Google-approved (and Google-locked) software, firmware, and hardware stack, and 
to enable persistent, lifelong tracking per user of every action ever taken on 
the Web.

If a bank or similar requires it, then a separate (locked) commercial device 
should be used to interact with that specific commercial entity.  It is not our 
responsibility as open source developers to work for free, or at the expense of 
companies supporting open ecosystems, in order to make it easy to access the 
services provided by hostile for-profit entities.  Furthermore, it is the 
responsibility of the company requiring the locked commercial device to ensure 
it is fit for purpose, etc. at their own expense, and they need to bear the 
full financial and legal liability of that requirement.

In some ways this is no different than the old Bluray fight.  Illegal (in the 
US) access methods aside, people got used to using a separate player or other 
device and continued to enjoy their freedom to modify and use their Debian 
computers, privately, as they always had.  This did not measurably harm Debian, 
and in fact probably helped as people begain to understand that the Debian 
ecosystem was trustworthy in the true sense, i.e. not watching every move or 
preventing access to key OS components.

If this code is not removed, I would probably need to stop helping with the 
maintainance efforts.  Conversely I am happy to step up and assist with the 
removal process.

Reply via email to