Place a link to a moo.do outline in the original post. Presto, integration without really integrating the code. Even this half baked setup is superior to all dedicated pm solutions that I have tried. For me, efficiency is the primary factor when evaluating software. How quickly we can download the data we need and upload our input. Number of clicks is a useful metric.
Having every resource available on the home page is a highly efficient design for a workflow tool. I view nodebb as the best version of this concept.
Its easy to recommend the popular product. Actually testing all of them to isolate value is challenging. Try not to anchor yourself until you've done the research.
Our community would like the ability to be able to put a thread into multiple categories. (This might need to be moderator and above privilege).
I'm assuming this is not currently possible. Would it be possible to add this, whether in the core or as a plugin?
I'm not quite sure what the current db schema looks like. I understand everything is just in a single collection. Would it be as simple as having some kind of interface which ads a linking between a thread and a category, or is it a huge lift?
hmmm... well ideally plugins and core would only load their assets when necessary. For instance, in core, we only load jQuery UI if we have some jQuery UI thing. There are many other places where we could pull more code out to be on-demand.
you mean ideally but not on reality, right? 😄
my idea was for example to enable plugins like...
-people viewing this topic, reactions, polls, etc only on desktop
The reason for the recaptcha/antispam question before SSO, is to avoid spammers using scripts to use SSO with a burner account (which I am seeing here on this forum). That is one way to avoid spam filters and creating more spam, which can annoy some forum users/admins.
So in other words...
click on Register -> click on SSO link -> Antispam question/recaptcha -> then click SSO login/agree button
The idea that Redis stores everything in-memory is the key to its speed. However, it's also a huge crutch in that yes... the less-often used data is still in-memory when it could rightly just be put in the hard drive and queued up when needed.
That's why we suggested migrating to Mongo, because, well... it does just that 😄