3 ms·
Just never allow such a transfer force a new user to create a new name. Ensure this is part of the terms of service. Prosecute violators that is to say buyer an
by michaelmrose 7y ago
Just never allow such a transfer force a new user to create a new name. Ensure this is part of the terms of service. Prosecute violators that is to say buyer and dev under cfaa and ensure a hefty fine is levied with prison time. Nefarious parties will find few sellers thereafter.
- zzzcpan 7y agoYou forgot to mention a small detail: force every other country in the world to enforce your ridiculous laws.
- michaelmrose 7y agoShow whether extensions are certified by counties with similarly ridiculous laws and wait for that to become a required after the first 100 million people get pwned.
- adrianN 7y agoThanks to the movie industry, this is mostly a solved problem.
- deleted 7y ago[deleted]
- unionpivo 7y ago\s Right that solved pirating, torrenting and hacking. None of the above happens on internet any more since cfaa was passed. Shady people will do shady stuff, no mater what law says. And you will never catch all or even most of them. So if it's all the same it would be better if we come with solution, that prevents abuse from happening in the first place
- michaelmrose 7y agoThe point is not to stop anyone on earth from behaving in a shady fashion its to make it systematically challenging for the normal behavior of non malicious people to enable malicious people. If you can buy or take over responsibility for extension foo and automatically exploit thousands of people who automatically get updated to foo 1.1 now with 1000% more malware then it will happen. If you have me/foo and you want to take over maintaining foo and you have to create you/foo and convince people to remove the working version of me/foo and switch to your you/foo this is a small burden for legitimate users but a higher bar for scummy companies whose accounts will doubtlessly either have a bad history or far more likely none at all to lean on. Further the time required to convince users to switch will be much longer leading to more time for something to be discovered as malicious before users are effected. Best this whole process makes exploiting users much less valuable and thus you have less of it to start with.
- michaelt 7y agoAs long as an extension can be owned by a company, you can bypass restrictions on transferring the extension by transferring ownership of the company. Unless you think plugins for HTTPS Everywhere, Google Translate, and LastPass should be signed by an individual developer - in which case you'll have to solve the problem of what to do when that developer moves between jobs :)
- Mindwipe 7y agoIndeed. It's a superficially attractive answer, but the reality is that it's unenforceable. Nation states get unstuck here on taxation, and bluntly it is unlikely any browser vendor will ever invest as heavily as nation states do on getting revenue.
- michaelmrose 7y agoIf you can't enforce the rules on an extension/library developer because they are based in a non compliant nation just kick them off the market. To be blunt most current software in use in US/Europe already comes from US/Europe.
- michaelmrose 7y agoThe point is not whether its possible to transfer ownership of the code it's whether its possible to transfer it in a way that causes a user who agreed to trust Bob or Bobco inc to automatically end up trusting Crook or Crookco inc. A buyer company or individual ought to have to create a different name and convince users to install/trust their extension if ownership is transferred instead of merely taking control of the existing name and having the next automatic update install malware. Extension systems and language specific package managers on the overall have garbage security and are going to be a way bigger problem in the future. They are low hanging fruit.
- michaelt 7y agoRight, but if a user has trusted an extension by Bobco Inc, and Bobco becomes a wholly-owned subsidiary of Crookco Inc, then Crookco can put what they like into the trusted extension. I suppose you could argue that when Facebook buys Instagram the Instagram app should be uninstalled from users' phones and all their accounts and posts deleted, because they didn't agree to trust Facebook or consent to the data being shared with Facebook. There's a certain logic to that, but it would be a big change to how the current tech ecosystem works.