Difference between revisions of "Talk:1963: Namespace Land Rush"
Snowblinded (talk | contribs) m |
|||
Line 19: | Line 19: | ||
So '''OkThisIsKindOfConfusingButIt's <LessThan\ForwardSlashHTML GreaterThanActualGreaterThan Symbol>Yes,ThatWasAllPartOfThe Name,ButSoIs...Ok,LetMeStartOver''' actually is "<<\/HTML>> or is it just supposed to be </HTML>? [[Special:Contributions/141.101.105.180|141.101.105.180]] 13:46, 6 March 2018 (UTC) | So '''OkThisIsKindOfConfusingButIt's <LessThan\ForwardSlashHTML GreaterThanActualGreaterThan Symbol>Yes,ThatWasAllPartOfThe Name,ButSoIs...Ok,LetMeStartOver''' actually is "<<\/HTML>> or is it just supposed to be </HTML>? [[Special:Contributions/141.101.105.180|141.101.105.180]] 13:46, 6 March 2018 (UTC) | ||
+ | :: Do you really think there's a definitely correct answer to that question? [[Special:Contributions/162.158.155.38|162.158.155.38]] 14:25, 7 March 2018 (UTC) | ||
+ | |||
* I am not confident enough about this to make the edit myself, but wouldn't the names listed in '''Causing Trouble (Usernames that might cause errors when mixed with the service's back-end code)''' (user, guest, etc) be used not so much to trying to fool other people, but because those names are often used as placeholders when the site is in development, and may therefore still have odd/altered permissions, allowing potential malicious access assuming the devs were lazy? [[User:Snowblinded|Snowblinded]] ([[User talk:Snowblinded|talk]]) 18:04, 6 March 2018 (UTC) | * I am not confident enough about this to make the edit myself, but wouldn't the names listed in '''Causing Trouble (Usernames that might cause errors when mixed with the service's back-end code)''' (user, guest, etc) be used not so much to trying to fool other people, but because those names are often used as placeholders when the site is in development, and may therefore still have odd/altered permissions, allowing potential malicious access assuming the devs were lazy? [[User:Snowblinded|Snowblinded]] ([[User talk:Snowblinded|talk]]) 18:04, 6 March 2018 (UTC) |
Revision as of 14:25, 7 March 2018
- Ahh, he left off root under Causing More Trouble. Nutster (talk) 05:41, 5 March 2018 (UTC)
- Also "null"... 162.158.62.237 21:09, 5 March 2018 (UTC)
- I'm very disappointed he left out dotnotreplay@... --05:43, 5 March 2018 (UTC)~
- Is "gibberish name no one can pronounce" a reference to xkcd? 108.162.215.64 05:56, 5 March 2018 (UTC)
- No test included. Frankly speaking I have seen people using testtest,testtesttesttest, and so on, up to the maxiumn allowed character limit. Jackomatt (talk) 06:35, 5 March 2018 (UTC)
- Took me some time to type the transcript. Randall made it quite hard. Klyxm (talk) 06:38, 5 March 2018
- The thing at the bottom-right, he wrote "forward slash" but used a backslash. 162.158.126.76 08:35, 5 March 2018 (UTC)
- Null! Where's null? PenguinF (talk) 09:14, 5 March 2018 (UTC)
- I think this whole comic is a reference to the video Worst Wifi Password Ever [1] --162.158.238.76 11:13, 5 March 2018 (UTC)
This is analogous to the way that land was distributed in America
There is so much wrong with that sentence. --162.158.154.25 12:26, 5 March 2018 (UTC)
- I think is what he means by rtl override: https://krebsonsecurity.com/2011/09/right-to-left-override-aids-email-attacks/ and I agree surprised he didn’t include the null character; maybe because it’s so hard to get it to actually reach the service? 172.68.54.136 15:24, 5 March 2018 (UTC)
- Emojis don't work in databases? They should be treated no differently from any other UNICODE characters. They would be hard to type if you're using an OS/browser that doesn't have a convenient Emoji-picker, but I would think that they should work as long as the server isn't filtering them out. But I've never deployed a service like this so there may be something important I'm missing here. Shamino (talk) 17:53, 5 March 2018 (UTC)
- The "emoji not work" refers specifically to emojis requiring four characters when encoded in UTF-8, as many programs including databases like MySQL used to only support three-byte UTF-8 characters. There are emoji which fits into three bytes and non-emoji characters requiring four bytes, but for most people, support for four-byte UTF-8 is equivalent to support of (new) emoji. -- Hkmaly (talk) 00:56, 6 March 2018 (UTC)
- (Obviously, when you want to test database, you should be creative and instead of "any" emoji try something like "fairy girl with dark skin tone" 🧚🏿♀️ - that's five UTF characters, 18 bytes total, and is supposed to render as single character) -- Hkmaly (talk) 01:08, 6 March 2018 (UTC)
Someone once told me that on old email databases, you could send a message to "*@example.com" and it would send the message to everyone with an account on that domain. No idea if its true or not, but it seems like the username "*" could cause problems. 162.158.75.16 19:56, 5 March 2018 (UTC)
So OkThisIsKindOfConfusingButIt's <LessThan\ForwardSlashHTML GreaterThanActualGreaterThan Symbol>Yes,ThatWasAllPartOfThe Name,ButSoIs...Ok,LetMeStartOver actually is "<<\/HTML>> or is it just supposed to be </HTML>? 141.101.105.180 13:46, 6 March 2018 (UTC)
- Do you really think there's a definitely correct answer to that question? 162.158.155.38 14:25, 7 March 2018 (UTC)
- I am not confident enough about this to make the edit myself, but wouldn't the names listed in Causing Trouble (Usernames that might cause errors when mixed with the service's back-end code) (user, guest, etc) be used not so much to trying to fool other people, but because those names are often used as placeholders when the site is in development, and may therefore still have odd/altered permissions, allowing potential malicious access assuming the devs were lazy? Snowblinded (talk) 18:04, 6 March 2018 (UTC)