If it does, then it turns out that there is this tiny bit more than JS validation as you said.
-
-
Replying to @klon
Point is there's no server side validation for who is supposed to have the feature available.
1 reply 0 retweets 0 likes -
Replying to @marcan42
Point is, it still requires some technical knowledge most of the people don't have to (ab)use so it really doesn't matter...
1 reply 0 retweets 0 likes -
Replying to @klon
Mental note: you're banned from security work for anyone I work with :p
1 reply 0 retweets 1 like -
Replying to @marcan42
Mental note: you're banned from work involving risk or impact calculations for anyone I work with :p
1 reply 0 retweets 1 like -
Replying to @klon
Let me know what your mitigation is for all the tweets with >140 CJK chars being posted in violation of intended policy :p
1 reply 0 retweets 0 likes -
Replying to @marcan42
Let me know why anybody should implement a mitigation for something that is having little to no impact on data, users nor the company.
1 reply 0 retweets 0 likes -
Replying to @klon
So you're saying it's okay to let users *permanently* make posts *against* the rules, thus polluting the DB with inconsistent data?
1 reply 0 retweets 0 likes -
Seriously, I hope I never have to fix a system you designed or audited :p
1 reply 0 retweets 0 likes -
Replying to @marcan42
You could have fitted that in a 280 character tweet, yet you didn't. Why?
2 replies 0 retweets 0 likes
Because I'm having a coffee with my family and not really intent on reverse engineering this on my phone.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.