Re: Retardedness

Let's see what "Kadaitcha Man" <***-you.ya.***@xxxxxxxxxxxxxxxxxxxxxxxxx>
has up their dress.

>useit@xxxxxxx, <useit@xxxxxxx>, the misanthropical, brainwashed grease
>stain, and boiler attendant, drawled:
>> Let's see what "Kadaitcha Man"
>> <***-you.ya.***@xxxxxxxxxxxxxxxxxxxxxxxxx> has up their dress.
>>
>>> useit@xxxxxxx, <useit@xxxxxxx>, the anterior, scatterbrained
>>> spleenwort, and keeper of the market stall, oozed:
>>>> Let's see what useit@xxxxxxx has up their dress.
>>>>
>>>>>
>>>>> What's the deal;
>>>>
>>>> ...thanks to all for participating... ;->
>>>
>>> Much to my surprise, Gazwad helped you; I certainly wasn't going to.
>>> Indeed, he gave you accurate advice. It's entirely your problem if
>>> you're too fucking dense to figure it out.
>>
>> When does anything ever surprise you anymore?
>
>Just then. You being a nix*** and all.

Good, then.

>> Moreover, you are correct in that his advice was indeed correct.
>>
>> However, what's the deal?
>>
>> I heard on the grapevine, that you've written some new NNTP code
>> that's *fast*. You have anything juicy that does *fast* and
>> *efficient* reverse DNS lookups?
>
>Yes, I have written some extremely fast and sophisticated NNTP code. No, I
>have not written any reverse DNS code.
>
>I wrote the NNTP code because I was right pissed off at Indy.Sockets, which
>kept destroying subject and organization headers by translating normal text
>into UTF-8 ***. Of course, the fuckwits at Indy blamed .NET 2005 for being
>Unicode-based. It seems odd that I could write my own NNTP code and never
>have such an issue at all.

Much to my surprise and chagrin, I have accepted .NET as a *solid* and
*genuine* platform, notwithstanding the obvious relevance of JAVA, still.

>You have a few choices for DNS. Check out Indy.Sockets, which is freeware,
>or use the DNS class in .NET 2005, for example. The DNS class supports:

The deal is; apart from some "bare bones" knowledge of pure "C", when I
need to write a wrapper, or need something to execute *fast*, I'm too lazy
to learn anything other than highly interpreted languages. Therefore, shell
scripts and similar remain standard fare.

>BeginGetHostAddresses: Asynchronously returns the Internet Protocol
>(IP) addresses for the specified host.
>
>BeginGetHostByName: Begins an asynchronous request for IPHostEntry
>information about the specified DNS host name.

Yeah, they're the standard methods, API wise.
However, the reasons for avoiding this are manifold. Most pertinent are:
1. As above, I don't want to write anything this way.
2. I have issues with these mechanisms anyway, as I just want to *quickly*
write, *modular* and *portable* snippets of code, and require more
extensibility in terms of returned information. Sure I can just write a
script to parse any kind of verbosity, but then, why not just write a
script to do it *all* in the first place?

Point is; "piping" a few scripts onto each other with a few supplied
arguments, such as the actual "SOA Domain Server", and info I want returned
is trivial, and is invaluable when parsing "web logs", using other tools
etc. Bots love this kind off stuff, it gives them stuff to eat.

Mind you, there is always more than one way to "Pluck-a-Penguin".

>> Furthermore, do your bots "play well" with others?
>
>What is that supposed to mean?

I can foresee the forthcoming "war of the NNTP bots", and as a result, I am
already formulating a contingency plan, so; whomsoever enters into any
conflict, may need an army, or army of one...

PS: And a big *THANKS* to all those who *clicked* on the provided links...

--

Leela: "It's the twentieth century, professor!"
Professor: "Oh, right! I'll have a croque monsieur, the paella, two mutton
pills and a stein of mead."
http://203.102.255.156/downloads/misc/19.mp3


.