Hi folks! Another week in the books and I hope that things are going well for all of you! Welcome to another general discussion thread. Feel free to post about anything you want that is anime-related here. I have provided some relevant examples below:
- Recent news:
- John Wick anime? Wasn’t that Lycoris Recoil?
- Hot takes:
- I just don’t get the hype around Suzume.
- Questions:
- Of all the characters in Kotono Mitsuishi’s storied career, which is your favorite?
In any case, make sure to tag your spoilers!
Example spoiler syntax:
::: spoiler Spoilers Within
Place your spoilery text here.
:::
produces
Spoilers Within
Place your spoilery text here
It means putting show spoilers behind Lemmy’s spoiler syntax. I have provided an example below. Do note that not every Lemmy app renders spoilers correctly. For instance, the Boost app just doesn’t hide spoilers at all. They work on the web interface and in the Jerboa app, but others can be hit or miss. I really loathe the Lemmy spoiler syntax, but I can’t really do anything about it.
Example spoiler syntax:
::: spoiler Spoilers Within Place your spoilery text here. :::produces
Spoilers Within
Place your spoilery text here
This does not work on kbin.social, unfortunately.
Nor in some Lemmy clients (like Voyager), hopefully spoiler support would get better over time.
In addition, kbin does not federate posts posted by bots (currently), so [email protected] appears empty on kbin.social even though they are federated. You’ll need to use an account on a Lemmy instance to participate there at this time, unfortunately.
Thanks for bringing this to my attention. I wasn’t aware of this limitation in kbin. I made a post about spoiler best practices in light of this. I am not a mod in this community, but I would imagine that similar guidelines would be acceptable here given the complications of federating different platforms.
Exactly what I was thinking about 😭
I wasn’t aware of this limitation in kbin. I made a post about spoiler best practices in light of this. I am not a mod in this community, but I would imagine that similar guidelines would be acceptable here given the complications of federating different platforms.