But this list from OP is even more interesting! That list is a wonderful (mine?)field of rabbit holes! Bookmarked and thank you.
Also as someone who easily succumbs to analysis paralysis, this has made it quite difficult to motivate myself to start another one.
Even if you could get the above working yourself, good luck trying to get someone else to so you can collaborate on a project.
Developers often dismiss ‘marketing’ as though it is just a fluffy icon or slick website, but how a product is positioned (in Dropbox case for ease of use and the fact that the project is engineered to ‘feel like a folder’) is absolutely marketing and critical to its success.
What I should have thought: "Wow this guy is an idiot, no consumer will ever do that."
What I did think: "Wow I'm an idiot, I need to learn linux better."
Clocks, motors, stuff like that?
It was good timing too because the motherboard on my 3d printer just shorted out. I didn't want to pay the full price ($115) for a replacement board. So I bought an open source board similar to the one I used for my MPCNC. Since I had just put that togheter I knew what I was doing even though there was limited help in converting my particular printer available online.
For something that has "open source" in the title, it was remarkably hard to find the actual plans -- there are many blank and broken pages; even the info page for "CEB press" (which seems the first machine they did) is spread over 3 different websites and has many empty/broken pages.
The only thing that is clear form the website is that they are happy to sell you workshops.
Although, you might not want to do this, depending on your threat model. Take care if you do (now both password + 2FA can be obtained by having your password manager compromised, but at least your protected if only your password leaks from some dump)
Part of the problem is that GitHub is both a source code repository frontend (calling for tighter security) and a social network (calling for minimal security). So the cookie expiration policy makes sense for the former case but not the latter. A compromise might be letting the user mark a specific browser instance as trusted, so that the site can either set a longer expiration or else not ask for the second factor from that instance.
Anyway, was hoping someone had figured out which cookie held GitHub's token and knew a browser extension that could extend its lifetime. Not really looking to learn about password managers, which I already use.
DNS is actually pretty simple if you don't want to implement DNSSEC.
With the understanding, of course, that this isn't necessarily a bad thing! Understanding is certainly useful, but if it works, then it works, regardless of who built it. Reimplementing, say, a standard library will make you a better programmer, but if just including libraries to do the heavy lifting produces a working system, then that has value too. There are only so many hour in the day; there's value in knowing when to just hand-wave the giants whose shoulders you stand on.