A coiled giant anaconda. They are the largest snake species in Brazil and play a major role in legends including the ‘Boiuna’ and the ‘Cobra Grande.’ CREDIT: Beatriz Cosendey. Get the Popular Science daily newsletter💡 Breakthroughs, discoveries, and DIY tips sent every weekday. South America’s lush Amazon region is a biodiversity hotspot, which means that every living thing must find a way to co-exist. Even some of the most feared snakes on the planet–anacondas. In a paper published June 16 in the journal Frontiers in Amphibian and Reptile Science, conservation biologists Beatriz Cosendey and Juarez Carlos Brito Pezzuti from the Federal University of Pará’s Center for Amazonian Studies in Brazil, analyze the key points behind the interactions between humans and the local anaconda populations. Ahead of the paper’s publication, the team at Frontiers conducted this wide-ranging Q&A with Conesday. It has not been altered. Frontiers: What inspired you to become a researcher? Beatriz Cosendey: As a child, I was fascinated by reports and documentaries about field research and often wondered what it took to be there and what kind of knowledge was being produced. Later, as an ecologist, I felt the need for approaches that better connected scientific research with real-world contexts. I became especially interested in perspectives that viewed humans not as separate from nature, but as part of ecological systems. This led me to explore integrative methods that incorporate local and traditional knowledge, aiming to make research more relevant and accessible to the communities involved. F: Can you tell us about the research you’re currently working on? BC: My research focuses on ethnobiology, an interdisciplinary field intersecting ecology, conservation, and traditional knowledge. We investigate not only the biodiversity of an area but also the relationship local communities have with surrounding species, providing a better understanding of local dynamics and areas needing special attention for conservation. After all, no one knows a place better than those who have lived there for generations. This deep familiarity allows for early detection of changes or environmental shifts. Additionally, developing a collaborative project with residents generates greater engagement, as they recognize themselves as active contributors; and collective participation is essential for effective conservation. Local boating the Amazon River. CREDIT: Beatriz Cosendey. F: Could you tell us about one of the legends surrounding anacondas? BC: One of the greatest myths is about the Great Snake—a huge snake that is said to inhabit the Amazon River and sleep beneath the town. According to the dwellers, the Great Snake is an anaconda that has grown too large; its movements can shake the river’s waters, and its eyes look like fire in the darkness of night. People say anacondas can grow so big that they can swallow large animals—including humans or cattle—without difficulty. F: What could be the reasons why the traditional role of anacondas as a spiritual and mythological entity has changed? Do you think the fact that fewer anacondas have been seen in recent years contributes to their diminished importance as an mythological entity? BC: Not exactly. I believe the two are related, but not in a direct way. The mythology still exists, but among Aritapera dwellers, there’s a more practical, everyday concern—mainly the fear of losing their chickens. As a result, anacondas have come to be seen as stealthy thieves. These traits are mostly associated with smaller individuals (up to around 2–2.5 meters), while the larger ones—which may still carry the symbolic weight of the ‘Great Snake’—tend to retreat to more sheltered areas; because of the presence of houses, motorized boats, and general noise, they are now seen much less frequently. A giant anaconda is being measured. Credit: Pedro Calazans. F: Can you share some of the quotes you’ve collected in interviews that show the attitude of community members towards anacondas? How do chickens come into play? BC: When talking about anacondas, one thing always comes up: chickens. “Chicken is her [the anaconda’s] favorite dish. If one clucks, she comes,” said one dweller. This kind of remark helps explain why the conflict is often framed in economic terms. During the interviews and conversations with local dwellers, many emphasized the financial impact of losing their animals: “The biggest loss is that they keep taking chicks and chickens…” or “You raise the chicken—you can’t just let it be eaten for free, right?” For them, it’s a loss of investment, especially since corn, which is used as chicken feed, is expensive. As one person put it: “We spend time feeding and raising the birds, and then the snake comes and takes them.” One dweller shared that, in an attempt to prevent another loss, he killed the anaconda and removed the last chicken it had swallowed from its belly—”it was still fresh,” he said—and used it for his meal, cooking the chicken for lunch so it wouldn’t go to waste. One of the Amazonas communities where the researchers conducted their research. CREDIT: Beatriz Cosendey. Some interviewees reported that they had to rebuild their chicken coops and pigsties because too many anacondas were getting in. Participants would point out where the anaconda had entered and explained that they came in through gaps or cracks but couldn’t get out afterwards because they ‘tufavam’ — a local term referring to the snake’s body swelling after ingesting prey. We saw chicken coops made with mesh, with nylon, some that worked and some that didn’t. Guided by the locals’ insights, we concluded that the best solution to compensate for the gaps between the wooden slats is to line the coop with a fine nylon mesh (to block smaller animals), and on the outside, a layer of wire mesh, which protects the inner mesh and prevents the entry of larger animals. F: Are there any common misconceptions about this area of research? How would you address them? BC: Yes, very much. Although ethnobiology is an old science, it’s still underexplored and often misunderstood. In some fields, there are ongoing debates about the robustness and scientific validity of the field and related areas. This is largely because the findings don’t always rely only on hard statistical data. However, like any other scientific field, it follows standardized methodologies, and no result is accepted without proper grounding. What happens is that ethnobiology leans more toward the human sciences, placing human beings and traditional knowledge as key variables within its framework. To address these misconceptions, I believe it’s important to emphasize that ethnobiology produces solid and relevant knowledge—especially in the context of conservation and sustainable development. It offers insights that purely biological approaches might overlook and helps build bridges between science and society. The study focused on the várzea regions of the Lower Amazon River. CREDIT: Beatriz Cosendey. F: What are some of the areas of research you’d like to see tackled in the years ahead? BC: I’d like to see more conservation projects that include local communities as active participants rather than as passive observers. Incorporating their voices, perspectives, and needs not only makes initiatives more effective, but also more just. There is also great potential in recognizing and valuing traditional knowledge. Beyond its cultural significance, certain practices—such as the use of natural compounds—could become practical assets for other vulnerable regions. Once properly documented and understood, many of these approaches offer adaptable forms of environmental management and could help inform broader conservation strategies elsewhere. F: How has open science benefited the reach and impact of your research? BC: Open science is crucial for making research more accessible. By eliminating access barriers, it facilitates a broader exchange of knowledge—important especially for interdisciplinary research like mine which draws on multiple knowledge systems and gains value when shared widely. For scientific work, it ensures that knowledge reaches a wider audience, including practitioners and policymakers. This openness fosters dialogue across different sectors, making research more inclusive and encouraging greater collaboration among diverse groups. The Q&A can also be read here.

Jun 16, 2025Ravie LakshmananMalware / DevOps Cybersecurity researchers have discovered a malicious package on the Python Package Index (PyPI) repository that's capable of harvesting sensitive developer-related information, such as credentials, configuration data, and environment variables, among others. The package, named chimera-sandbox-extensions, attracted 143 downloads and likely targets users of a service called Chimera Sandbox, which was released by Singaporean tech company Grab last August to facilitate "experimentation and development of [machine learning] solutions." The package masquerades as a helper module for Chimera Sandbox, but "aims to steal credentials and other sensitive information such as Jamf configuration, CI/CD environment variables, AWS tokens, and more," JFrog security researcher Guy Korolevski said in a report published last week. Once installed, it attempts to connect to an external domain whose domain name is generated using a domain generation algorithm (DGA) in order to download and execute a next-stage payload. Specifically, the malware acquires from the domain an authentication token, which is then used to send a request to the same domain and retrieve the Python-based information stealer. The stealer malware is equipped to siphon a wide range of data from infected machines. This includes - JAMF receipts, which are records of software packages installed by Jamf Pro on managed computers Pod sandbox environment authentication tokens and git information CI/CD information from environment variables Zscaler host configuration Amazon Web Services account information and tokens Public IP address General platform, user, and host information The kind of data gathered by the malware shows that it's mainly geared towards corporate and cloud infrastructure. In addition, the extraction of JAMF receipts indicates that it's also capable of targeting Apple macOS systems. The collected information is sent via a POST request back to the same domain, after which the server assesses if the machine is a worthy target for further exploitation. However, JFrog said it was unable to obtain the payload at the time of analysis. "The targeted approach employed by this malware, along with the complexity of its multi-stage targeted payload, distinguishes it from the more generic open-source malware threats we have encountered thus far, highlighting the advancements that malicious packages have made recently," Jonathan Sar Shalom, director of threat research at JFrog Security Research team, said. "This new sophistication of malware underscores why development teams remain vigilant with updates—alongside proactive security research – to defend against emerging threats and maintain software integrity." The disclosure comes as SafeDep and Veracode detailed a number of malware-laced npm packages that are designed to execute remote code and download additional payloads. The packages in question are listed below - eslint-config-airbnb-compat (676 Downloads) ts-runtime-compat-check (1,588 Downloads) solders (983 Downloads) @mediawave/lib (386 Downloads) All the identified npm packages have since been taken down from npm, but not before they were downloaded hundreds of times from the package registry. SafeDep's analysis of eslint-config-airbnb-compat found that the JavaScript library has ts-runtime-compat-check listed as a dependency, which, in turn, contacts an external server defined in the former package ("proxy.eslint-proxy[.]site") to retrieve and execute a Base64-encoded string. The exact nature of the payload is unknown. "It implements a multi-stage remote code execution attack using a transitive dependency to hide the malicious code," SafeDep researcher Kunal Singh said. Solders, on the other hand, has been found to incorporate a post-install script in its package.json, causing the malicious code to be automatically executed as soon as the package is installed. "At first glance, it's hard to believe that this is actually valid JavaScript," the Veracode Threat Research team said. "It looks like a seemingly random collection of Japanese symbols. It turns out that this particular obfuscation scheme uses the Unicode characters as variable names and a sophisticated chain of dynamic code generation to work." Decoding the script reveals an extra layer of obfuscation, unpacking which reveals its main function: Check if the compromised machine is Windows, and if so, run a PowerShell command to retrieve a next-stage payload from a remote server ("firewall[.]tel"). This second-stage PowerShell script, also obscured, is designed to fetch a Windows batch script from another domain ("cdn.audiowave[.]org") and configures a Windows Defender Antivirus exclusion list to avoid detection. The batch script then paves the way for the execution of a .NET DLL that reaches out to a PNG image hosted on ImgBB ("i.ibb[.]co"). "[The DLL] is grabbing the last two pixels from this image and then looping through some data contained elsewhere in it," Veracode said. "It ultimately builds up in memory YET ANOTHER .NET DLL." Furthermore, the DLL is equipped to create task scheduler entries and features the ability to bypass user account control (UAC) using a combination of FodHelper.exe and programmatic identifiers (ProgIDs) to evade defenses and avoid triggering any security alerts to the user. The newly-downloaded DLL is Pulsar RAT, a "free, open-source Remote Administration Tool for Windows" and a variant of the Quasar RAT. "From a wall of Japanese characters to a RAT hidden within the pixels of a PNG file, the attacker went to extraordinary lengths to conceal their payload, nesting it a dozen layers deep to evade detection," Veracode said. "While the attacker's ultimate objective for deploying the Pulsar RAT remains unclear, the sheer complexity of this delivery mechanism is a powerful indicator of malicious intent." Crypto Malware in the Open-Source Supply Chain The findings also coincide with a report from Socket that identified credential stealers, cryptocurrency drainers, cryptojackers, and clippers as the main types of threats targeting the cryptocurrency and blockchain development ecosystem. Some of the examples of these packages include - express-dompurify and pumptoolforvolumeandcomment, which are capable of harvesting browser credentials and cryptocurrency wallet keys bs58js, which drains a victim's wallet and uses multi-hop transfers to obscure theft and frustrate forensic tracing. lsjglsjdv, asyncaiosignal, and raydium-sdk-liquidity-init, which functions as a clipper to monitor the system clipboard for cryptocurrency wallet strings and replace them with threat actor‑controlled addresses to reroute transactions to the attackers "As Web3 development converges with mainstream software engineering, the attack surface for blockchain-focused projects is expanding in both scale and complexity," Socket security researcher Kirill Boychenko said. "Financially motivated threat actors and state-sponsored groups are rapidly evolving their tactics to exploit systemic weaknesses in the software supply chain. These campaigns are iterative, persistent, and increasingly tailored to high-value targets." AI and Slopsquatting The rise of artificial intelligence (AI)-assisted coding, also called vibe coding, has unleashed another novel threat in the form of slopsquatting, where large language models (LLMs) can hallucinate non-existent but plausible package names that bad actors can weaponize to conduct supply chain attacks. Trend Micro, in a report last week, said it observed an unnamed advanced agent "confidently" cooking up a phantom Python package named starlette-reverse-proxy, only for the build process to crash with the error "module not found." However, should an adversary upload a package with the same name on the repository, it can have serious security consequences. Furthermore, the cybersecurity company noted that advanced coding agents and workflows such as Claude Code CLI, OpenAI Codex CLI, and Cursor AI with Model Context Protocol (MCP)-backed validation can help reduce, but not completely eliminate, the risk of slopsquatting. "When agents hallucinate dependencies or install unverified packages, they create an opportunity for slopsquatting attacks, in which malicious actors pre-register those same hallucinated names on public registries," security researcher Sean Park said. "While reasoning-enhanced agents can reduce the rate of phantom suggestions by approximately half, they do not eliminate them entirely. Even the vibe-coding workflow augmented with live MCP validations achieves the lowest rates of slip-through, but still misses edge cases." Found this article interesting? Follow us on Twitter  and LinkedIn to read more exclusive content we post. SHARE    

Development and Testing  Rate this post Sorting is a basic task in programming. It arranges data in order. There are many sorting algorithms. Selection Sort is one of the simplest sorting methods. It is easy to understand and code. But it is not the fastest. In this guide, we will explain the Selection Sort Time Complexity. We will cover best, worst, and average cases. What Is Selection Sort? Selection Sort works by selecting the smallest element from the list. It places it in the correct position. It repeats this process for all elements. One by one, it moves the smallest values to the front. Let’s see an example: Input: [5, 3, 8, 2]Step 1: Smallest is 2 → swap with 5 → [2, 3, 8, 5]Step 2: Smallest in remaining is 3 → already correctStep 3: Smallest in remaining is 5 → swap with 8 → [2, 3, 5, 8] Now the list is sorted.How Selection Sort Works Selection Sort uses two loops. The outer loop moves one index at a time. The inner loop finds the smallest element. After each pass, the smallest value is moved to the front. The position is fixed. Selection Sort does not care if the list is sorted or not. It always does the same steps. Selection Sort Algorithm Here is the basic algorithm: Start from the first element Find the smallest in the rest of the list Swap it with the current element Repeat for each element This repeats until all elements are sorted. Selection Sort Code (Java Example) javaCopyEditpublic class SelectionSort { public static void sort(int[] arr) { int n = arr.length; for (int i = 0; i < n - 1; i++) { int min = i; for (int j = i + 1; j < n; j++) { if (arr[j] < arr[min]) { min = j; } } int temp = arr[min]; arr[min] = arr[i]; arr[i] = temp; } } } This code uses two loops. The outer loop runs n-1 times. The inner loop finds the minimum. Selection Sort Time Complexity Now let’s understand the main topic. Let’s analyze Selection Sort Time Complexity in three cases. 1. Best Case Even if the array is already sorted, Selection Sort checks all elements. It keeps comparing and swapping. Time Complexity: O(n²) Reason: Inner loop runs fully, regardless of the order Example Input: [1, 2, 3, 4, 5] Even here, every comparison still happens. Only fewer swaps occur, but comparisons remain the same. 2. Worst Case This happens when the array is in reverse order. But Selection Sort does not optimize for this. Time Complexity: O(n²) Reason: Still needs full comparisons Example Input: [5, 4, 3, 2, 1] Even in reverse, the steps are the same. It compares and finds the smallest element every time. 3. Average Case This is when elements are randomly placed. It is the most common scenario in real-world problems. Time Complexity: O(n²) Reason: Still compares each element in the inner loop Example Input: [3, 1, 4, 2, 5] Selection Sort does not change behavior based on input order. So the complexity remains the same. Why Is It Always O(n²)? Selection Sort compares all pairs of elements. The number of comparisons does not change. Total comparisons = n × (n – 1) / 2 That’s why the time complexity is always O(n²).It does not reduce steps in any case. It does not take advantage of sorted elements. Space Complexity Selection Sort does not need extra space. It sorts in place. Space Complexity: O(1) Only a few variables are used No extra arrays or memory needed This is one good point of the Selection Sort. Comparison with Other Algorithms Let’s compare Selection Sort with other basic sorts: AlgorithmBest CaseAverage CaseWorst CaseSpaceSelection SortO(n²)O(n²)O(n²)O(1)Bubble SortO(n)O(n²)O(n²)O(1)Insertion SortO(n)O(n²)O(n²)O(1)Merge SortO(n log n)O(n log n)O(n log n)O(n)Quick SortO(n log n)O(n log n)O(n²)O(log n) As you see, Selection Sort is slower than Merge Sort and Quick Sort. Advantages of Selection Sort Very simple and easy to understand Works well with small datasets Needs very little memory Good for learning purposes Disadvantages of Selection Sort Slow on large datasets Always takes the same time, even if sorted Not efficient for real-world use When to Use Selection Sort Use Selection Sort when: You are working with a very small dataset You want to teach or learn sorting logic You want stable, low-memory sorting Avoid it for: Large datasets Performance-sensitive programs Conclusion Selection Sort Time Complexity is simple to understand. But it is not efficient for big problems. It always takes O(n²) time, no matter the case. That is the same for best, worst, and average inputs. Still, it is useful in some cases. It’s great for learning sorting basics. It uses very little memory. If you’re working with small arrays, Selection Sort is fine. For large data, use better algorithms. Understanding its time complexity helps you choose the right algorithm. Always pick the tool that fits your task. Tech World TimesTech World Times (TWT), a global collective focusing on the latest tech news and trends in blockchain, Fintech, Development & Testing, AI and Startups. If you are looking for the guest post then contact at techworldtimes@gmail.com

Interviews Love, Death + Robots – Volume 4: Tim Miller (Creator & Director) & Jennifer Yuh Nelson (Supervising Director) By Vincent Frei - 02/06/2025 Earlier this year, Tim Miller spoke to us about his animated anthology Secret Level. Now, he returns to discuss the latest season of Love, Death + Robots. Jennifer Yuh Nelson talked about season two of Love, Death + Robots in 2021. She later worked on The Sea Beast, before returning once again to the anthology universe. What was your overall vision for the fourth season of Love, Death and Robots and how did it evolve from previous seasons? Tim Miller (TM) // We have the same strategy as every volume – we try to pick the best stories we know of and provide a mix that is hopefully appealing to everyone. There are a lot of variables to consider. Including genre, tone, and style of animation, such as stop motion, CG, and 2D. We try not to have two stories that are too similar. For example, if there’s already a military sci-fi story, we avoid selecting another one. We like to mix humor, horror, sci-fi, fantasy, and anything else that we think might be interesting from either a story or animation perspective. How did you approach the balance between experimenting with new styles and maintaining the signature identity of the show? TM // Honestly, we just try and follow our gut. What we think is interesting as filmmakers, animators, and storytellers will also be interesting to the animation community and fans alike. So, we keep an eye out for new voices, filmmakers, and new ways of doing things to keep things interesting. I’m not sure we have an identity of the show. In fact, I think if we did have an identity, it would be that we don’t have an identity… but we try and do whatever we think is interesting. Jennifer Yuh Nelson (JYN) // The fortunate thing about LDR is that the signature itself is experimenting with new styles. The trick is finding new aggressively experimental styles that still communicate to a mass audience. The stories are key to that. If the story is engaging, even to an audience that doesn’t usually gravitate to animation, then you can make it looks as weird as you want. What are some of the key challenges you faced while overseeing this season and how do you tackle them? TM // This season, there was a lot going on in the animation community that created some challenges with getting work done, whether studios were too full or ceased to exist entirely. Everyone struggled with budgets. But I didn’t feel like it was a problem with our show but rather a problem with the entire industry. People were struggling. And then it’s just always difficult when your ambition is high, your budgets are reasonable but still challenging, and you have to wrangle hundreds of people to get on board with your vision. (JYN) // These shows take a long time to make. R&D for a look that doesn’t exist can take a lot of trial and error. For example, Emily Dean, who directed Very Pulse of the Machine last season, did For He Can Creep this season. She had a cool angle of making her episode look like lithography. That was very very hard, but somehow Polygon, the studio that made both shorts, came through with it. And I think it turned out very well. Can you talk about how you selected the different animation studios for this season? What made you decide to work with the studios involved? (JYN) // We’ve been very fortunate to have worked with amazing people and studios these last few seasons, so it made sense to float some stories by them again. But it really comes down to the stories, and how each leans towards a certain technique. For example, How Zeke Found Religion was holding a slot where we wanted something 2D. We went to Titmouse because they were great with pushing the boundaries of 2D animation, and they suggested Diego Porral as a director who could bring a modern edge. How do you ensure each studio’s unique visual style complements the story and tone of each episode? TM // I know this sounds a little mystical and I don’t mean it to be, but I think the story speaks to you about style. Some things just feels right, and you have an innate concept of what would be the best version of the story, whether it’s stop motion, CG, 2D animation, or even live action. When you start thinking about the story in a creative way, a style becomes apparent. Which is not to say there aren’t many ways to do things and tell stories, but we feel a best version becomes clear. (JYN) // We do a lot of research, not just into what the studios have done before, but also into what they wish to do but haven’t had the chance to do. Often it’s just a matter of getting to know them and seeing if they have a philosophy of pushing for experimentation and risk. Then we try to support them as much as possible in their creative R&D. You both directed episodes for this season, what was that experience like? How did it differ from your work as overseeing directors? TM // For me, it’s really just trying to create the best story and I love working with the artists and trying to be open to what everybody brings to the table because everybody wants to do the best possible episode they can. I try and be open to letting people help carry that load. The best thing about being a director is that you get to pick and choose between all the great ideas that everybody has and shape the narrative by getting the benefit of everyone’s expertise and talent. (JYN) // It’s a different mindset. As a Supervising Director, I help. As a Director, I do. On episodes I’m not directing, I am deciphering that director’s ambition and pushing for whatever is required to make that absolutely great. On an episode I’m directing, every choice and image has to go through my brain so it’s more a reflection of my personal taste. Plus I tend to storyboard a lot more on my own episodes since it’s a way for me to communicate to the crew. I storyboard a lot on other episodes, but mainly to help figure out problems here and there. It also doesn’t come out of those director’s budgets so the free storyboarding is often welcomed. How did you choose the episode you worked on yourself and what aspects of it made it resonate with you both? TM // In my case with “The Screaming of the Tyrannosaur,” it was really by default. I had written the episode for Zack Snyder but Zack was too busy, and by that time I’d already fallen in love with the story, so I figured, why not just do it myself? As for “Golgotha,” I always loved the story. It was very efficient and short, which is hard to find in a story – it felt like a full meal. It has a beginning, middle, and end and it resolves in a satisfying way. “Golgotha” had all of that, plus it was funny. (JYN) // Spider Rose was on the story wall since the beginning. It was one of the “special” ones- very hard, ambitious, uncomfortable. Over the seasons we offered it to different directors and they veered away from it for one reason or another. But it glowed with a complexity that’s rare in a short story. I think that’s because it was written as an exploration for a far larger world that Bruce Sterling was developing. For me, it was the raw emotionality that drew me in. It’s how I understand how to communicate any story. And I love the way Spider Rose draws you in with emotion then shivs you with it. Were there any episodes in this season that particularly pushed the boundaries of what you had done before? How did that push happen? TM // I think “How Zeke got Religion” pushed the boundaries of 2D animation. The amount of detail and action that the guys at Titmouse were able to pull off was truly astonishing. Once again, Robert Valley outdid himself with 400 boys. The action scene at the end was one of my favorite pieces of animation in all of Love, Death, and Robots. (JYN) // Golgotha, Tim’s episode is live action, which is a rarity for the show. There was one live action episode in season 1, but none since. It is primarily an animation series, but nowadays, the line is so fuzzy that it seemed to make sense. How do you balance creative freedom with the thematic unity required for a show like Love, Death, and Robots? TM // There isn’t really a thematic unity. We’re just trying to create the best version of each of the episodes. They don’t tie into each other, they don’t relate to each other, they aren’t supposed to be about either Love, Death or Robots – the title is a meant to be a “catchall” that could hold ANY story or visual art we thought might be cool. Hopefully, the overall assemblage feels like a balanced meal with a little bit of something for everybody. But thematically speaking, again, I think our theme is that there is no theme. (JYN) // We try to set the foundation with a good story, based off the many short stories Tim has read over the years. Then the HOW of what that story becomes is the wooly Wild West. The directors and studios are fully encouraged to push all the boundaries of how to make these as innovative, impractical, and beautiful as they want. And, since each short is under 15 minutes, the studios we choose can be as experimental and scrappy as each story demands. Looking at the overall direction of the season, was there any unexpected moments or surprises that stood out to you during production? TM // Yeah, I think the color palette for “Zeke” was a shock to me in a wonderful way because it was completely unexpected and nothing I would ever do as a director but boy did I love it. And I think that “Can’t Stop” was an interesting addition. We wanted to do a music video from volume 1 onward, and this was the moment that we took to do it. I think it’s the greatest concert video ever made. (JYN) // Why do we have so many cats and babies? I’ve no idea. But when we saw the first giant baby shots in 400 Boys, it was a rare joy. They walk like babies, real babies. And somehow that was both accurate and terrifying. Looking forward, where do you see the show heading in future seasons, are there any new themes or concepts you’d love to explore? TM // So many directors in the industry have asked if they could play in our sandbox, and I would like to expand our reach to get some established names. Not that we don’t want new talent – we will always want that – but it would be great to have some really fantastic directors who have accomplished big movies come and play with our stories. I also think there’s a version where we bring in some content that may have existed in other mediums like comic books and perhaps tell some larger stories that take more than one episode to tell. Truthfully, I’ve already got a some really interesting stories picked out for the next few seasons, — of course those will change as the show evolves, but they’re fascinating stories that explore the whole arc of history… past, present, and future and some of the big challenges that humanity is facing today. I’d be lying if I didn’t mention that many of them explore the future of what mankind will become with the advent of AI and how artificial intelligence and humanity’s future intersect. (JYN) // Often themes only show up afterwards. There is a bit of a “herding cats” energy to the show that promises surprises in the production process. But the point of a show like this is that it is surprising. It has its own energy, and sometimes we just have to listen to it rather than dictate. If you had the opportunity to create any kind of story for Love, Death, and Robots, what would your dream narrative and what type of animation style would you envision for it? TM // Well, I have to say that I love high-end 3D animation, and that’s what Blur does for a reason. And secondly, I’d like to do a kind of story that could be live action and has some vast scope to it, but we choose to do it in animation because we get more value from using the techniques that animation brings. We can tell a bigger story, with more scope, and more action than we would using any other methodology…. and it competes favorably with live action in terms of the kind of audience that comes to watch it. Not just fans of animation, but fans of good cinema. (JYN) // I’d love to see an anime episode, like a Tsutomu Nihei fight scene, or something by Katsuhiro Otomo. A big thanks for your time. WANT TO KNOW MORE?Blur Studio: Dedicated page about Love, Death + Robots: Volume 4 on Blur Studio website. © Vincent Frei – The Art of VFX – 2025