Perhaps patients have their place but software patients make no sense. One big issue is that it is not practical to avoid writing a system that already exists because there are many, many ways to describe the same software system. It’s so difficukt to search that multiple people could have already patiented the same thing and be unaware the other exists.

It’s an optional field in the userdb JSON object. It’s not a policy engine, not an API for apps. We just define the field, so that it’s standardized iff people want to store the date there, but it’s entirely optional.

“I’m not picking a side” and “this future proofs standardization” is of little comfort, that is seriously suspect. I ought to look to alternatives to SystemD(odge the issue failed).