The instructions that are being read are implying longer cook times if the chicken breasts are considered large. The joke is that the character realizes she has large breasts herself, and bases cook time on her own breasts rather than the chicken she’s actually cooking
Well, the person above me didn’t actually use the spoiler tags, they were just showing how it would look like while editing, here’s an example to see if it works for you
Huh?
The instructions that are being read are implying longer cook times if the chicken breasts are considered large. The joke is that the character realizes she has large breasts herself, and bases cook time on her own breasts rather than the chicken she’s actually cooking
…and now it’s not funny anymore.
Explaining a joke is like dissecting a frog. You understand it better, but something does in the process.
I mean it should have gone through spoilers, but to be fair I don’t even know how to do that.
Just write SPOILERS AHEAD then do a bunch of line breaks so people have to scroll a while to see it
or you do spoilers like this
I like large breasts
Also
I like small breasts too
I see the text. Might just be the app
Likely. The markdown engine Lemmy-UI uses has a couple extensions like spoiler blocks and tables.
By writing >! text here !<
Isn’t that limited to certain clients and not universal like
spoiler
this is a spoiler
Neither you nor the person above have spoiler tags that work for my app. 🙃
Well, the person above me didn’t actually use the spoiler tags, they were just showing how it would look like while editing, here’s an example to see if it works for you
Nope. :/
https://imgur.com/a/sq15hfi