perl -e'$_="074043072044-12077033078038066035079-47127-26140-320640080
+89010097004110-66076";do{print chr$_+$;;$;=$_}for/(...)/g'

[download]
Looks like an UID, so that's nice.
Not too inspired for this one, just got the random idea to make this.

perl -e'$_="kJ/u,sGt: iABnWo%thhTe,r_ JPAeGrfl; KHGafcVkserr,";s/(.)(.
+)/$2/g;$|=1;do{print;sleep 1;$:=$_;print chr()x length$:for 8,32,8}fo
+r/\w+?\W/g'

[download]
Could've made it shorter, but I kind of liked using (.)(.) and a small bit of obfuscation, so sue me. :P.
Anyway, this one's based on something I saw here a while ago, but I can't find the node. It used the same type of "clearing" I'm using :P.
It's tested on Linux with gnome-terminal, so I don't know if it'll work on Windows, I hope so.


Anyway, hope you like them, and can find ways to golf these, the second one should be very golfable, not too sure about the first one :)

Replies are listed 'Best First'.
Re: A couple of snippets
by mk. (Friar) on Jan 13, 2006 at 12:30 UTC
    the second one is not actually that obfuscated, but i must say i really like the blinking idea.
    =)


    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    grrr.... argh!
[reply]
Re: A couple of snippets
by ww (Archbishop) on Jan 13, 2006 at 18:02 UTC
    re OP's observation/question on operability under W32:
    requoting the second snippet, first:
    perl -e"$_= qw(kJ/u,sGt: iABnWo%thhTe,r_ JPAeGrfl; KHGafcVkserr,);s/(.)(.)/$2/g;$|=1;do{+print;sleep 1;$:=$_;print chr()x length$:for 8,32,8}for/\w+?\W/g"

    prints

    <Reveal this spoiler or all in this thread>
    and -- again as you would expect -- "disappears" it.

    update: My bad! The plus sign before the first print (above) is an artifact of a dumb_job_of_copy_paste. NB, however: removing it (eh??? ) has no obvious impact on the output in the spoiler, above. However, requoting OP's first for windows as:
    perl -e "$_=qw(074043072044-12077033078038066035079-47127-26140-32064008089010097004110-66076);do{print chr$_+$;;$;=$_}for/(...)/g"
    produces precisely what one might expect.

[reply]
[d/l]
[select]
Re: A couple of snippets
by chargrill (Parson) on Jan 13, 2006 at 23:20 UTC
    Just as an FYI, the second one works just fine on a Mac, Perl 5.8.6.

    I suppose reading obfuscations easier comes from writing them. Without running it, I knew where the text was coming from, so I stopped reading after I assumed the sleep 1 put in a second delay between each character.

    Nice little surprise :)

[reply]

Back to Obfuscated Code