Validation of javascript forms - name, password, password retype validation and Number Validation
It is critical to check the user-submitted form since it may include incor- rect information. As a result, validation is required to authenticate the user. Because JavaScript allows form validation on the client side, data processing is faster than server-side validation.15 JavaScript form validation is preferred by the majority of web developers. We can validate name, password, email, date, cell numbers, and other data using JavaScript. https://chat-to.dev/post?id=12#javascript#web#programmer
Even with a strong Captcha system in place, you will still find users trying to manually spam your web site. They tend to be people who discover your site through a very specific search engine query, for which they would like their own site to also rank well, and they hope that by adding a link back to their site from yours this will happen. Using this recipe, you can specify a set of keywords that will trigger spam detection, and then use the level of spam certainty returned by the function to decide whether to ignore a user post. https://www.chat-to.dev/post?id=11#php#programming
Sure… But assuming you’re running a business, and you want potential future customers to be able to reach you… then you need some sort of contact form, and you’ll get spam on that form which is annoying.
use any fonts you like on your web pages thanks to this recipe.
Although web browsers come with a reasonable range of default fonts, they don’t always provide the look you need for a particular web site. In such cases, you usually must resort to calling up a graphic editor and creating logos or headlines there. However, with this recipe all you have to do is upload the TrueType fonts you wish to use to your web site and you can then display text in these fonts by having the GD library convert it on the fly to GIF images. https://chat-to.dev/post?id=9#php#backend
When accepting user input for redisplay, and particularly if it will be inserted into a database, it’s important that you sanitize the input to remove any malicious attempts at hijacking your server, or otherwise injecting unwanted MySQL commands, HTML, or JavaScript. https://chat-to.dev/post?id=6
FANTASTICO! this site led me to learn more about the BOSSES ;) in video games
i've changed the appearance (layout) of the biggest video game site. do you know it? https://playstationcouch.com
why node.js makes me uncomfortable
I've always programmed with php for the web and during that time I've never needed to download packages (like npm) and update them. When I needed a specific function, like sending emails, uploading files or making my application drier, I just had to look at the documentation and implement it. But with node.js it doesn't work like that, and that bothers me. If I'm wrong, please correct me
You’re not wrong. Dependencies pulled directly from other developers get very little oversight compared to a language’s standard library. They introduce more opportunities for failure and increase the attack surface in your software. (The latter is at the core of the so-called supply chain attacks that have been in the news lately.)
To be fair, the problem is not unique to Node.js. Rust has it too, as does every other platform that encourages developer-to-developer library sharing.
The lesson is to be judicious with your dependencies. Look for the functionality you need in your language’s standard library first, and then in the standard software archive maintained by your target OS. (Packages that are officially part of the major Linux distros, for example.) If you can’t find it in either of those places, consider whether you truly need it, or whether writing a minimal implementation yourself would make sense.
In cases where you really must use some random person’s library, look for one that’s widely used, responsibly maintained, and ideally, small enough that you can keep track of its changes between versions. The responsibility for protecting your users is yours.