Leet Lord's Prayer
Everything2's Mikebert has posted a leet-speak Lord's Prayer that begins, "Our sysadmin, who chills in Heaven,
feared be thy name."
0ǔr $¥$@dM!n, \/\/|-|0 ©|-|!££$ !n |-|34\/3|\|Link (via Making Light)
ph34r3d β3 7|-|¥ |\|@m3
†|-|ÿ p\/\/n@g3 ©0|\/|3, †|-|ÿ $©r!p7$ b3 d0|\|3 !n /earth @$ i7 !$ i|\| /heaven.
$33|) u$ 7h!5 |)@ÿ oǔR d@!£ÿ R0|\/|$.
f0rG!\/3 u$ 0ǔr n00b 3xP£017$ @$ \/\/3 f0rG!\/3 $©r!P7 | R3\/34£ t0 u$ |\|07 Ζ3R0 |)@ÿ \/u£|\|$, βu7 $A\/3 u$ fR0|\/| t3h RIAA.
f0r 7|-|!|\|3 i$ t3h |\|37\/\/0R|<, @|\|d t3h rm -rf*, @|\|d @££ 0ǔR β@$3 @r3 β3£0|\|G t0 j00, f0R3\/3R @|\|d 3\/3R.
4|\/|3|\|.
the latest
latest episodes
Good Lord!
Could someone slightly more fluent in Leet post a translation? I spent 5 minutes trying to just understand the first line, and it's already translated...
Our sysadmin, who chills in Heaven, feared be thy name.
Thy pwnage come, thy scripts be done in earth as it is in heaven.
Send us this day, our daily roms. Forgive us our noob exploits as we forgive script reveal to us not zero day vulns, but save us from the RIAA.
For thine is the network, and the rm-rf*, and all our base are belong to you, forever and ever.
Amen
Think that's what it says.. what the hell is a vuln.. and a rm-rf*?
Vuln is vulnerability, rm -rf * is a linux command. -rf deletes files recursively (r) and without prompting (f for force), and * means everything. rm -rf / is more dangerous
It's also "Seed us this day"
oh yea, seed.. I wonder why I put send. Hmm. I still don't get it.. and I'm shocked I could actually make that out.. too much world of warcraft maybe (:
Thanks for the explanation corpse.
"R3\/34£ t0 u$ |\|07 Ζ3R0 |)@ÿ \/u£|\|$, βu7 $A\/3 u$ fR0|\/| t3h RIAA"
I really love this line. Very topical.
I have a feeling I saw something similar (including the "All your base" reference) quite a few years ago. Like, when people still made "all your base" cracks...
I'm a little shocked I can make it out too.
700 |V|u
This has got corrupted somewhere. The second half of line 5 is missing and line 6 has been concatenated on the end. Which makes it even harder to decipher. The original is here.
I am not leet, but as it was explained to me, using a leet substitution for every single character isn't leet, it's trying too hard.
Looks more like the Spam I get on a regular basis.
c|-|E4p \/1@gr4 4 u 2 [u/\/\
Could somebody translate that into Klingon so I can read it??
:P
@Kieran:
Yes, the older version that's FAR easier to read is this:
Our Father, who 0wnz heaven, j00 r0ck! May all 0ur base someday be belong to you! May j00 0wn earth just like j00 0wn heaven. Give us this day our warez, mp3z, and pr0n through a phat pipe. And cut us some slack when we act like n00b lamerz, just as we teach n00bz when they act lame on us. Please don’t give us root access on some poor d00d’z box when we’re too pissed off to think about what’s right and wrong, and if you could keep the f3i off our backs, we’d appreciate it. For j00 0wn r00t on all our b0x3n 4ever and ever, 4m3n.
@8 -- The standard WoW "leetspeak" is a very watered-down version. As I've known it for something like 15 years -- since the days of 1400bps modems and BBS's -- genuine leet looks like this prayer, here.
@13
I know exactly where you are coming from and I'd argue that while this is indeed a more accurate representation of oldschool leetspeak it still goes a little too far. At least the people I remember on BBSs (dude, its plural not possessive) and IRC wouldn't go so far as to spell out every single word in such a manner. Just the ones they thought could throw up flags to the sysop or perhaps Echelon (yes, they were often that full of themselves).
*cough* BBSes, not BBSs. :)
*cough* ANDREWJC's wrong */cough*
Bit of a quick test: If there's no text after the unescaped less than, you guys probably need to be taking a look at how you handle form input in this system. (I say this because my previous post got truncated...)
Less than sign, XML-escaped: <
Less than sign, unescaped:
Some stuff which will probably get truncated.
One more test, a less than followed by some garbage without any whitespace, then some garbage seperated by a space, then some carriage returns and a Hmmm...:
Hmmm...
OK, so your system kills anything after a "<", probably while trying to treat it as an XHTML tag, but only on the same line...
Perhaps, if there's a < and no valid (or permitted) tag, you should just escape it, and put in whatever follows verbatim?
Anyway, what I meant to say earlier was:
"700 |V|u<|-| 1|\|73r|\|37$"
(And that will teach me to escape my l33t when pasting it into an XHTML-based system.)
lol.
For us n00bs, how do you "escape" such a symbol?
LOL Hilarious. omg... I loved that it used geek lingo together with the leet. I'll be spamming my friends with links.
I wonder if that's what's intermittently been eating Antinous's comments?
@20: You can escape "<" by writing it "&<".
All XML reserved characters have to be scaped in this way (by being enclosed between "&" and ";").
Of course, the BB software tries to intelligently escape these for you, so you shouldn't have to worry, but it's struggling with <, most likely because they need to allow some through when they form parts of %lt;a> tags.
Another test case for the broken functionality:
1. Enter some text with an escaped < into the comment box.
2. Click preview - the text in the comment box appears with the < unescaped (just "<", not "<").
3. Click preview again - the < and everything after gets truncated.
OK, you most definitely do not escape it by writing "&<", you escape it by writing &<;.
(But of course I'm having to escape both the & and the < there, which is not helping.