25
Here are current recommended (but optional) tags for c/anime:
[DISC]or[Discussion]for general discussion/question posts[WT!]Watch This! posts with a recommendation/review[Clip]a video clip post[News]for news and updates[Spoiler]for discussions with spoilery content - indicate the series that is being spoiled
Here are the ones for c/manga:
[Discussion],[DISC]- chapter discussion threads[Art]- Official art from a series or author, OC fan-art is also allowed[News]- news updates about series, authors, publishers, etc.[RT!]- Read This! posts are posts in which you recommend a series to others. Please provide a short review and information about the series as well.
IMO these guidelines could use some updates.
Here are my suggestions:
| anime | manga | rationale |
|---|---|---|
[Episode] |
[Chapter] |
Makes it clear the thread is about a newly-released episode / chapter |
[Clip] |
[Art] |
Keep as is; small snippet regarding the anime / manga |
[Recommendation] |
[Recommendation] |
For any posts asking for a recommendation, or posts that recommend an anime or manga; replaces WT! and RT!; see below for fine-grained alternatives |
[Community] |
[Community] |
For any posts that start a general discussion in the community (e.g. your favorite anime / manga); alternatively: [General] |
[Spoiler] |
[Spoiler] |
Keep as is |
[Meta] |
[Meta] |
For posts regarding the community itself; for posts like this |
If the proposed [Recommendation] has to be more fine-grained:
| anime | manga | rationale |
|---|---|---|
[Watch This!] |
[Read This!] |
Same as before; for posts recommending others to watch this anime / read this manga |
[Review] |
[Review] |
For reviews of an anime / manga |
[Recommendation] |
[Recommendation] |
For posts specifically asking for recommendations |
The [Discussion] tag was excluded because if you think about it, every post is a discussion thread.
This proposal applied to c/anime and c/manga because there is likely a significant overlap between these two communities; would be nice to keep them aligned.
The final set of tags doesn't have to follow this proposal exactly; thought this could make a good starting point.
What are your thoughts?
I don't think we've got such a flood of posts that I need to search by hashtag to find what I want to read.
But that might just be me.
Has anyone had any problems reading or finding desired content in this /c so that tagging posts would be useful?
The only thing that I have a gripe with would be that ~~tags~~ flairs on Piefed side are not really synchronised with typically used tags.
The post flair situation on piefed.social is a bit of a transient one. I had originally made the flairs as a bit of an experiment to see how the piefed/lemmy interop worked with them. The tl;dr is that it is pretty janky at the moment because lemmy will forward flair information in some cases and not in others. This should all be improved once lemmy 1.0 comes out. When that happens, the post flair will be created/standardized on the lemmy side since that is the community's home instance.
Technical Details
As a community moderator, I am able to create post flair for the communtiy on piefed.social. However, when doing so, the post flair information is just silently dropped by the ani.social instance because lemmy doesn't know what it means.However, if I (or somebody else) make a post from my piefed.social account, lemmy will dutifully forward that post's json out to all the other instances, even including the post flair information. This is the only way that post flair can currently federate out to other piefed instances. Then, users on remote piefed instances can only use the flair that has been federated out in this way.
It's still unclear if lemmy will support all the features in their post flair system that piefed does (spoiler blurring, colors, etc.). So, when 1.0 is closer to release, the post flair will probably be changed to some degree.