tbuehlmann / ponder Goto Github PK

Implement a ban method.

Get on :on user_mode event handler.

Auto rename does not work as intended.

Get MODEs after joining a channel. Adapt the on :join handler. Let's have two, one "raw" after joining and one "initialized" one for the moment we got the user list and modes?

Also, parse incoming mode answers, like 324, 329.

Update README regarding :defer => true and Async IRC methods.

Remove code for popping a queue for async responses and rewrite it with EM::Deferable.

Have a configuration for hiding PING PONG events.

Add some information about EM::Timer and EM::PeriodicTimer.

Get DCC support for sending files.

Add Formatting information to the README.

Get on :channel_mode event handler.

Rewrite tests. Test async methods with an emulated an IRC Server. Rewrite test_helper, remove Pathname. Test filters.

Would be nice to have ISUPPORT: http://www.irc.org/tech_docs/draft-brocklesby-irc-isupport-03.txt.

Try to have all known users (in @user_list) to be as up to date as possible. Update user data on whois and other events.

I want an on :disconnect { … }!

Have a config option for rejoining a channel after being kicked.

Add a redis Last Seen example.

More Wiki contents needed.

• Mention that in the on :join handler the user has no access to the channel's user list or chanel modes.

Use Travis CI's Build Matrix for testing different EventMachine versions.

Rewrite Logging.

Add Notifications to be able to do metrics and debugging. Maybe logging through Notifications?

Move stuff from https://github.com/tbuehlmann/ponder/blob/7af6ffcb53e364f9077e26b9bf28583403721e08/lib/ponder/irc.rb to the User and Channel classes.

The examples could need an overhaul.

Don't defer each and every callback, let the user decide whether the processing should be defered.

Something like:

@ponder.on(:channel, :defer => true) do |event_data|
  # ...
end

Hi, is there anyway to disable the bot from logging to stdout?

Exceptions thrown inside an on-block will be handled. When using Async methods like whois, the provided callback/errback code will run inside the EM-reactor and won't be exception handled. Example:

@ponder.on(:channel, /foo/) do |event_data|
  # does not explode
  1/0
end

@ponder.on(:channel, /!explode/) do |event_data|
  whois = @ponder.whois('foo')

  whois.callback do |whois_data|
    # does explode
    1/0
  end
end

I'm pondering about using Fibers to stop execution on whois and resume it when the whois_data has arrived. Will also reduce entangled evented spagetti code. Gonna check if possible and non-blocking..