Ankush Menat

+1 Specifically users should be allowed to hide their online status.

> Also, double tap to like please (👍) I don't like this TBH, very social-media-esque UX :woozy_face:

@NagariaHussain I don't believe this is really required. We can work with single large community server with multiple channels for communities. The same way we run discuss.frappe.io.

@rmehta they can just be 3 distinct sites? :sweat_smile: Site based isolation is also much better for security. No way to mess it up.

Potential CLI: `rq worker-pool --queue x,y,z:5 --queue a,b,c:2` Internal structure can be `dict[tuple[queue, ...], int]`

@selwin will you accept a PR for something like this?

Example of shortcut?

This is a bad idea :sweat_smile: It should be opted in for a few requests that can actually be cached. ALMOST every request is not cacheable. This will introduce subtle...

@blaggacao this is micro-optimization at best that doesn't work as well as you think. 1. You're adding etag computation overhead on EVERY request. >99% of requests that hit python workers...

Third category of patches required? - `after_migrate` ?