Here are current recommended (but optional) tags for c/anime:
[]or[]for general discussion/question posts[]Watch This! posts with a recommendation/review[]a video clip post[]for news and updates[]for discussions with spoilery content - indicate the series that is being spoiled
Here are the ones for c/manga:
[],[]- chapter discussion threads[]- Official art from a series or author, OC fan-art is also allowed[]- news updates about series, authors, publishers, etc.[]- 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 |
|---|---|---|
[] |
[] |
Makes it clear the thread is about a newly-released episode / chapter |
[] |
[] |
Keep as is; small snippet regarding the anime / manga |
[] |
[] |
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 |
[] |
[] |
For any posts that start a general discussion in the community (e.g. your favorite anime / manga); alternatively: [] |
[] |
[] |
Keep as is |
[] |
[] |
For posts regarding the community itself; for posts like this |
If the proposed [] has to be more fine-grained:
| anime | manga | rationale |
|---|---|---|
[] |
[] |
Same as before; for posts recommending others to watch this anime / read this manga |
[] |
[] |
For reviews of an anime / manga |
[] |
[] |
For posts specifically asking for recommendations |
The [] 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?
You must log in or # to comment.
About the post tags…it was all pretty much just lifted from reddit since that is the system people were most familiar with at the time. By now, I think it is fair to reevaluate and figure out what makes the most sense for our use case and scale. Lemmy 1.0 (when that finally gets released) is planning on having support for piefed/reddit-style post flairs, so that can hopefully serve the role of these tags more formally.
One thing that I do like from your list is the switch from RT/WT to just a more general recommendation tag. RT/WT aren’t very clear or easy to guess what the abbreviations mean unless you are already familiar with the culture coming from the subreddits or have read the sidebar (which isn’t always easy to view depending on the app you use). I do think that keeping it shorter is probably better, so maybe something like [Rec] like @ReluctantZen@feddit.nl suggested might be best.
DISC/Discussion is tricky. I agree that discussion as a topic is pretty broad and can cover much more than just chapter discussions. However, this is a tag that is so ingrained in the muscle memory of people it might be too hard to dislodge. I suspect that this might be a case where the tag in the post title might end up staying as DISC, but we can create more fine-grained post flair once lemmy 1.0 comes out to help people filter and categorize more.
I prefer scene abbreviations:
[Rec.][Title][S##E##T##:##:##/V##Ç##P###N##]
Season, Episode, Timestamp / Volume, Chapter, Page, Panel
[PV]/[Sc]/[URI]etc.
Preview, Scene, Uniform Resource Identifiers
fine w/[Meta],[DISC],[Art],[News],[Review]we also have spoiler tags in 🧵🌐. e.g.
[DISC] Ichi the Witch V02Ç15P17N4
I agree with the others so far. It’s fine as is in my opinion. I agree with the notion that every post is a discussion, so it feels a bit redundant.
I personally think the current ones are fine as they are, though I do like your suggestion “Recommendation” instead of “RT/WT”. Maybe shorten it to “Rec” though, so it doesn’t take up so much space. “DISC” covers most use cases pretty well. By specifying it to “Episode”/“Chapter”, you exclude things like films, one-shots and specials. I suppose you could fine-grain it more, but I don’t really see the point tbh, unless we know it’s confusing people.
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
tagsflairs 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.
