Appreciate the in-depth reply. I get what you're saying about the challenge of getting people to utilise threading well, but my experience (also in tens of com

Appreciate the in-depth reply. I get what you're saying about the challenge of getting people to utilise threading well, but my experience (also in tens of communities) does not align quite as strongly as yours on Slack. There are frequent times where a reply goes in the channel as opposed to in a thread, yes, but in my experience that is far from the norm and isn't really a major issue. However, the threading approach on Discord definitely is less ergonomic in terms of starting one and I quite rarely see people utilise them in channels, that's true. I can't say I understand what distinction you see between Discord's forum channels and the proposed behaviour of Struct's upcoming chat platform. > would have liveness indicators, and threads would be presented in a real-time format. I do get frustrated that Slack doesn't give a clear indicator of the last message, but Discord does have various ways of indicating that: "There are no recent messages in this thread." (literally just copied that from a thread on Discord), including having the forum channels be ordered by most recent updates. On the topic of pricing, I could see it being better for large but inactive communities, provisioning a paid Slack workspace for an open-source project is often inviable after all. But for companies and teams that actively use Slack as their main source of communication, I'm not sure I'm convinced by the numbers right now. Typesense seems to have had those ~600 threads in 4mo (the earliest one I can see on the index), which will be an ongoing monotonically increasing cost even if their users stagnate. However, I think those ~600 threads are not at all representative of the average entity that uses Slack for professional purposes; our Slack for example sees thousands of messages a day (a large amount coming from bots that we use to notify about various things) but I appreciate that is unlikely to be a use-case Struct is aiming to support. So if we ignore the bots, there are still tens of threads a day for a team under 10 at the moment, and many companies below 100 people will see hundreds of threads a day. If we assume a conservative 25 threads a day for 50 people, then in 4 months you'd see 3000 threads, which to my understanding of the pricing would be ~$500 in Struct, compared to ~400 via Slack. I'll admit those numbers are actually a lot closer than I initially thought upon looking at your pricing, but that's assuming what I believe to be a very conservative amount for a few people, and giving up a lot of the other benefits of having Slack / Discord (interfacing with bots, getting other kinds of notifications), and after 8 months you'd be paying well over double without starting to "forget" a large amount of your history.