Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make bots able to join other channels on command #16

Open
MasterDuke17 opened this issue Jul 30, 2016 · 8 comments
Open

Make bots able to join other channels on command #16

MasterDuke17 opened this issue Jul 30, 2016 · 8 comments
Labels
blocked ☹ Underlying issue is outside this repo, a ticket was filed whateverable Issues affecting the bot framework (and therefore all of the bots)

Comments

@MasterDuke17
Copy link
Collaborator

MasterDuke17 commented Jul 30, 2016 •
edited
Loading

Requested by @zoffixznet. See http://irclog.perlgeek.de/perl6-dev/2016-07-30#i_12939167
@MasterDuke17
Copy link
Collaborator Author

MasterDuke17 commented Jul 30, 2016 •
edited by AlexDaniel
Loading

Depending on how soon the 6lang re-write happens, this might be as simple as switching to Bot::BasicBot::Pluggable (https://metacpan.org/pod/Bot::BasicBot::Pluggable), which has a Join module (but also many more dependencies).

@zoffixznet
Copy link
Contributor

zoffixznet commented Jul 30, 2016 •
edited
Loading

To clarify: I don't really care if the bots can join other channels on command. I'm just going through old bugs and the bots are useful to make tests for those that are already fixed.

I just don't want to spam #perl6-dev with bot use and wanted the bots in #zofbot too.

@MasterDuke17
Copy link
Collaborator Author

I could (at least temporarily) start them in #zofbot for you. Is that on irc.freenode.net?

@zoffixznet
Copy link
Contributor

yeah

@MasterDuke17
Copy link
Collaborator Author

They should be started there.

@AlexDaniel
Copy link
Member

Instead we can just allow private messages and that will be it.

My logic about private messages is the following: given that RESTRICTED setting does pretty much nothing, anybody can submit any kind of crap in an attempt to make fun of my server. At this moment, the bot is not even running in an LXC container, so I am a bit worried (it does run as a separate user, but that is often not very helpful).
So right now if somebody is willing to do crap, then he kinda has to do it in public. Which probably reduces the desire to experiment with it.

Of course, the current setup is non-ideal and we will work on it. Also, the issue will probably go away once we move it to hack, which is something I was planning to do for a long time. The need for the move gradually emerges as I'm running out of space, so I think that the move will happen really soon.

By the way, what about LXC on hack? :)

@AlexDaniel AlexDaniel added all bots Issues affecting all (or most) of the bots whateverable Issues affecting the bot framework (and therefore all of the bots) and removed all bots Issues affecting all (or most) of the bots labels Sep 21, 2016
@AlexDaniel AlexDaniel added the testneeded Issue is generally resolved but tests were not written yet label Jan 6, 2017
@AlexDaniel AlexDaniel removed the testneeded Issue is generally resolved but tests were not written yet label Mar 12, 2017
@AlexDaniel
Copy link
Member

Blocked by #25.

@AlexDaniel AlexDaniel added the blocked ☹ Underlying issue is outside this repo, a ticket was filed label Jul 21, 2017
@AlexDaniel
Copy link
Member

I feel like rejecting this in favor of #122.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked ☹ Underlying issue is outside this repo, a ticket was filed whateverable Issues affecting the bot framework (and therefore all of the bots)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AlexDaniel @zoffixznet @MasterDuke17