<commit_before># Reply Highlighting

To better support conversations in high-activity rooms, this plugin highlights any message that contains "@yourusername"

## Usage

```HTML
<script type="text/javascript" src="candyshop/replies/candy.js"></script>
<link rel="stylesheet" type="text/css" href="candyshop/replies/candy.css" />
```

```JavaScript
CandyShop.Replies.init();
```<commit_msg>Updated README with a known issue.<commit_after># Reply Highlighting

To better support conversations in high-activity rooms, this plugin highlights any message that contains "@yourusername"

## Usage

```HTML
<script type="text/javascript" src="candyshop/replies/candy.js"></script>
<link rel="stylesheet" type="text/css" href="candyshop/replies/candy.css" />
```

```JavaScript
CandyShop.Replies.init();
```

## Known Issues

If people have subset usernames, like "drew" and "drewww", there will be some confusion for the user with the shorter name. I thought about some workarounds (look for '@username?' where ? is [ ,.!-]) but it seems like those will cause more false negatives than we're likely to see false positives right now in normal naming situations. If it's a problem in your community, let me know if you have an idea for a good approach!
{'fraction_non_alphanumeric': 0.11764705882352941, 'fraction_numerical': 0.0, 'mean_word_length': 5.536842105263158, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 1, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7084418', 'n_tokens_mistral': 365, 'n_tokens_neox': 354, 'n_words': 138}