Log in to your ChatNet account to give feedback

Feature Requests

Spammer issues, spammer bypass captcha, flood control, crashing the site.
Please see my regular user and mod feedback: happening on https://chatroom.talkwithstranger.com/ I turned on guest accounts again cause theres NO POINT disablng them when the spammers make an account in seconds cant turn on email verification cause you dont have that set up so there would be 0 new users with that enabled and guests disabled. captchas are useless as the spammers have bots to bypass captchas so just so you know martin can spam main chat EVEN WHEN ITS CLOSED i kicked and inactived him to stop spam closed main he logged into a new guest (verified by ips of a member and other guests kicked) and main has NOT been re-opened the message count on the dashboard keeps rising significantly this was at 11k about 20 min ago ... he has since stopped on his own but it went up AFTER he was kicked and he rejoined on a new guest (verified by IP) so there is nothing we can do ..... been dealing with this for an hour DO YOU NOT READ HE MAKES REGISTERED ACCOUNTS IN SECONDS i was told by a coder mod the code for genderchat is public there is a backdoor only you have access to change the codes Janet, 8:49 PM keeping main closed so the site doesnt crash and aimee and i are deleting mains chats when he spams to decrese site lag we have a private passworded chat for regular registerd users for now you really do not read what i type do you. and you do not know about temp emails and auto confirm emails? he knows how to bypass all that 100% he can bypass that in less than a few min and besides you didnt even read that he cant be kicked half the time and he can spam EVEN IF CHAT IS CLOSED several mods know how to bypass email verifications they said the only thing that can fix the site is fixing the code the site code what the fuck dude are you seriously this clueless we have mods that have emailed you several times about what needs to be fixed on all your chats idk about code but saw several mods laughing at the security of genderchat coding.. its all shit they said its not secure theres backdoors and people can change things to spam anyone can do it they said the code is public. Please fix all these issues asap to stop spammers. spammers are spamming the public groups chats where each new user joins by default, they send too many msgs every few seconds using JS bot code at client side, and your flood control and captcha are useless especailly they make dummy fake guest accounts, even they make so many registered accounts so fast to continue spamming. please fix all these issues. when will you release the new update for all these issues?
0
List of improvements to integrate
Here is a list of my improvements to integrate, each with a short explanation : Reorganize the project following MVC (or a clean structure) o Why? Separating responsibilities (Controllers, Models, Views) makes the code more readable and maintainable. Refactor controllers o Why? Splitting large methods into smaller private methods and avoiding deep if nesting improves clarity and testability. Use a dedicated router (AltoRouter, FastRoute, etc.) o Why? Avoid manually handling $_GET; a routing library streamlines route definitions and maintenance. Adopt PSR-4 for autoloading & PSR-12 for coding style o Why? Adhering to standards ensures consistent structure, better teamwork, and easier integration with tools (linters, IDEs). Centralize configuration o Why? Keep logic and parameters (DB credentials, API keys, etc.) separate; simplifies environment management (dev/staging/production) and boosts security. Separate frontend assets in a public/ folder o Why? Clearly isolate CSS, JS, media, and prevent direct access to sensitive code outside the public directory. Validate and escape all user inputs o Why? Prevent XSS and SQL injection attacks. o How? Use prepared statements (PDO) for queries, htmlspecialchars() for output, and a centralized validation library (Valitron, Respect\Validation, etc.). Implement CSRF protection o Why? Block malicious attempts to make a user perform unwanted actions (Cross-Site Request Forgery). o How? Generate a session-based token, add it to forms, and verify on submission. Control or sanitize redirects o Why? Avoid Open Redirect vulnerabilities by only allowing safe, expected URLs. Optimize database queries o Why? Improve performance and reduce load. o How? Add indexes on frequently used columns, reduce repeated queries (cache some data in sessions or memory). Factor out common code o Why? Avoid duplication (e.g., reCAPTCHA checks, Twig rendering). Centralize this logic into helper methods or services. Use a proper templating structure (Twig, Blade, etc.) o Why? Create reusable layouts (header, footer) and specific templates for each page or section. o How? Organize them in separate folders (templates/admin/, templates/auth/, etc.). Secure and isolate the installer/ folder o Why? Installation/upgrade scripts should not be publicly accessible in production. o How? Restrict access (via .htaccess or server config) or remove the folder after setup. These improvements will make your application more secure, performant, and maintainable.
0
Load More