Building a Website That Can Do Everything #2: To-Do List with Admin Panel Interaction

[@Monkhaus]

THE RULES: 1. Try to not suggest vague / large features. 2. If the most popular feature is small, I might also implement the next most popular feature as well so definitely leave your idea below. 3. Try to be creative. Your idea does not have to follow on from a previous idea and doesn't have to be logical either. 4. You can suggest a technology with which you want to implement the feature. If not I will do it with whatever I think is easiest. Of course this won't always apply. 5. Try to not comment features that have already been commented

[@zakchips]

Another suggestion: video about caching. For example to take to third party packages (django-cacheops and cacheops) and compaire their pros and cons using simple project. I'd like to learn how to choose between alternatives. Thank you.

[@Monkhaus]

Hey always appreciate comments and suggestions but for this particular series I would love it if you gave suggestions in forms of features you want to see in this series. But i'll jot this down as an idea and try to work my way round to it. I might still implement your comment from the previous video too!

[@zakchips]

@@Monkhaus Quite strange but my previous comment might be deleted. I tried to share my github name and name of the project with nested comments (the way I implemented it). But YT doesn't like it although it wasn't even a link. ⛔

[@Monkhaus]

@@zakchips yeah that is weird, ns how you get around that lol. It's not in my held for review comments or anything. I think KZbin might be recognizing what a git username looks like and a repo. Could try without special characters if possible.

[@dodokwak]

There many ways how to protect your site from diff bots. I can mention a honey pot field in a form. Are their other ways to protect our forms? If my user needs to authenticated, if it enough not to worry about bots?

[@Monkhaus]

I don't know loads about this stuff, but I guess some traditional ways are captchas or rate limiting if you're using an api for example. But user authentication is definitely a really good way to avoid bots assuming the authentication isn't too simple. If they require email verification for example that would definitely make it harder for bots, especially if emails need to be unique. But a honeypot field seems like a good approach too. I wasn't sure if this was just a question, or if you want me to implement a feature regarding this. If so, feel free to respond and add some more info, or a more specific request (but don't feel obliged 🙂)

[@dodokwak]

@@Monkhaus Yes, that was my question. I've seen strange bot's activity when user needed to be auth-ed. Somehow they managed to force the defense.