community

Describe the bug

In many (if not all!) of the places where the Follow button is rendered (with the class follow-action-button), the button always renders the text Follow by default. Once the user's data is fetched, it then may update to Following. This step of fetching the data async and then updating the text after the button and text have already rendered leads to a glitchy UI

Yuck.

Whoever wants to tackle this, .chats-full should be a flex item instead.

Currently, there's a lot of duplication between the tags Tag content handler and core's Index content handler. Similar duplication exists in "index" blade template vs "tag" bla

separe opensource apps from comercial

如题，Feedburner 已经苟延残喘很久，可是一直没找到可以提供类似的 Feed 烧制功能的替代应用，想问一下您是否有了解？

Summary

This is a follow-up issue to alan-turing-institute/the-turing-way#1210

Now that our default branch is called main we should do a search for other such terms (e.g. blacklist and whitelist) and update them with more modern alternatives, (e.g. denylist and allowlist).

What needs to be done?

• Curate a list of terms to avoid and appro

Describe the bug

When I have a conversation with a deleted account I can still reply to it.

To Reproduce

Steps to reproduce the behavior:

1. Sign in as a participant (ie [email protected])
2. Create a new conversation with another participant (ie [email protected])
3. In a private browser window, sign in as the other participant ([email protected]), delete the account
4. As the