Hacker News new | past | comments | ask | show | jobs | submit login

Some ideas:

If folks actually value "right to repair" support companies that offer right to repair.

If no tractor company exists that offer the type of open setup you want and you think this is critical - start a company up and take out Deere and others.

Deere's views on software changes by users in the field is pretty darn clear.

My own view - having watched individuals and dealers etc "tune" trucks etc (with all the endless problems involved) - is that for something like a 10,000 part count + heavy piece of equipment - Deere is going to want to keep stuff locked up tight to preserve brand value. Apple has done this with iphones, and the resale value after 5 years on an iphone is incredible compared to players pushing out android phones.




It was easier to pass an automotive right to repair passed in Massachusetts in 2012 than it was to start a successful auto company that could have anywhere near the same impact.

The car companies, threatened by having to comply with different laws in different states, came to an agreement that the car companies would follow the Massachusetts law across the US.

You can watch individuals and dealers etc "tune" trucks now as a direct consequence of that 10 year old law passing.

There's no obligation for the law to preserve brand value when considering an anti-monopoly case. Standard Oil wasn't broken apart because of gung-ho oil companies.


"don't like it? just build your own X" isn't a solution, it's a sneering dismissal: let them eat cake.

we need regulation. force companies to provide a minimum standard of repairability.


Unfortunately 'regulation' is entirely in Deere's favor, thanks to the USPTO and their habit of allowing companies to claim underlying ideas rather than specific implementations.

E.g., US8874261 mentioned in this article:

https://www.ipwatchdog.com/2015/02/18/john-deere-patents-hyb...

https://patents.google.com/patent/US8874261B2/en?oq=8874261

Claim 1 from that patent:

A method for operating a mobile robot, the method comprising:

- Collecting range data of one or more objects in an environment around the robot;

- Identifying uniquely identifiable ones of the objects as navigation landmarks:

- Storing a reference map of the navigation landmarks based on the collected range data;

- Establishing a list or sequence of way points for the robot to visit, each way point defined with reference to one or more landmarks;

- Reading a message on a tag posted at or near one or more way points; and

- Managing a task based on the read message.

When this claim was granted by the USPTO, John Deere was given exclusive rights to the general concept of robot navigation between waypoiints with the addition of "reading a message on a tag" and acting accordingly. To the layman this language sounds specific enough, but those skilled in the art (or in possession of an HN user name) will recognize it as Turing equivalence. Indeed, the next few claims make it clear that ownership of the idea of conditional execution of tasks at waypoints is exactly the goal of the patent.

So, good luck building a competing farm implement that actually does anything useful. The "innovators" at Deere have made sure that you can do no such thing for the next 12 years.


That's not how patents work. Each claim is not a patented thing. A chain of claims forms the patented thing. There's at least 9 dependent claims hanging on that first one.


Right. It’s best to think of the claims in a patent as a set of DAGs (a single patent can contain multiple “inventions”). To infringe, you have to go from a starting node to a connected ending node and implement/match all nodes along the path.


Have to admit I've never heard this in my life. If this is the case, then TIL, thanks!

I will say that my point largely stands, though: the leaf nodes of this particular DAG are places where you will almost inevitably end up if you want to implement robotic farm machinery. Deere averages a couple hundred patents a year, so if you don't step on this specific land mine, another one will get you.


The dependency chain flows upward, not downward. Later claims depend on the earlier ones that they reference ("2. The method of claim 1..."), but the presence of claim 2 does not alter the meaning or enforcability of claim 1.

(I should point out that IANAL, so if there are instances in which this isn't strictly correct, it'd be interesting to learn about them. Downvoting without comment doesn't enlighten anyone.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: