I could easily see companies, especially enterprise-level companies, expect code that was generated with AI to have some level of ownership attributed to that AI. Whether a simple "Co-Authored-by Copilot" byline on the commit is the right way to do that is another question though.
I think the tyre problem is not really a thing. EVs use synchronized motors and traction control to avoid extra wear due to uneven torque during normal driving.
I can't remember if it was here or on reddit, but I read from a tyre shop / mechanic, that some EV users replace their tyres very often, because EV cars make it easy to drive very aggressive.
My understanding is that the torque control speed is much faster though, so it's actually difficult to get the tires to slip. I can't screech my tires in my EV, but it'll do 0-60 ridiculously fast.
Anecdotally, my Kia Niro EV goes through tyres a lot faster than the two equivalent internal combustion vehicles in the family.
That said, the Niro weighs ~50% more than the other vehicles, and it has significantly higher acceleration/braking, so I'd hazard it gets driven harder on average.
> The frustrating part is that it's not a workflow _or_ model issue, but a silently-introduced limitation of the subscription plan. They switched thinking to be variable by load, redacted the thinking so no one could notice, and then have been running it at ~1/10th the thinking depth nearly 24/7 for a month. That's with max effort on, adaptive thinking disabled, high max thinking tokens, etc etc.
So Boris' explanation isn't really an explanation.
While simultaneously drastically reducing the amount of work you can get done even at $200 a month. I've cancelled my subscription, it's not worth it anymore.
Section 116 (2) A plaintiff is not entitled by virtue of this section to any damages or to any other pecuniary remedy, other than costs, if it is established that, at the time of the conversion or detention:
(a) the defendant was not aware, and had no reasonable grounds for suspecting, that copyright subsisted in the work or other subject - matter to which the action relates;
(b) where the articles converted or detained were infringing copies--the defendant believed, and had reasonable grounds for believing, that they were not infringing copies; or
(c) where an article converted or detained was a device used or intended to be used for making articles--the defendant believed, and had reasonable grounds for believing, that the articles so made or intended to be made were not or would not be, as the case may be, infringing copies.
Does this not mean the opposite of your claim? It sounds to me that if you unwittingly bought a dodgy copy of something, the law thinks the copyright owner can get you to pay for a legit copy, but not punish you for your mistake.
In the specific case of the Harry Potter works, the fame might meet the threshold of reasonable grounds for believing, but noosphr's argument that "Up to 80% off all works that are in copyright terms are accidentally in the public domain" could grant a reasonable grounds for believing it is not.
This is one of those things that causes interesting court cases because a reasonable grounds for believing X is not the same thing as not reasonable grounds for believing not X.
Reasonable grounds for suspicion probably carries more weight here than reasonable grounds for the absence of suspicion, but cases have hung on things like this before , like the presence or absence of an Oxford comma.
reply