Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re^5: Do Not Feed the Trolls!!! (ban)

by ysth (Canon)
on Dec 24, 2007 at 10:09 UTC ( #658862=note: print w/replies, xml ) Need Help??


in reply to Re^4: Do Not Feed the Trolls!!! (ban)
in thread Do Not Feed the Trolls!!!

Sigh. Last time it was me, and I don't think I learned anything (other than to not do it again (or so I hope)).

Replies are listed 'Best First'.
Re^6: Do Not Feed the Trolls!!! (ban)
by herveus (Parson) on Dec 24, 2007 at 14:22 UTC
    Howdy!

    Been there, got all muddy. Remember, mixing it up with a troll usually involves descending to it's level, where it beats you with experience.

    yours,
    Michael
      mixing it up with a troll usually involves descending to it's level, where it beats you with experience

      That bit of wisdom actually applies to a flamer and not to a troll and this is an important distinction. As stated, I think that nugget is more likely to encourage people to try to "beat" a troll at some point.

      If you "mix it up with a troll", your experience at trolling or flaming makes little difference to the troll. If you win an argument, the troll doesn't care because they were just pretending to take the stance you argued against anyway. Even if they expressed something that they actually believe in, they still don't care because they can just pretend that they didn't believe in it (or pretend they didn't understand your argument or pretend any number of other things to see what reaction they can fake out of you next).

      And if you are trying to only respond to a troll's reasonable postings and only in reasonable ways so that they will see how much more rewarding reasonable discourse is, you are likely a fool still. If someone is still trolling, then their reasonable postings are most likely mostly fiction. Rewarding those with reasonable discourse just makes the troll laugh at the fool who believed the pretend tone, encouraging more trolling behavior, giving them one more type of bait to drag around waiting for the next gullible fish.

      Yes, given enough time, a troll will either leave or join (where "join" means stop trolling and start participating like a normal person not like a troll). But trying to encourage joining by demonstrating how reasonable discourse works isn't going to work while the person is still in trolling mode. I think that strategy is likely to be about as successful as trying to reform an alcoholic by demonstrating to them how much fun can be had with responsible, social drinking.

      - tye        

        Agreed, but then how do you win? Just don't answer them?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://658862]
help
Chatterbox?
[ambrus]: what push_write thing? I don't think you need that. that's implemented generically by AnyEvent::Handle
[Corion]: ambrus: Yeah, that's what I think as well. But you give me an idea, maybe I should start with implementing the timer, as that should be far simpler and with fewer edge-cases/nasty interaction than the file watcher
[ambrus]: You only provide the watcher part that tells when the handle is readable or writable, not the actual writing and reading.
[Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
[Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
[Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread
[ambrus]: You hvae to be careful with the timer, because apparently Prima::Timer insists on being periodic, wheras AnyEvent::Impl:: Whatever::timer should give a one-shot timer watcher

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (6)
As of 2016-12-08 12:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.