Claire

> Any guess on a spec which would expose the regression? I suppose calling something like `I18n.t('accounts.followers', count: 530, locale: :'sr-Latn')` and checking the result would work, but it's too...

I think it makes sense to redirect to `/home` if the newly-logged-in user would otherwise be redirected to what can be a logged-out landing page: `/about`, `/explore`… or the single...

Actually we already have that kind of logic, it was just not updated with the addition of the explore page.

Thanks for the report, I'll try to track it down. I currently don't know what is happening, but a similar issue has been fixed a while ago (#20719, in 4.0.2)....

I'm feeling uncomfortable with this, as, similar to the full-text search discussion, posting a link does not necessarily mean you want to be found when searching the link.

I am still unable to reproduce or identify the issue, but if you're affected, try applying this patch and watching for “Cached filters were already set”, “Account filter mismatch” and...

I believe I have identified the issue, can you give #26159 a try?

I assume you are talking about the following banner?  > It serves no purpose whatsoever. It's used to guide people to the explore feature, as some people complain that...

Storing that information server-side rather than in localStorage would make sense indeed, I'll have a look.

> Everything else matches 4.1.4's yarn.lock - except caniuse-lite which I have updated to version "1.0.30001515" Do not! Please revert `yarn.lock` to its original state and try again!