It wasn’t a mistake; I was curious to see what it did. (And since I didn’t see any comments between when I logged out on Sunday and came back to the site today to see this, I still don’t know what “inline” reacts are.) If the team made a mistake by exposing a menu option that you didn’t actually want people to use, that’s understandable, but you shouldn’t call it user error when you don’t know that it wasn’t completely intentional on the user’s part.
(this post had “inline reacts” enabled by mistake, but we’re not rolling that out broadly yet, so I switch it to regular reacts)
It wasn’t a mistake; I was curious to see what it did. (And since I didn’t see any comments between when I logged out on Sunday and came back to the site today to see this, I still don’t know what “inline” reacts are.) If the team made a mistake by exposing a menu option that you didn’t actually want people to use, that’s understandable, but you shouldn’t call it user error when you don’t know that it wasn’t completely intentional on the user’s part.
Sorry, I meant that it was a mistake on our part. Was not user error! Check out the latest Open Thread to see the experiment there.