Also, the game theory that gives us insight into voting systems, telling us the current system leads to a 2 party system, did not exist when the US constitution was written.

They were removed from MAINTAINERS, which is what identifies the people responsible for maintaining a piece of code, a subsystem of Linux, not the credits, which is encoded in the git commit history.

A very similar situation to that analysed in this paper that was recently published. The quality of what is generated degrades significantly.

Although they mostly investigate replacing the data with ai generated data in each step, so I doubt the effect will be as pronounced in practice. Human writing will still be included and even curation of ai generated text by people can skew the distribution of the training data (as the process by these editors would inevitably do, as reasonable text could get through the cracks.)

Trump supports Russia and Israel, the dems support Israel. If you pick Trump, both groups pay the price. Depending on who you pick one group will pay the price or not, one group will pay the price no matter what; yet for this group (the Palestinians) the degree to which will probably differ, I suspect Trump may be worse given that he avoids supporting a ceasefire at all and tells the Israeli government to finish what they started. People from Palestine state the same: Trump would be worse, but neither choice would support them.

Neat idea. This could be refined by adding a git hook that runs (rip)grep on the entire codebase and fails if anything is found upon commit may accomplish a similar result and stop the code from being committed entirely. Requires a bit more setup work on de developers end, though.

Do keep in mind that in Europe there are often required checks whether a car is ‘roadworthy’, in Norway this seems to be a biannual check: so you cannot really skip maintenance to the extent that that would be a huge factor.