Project/Code improvements

[VamatoHD]

Discussion related to improvements that could be made in the overall project and in the code.

[VamatoHD]

@kaifcodec I've opened this discussion since I had some ideas to improve the code, such as:

• Like other projects, each category could be under a folder called modules or categories, allowing for a cleaner project structure;
• Maybe using a random user agent for each request, primarily in permutations, is a good idea;
• Shouldn't the GitHub action checks be checked on every push in order for the user to know if the contribution passes before opening a PR?

[kaifcodec]

Yeah, previously the workflows were configured to run only on pushes and pull requests targeting the main branch. You were probably pushing to a sub-branch, which is why they weren’t running. I’ve fixed that now, so once you sync your branch, it should work as expected.

Regarding the categories and new folder structure, I think I suggested a similar approach in discussion #119 as well?

[VamatoHD]

Regarding the categories and new folder structure, I think I suggested a similar approach in discussion #119 as well?

Yes, you're right.

[kaifcodec]

@VamatoHD regarding the suggestions you mentioned at the end of the #119 discussion:

I’d prefer not to structure the codebase that way, because it will make maintenance harder when a site’s API URL or configuration changes.

Keeping separate modules for each site helps a lot with readability and long-term maintenance. It also gives us the flexibility to define custom headers, request bodies, and logic per site, which is often necessary and cleaner than trying to generalize everything too early.

[VamatoHD]

@kaifcodec have you heard of Issue templates? It would allow us to have, for example, a checkbox for whether the user has tried updating to the latest version before submitting an issue.

[kaifcodec]

@VamatoHD Yeah, I’m aware of issue templates. Earlier, issues weren’t frequent enough to justify adding them, so I didn’t prioritize it.
If you’d like to add them, feel free to go ahead. I’m currently more focused on adding support for new sites.

[shredzwho]

@kaifcodec can we add stealth integration into this (we will make it optional) , so that requests look legit, we can add libraries like a playwright-stealth, and build a custom XCSRF and CSRF token forger(if we are planning on scrapping more details on usernames)

[shredzwho]

trust me when I implemented curl_cffi, in my IG-detective project, results were not happy

[kaifcodec]

@shredzwho Ok, go on if you want to implement it. Open a Draft PR from the start of your work so we can push commits to it together.

[shredzwho]

alright I'll draft a PR by 8PM GMT Mumbai

[kaifcodec]

Yeah no worries, no rush, take your time learn about the core files and open it.

[shredzwho]

alright chief you got it

[shredzwho]

By the way I noticed one thing, documentation is missing in this project.. are you guys working on it ?

[kaifcodec]

Documentations for what?

[shredzwho]

Documentation like instructing architecture, core modules and additional info

[kaifcodec]

The installation guide, library usage instructions, and other details are already covered in the README.md and the docs/ directory. I'm not sure what specific documentation you are referring to. Could you clarify?