Code improvement: thread following is not a restriction #1689
Description
Nothing broken, just a potential improvement to code clarity raised separately to avoid scope creep.
When a user follows a comment thread, the route used is thread/:id/restrict, or unrestrict to unfollow. The other actions that use this route (lock, archive, delete) are all restrictive (preventing user actions), but follow is not. This gives the potential for a reader to assume they have misunderstood what it means to follow, causing needless investigation.
Can this route either be renamed to reflect that it is not always about restriction, or be kept solely for restrictive actions, with a separate route for following?