aia

Cake is a lie

That's not true, guests and bots will receive whatever is set in their Accept-Language header, which is configured at the browser level for users. Additionally, we have more than just guests and bots in our communities. All users are affected by this issue, regardless of whether they are bots, guests, or logged-in users.

That's not quite true. This tool also manipulates titles, which are translatable at the category name level. However, they become untranslatable when you use this tool. This means that while forum section titles can be translatable even in the current state of the software, using this tool effectively breaks that ability, as you are forced to stick with only one language. The category names are just an example. The same problem exists everywhere, especially important in the forum's main page title.

When a community is multilingual, it does not have a 'primary community language.' When a community has a 'primary community language,' it is not a multilingual community by definition.

The title and meta tags editing tool must support localization. But, it currently does not, making the tool completely useless for multilingual communities.

Absolutely not a clickbaity filename for the image.avif

The sad part is that we can't use Elasticsearch's multilingual capabilities in IPS. Even your screenshot shows that we can only use one language analyzer, which is not suitable for multilingual websites 😢

Currently, we have leaderboards based on reactions, but a leaderboard based on the number of "Solutions" will encourage people to write more useful answers. Therefore, a Leaderboard and Widget (similar to "Popular Contributors," but based on solved topics) would be very useful.

https://clerk.com/blog/open-response-type-vulnerability

Unfortunately, it does not. I hope it will be fixed before the release.

The requirement to use Invision email and password during the upgrade process is problematic because it conflicts with saved admin emails in autocomplete. It would be much more convenient and safer to use an app key (token) that is saved for future upgrades and does not depend on Invision email or password.

Why Apache and not Nginx? Also, for every Docker image, I’d use the lightest possible image (Alpine-based instead of Bookworm, for example). For php.ini, I’d add opcache configuration. Also, consider using the ImageMagick PHP extension.

*Hidden, not removed. You can't remove things with CSS. Any removal for performance goals should be done at the PHP level, before transmitting HTML to the user. Otherwise, it will not solve the problem.

I mean cross-document navigations, the CSS View Transitions Module Level 2 spec. View transitions when navigating between different URLs. As a starting point, you can simply add this simple CSS rule: @view-transition { navigation: auto; } and observe how it affects the look and feel when you switch between pages. It immediately becomes smoother, less jumpy, etc. The other details (exact animations) are depend on designer preference

View transitions are a great way to make websites and web apps feel smooth and pleasant to use. This feature is now available in major browsers and will soon be added to others. It's also a progressive (non-breaking) enhancement, meaning we don't have to wait for universal browser adoption. Users of major browsers will immediately notice the difference, while users of other browsers won't experience any change until their browsers are updated. Also, the good part is that some generic transitions can be implemented with CSS alone, without any JavaScript. JavaScript is optional for very specific cases but not mandatory at all. For more information on how view transitions work: General description: https://developer.chrome.com/docs/web-platform/view-transitions Specifics for multipage applications: https://developer.chrome.com/docs/web-platform/view-transitions/cross-document