Git repos are distributed by design. I bet all the contributors have at least 1 branch (probably closer to an average of 3) of this project on at least 1 computer that they own.
Decentraleyes extension on Firefox results in garbled text. Not sure why this happens. It is supposed to serve some common assets locally instead of requesting them over the network.
I only skimmed the article. But my stance is, anyone that ever used cherry-pick or reverted multiple commits is impacted by clean git history. Unclean git history could make a simple 2 minute cherry-pick or revert task to a 30 mins+ job.
I have one of those wireless magic mouse that takes 2x AA batteries.
The optical sensor started behaving in a weird way back in 2018 I think, so I stopped using it. I wouldn't mind risking breaking it by trying to fix the sensor (cleaning the lens from the inside is probably enough), adding a rechargeable battery (and whatever circuitry that entails) and maybe even enhancing the ergonomics if it still works after that.
I mostly agree with the points but I hard disagree with point number 3.
Clean code makes the project more easily maintainable. We generally try to keep a standard in code quality (and I would say 98% of the codebase we touch is well written). We also try to schedule refactoring rounds (but that doesn't always happen because of time constraints).
I would imagine it would enable you to run MacOS specific pipelines like building a project and have it work semi-portably across different machines/users.
They don't have to be static but making them dynamic might not worth the cost.
From a simple static page, now you need an API service, most probably connected to a DB or somehow integrated to the rest of your backend. So markdown suddenly isn't enough and you need some server-side logic.
For random strings, you can do this with client-side logic, which in some cases might be easier than server-side logic. But you are still moving from no-logic (static) to somewhere-logic.
I'm thinking if invalid characters in the examples given would be an acceptable solution.
For DNS records this could be XML-like tags like <someprefix>.<yourdomain>.<tld>
On one hand, it prevents blind copy-pasting but on the other hand, your example is invalid.