Inconsistent naming of statuses/posts #721

Open
opened 2019-11-23 16:08:57 +00:00 by rinpatch · 2 comments
Member

Currently the English translation names statuses inconsistently. In notification panel they are named "Statuses", however in settings they are mostly named "Posts". We should decide on how to name them and make it consistent.

Speaking of naming, am I the only one who finds it weird that the Status modal says "Submit"? In my experience "Submit" is usually said about a form, but with statuses "Post" is used

Currently the English translation names statuses inconsistently. In notification panel they are named "Statuses", however in settings they are mostly named "Posts". We should decide on how to name them and make it consistent. Speaking of naming, am I the only one who finds it weird that the Status modal says "Submit"? In my experience "Submit" is usually said about a form, but with statuses "Post" is used
Owner

How about we call them Prööts everywhere? :DD :DDD

Submit is because you do in fact submit a form for a post. But could be replaced with "Post", but again, i feel like "Post" is one "Post" too many, i.e. you "post a post" sounds weird.

I don't like inconsistencies but I don't think post/status matters all that much, it's like calling e-mail a mail/email/message - it's inconsistent but doesn't really matter all that much.

At very least we don't call them toots, that would have been embarrassing.

How about we call them Prööts everywhere? :DD :DDD Submit is because you do in fact submit a form for a post. But could be replaced with "Post", but again, i feel like "Post" is one "Post" too many, i.e. you "post a post" sounds weird. I don't like inconsistencies but I don't think post/status matters all that much, it's like calling e-mail a mail/email/message - it's inconsistent but doesn't really matter all that much. At very least we don't call them toots, that would have been embarrassing.
Member

It seems to me that the fact you're actually summitting a form is technical consideration that doesn't inform the user the actual action they are taking. And that action is: posting.
My understanding of UI is that it should be as clear as possible to the user, what will result of is action. Here, "submit" isn't the result from a user point of view, the result is posting. I get what you're saying about "posting a post" but I'm afraid that's just how English works.

Generally, I support the idea to unify whether we call what user put out there publicly a "status" or a "post". It would make documenting and translating easier. Generally, the more consistent it is, the clearer and the easier it is to communicate and eventually solve problems.

It seems to me that the fact you're actually summitting a form is technical consideration that doesn't inform the user the actual action they are taking. And that action is: posting. My understanding of UI is that it should be as clear as possible to the user, what will result of is action. Here, "submit" isn't the result from a user point of view, the result is posting. I get what you're saying about "posting a post" but I'm afraid that's just how English works. Generally, I support the idea to unify whether we call what user put out there publicly a "status" or a "post". It would make documenting and translating easier. Generally, the more consistent it is, the clearer and the easier it is to communicate and eventually solve problems.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe#721
No description provided.