Summary of Reddit Comments on "Phishing Detector"

Project Review and Suggestions

• Docstrings: Commenters highlighted the need for improved Docstrings to describe methods better.
• Effort and Documentation: Emphasis on detailing the project's AI aspect for cybersecurity and building trust.
• Tests and Demonstrations: Suggestions to add tests, including behavioral-driven ones, and demonstrations using Selenium.
• Code Organization: Recommendations for organizing code into folders and files for clarity and easier maintenance.
• Unit Testing: Suggested setting up Jest for Unit Testing.
• GitHub Publishing: Advised against publishing to GitHub unless creating a library for import.

Concerns and Trust Issues

• Trust and Security: Strong sentiments against installing a "school project" extension due to Trust and Security concerns.
• User Responsibility: Advocacy for users to learn internet security instead of relying on AI.
• Code Verification: Doubts about trusting uploaded extension code matching the source code.
• Extension Safety: Caution against using unknown extensions in Chrome, emphasizing potential risks.

Viability and Implementation

• Local Flask Server: Positive feedback on hosting the project on a local Flask server for a school project.
• Phishing Data Training: Recommending pre-built models for quicker start and accuracy, highlighting the challenge of training on real phishing data.

General Comments

• Positive Feedback: Appreciation for the project as a legitimate effort.
• Grandma Reference: Mention of the risk associated with unknown Chrome extensions, especially for less tech-savvy users.

Overall, the comments provide a mix of feedback on project documentation, Code Organization, trust issues, security concerns, and implementation suggestions for the "Phishing Detector" project.