trichoplax

Even the signed out test "what does basic user see in main with log out first" shows zero posts in main after basic_user fails to log in, so it does...

Yes that's what triggered me raising this issue. You saw this and commented before I had finished my review that links to it... Not sure if you can see that...

I prefer JS-style too. Would standardising on it mean we need to work around those cases it doesn't support, or does standardising mean avoiding those cases altogether? I'm pretty happy...

> I would _hope_ (but haven't researched) that rubocop is smart enough to recognise when we have to use rocket syntax because of the key type. Yes (just looked it...

## Possible solution We could store a hash of the user filters in the user filters object, which will mean it is automatically stored both serverside and clientside (in localStorage)....

See Discord discussion pointing out that a hash is not necessary as we can use the last update datetime: https://discord.com/channels/634104110131445811/635510793961472020/1127623991792779375

I like that approach. Listing like that on one line means in cases where someone has the status on a large number of communities it won't take up too much...

Merging in the develop branch triggered the tests again and they all passed this time.

My reasons for preferring native JS over jQuery: - Nowadays jQuery isn't much shorter than native JS, and browser compatibility is no longer a problem (any counterexamples that still apply?)...

There is some older discussion on Codidact Meta: - [Show question title before community name in browser tab](https://meta.codidact.com/posts/287743) An answer there mentions some potential customisation that may need to be...