Cleaned this up a bit. Not 100% sure about the design aspect though. Here's how it looks:

The first is for yourself and the second for the simul host.

@Tvallejos Some tips for future PRs:

• You can create a PR as a draft if it's not finished yet
• You don't need to put changed files in the description. We can look at the files changed tab on GitHub for that.
• If a PR fixes/closes an issue, you can use "Closes #issue number" or "Fixes #issue number" so that GitHub will auto-close the issue. Also, you can just use "#issue number" instead of a link.
• It's a good idea to auto-format your code before creating a PR, either via a Prettier extension in your editor or via yarn run format.

Okay, thanks for the tips. Own messages looks good, but I'm not sure either for host messages