20:22 <tinnvec> in the vein of making a plugin into a gem, how to implement Authentication feels a bit muddy

20:23 <tinnvec> I'm not sure if I should include the "enable_authentication" and associated parts in the main plugin file (like it is currently, in the plugin's non-gem state)

20:24 <tinnvec> or if the example shown in the authentication documentation would work without having the associated include and such in the plugin

20:24 <tinnvec> https://github.com/britishtea/cinch-authentication/blob/master/examples/channel_status.rb

20:25 <tinnvec> sorry, had wrong link on copy, this is correct one: https://github.com/britishtea/cinch-authentication/wiki/Configuration

20:26 <tinnvec> and I'm referring to the "per-plugin basis". I may also be misconstruing the "Admin" that is being used in this example as well

20:27 <leftylink> hmm... it is a bit confusing to me because that looked like authorization rather than authentication, but I will attempt to press on. also, I interpret that Admin is the name of some plugin

20:28 <leftylink> yeah Admin has to be a plugin since it's being pushed onto c.plugins.plugins

20:28 <tinnvec> ah okay, maybe that's where I'm getting confused then heh

20:28 <leftylink> the example might be clearer if that were something like AdminCommands

20:29 <tinnvec> yeah, so it looks like the only way to even enable the use of "authentication" (you're right, more correctly it would be authorization) would be the standard way of including it in the plugin class