No need to wait for the courts’ opinions: controllers must keep the data for a limited amount of time (which can be something like “3 years after the last connection”) under GDPR article 5(1)e.
There is no copyright assignment on wikipedia. You are required to license your work under CC-BY-SA 4.0, so the WMF can distribute it, and other editors can reuse and modify it.
> It seem like the normal mode (protected flight envelope) is just encouraging bad habits?
Maybe, but at the same time it helps avoiding crashes like Sriwijaya 182 or Flydubai 981. Airbus has shown that planes with fly-by-wire and any kind of flight envelope protection (A320 and newer, A220, B777 and 787, etc.) experience less fatal accidents and less hull losses than planes with traditional controls (A300, A310, B737, etc.), even today: https://accidentstats.airbus.com/fatal-accidents/
Unfortunately, these safety improvements mean that we only hear about cases where automation fail to help, like in the case of AF447, but not cases where it prevented an accident.
GP claimed “there doesn't exist any situation, in any plane in any conditions, where holding the stick back the entire time would be an appropriate input. Literally doesn't exist.” That's what I was replying to.
The same thing happens on the 777 and 787: if too much opposite force is applied on both yokes, they lose their linkage and are averaged. There is no warning or priority button, unlike on Airbus planes.
Older Boeing planes also have a mechanism to unlink the controls if too much opposite force is applied. The left yoke would control the left side of the plane, the right yoke would control the right side.
Going by CVEs, Haiku is more secure than OpenBSD. Linux has had strong kernel-level crypto enabled by default on major distributions for years, see AF_ALG or LUKS.
On the wiki page you provided, the only thing that really stands out at the kernel level is KARL, which has a dubious utility: https://isopenbsdsecu.re/mitigations/karl/ It is not even up to date: strlcpy(3) and strlcat(3) were implemented in glibc 3 years ago.