@[email protected] @[email protected] nooooooo whyyyyyy

- posted by Chloe

@[email protected] @[email protected] please just mention people in your posts

- posted by Chloe

@[email protected] @[email protected] aaahhhh

- posted by Chloe

@[email protected] @[email protected] i have normal opinions about this

- posted by Chloe

elaborate on them, I wanna see what you have to say and whether or not this actually, yknow, makes a difference

@Chloe

@[email protected] well,

a) when I'm not mentioned in a reply it feels like the other user is trying to remove me from the conversation

2) if I'm not tagged in a reply, then another reply is made to that reply, I won't get notified (at least in *key)

so basically
<my post>
|> reply (I get notified)
| | > reply to reply (I dont' get notified unless I'm tagged in the text)

- posted by Chloe

@[email protected] I think the first reason is mainly because there's an expectation that you will always be tagged in replies since thats how most software works

- posted by Chloe

couple of things

I find it hilarious that you started with a) then went to 2)

either way this is a purely cosmetic change because all we're doing is:

introducing a UI element instead of having it in the composer

stripping mentions from the plaintext but keeping them in the AP data (specifically, the tag field)

What we aren't doing is changing who gets tagged. Or well at least we shouldn't but it seems gabbo changed the logic probably as a result of rewriting some things (CC @gabboman cough we should tag everyone up the thread by default for parity with old behavior)

really what I think this was supposed to be is moving them out of the plaintext and into exclusively the tag field like what snac does

That said, that's a *key bug. If there is a mention for you in the tag field then *key should probably respect that 

notification towards user should be ok, but other users may not