Comment on [Meta] Proposal regarding post tags for c/anime and c/manga
zabadoh@ani.social 1 day ago
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?
ludrol@bookwyr.me 1 day ago
The only thing that I have a gripe with would be that
tagsflairs on Piefed side are not really synchronised with typically used tags.wjs018@piefed.social 1 day ago
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.