Day: July 8, 2026

It was one of those dreary Tuesday afternoons when the sky couldn’t decide whether to rain or shine, so it just hovered in a blah gray. The kind of day that demands something bright and cheerful to rescue you from the monotony. I found myself in the kitchen, eyeing a lonely lemon on the counter. It hit me – pressed lemon butter cookies! They’re the perfect pick-me-up: buttery, zesty, and just the right amount of sweet, without the gluten. These cookies are impressive enough for a tea party yet simple enough for a midweek treat. If you, like me, need a little sunshine on a plate, these cookies are your answer.

Jump to Recipe

What You’ll Need

I bet you’ve got most of these tucked away in your pantry and fridge. It’s a short, sweet list that’s all about that lemony punch and buttery goodness. Here’s what you’ll need:

• Unsalted butter
• White sugar
• Egg yolks
• Lemon extract
• Lemon zest
• Fresh lemon juice
• Gluten-free flour
• Xanthan gum

How to Make Gluten-Free Pressed Lemon Butter Cookies

1. Preheat your oven to 350°F (175°C). This is the perfect moment to get cozy with that mixing bowl and let the anticipation build.
2. In a world where flour can be tricky, whisk or sift your gluten-free flour with the xanthan gum. This step ensures everything blends smoothly, trust me.
3. Grab your standing mixer with the paddle attachment and cream the unsalted butter until it’s fluffy and inviting. The butter should look like a pillowy cloud.
4. Add in the white sugar and continue to cream until the mixture is light and airy. You’re looking for that dreamy consistency.
5. Introduce the egg yolks to the party, one at a time, making sure each is fully incorporated before adding the next.
6. Now for the zesty kick: add the lemon zest, lemon extract, and fresh lemon juice. Mix them in until the batter sings with lemony aroma.
7. Slowly fold in the flour mixture at a gentle speed, then increase the speed until it’s all well-incorporated. Your dough should be soft, but firm enough to hold its shape.
8. Load your cookie press with the dough and press onto ungreased cookie sheets. This is where the magic happens – each press is a little masterpiece.
9. Bake one sheet at a time, for about 12-15 minutes, until the edges are lightly browned and your kitchen smells like a citrus grove.
10. Patience, my friend. Let them cool completely on the sheets before gingerly using a thin spatula to lift them. They’ll be delicate but oh-so-worth-it.

Cook’s Notes

Here’s a little insider scoop: when working with gluten-free flour, sifting is your best friend for a smooth texture. These cookies keep well in an airtight container for up to a week, but let’s be real, they’ll probably disappear way before that. If you’re planning ahead, the dough can be made a day in advance and refrigerated. Just let it come to room temperature before pressing. And whatever you do, don’t skip the cooling step – they’re fragile when fresh out of the oven.

Make It Your Own

With a recipe like this, there’s room to play around. Here are a few ideas to shake things up:

• Swap the lemon for orange zest and juice for a sweet, floral twist.
• Add a teaspoon of vanilla extract alongside the lemon for a more rounded flavor.
• Sprinkle a little coarse sugar on top before baking for a touch of sparkle and crunch.
• Mix in a tablespoon of poppy seeds for a delightful texture and a nod to classic lemon-poppy duo.

If you try this, I’d love to hear how it turns out — drop a comment or tag me! Knowing these cookies brought a little sunshine to your day would make mine. Enjoy each zesty bite!

Related Reading

• Triple Chocolate Pumpkin Pie | Made by Meaghan Moineau
• Coconut Macaroons With Chocolate Drizzle | Made by Meaghan Moineau
• Traditional Banana Bread | Made by Meaghan Moineau
• Banana in brown sugar ice cream | Made by Meaghan Moineau
• Apricot Clafouti With Lavender & Pecans | Made by Meaghan Moineau

Related update: Gluten-Free Pressed Lemon Butter Cookies

Related update: Dried Cranberry Chocolate Cookies

TL;DR

• Epic settled with ex-contractor Hayden Cohen over Fortnite leaks: a proposed court injunction would permanently bar Cohen from handling Epic Games’ confidential info, with no monetary relief disclosed—deterrence now runs through the Defend Trade Secrets Act (DTSA), not damages [1][2][4].
• The core risk wasn’t a few skins; it was partner trust—brands like South Park, Minecraft (Mojang/Microsoft), and Overwatch (Blizzard) don’t tolerate surprise-killing leaks that derail synchronized co-marketing plans [1].
• An injunction-first deal can be smarter than a damages fight: it avoids discovery that could surface partner decks and drafts, while creating a personal tripwire for any future breach under 18 U.S.C. § 1836 [2][4].

What the source said

Video Games Chronicle reported that Epic Games reached a settlement with Hayden Cohen, a former associate producer accused in March 2026 of leaking upcoming collaborations—South Park, Minecraft, and Overwatch—via an X account that gained roughly 13,000 followers before deletion [1]. The deal seeks a stipulated court injunction barring Cohen from possessing, accessing, using, or disclosing Epic’s confidential or trade secret information [1]. PC Gamer corroborated that the filing mentions no monetary relief, and Epic declined to comment on damages [2]. Epic spokesperson Natalie Munoz said the company sought the injunction “to ensure [Cohen] cannot publish or share Epic’s confidential information again” [1].

Why it matters

Three constituencies are on the line. First, Epic’s live-service cadence: Fortnite relies on tightly timed “surprise” drops that lift Item Shop conversions and engagement each season; a reliable insider leak collapses that timing [1]. Second, IP partners like Mojang/Microsoft (Minecraft), Blizzard (Overwatch), and South Park’s rights holders budget around synchronized beats; early spoilers blunt conversion and trigger contractual friction [1]. Third, the creator economy orbiting Fortnite—Support-A-Creator affiliates, Twitch streamers, and YouTube channels—plans sponsor slots and programming around reveal windows.

The settlement also draws a bright line between datamining and insider misappropriation. Datamining scrapes assets already in public builds; insider leaks extract pre-build plans and partner decks. Under the DTSA, federal courts can tailor injunctions to halt threatened misappropriation, which is exactly what Epic is asking the court to endorse here [4].

Original analysis

The consensus—and why it’s wrong

• Consensus: “No damages? Then the Fortnite leaker settlement is a slap on the wrist.”
• Contrarian read: a permanent injunction is the sharper penalty. Why?
  • It’s individualized and enforceable: violate it and you face contempt or enhanced DTSA remedies without relitigating liability; courts treat injunction breaches as defiance of the court itself [4].
  • It preserves partner confidence without messy discovery: depositions and brand-deck productions would risk fresh leaks. An injunction locks the door; a damages trial opens the blinds. That trade-off is rational for Epic and for licensors who prefer to stay out of the record [2][4].

Back-of-envelope: what a “spoiled” collab can cost (hypothetical scale)

• Anchor: Sacra estimates Epic’s 2024 revenue at about $5.7 billion, with Fortnite as the driver [5].
• Hypothesis: If diminished “surprise” clips even 0.5% of annual monetization across a few anchor drops, then:
  • $5.7B × 0.5% = $28.5M at risk in a year (scale illustration, not a damages claim) [5].

2x2: leak types Epic actually cares about

• Axis A (Epic info location): internal systems vs. public game builds [4].

• Axis B (timing window): pre-build plans vs. in-build assets, which dictates DTSA exposure and PR risk [4].

• Insider pre-build (most severe): Internal roadmaps, partner pitch decks, and code names—what Epic alleged here. Consequence: direct DTSA exposure and reputational damage with licensors [2][4].

• Insider in-build: Early access to staging/QA branches; still severe (see Epic’s 2019 case vs. a tester who leaked the Chapter 2 map) [6].

• Public in-build (datamining): Players parse shipped binaries; often tolerated unless it prematurely reveals licensed IP like South Park or Minecraft [1].

• External partner leak: Retail listings or vendor packshots. Contractual friction and takedowns usually contain it, but timing damage still lands [1].

Cohen’s case sits top-left (insider/pre-build), which explains a push for a permanent injunction rather than a headline damages number that would prolong attention on the leaks [1][2][4][6].

Historical analogue: Pokémon’s 2021 hammer vs. leakers

In 2021, The Pokémon Company secured $150,000 apiece from two Sword and Shield leakers who posted strategy-guide images ahead of launch, showing courts will back meaningful monetary penalties tied to pre-release marketing assets [7]. Epic’s path differs—favoring a stipulated injunction—but the throughline is similar: when surprise becomes product, premature disclosure is framed and treated as trade secret misappropriation under federal or state law [4][7].

Named-stakeholder breakdown

• Epic Games: An injunction-centric outcome delivers a standing enforcement tool and reduces discovery that could expose internal processes or partner contracts. It also signals to staff and contractors that DTSA remedies—not just NDAs—govern insider conduct [2][4].
• Microsoft/Mojang and Blizzard (Minecraft, Overwatch): Fewer uncontrolled spoilers mean cleaner timing across Xbox, Battle.net, and social beats, stabilizing conversion models for Item Shop windows and Twitch drops [1].
• South Park rights holders (e.g., South Park Digital Studios/Paramount affiliates): Comedy IP depends on reveal timing; leaks dull punchlines. A consistent legal posture from Epic lowers brand risk on future crossovers [1].
• “Leak economy” accounts on X/Discord: A federal injunction targeting an alleged insider shifts risk: amplify a known-insider leak and you may face subpoenas or preservation demands, even if you never touched Epic systems [2][4].
• Competing publishers: Expect imitation. Nintendo, The Pokémon Company, and Epic are converging on a norm: escalate insider cases under DTSA or equivalents, reserve PR-friendly takedowns for datamining [6][7].

Why the Fortnite leaker settlement is more than PR cleanup

Epic’s complaint was filed March 5, 2026, in the Eastern District of North Carolina (Case No. 5:26-cv-00135-BO) and alleges Cohen—operating AdiraFN/AdiraFNInfo—“repeatedly misappropriated Epic’s trade secret information” via X and Discord while bound by an NDA, seeking injunctive relief plus compensatory damages and fees [3]. The proposed deal delivers the first ask: a court-ordered ban on accessing or sharing Epic’s confidential info, which removes the account’s unique edge [1][2][3]. Without insider pre-build access, any future presence would devolve into ordinary datamining rather than live-plan disclosure [1]. Under 18 U.S.C. § 1836, injunctions must be based on evidence of threatened misappropriation, cannot be used to bar employment per se, and can be paired with royalties or damages for future misuse—deterrence that follows the defendant across jobs and platforms [4].

What others are missing

Coverage focused on the absence of a damages figure. The overlooked angle is discovery risk management: a full-dress damages trial could force emails, roadmaps, or draft licensing terms into the record, compounding exposure for South Park Digital Studios, Mojang, and Blizzard. By securing a stipulated injunction under a federal statute tailored to trade secrets, Epic minimizes the chance of partner materials hitting PACER or the tech press while still obtaining ongoing relief [1][2][4].

What to watch next

1. By Q3 2026, Epic will update contractor NDAs and onboarding to cite DTSA remedies and ex parte seizure provisions, and at least one hire will publicly reference these changes in job docs or a LinkedIn post.
2. By Q4 2026, at least one major publisher besides Epic will file a DTSA-centered complaint against an insider leaker tied to a live-service crossover, with the primary prayer for relief being a permanent injunction.
3. By Q2 2027, a Fortnite partner named in the 2026 leaks (Minecraft, Overwatch, or South Park) will run a synchronized relaunch or “reprise” event, confirming partner retention post-settlement.

My take

Epic picked the right hill to hold. A clean, court-backed injunction beats a pyrrhic damages press release that trades headlines for discovery risk [2][4]. When Fortnite remains a multibillion-dollar franchise on 2024 revenue estimates, even small percentage swings justify aggressive timing protection [5]. I expect more studios to mirror this template: move fast in federal court, lock the injunction, and starve the leak economy of its only real edge [2][4].

Sources

1. Epic settles with Fortnite leaker who shared South Park, Minecraft and Overwatch collabs — Video Games Chronicle (https://www.videogameschronicle.com/news/epic-settles-with-fortnite-leaker-who-shared-south-park-minecraft-and-overwatch-collabs/) — Baseline report on the settlement, brands implicated, follower count, and Epic’s on-record statement.
2. Epic reaches lawsuit settlement with former contractor who was also a notorious Fortnite leaker — PC Gamer (https://www.pcgamer.com/games/epic-reaches-lawsuit-settlement-with-former-contractor-who-was-also-a-notorious-fortnite-leaker/) — Confirms proposed settlement terms (permanent bar via injunction), timing, and lack of disclosed monetary relief.
3. Complaint, Epic Games, Inc. v. Hayden Cohen (Case 5:26-cv-00135-BO) — DocumentCloud (https://s3.documentcloud.org/documents/27772901/epic-games-v-hayden-cohen-complaint.pdf) — Primary filing establishing venue, allegations of insider misappropriation, and requests for injunctive relief and damages.
4. 18 U.S.C. § 1836 (Defend Trade Secrets Act) — Cornell Law School Legal Information Institute (https://www.law.cornell.edu/uscode/text/18/1836) — Statutory basis for injunctions and remedies in federal trade secret cases; explains the potency of tailored injunctive relief.
5. Epic Games revenue estimate 2024 — Sacra (https://sacra.com/c/epic-games/) — Independent estimate used to size the hypothetical financial impact from “spoiled” surprise drops.
6. Epic sues tester over Fortnite Chapter 2 leaks — Video Games Chronicle (https://www.videogameschronicle.com/news/epic-sues-tester-over-fortnite-chapter-2-leaks/) — Context on Epic’s prior insider-leak litigation in 2019 against a QA tester.
7. Pokémon Sword and Shield leakers to pay $150,000 each — GameSpot (https://www.gamespot.com/articles/pokemon-sword-and-shield-leakers-to-pay-150000-each-to-nintendo-for-damages/1100-6493184/) — Historical analogue showing courts awarding significant damages for pre-release marketing asset leaks.

Picture this: It’s a chilly Tuesday evening, and I’ve just managed to duck out of the rain and into my cozy kitchen. My cat, Oliver, is curled up on the windowsill, and the whole place is alive with the soft patter of raindrops. It’s the kind of night that calls for something deeply comforting, something that can fill not just the belly but also the soul. Enter Classic Boeuf Bourguignon — my go-to when I crave something hearty and a tad bit indulgent but without spending hours in the kitchen. Honestly, the magic of this dish lies in its ability to transform simple ingredients into something truly extraordinary. The smell of beef simmering with red wine and herbs is, quite literally, poetry in a pot. Plus, it’s the kind of recipe where you can pop it all into a Dutch oven, let it work its magic, and you’ll still have time to catch up on that new series everyone’s been talking about.

Jump to Recipe

What You’ll Need

Just a heads-up: You might already have most of these tucked away in your pantry, and the rest? Well, they’re worth the trip to the store. Trust me.

• Bacon – Adds a smoky depth to the dish.
• Olive oil
• Beef stew meat – The star of the show.
• Garlic
• Diced onion
• Fresh thyme
• Bay leaves
• Parsley
• Pearl onions
• Button mushrooms
• Carrot
• Red wine – Go for something you’d drink.
• Beef broth
• All-purpose flour
• Salt and pepper

How to Make Classic Boeuf Bourguignon

1. Preheat your oven to 400°F (200°C). Get that Dutch oven ready – it’s about to work its magic.
2. Heat olive oil over medium heat and toss in the bacon. Let it sizzle for about 2-3 minutes until it’s just perfectly cooked. Transfer the bacon out with a slotted spoon and let it hang out on the side.
3. Pat the beef dry with paper towels for a better browning. Crank up the heat to medium-high, throw the beef into the bacon fat, and let it sear for 4-5 minutes until every piece is gloriously browned. Spoon them out and set aside.
4. Lower the heat back to medium. Toss in the carrots, garlic, onions, parsley, thyme, and bay leaves. Give them a good stir for about 2-3 minutes. Out they go with the slotted spoon, into a separate dish.
5. Add pearl onions and mushrooms to the Dutch oven. Sauté them until the onions start to brown and the mushrooms become tender. Move them to the dish with the bacon.
6. Return the beef to the pot and sprinkle one tablespoon of flour over it. Give it a good toss to coat. Season generously with salt and pepper. Pop it in the oven for about 4-5 minutes to develop a gorgeous crust.
7. Remove the pot from the oven and set it on the stovetop. Pour in the red wine and deglaze, scraping up all those tasty bits. Add the beef broth, bring it to a gentle simmer.
8. Introduce the carrot, onion, and spice mixture back into the pot. Lower the heat, cover, and let it simmer away for an hour, filling your kitchen with the most intoxicating aroma.
9. After an hour, add the pearl onions, mushrooms, and bacon. Continue to simmer, allowing the beef to tenderize further, about another 30 minutes.
10. Use a slotted spoon to fish out the solids and set them aside. Crank up the heat; let the sauce come to a rapid boil.
11. In a small bowl, mix the remaining tablespoon of flour with two tablespoons of sauce. Stir until smooth and lump-free. Add to the pot, stirring constantly until the sauce thickens.
12. Remove the bay leaves and thyme sprigs. Discard them. Return the solids to the pot, stirring to coat evenly with the enriched sauce. Serve warm, perhaps over a bed of egg noodles or rice if you’re feeling it.

Cook’s Notes

Let’s talk practicalities. This dish is one of those gems that get even better the next day — so if you can resist not devouring it all, it’s perfect for leftovers. Store it in an airtight container in the fridge, and when you reheat, just do it gently over low heat to keep that beef tender and juicy. If you’re prepping ahead, you can cook everything up to the point just before adding the flour in step 10. Refrigerate and proceed with the sauce thickening when you’re ready to serve. Also, don’t skimp on the wine. A good wine makes all the difference. Taste as you go, and adjust the seasoning if needed.

Make It Your Own

Feel free to get creative and put your own spin on this classic:

• Vegetarian Twist: Swap out the beef for hearty mushrooms like portobello or cremini, and use vegetable broth instead of beef.
• Poultry Option: Switch the beef out for chicken thighs. They’re just as comforting and cook a bit quicker.
• Root Veggie Addition: Try adding some parsnips or turnips along with the carrots for a little extra earthy sweetness.
• Herbaceous Flair: Add rosemary or sage for an aromatic twist that complements the wine beautifully.

If you try this, I’d love to hear how it turns out — drop a comment or tag me! Sharing your kitchen adventures makes my day. Plus, who knows, your twist might just inspire someone else!

Related Reading

• Cauliflower Chickpea Stew | Made by Meaghan Moineau
• Grilled Lemongrass Shrimp | Made by Meaghan Moineau
• Carrot and Coriander Soup | Made by Meaghan Moineau
• Blast Of Color Mexican Stuffed Bell Peppers | Made by Meaghan Moineau
• Spinach and Gorgonzola Stuffed Flank Steak | Made by Meaghan Moineau

Related update: Classic Boeuf Bourguignon

It was one of those weeks where everything seemed a bit too chaotic, and the weather was veering into that crisp, cozy fall vibe that just screams for comfort food. I was rummaging through my pantry, trying to figure out what on earth I could throw together without needing a last-minute grocery run. There it was, a can of chickpeas and some cauliflower that had been patiently waiting for their moment to shine. Enter the Cauliflower Chickpea Stew: a dish that’s hearty, full of flavor, and surprisingly easy to whip up. It’s one of those recipes that feels like a warm hug after a long day, plus it’s packed with spices that make your kitchen smell absolutely divine. Definitely a go-to for those nights when you need something nourishing but not overwhelming to make.

Jump to Recipe

What You’ll Need

I love this recipe because it relies on pantry staples but still feels a bit exotic thanks to the spices. Chances are you already have most of this hanging around your kitchen.

• Olive oil
• Brown rice
• Twice the amount of water to rice
• Garlic cloves
• Turmeric
• Salt & pepper
• Onion
• Canned tomatoes
• Tomato puree
• Fresh cm ginger
• Fresh chili
• Cinnamon
• Garam masala
• Paprika
• Sweet potatoes
• Lemon (juice)
• Additional water
• Cauliflower
• Canned chickpeas

How to Make Cauliflower Chickpea Stew

1. Start by heating some olive oil in a large saucepan over high heat. You’ll want it shimmering but not smoking.
2. Crush your garlic cloves and toss them in the pan with a generous pinch of turmeric, salt, and pepper. Fry for about a minute until everything is golden and fragrant.
3. Add the brown rice, stirring occasionally. Let it fry for 4-5 minutes until the grains become slightly translucent.
4. Pour in water (twice the amount of your rice) and bring it to a boil. Once boiling, reduce the heat to low-medium and let it simmer for 30 minutes. The rice should be tender and the water absorbed.
5. While the rice does its thing, chop your onion, sweet potatoes, and cauliflower into bite-sized pieces. Grate the ginger and finely slice the chili.
6. In another pot, heat more olive oil and sauté the onion until it’s soft and just starting to brown.
7. Add the canned tomatoes, tomato puree, grated ginger, chili, cinnamon, garam masala, and paprika. Stir this mix for a couple of minutes until it’s well blended and aromatic.
8. Throw in the sweet potatoes and stir them to coat in the sauce. Let them cook for about 5 minutes.
9. Add the cauliflower and canned chickpeas, followed by a splash of water to help everything come together. Simmer for about 15 minutes until the veggies are tender but not mushy.
10. Squeeze in the juice of a lemon, give it one last stir, and taste to adjust the seasoning as needed.
11. Serve the stew over the cooked brown rice, and you’re ready to dig in!

Cook’s Notes

This stew is pretty forgiving, which is what makes it perfect for busy weeknights. A couple of things to keep in mind:

• Be sure not to rush cooking the garlic and spices at the beginning. This step is key for building flavor.
• Leftover stew keeps beautifully in the fridge for up to three days. Just reheat gently on the stove or microwave.
• If you’re prepping ahead, you can chop the veggies and have them ready to go in the fridge—makes the actual cooking a breeze!
• Remember that simmering times can vary depending on the size of your veggie chunks, so keep an eye on them to achieve that perfect tender texture.

Make It Your Own

This stew is a canvas for your creativity. Here are a few ways to switch it up:

• Swap the sweet potatoes for butternut squash if that’s more your style.
• Use coconut milk instead of water for a creamier, richer stew.
• Add spinach or kale at the end for some extra greens.
• Top with a dollop of Greek yogurt for a tangy finish.

If you try this, I’d love to hear how it turns out—drop a comment or tag me! Your feedback makes my day and helps others find their new favorite cozy meal. Happy cooking!

Related Reading

• Lemon Chickpea & Tomato Stew | Made by Meaghan Moineau
• Paella for Four; A Wonderful Spanish Mixed Seafood Stew | Made by Meaghan Moineau
• Venison Stew | Made by Meaghan Moineau
• Oxtail Ragout | Made by Meaghan Moineau
• Oxtail Ragout | Made by Meaghan Moineau

Related update: Cauliflower Chickpea Stew

Related update: Classic Boeuf Bourguignon