I’d say this would be a great thing for the community to build, but would take a great deal of time and effort to produce something of the same quality that discourse already provides. For this reason it isn’t something I would like to see the core team focus on. Their plate is already overflowing.
I think that Meteor is actually a much better foundation for this. I often run into annoying race condition errors in the Discourse UI due to its pull-based design (and maybe mismanagement of async code on their part, but this simply becomes easier to manage in the Signals and Effects paradigm (Tracker.aurotun and ReactiveVar with declarative-reactive templating, similar to Solid.js, etc)).
For example, on Discourse, if you click one thing, then click another thing before the first thing is done loading, the UI can get into the wrong state and whow the wrong thing (shows the previous loaded item rather than the last).
In Meteor’s paradigm where reactive code simply displays latest values without having to write procedural async code, things are much cleaner and less likely for people to create these types of issues.
Yeah, of course. I’m all for the Meteor paradigm, I just don’t think this is something the core team should be working on. A community effort would be great.
I shared this a few months ago: Heahy.com - meet people from all over the world
I created meteor chat but you can also create a channel with threads. The only thing it’s a bit like image board so you have to add some image when creating new threads.