Large number of tags

chriskuta

Hi, I have an application that requires the use of large number of tags (>10k). In it's current form Flarum fetches and processes ALL tags/sub-tags for navigation (and also permissions I think). However what if I simply wanted to fetch just the messages from a specific tag like https://discuss.flarum.org/t/theming and not require anything outside this tag for navigation (for anything), basically treat it likes its own pseudo sub-community, is there a way to decouple or disable the existing tags processing? Or would it be better to develop my own frontend and use Flarum as a API.

zyronix

Restricting tags in the left navigation should be simple enough if that's your sole complaint. If you insisted on further changes I would modify the tags extension before forking flarum's frontend, to suit your needs.

Sounds like you might want subcommunities to carry the same primary tags as root index, but hard to tell from the vague post. Eliminate all extension options before even considering a fork.

chriskuta

Thanks for the reply, I'm happy to share more details and wasn't being deliberately vague. At its core specs are much like discord (but a forum not chat) where you join channels (in our case communities with their own sub-areas) these are essentially self contained. You have one login and you can join / leave any community freely (public). You have one profile and when viewing your own profile you can see a list of communities you are part of (or follow). Able to have moderator per community. A nice to have is search globally across all communities. Flarum actually meets pretty much all of this, however at high tag counts performance suffers exponentially. This is understandable given how the SQL statements are generated, as permissions are religiously checked across every tag and subtag - I can get more detail from my dev team on what we've found / tried to patch so far).

tankerkiller125

chriskuta This sounds like it would be better served by some sort of SSO system (Laravel Passport Maybe?) with each community on a seperate sub-domain. It would break global search but it would fix the whole performance issue. And once Flarum introduces the capability to change the search provider global search could be re-introduced by sending all of the data to a single index.

Another option maybe is some heavy modifications to the current tags extension could also be made to potentially do what your looking for.

chriskuta

hey @tankerkiller125 - thanks for the reply. We have considered multisite & sso however unified notifications, settings and the profiles become harder to manage. But it's a half dozen of this or half dozen of that situation doing it either way. We are leaning towards heavy modification of the current tags extension (which we've already started hacking on).