|
Joined a week ago, first post, site driving to his DB GUI app: Joe Ngg - Professional Profile[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
modified 21-May-18 11:30am.
|
|
|
|
|
|
.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
|
|
I just realized that some of the emoji are offensive. I am wondering if Chris should add some code to filter out some of these Unicode characters.
🖕
I looked through them all but this was the only one I find offensive. I think some sites are also filtering out the guns.
What do you protectors think?
Best Wishes,
-David Delaune
|
|
|
|
|
I read somewhere recently that a lot of font providers (social media outlets included) are replacing the gun graphics with water pistols and otherwise sanitising the rendering of emoji.
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
it doesn't show anythign on my side, just a square
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Wow - nicely spotted. I've added this to the bad word filter and will deploy after this messy Canadian long weekend is over.
cheers
Chris Maunder
|
|
|
|
|
|
|
|
|
gone
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
.
667: The neighbour of the Beast
|
|
|
|
|
|
.
667: The neighbour of the Beast
|
|
|
|
|
|
gone
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
Possible he is the author of the book? Look like most of the contents were copied from the book.
For instance, just to point out a few, the below paragraphs are from page 106
Quote: First: anything that comes from the outside world should not be trusted initially. Malicious users can enter all sorts of exploits through a form that can undermine the security of your site. So, any form data must be sanitized before you use them.
Secondly: the field values in request.POST or request.GET are just strings. Even if your form field can be defined as an integer (say, age) or date (say, birthday), the browser would send them as strings to your view. Invariably, you would like to convert them to the appropriate Python types before use. The form class does this conversion automatically for you while cleaning.
page 109
Quote: CSRF_Token is the security mechanism against Cross-Site Request Forgery (CSRF) attacks for your forms. It works by injecting a server-generated random string called a CSRF token, unique to a user's session. Every time a form is submitted, it must have a hidden field that contains this token. This token ensures that the form was generated for user by the original site, rather than a fake form created by an attacker with similar fields.
Bryian Tan
|
|
|
|
|
Well ... the names aren't even close, and if you wrote a book on this, and you copied whole passages for an article wouldn't you want to reference the original in the hope that someone might buy it?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
"This is the third article..."
Did you look at the other two?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|