Content Notes for blog posts #710
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#710
Loading…
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?
People can enter a content note for comments, but I cannot enter CNs as an author for my blog posts (or even my blog as a whole).
Similar to Mastodon, a field for CNs which when filled blurs or hides the actual content of the blog post. A button for revealing the content could be placed at the top of the hidden content.
I'm on the fediverse.blog instance which uses 0.3.0 of Plume.
I can use the sub title for CNs for now since it can be used as a teaser on the overview page, too.
Do you mean content warning by content note? If so, is it really needed to have both a subtitle and a content warning? Can't the warning/note be included at the end of the subtitle?
Yeah, after I'd thought of reusing the subtitle for it, it probably suffices. Leaving it to you to close this issue.
I'm closing for the moment, but if someone has another argument in favour of this feature I will re-open. Thanks for the suggestion anyway!