Rename reshares #74
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#74
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't like the term "reshare". I understand that the idea behind this word is to say that we share a second time, but I think that a second share should still be named a "share".
We use the word "Publish" in the button to create a new blog post, why not using this word again and rename "reshare" to "republish"?
At the risk of starting a long bikeshed, I'd like to suggest 'boost' as the alternative. When you share an article somebody has written, you're boosting its visibility and it sounds less technical than republish or share
I really like the idea that "boost" conveys, it doesn't feel like you are "stealing" someone else work.