4 ms·
No, I wouldn’t support this for software that doesn’t include a right-to-repair-license. It’s the software maker’s choice to offer it and the consumer’s choice
by paulcole 4y ago
No, I wouldn’t support this for software that doesn’t include a right-to-repair-license. It’s the software maker’s choice to offer it and the consumer’s choice to buy it or not.
- thfuran 4y agoDo you oppose all consumer protections or just this one?
- paulcole 4y agoThis one specifically because: 1) It’s the one we’re talking about here 2) “All” is pretty broad
- LocalH 4y agoSo you support the defacto removal of right-to-repair across the board? Or just for software?
- paulcole 4y agoI don’t know enough about right-to-repair across the board to make a sweeping declaration. That said, I tend to fall on the side of letting product/service providers set limits on how their products and services are used — as long as they are up front about those limits and don’t change them after the fact. And I’m generally against the idea that when a customer buys a product or service they’re owed anything beyond the product or service that they’re buying.
- mindslight 4y agoYou seem to be leaning on the virtue of free market interaction, but copyright/patents/etc are severe market distortions that makes such reasoning specious. IMO if a company wants to benefit from copyright regulations, then they should have to escrow the buildable source code (the original creative work), to be released into the public domain when the copyright term is up.
- paulcole 4y ago> IMO if a company wants to benefit from copyright regulations, then they should have to escrow the buildable source code (the original creative work), to be released into the public domain when the copyright term is up. That is definitely an opinion you can have. But it doesn't seem like there's any realistic chance of this happening in the United States.