Better Threads #160

New issue

Open

opened 2026-04-17 01:29:33 +00:00 by Ghost · 1 comment

Ghost commented

2026-04-17 01:29:33 +00:00

(Migrated from codeberg.org)

The goal of this collection of issues is making a more usable version of threads. The main improvements we've come up with is as follows:

Thread Lifetimes
One of the issues with threads so far is the inability to have a thread last longer the 24 hours. With server boosting you can increase the lifetime to a week, but we want to eliminate this paywall.

Have an admin subcommand that would keep a thread alive forever until an admin runs another subsequent subcommand that archives it.

Dual Sending
One of the complaints about Discord threads from Slack is the inability to have the option to send in a thread and in the main channel the thread is linked to.

Implement a command that takes a message to be sent in both the thread and the main channel. Dalmatian would send a message for the user in the thread and in the main channel as the user (or at least appearing as the user).

Thread Visibility
Visibility of threads are also a common annoyance with threads often getting buried when people talk in the main channel. Automatically adding people to a thread when its made is a solid solution, however, discord's API rate limits would limit us to automatically add everyone in a large server like CMU's class servers, so an alternative solution must be used.

One possible solution is making a thread directory. For example, Dalmatian will pin a thread and if there is at least one pinned thread there would be an automatically maintained and posted message from Dalmatian in the channel linking them.

Thread Archive Navigation
After a thread is archived Discord doesn't have a good way to look up past threads. Dalmatian can serve as this to maintain an archive of archived threads that could be looked through.

A search thread command could be implemented to find specific threads based on metadata.

The goal of this collection of issues is making a more usable version of threads. The main improvements we've come up with is as follows: **Thread Lifetimes** _One of the issues with threads so far is the inability to have a thread last longer the 24 hours. With server boosting you can increase the lifetime to a week, but we want to eliminate this paywall._ - Have an admin subcommand that would keep a thread alive forever until an admin runs another subsequent subcommand that archives it. **Dual Sending** _One of the complaints about Discord threads from Slack is the inability to have the option to send in a thread and in the main channel the thread is linked to._ - Implement a command that takes a message to be sent in both the thread and the main channel. Dalmatian would send a message for the user in the thread and in the main channel as the user (or at least appearing as the user). **Thread Visibility** _Visibility of threads are also a common annoyance with threads often getting buried when people talk in the main channel. Automatically adding people to a thread when its made is a solid solution, however, discord's API rate limits would limit us to automatically add everyone in a large server like CMU's class servers, so an alternative solution must be used._ - One possible solution is making a thread directory. For example, Dalmatian will pin a thread and if there is at least one pinned thread there would be an automatically maintained and posted message from Dalmatian in the channel linking them. **Thread Archive Navigation** _After a thread is archived Discord doesn't have a good way to look up past threads. Dalmatian can serve as this to maintain an archive of archived threads that could be looked through._ - A search thread command could be implemented to find specific threads based on metadata.

Ghost commented

2026-04-17 01:39:53 +00:00

(Migrated from codeberg.org)

I think adding on the dual sending, there should also be a way to set a certain thread to automatically send in the channel as well.