-
-
Notifications
You must be signed in to change notification settings - Fork 34
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.
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
>mdial #245
Comments
>conference ? |
I was thinking >m(ulti)dial becuz it kinda fits with our naming scheme (dial/rdial/adial(might get added in V4)) |
so like you can have multiple people in the call? like a 3 way or 4 way call? |
that's what I'm understand this as. I think there definitely should be a limit for how many numbers (participants?) can be in one call otherwise it'd be chaotic. Someone being called should be told that it's an mcall/conference and how many people are in said mcall, also how will this be formatted in #bot-log? |
precisely
I think 4 is a good maximum, maybe even 5
yeah, maybe even list the numbers involved
maybe something like "User invited insert number here to conference call call id from users number"? |
what's adial?
Yes, the limit should be like 3 or 4 other people in the call at first. The whole idea is already disorganized, so the less the better |
Will be in v4. I agree with @LaNgOStInode that it shouldn't be a VIP feature. Instead, this will most likely tie into the progression system. Limits to be further discussed. |
what would limits be based on? the highest-leveled-number, the lowest-leveled-number, the number who started the call, or the number whos attempting to add a new person? limits would be the amount of people per call, so some rando couldnt just call literally every number in dtel |
^ i would say "the number whos attempting to add a new person." so we could add like a "Maybe ask another number in the call to add this number?" also, we could add the number the person is in during the call in the message format. |
This command would let you call multiple numbers at once!
questions:
The text was updated successfully, but these errors were encountered: