Theme

Try to recreate a classic exploitable meme using AI!

I’m gonna switch up the scoring a little for this challenge, so be sure to read the score section:

  • Most ambitious: the most complex meme or the meme that I (a layman) feels would be very difficult to describe via prompt.
  • Most recognizable: the meme is the easiest to identify, and is the most accurate to the original
  • Do not include the name of the meme in the prompt: the challenge is to find a novel way to recreate the meme, not just get the model to spit out an image it was trained on. You can use words that are in the name of the meme, but avoid telling the model to just make the meme.

Rules

  • Follow the community’s rules above all else
  • One comment and image per user
  • Embed image directly in the post (no external link)
  • Workflow/Prompt sharing encouraged (we’re all here for fun and learning)
  • Posts that are tied will both get the points
  • The challenge runs for 7 days from now on
  • Down votes will not be counted

Scores

At the end of the challenge each post will be scored:

Prize Points
Most upvoted +3 points
Second most upvoted +2 point
Third most upvoted +1 point
OP’s favorite +1 point
Most ambitious +1 point
Most recognizable meme +1 point
Last two entries (to compensate for less time to vote) +1 point
Prompt and workflow included +1 point
Prompt includes the name of the meme -1 point

The winner gets to pick next theme! As always, have fun everyone! Previous entries

  • PeriodicallyPedantic@lemmy.caOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    Submissions are in and scores have been tallied. The winner for this week’s challenge is: @[email protected]! Congratulations! You get to pick next week’s challenge!

    Thanks to everyone who participated!

    Name Upvotes Upvote points Last two Prompt OP fav Most Ambitious Most Recognizable Meme Name Total
    @[email protected] 11 2 0 1 0 0 1 0 4
    @[email protected] 14 3 0 1 0 0 0 -1 3
    @[email protected] 11 2 0 1 0 0 0 0 3
    @[email protected] 7 0 1 1 0 1 0 0 3
    @[email protected] 9 1 0 1 0 0 0 0 2
    @[email protected] 4 0 1 1 0 0 0 0 2
    @[email protected] 4 0 0 1 0 1 0 0 2
    @[email protected] 8 0 0 1 0 0 0 0 1
    @[email protected] 6 0 0 1 0 0 0 0 1
    @[email protected] 6 0 0 1 0 0 0 0 1
    @[email protected] 8 0 0 0 1 0 0 0 1
      • PeriodicallyPedantic@lemmy.caOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        4 months ago

        Hmmm it should look like this (copied the formatting from theIsim’s post, but it’s hard to find out what the official markdown is, and what clients support what markdown)

      • ThelsimM
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        That’s strange, do you have the same problem with my post?

        • merde alors
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 months ago

          no, yours is correct. I use jerboa and infinity and the result is the same on both

          • ThelsimM
            link
            fedilink
            English
            arrow-up
            3
            ·
            4 months ago

            Hmmm… Looking at the code, the only cause I can think of is the larger amount of dashes on the second line. Other than that it looks like valid markdown. Maybe that’s why it doesn’t parse very well in your apps? They look OK in Voyager and Thunder.

            Anyway, I’ll see if I can keep this in mind for next week’s tally by adding an easier to read (and edit) alternative.

            • PeriodicallyPedantic@lemmy.caOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 months ago

              I’m not actually familiar with this markdown, so idk where even to find the spec. Let alone the official markdown for Lemmy or specific clients 😭
              Why couldn’t it just be CSV 😭lol

              Probably happened because I tried to get cute and make all the cells line up if the raw markdown was viewed (without word wrap) and I put a typo in somewhere

              • ThelsimM
                link
                fedilink
                English
                arrow-up
                1
                ·
                4 months ago

                That’s ok, I don’t think anyone could have foreseen this :)
                And don’t worry about making the cells line up, no one will ever get to see it unless they look at the source.

                In the future, there are plenty of online tools to quickly convert something like CSV to Markdown. I found this one with a simple search:

                https://tableconvert.com/csv-to-markdown

                • PeriodicallyPedantic@lemmy.caOP
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  4 months ago

                  The irony was that I want sure if this markdown was supported in all clients which is why I tried to make the cells line up; so it’d fall back to something resembling a table.
                  (Well, that and it was easier to make sure I was editing the right column)

                  I think I’ll just use such a tool in the future. I wonder if libre office or open office can export directly to it