[HN Gopher] Bringing Safety check to the Chrome://extensions page
       ___________________________________________________________________
        
       Bringing Safety check to the Chrome://extensions page
        
       Author : feross
       Score  : 14 points
       Date   : 2023-08-16 20:17 UTC (2 hours ago)
        
 (HTM) web link (developer.chrome.com)
 (TXT) w3m dump (developer.chrome.com)
        
       | j-bos wrote:
       | Wouldn't it be better to notify users if a long unupdated
       | extension suddenly updated?
        
         | Arainach wrote:
         | That's trivial to work around. It would lead to wasted
         | resources where developers push out no-op "updates" to keep
         | from being stale, and in the case of a sale a condition of the
         | sale would be that the original developer pushes out some
         | benign updates prior to the sale closing (or the new owner
         | would push a few benign updates until people stopped looking).
         | 
         | In other words it would cause more work for good developers and
         | extension reviewers and grant no additional safety.
        
           | montag wrote:
           | Very good adversarial thinking.
        
       | kwar13 wrote:
       | Should include extensions that have had a change in developer,
       | e.g. sold.
        
         | mappu wrote:
         | Is it possible to tell that if the sale included the whole
         | google account?
        
       ___________________________________________________________________
       (page generated 2023-08-16 23:00 UTC)