I know it's the age of ai, but one should do a little checking oneself before posting ai generated content, right? Or at least one should know how to use git and write meaningful commit messages?

1. there are hallucinatory descriptions in the Readme (make test), and also in the code, such as the rate limit set at line 158, which is the wrong number

2. all commits are done on github webui, checking the signature confirms this

3. too verbose function names and a 2000 line python file

I don't have a complaint about ai, but the code quality clearly needs improvement, the license only lists a few common examples, the thresholds for detection seem to be set randomly, _get_stargazers_graphql the entire function is commented out and performs no action, it says "Currently bypassed by get_ stargazers", did you generate the code without even reading through it?

Bad code like this gets over 100stars, it seems like you're doing a satirical fake-star performance art.

My memory is not very good, but it seems that something similar has happened 4 years ago, do you remember?

Specifically, I'm looking for help from some people who have experience with reversing on the Mac OS platform, and I'd like to address this issue, which is about how binary relocations handle memory addresses on Mac OS.

https://github.com/Zxilly/go-size-analyzer/issues/242

gsa obtains the memory address by calculating the address expression in the dwarf, and subsequently looks for the static content in the binary that actually corresponds to the memory address, but when the macho file contains relocations, the calculated memory address needs to be relocated with the same logic to get the correct binary content. I've been working on this problem for a while, but I'm really not familiar with the macho structure and I don't own a macbook, I'd like to get help from developers who have experience in this area.

Well, it's really hard.