Unpopular opinion, but most of that is duplicated information that makes sense to be duplicated because I’m not a machine that can scan the whole page and instantly get what I need.

Top right are action buttons, fork and stars on the center right let you see who else starred and forked the repo.

License information just makes sense to be in a repo summary, and it just happens that most license files are at the root and visible in the file tree.

I don’t see the top level stuff, you probably see that because you’re not authenticated, so github tries to “sell” itself for you.

I agree “releases” should be at the top though (it used to, and I use GitHub refined to bring it back), but having the latest one at a glance is nice and saved me a click many times.

No point in messing with swappiness settings, trust me. You want to address the reason this happens in the first place, not disable or reduce swap.

I’ve had a nearly identical scenario at work. The reason? A data verification process that went through 100s of thousands of files to run their checksums and check integrity. This was working as intended, but the system alerts were firing because of that high buffer/cache utilization. So check which processes have highest IO and you might find the answer. Swap is just a side effect.

sitting at a desk is mostly fine, as soon as you start moving it’s annoying as hell

set it up with wrong address/credentials to see it failing, if it succeeds, it’s not using your relay server

I’ve seen the login warning above, but I don’t self host it myself, so I just logged in

Right, like I mentioned, it’s a scale problem and how people feel about generated code. Abandonware have always been the majority of repos, because people don’t have time or interest to maintain most things they create. We just have more things being created now (whether they’re any good/usable or not).

Disagree. Most projects are never “done”. Whether that is defined by the user or by the users, there are nearly always things to work on. Maintainers just lose interest or don’t bother. This is as old as open source and it has nothing to do with LLMs, it’s only aggravated by it.

Hardly an issue with generated code. You could say the same about projects before LLMs were widely used for code generation: “most projects are abandoned within months of release”. The difference now is the scale and how some people feel about it.