Feature Req: Channels appear in category where requested

[jamescobalt]

In the interest of organization and privacy (for categories that are private), ideally new thread channels would appear in the same category the request was made from.

[Mailstorm-ctrl]

Once school stops being school I plan on rewriting the bot and address some issues it has. I think I can add this along with some other customizable features people requested.

…

-------- Original Message --------

On Apr 24, 2020, 12:00 PM, James Cobalt wrote: In the interest of organization and privacy (for categories that are private), ideally new thread channels would appear in the same category the request was made from. — You are receiving this because you are subscribed to this thread. Reply to this email directly, [view it on GitHub](#2), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMUWRNVAHKPA7PAX5EHNCBTROGZSLANCNFSM4MQG2VEA).

[Mailstorm-ctrl]

In the interest of organization and privacy (for categories that are private), ideally new thread channels would appear in the same category the request was made from.

I forgot to include this (I'm new to github despite being here for a few months so hopefully you get an email).

When you make a thread, it should inherit the same permissions as the channel it was invoked in. If this doesn't happen any more or I can't read, let me know and I'll make sure it does this in the re-write version.

[jamescobalt]

Haven't installed yet - researching moving community from Slack to Discord and people are anxious for solution to lack of threading. We have a couple devs so we might be able to help, but none are familiar with the Discord API yet.

[Mailstorm-ctrl]

Oh ok. Well you should know some limitation of discord: This won't operate the same as slack. The threads are an entirely separate channel and there is a hard channel limit imposed by discord. I think it's around 100 channels or 200. So archiving discussion isn't entirely possible. I don't know the api either lol. I just read the discord.py docs for the things I need and go from there. I'm in the middle of rewriting this to get features some people want working and improve performance since this seems to be growing. And also maybe easier to work with. Don't know when it will be done but it will be soon-ish.

…

-------- Original Message --------

On May 3, 2020, 1:34 PM, James Cobalt wrote: Haven't installed yet - researching moving community from Slack to Discord and people are anxious for solution to lack of threading. We have a couple devs so we might be able to help, but none are familiar with the Discord API yet. — You are receiving this because you were assigned. Reply to this email directly, [view it on GitHub](#2 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMUWRNSH4L36DV4YH72B4O3RPWTL3ANCNFSM4MQG2VEA).

[jamescobalt]

Thanks. Familiar with Discord as an end user, but not from API standpoint. Understood about separate channels to represent the threads, but I think that has its own good use cases (some people don't want certain discussions to stick around). This seems like the best approach I've seen so far.