Re: Why code is not posting

One might wonder why you've basically asked the same question with slight variations (differing mainly in where you're trying to post something) several different times.

Not to mention I doubt you're going to find many people willing to help you implement what looks like comment spamming.

Comment on Re: Why code is not posting

Replies are listed 'Best First'.
Re^2: Why code is not posting by monarch (Priest) on Nov 30, 2005 at 23:21 UTC
If indeed you are intending to comment spam then the best lesson I can give you is this: Automated rubbishing of human-oriented environments (like forums, e-mail, IRC) is hated by professional programmers everywhere. We all want to use technology to better our lives, but the pollution of automated scripts advertising where only humans should tread only makes life worse for EVERYONE. You ruin a customer experience. You make programmers attempt to find ways of minimising automated script invasion (extra work). You devour the economy by wasting money, resources, and time. So, unless you're completely stupid, do not underestimate how strongly the professional computing community would react to you if they learnt you were undertaking automated pollution activities.	[reply]

Replies are listed 'Best First'.

Re^2: Why code is not posting
by monarch (Priest) on Nov 30, 2005 at 23:21 UTC

Automated rubbishing of human-oriented environments (like forums, e-mail, IRC) is hated by professional programmers everywhere.

We all want to use technology to better our lives, but the pollution of automated scripts advertising where only humans should tread only makes life worse for EVERYONE.

You ruin a customer experience. You make programmers attempt to find ways of minimising automated script invasion (extra work). You devour the economy by wasting money, resources, and time.

So, unless you're completely stupid, do not underestimate how strongly the professional computing community would react to you if they learnt you were undertaking automated pollution activities.

[reply]