-
Notifications
You must be signed in to change notification settings - Fork 65
General Discussion Thread. Say Hi.
#16
Comments
Hi :). No worries about the ticket feed. I might've associated your profile picture with your Github username, anyway thanks :) See you later. |
True, DorkNet is relatively slow since it basically emulates a browser. Also,i'm not sure whether i spoke to you on Twitter about DorkNet but i remember having a conversation about the amount of results. Like i said then, DorkNet was primarily designed to be used with a list of dorks, so 10 dorks, with 20 results per page works out to 200 results even though i am only processing the first page of results per Dork, I will check Googler out, since it sounds interesting. Is it fair to assume Googler makes use of the Google API? By the way, when do you expect to have a functional BETA for this project? Pretty interested to see how it will turn out. Keep up the good work 👍 |
It wasn't me since I'm not on twitter. I think that Googler makes use of the text browser available ( such as lynx ): ref. I think it'll be functional in two or three weeks, and pretty stable maybe in a month or two. In fact, if I reach a beta state I would be pretty happy :) |
Cool, good to know. Once you have a functional beta, let me know. I'll check it out, if it works well, i'll post a little bit about your tool on my Twitter feed, if that's alright with you. Will certainly help with exposure for your project (n_n") |
Sorry for cluttering up your ticket feed. Your code base has changed a lot since last i checked it, I was wondering are you still incorporating DorkNet or features derived from DorkNet? And if so, if you made some cool improvements, consider opening a Pull Request. At my repo:
https://github.com/NullArray/DorkNet
Of course you will be accredited for any contributions. Acknowledgements are important.
Also;
I'm actually VectorSEC on Twitter. I know, confusing. If you want we could make this the
General Discussion Thread
like we had with AutoSploitLemme know. See you on Discord.
The text was updated successfully, but these errors were encountered: