yt-dlp has over 195,000 stars on GitHub, supports thousands of platforms, and is actively maintained by a global developer community. Unfortunately, the IFPI would like to see it on the EU's piracy watchlist.
Just so you know, the International Federation of the Phonographic Industry (IFPI) represents around 8,000 music labels across 70 countries.
In its submission to the EU's Counterfeit and Piracy Watch List consultation, the group calls yt-dlp "a major problem for the music industry" and names four of its maintainers by their GitHub handles.
A Piracy Watch List?
Run by the European Commission's Directorate-General for Trade and Economic Security, the Watch List identifies online services and physical marketplaces outside the EU reported to engage in or facilitate copyright infringement.
While it sounds serious, the undertaking isn't meant to gather legal findings and does not mandate any form of direct action. It's closer to a naming exercise intended to pressure operators and governments outside the EU into addressing the identified services.
The 2027 edition is being compiled from submissions received through September 2026, with the final list expected in Q2 2027.
What does their submission say?
IFPI's submission covers a wide range of copyright enforcement concerns, from AI music generators and cyberlockers to streaming fraud services and domain registrars. yt-dlp appears under the "stream ripping" section, grouped with commercial websites like Y2mate and Savefrom.
They describe the tool as an application that retrieves content by parsing web page data and interacting with platform playback endpoints, with GitHub serving as the primary delivery method for its source code, pre-compiled binaries, and installation instructions.
IFPI names four of the project's maintainers by their GitHub handles: pukkandan, who founded the project and led it between 2021 and 2024, and some core maintainers mentioned in the project's Maintainers.md file, like coletdjnz, bashonly, and Grub4K.
The same submission also flags X, Discord, Telegram, and Vimeo as platforms facilitating copyright infringement at scale.
It's a tool, not a service
The Watch List, as described by the European Commission, targets online service providers and physical marketplaces located outside the EU. yt-dlp fits neither description in any conventional sense.
IFPI acknowledges this by noting that the project's open source nature, its Unlicense licensing, and an extensive international developer community make it "difficult to contain and/or remove."
From their point of view, there's no central domain to block, no payment processor to cut off, and no hosting provider to strongarm into complying with a takedown request.
The source code is distributed globally and can be compiled by anyone with the skills to do so. But that doesn't mean yt-dlp is a piracy platform.
It's a command-line tool for downloading audio and video content, and categorizing it alongside dedicated ripping or piracy websites conflates a general-purpose downloader with services whose primary purpose is facilitating unauthorized copying.
Closing thoughts
The Watch List has been used in connection with enforcement against commercial stream-ripping platforms before.
Y2mate.com and eleven other stream-ripping sites were shut down in Vietnam in 2025, and Y2mate had previously appeared on the list.
Before that, in 2024, a German court held the host provider for youtube-dl.org liable in connection with facilitating circumvention. This shows that grouping an open source command-line tool with those commercial services in the same breath does not, by itself, make the tool one of those.
The first service call from an application that uses the AWS SDK for Java 2.x takes longer than subsequent calls. This problem is known as cold start. The new SDK client warm-up feature reduces cold-start latency. One call to SdkWarmUp.warmUp() during application startup exercises the SDK request path before your first service call. With AWS Lambda SnapStart, the warm-up becomes part of the snapshot, so the first request after every restore benefits as well.
How it works
On the first service call, the JVM loads and initializes the SDK classes for the request path, then runs that code in the interpreter until the just-in-time (JIT) compiler compiles it to native code. Establishing the connection adds a DNS lookup, a TLS handshake, and certificate chain validation. The calls that follow reuse the loaded code and a pooled connection, so they complete faster.
SDK client warm-up loads that code during application startup. It warms both the service client and the HTTP client:
The service client executes a local-only operation with a pre-written response rather than a AWS endpoint. This loads the request marshalling and response unmarshalling code.
The HTTP client makes one network call to an AWS endpoint, which loads the connection setup code. Because the call is unsigned and invokes no service operation, it requires no AWS credentials or permissions and incurs no AWS charges.
Requirements
SDK client warm-up ships in Java SDK version 2.54.0 and later as part of the sdk-core module, so it is available to every service client without an additional dependency. For more information about project setup, see Set up an Apache Maven project.
SdkWarmUp.warmUp()warms every service client on your classpath, along with the HTTP clients that they use. Use this method when your application calls each of those clients.
Invoke warmUp() with no arguments to warm all the clients on your classpath:
The SdkWarmUp.warmUp(Class<? extends SdkClient>... clients)overload warms only the clients you name, passed as SdkClient class objects. A synchronous client class warms the synchronous path (the service client and the synchronous HTTP clients), and an asynchronous client class warms the asynchronous path (the service client and the asynchronous HTTP clients).
If a dependency brings in service modules you don’t need, warmUp() warms those unused clients too, which adds to your startup time. To warm the clients you need and skip the rest, use the warmUp(Class...)overload.
The following example warms the synchronous service clients for Amazon S3 and Amazon DynamoDB:
Warm-up applies to any application that starts a new JVM, not only to functions that use SnapStart. In a service that runs on Amazon EC2 or in a container, call SdkWarmUp.warmUp() during startup, before the instance registers with a load balancer or reports itself healthy. The SDK request path is then already initialized when the first request arrives.
Use warm-up with AWS Lambda SnapStart
AWS Lambda SnapStart reduces cold starts by taking a snapshot of your initialized function and restoring from it on later invocations. When the warm-up is part of that snapshot, every restore starts with warm clients.
Call SdkWarmUp.warmUp() in the constructor of your function handler class:
import com.amazonaws.services.lambda.runtime.Context;
import com.amazonaws.services.lambda.runtime.RequestHandler;
import software.amazon.awssdk.core.warmup.SdkWarmUp;
public class MyHandler implements RequestHandler<String, String> {
public MyHandler() {
// Warm-up runs during initialization, before SnapStart takes the snapshot.
SdkWarmUp.warmUp();
// Your other initialization here.
}
@Override
public String handleRequest(String input, Context context) {
// Your handler logic here.
}
}
In this post, I introduced SDK client warm-up, a new feature in the AWS SDK for Java 2.x that moves SDK initialization from your first request to startup. I showed you how to warm every client on your classpath with a single call, and how to use warm-up in both long-running services and functions that use AWS Lambda SnapStart.
To learn more, see the SDK client warm-up topic in the AWS SDK for Java 2.x Developer Guide. Try it out today and share your feedback by creating an issue in the aws-sdk-java-v2 GitHub repository.
What’s new for command completion in IntelliJ IDEA
Modern IDEs are packed with power. The real challenge isn’t whether your IDE can do something – it’s remembering how to trigger it.
Some features live behind shortcuts. Others are available through intention menus, Search Everywhere, postfix completion, live templates, or tool windows. Discoverability is a constant tax on developer focus: As an IDE grows more capable, keeping every feature within reach gets harder.
That’s why we created command completion, a context-aware entry point to useful functionality from the place where you spend most of your time – the editor.
Typing .. anywhere in a file surfaces intelligent actions tailored to your current code and caret position. Whether you need to refactor, navigate, generate, document, explain, or fix code, you can act immediately without breaking your flow.
Rather than answering “What can I type here?”, command completion addresses a more useful question: “What can I do here?”
This feature has already been around for a while. In IntelliJ IDEA 2026.3 EAP, it is taking another big step toward becoming your primary interface for everyday coding assistance.
Here’s what’s new and improved:
Logpoints are easier to reach
Debugging with temporary println() statements is a habit many of us struggle to break. You add print statements, re-run the app, read the console, and then manually clean up the code afterward.
Logpoints are a cleaner, non-intrusive alternative – and now they are accessible right through command completion:
Simply type .. over an expression or block to drop a logpoint instantly, using the current expression or context as the logged value. Even better: IntelliJ IDEA will now suggest replacing existing print statements with logpoints, helping you move from messy code edits to clean, debugger-supported logging.
If you’re new to logpoints, take a look at the logpoints tutorial. It explains how to combine them with your AI agents in IntelliJ IDEA. If you missed our 2026.2 updates, logpoints got a revised UI, AI agent support, improved navigation, and faster evaluation, making them one of the most versatile debugging tools in your toolkit.
In-context AI assistance
You can now trigger AI actions using the same .. workflow. Need to explain a complex method, generate docstrings, or refactor a block? You no longer have to interrupt your flow, switch tools, or describe the exact location to the agent. Because the IDE already knows your active file, language, line number, and selected expression, it can give the agent this rich context.
Note: If you have the Air plugin installed, your requests will be automatically routed through it.
For actions that affect a specific class, method, or declaration, IntelliJ IDEA now highlights the target so it is clearer what the selected command will apply to before you run it.
Postfix completion and live templates
As part of our effort to unify completion workflows, postfix completion, live templates, and command completion now share a consistent interface. You’ll notice clearer filtering, sharper preview panels, and more intuitive discoverability directly from the completion popup.
More contexts
Command completion is also becoming useful in more contexts, including binary files and decompiled code.
We’ve also expanded support to structured and framework-specific environments. You can now use .. inside properties files, Spring workflows, and other domain-specific formats, with support for build scripts coming soon.
Why this matters
Command completion isn’t just another flavor of autocompletion. It is a fundamental shift in how you discover IDE functionality.
Instead of searching through top-level menus or memorizing hotkeys, you can start from where you already are – the code. IntelliJ IDEA continuously analyzes your syntax tree, scope, inspection state, and available actions to present only what is relevant in the moment.
For high-frequency actions, shortcuts remain the fastest choice. For everything else, command completion gives you a discoverable path directly from your code.
Try it out today
Open any Java, Kotlin, or Scala file in IntelliJ IDEA 2026.2 or 2026.3 EAP and type .. anywhere in the editor. Try it near a method, an expression, a regular expression, a declaration that needs documentation, or a place where you would normally open Search Everywhere. The completion popup will reflect what’s possible in that exact spot.
Command completion is continuously evolving, and we have big plans for future releases. Our core mission remains simple: one familiar entry point for whatever you want to do next in code.
Lyft has to pay out $272 million for the fraud they perpetrated on their employees from 2016 through 2020!
But then in 2020, they spent $200 million to make that fraud legal, so now they won't have to pay that again in the future!
According to methane-breathing money-ghouls who run our world, this was a great investment: they could have just spent an additional $50M/year on salaries, but now they legalized an across-the-board salary reduction that pays itself back in only 4 years. Half that, actually, because they went halfsies on it with Uber! Someone's getting a raise.
San Francisco City Attorney David Chiu said it was "the largest wage-and-hour settlement in California history." [...]
That's a time before voters approved Proposition 22, an Uber- and Lyft-funded ballot measure that classified ride-hail drivers as independent contractors, meaning they would not receive the benefits and wage protections afforded to other workers. The gig companies spent more than $200 million on the measure.
Die Bundesregierung plant ein Gesetz, das dem Bundeskriminalamt (BKA) und der Bundespolizei unter anderem Fähigkeiten zum „Hackback“ im Rahmen der „Gefahrenabwehr im Cyber-Raum“ geben soll. Dieses Gesetz würde den Behörden weitgehend unkontrollierte Befugnisse zum Eindringen in Computersysteme geben, auch von Opfern von Straftaten im digitalen Raum. Der CCC veröffentlicht dazu seine Stellungnahme. Darin warnt er vor kontraproduktiven Effekten für die IT-Sicherheit in Deutschland sowie vor einer Erosion des Vertrauens in das BSI und fordert eine Eingriffsgesamtrechnung für den Staat.
Luke Daley took his role as everyone’s favorite royal so seriously, the Kingdom Come: Deliverance 2 actor behind Hans Capon just opened a new medieval-inspired bar called The Nobleman. You’ll need to take a trip to the Czech capital of Prague if you want to experience your video game power fantasies (playing dice and getting drunk in a tavern) in real life, however.
Months after announcing plans to open The Nobleman – a bar inspired by the types of businesses real noblemen would gather and drink in – Daley has done it! The actor’s bar opened its doors to the public in Prague on October 1, and he’s been sharing pictures of the calmly-lit, old-timey business over the past few days. Check some out below.
“Nobleman” opens to the public tomorrow. pic.twitter.com/RJLEFReM1tSeptember 30, 2026
“Nobleman” opens to the public this Thursday. pic.twitter.com/LIFx3azJmSSeptember 29, 2026
One Kingdom Come fan over on Reddit shared that The Nobleman actually attracted quite the crowd on opening day, too: “Queue is not long but [the] wait is long. I heard it was 2 hours.” Developer Warhorse Studios is itself a Prague-based game maker, so it’s perhaps unsurprising to hear many Kingdom Come heads also live nearby.
“Ever since I can remember, I’ve always wanted to run a pub, a restaurant, a cafe, something. Something that was bricks and mortar, something that felt real,” Dale explained a few months ago. “Because so much of what I’ve done in my life has been acting, filmmaking, and more recently, streaming, and these things, however amazing they’ve been, there’s an element of which it doesn’t feel real to me, and I’ve always wanted a business that was mine that I could run and I could come to and I could be a part of a community and engender a great feeling in a community.”
Log in
