Podcasts about Piracy

In this episode of Power Talks, recorded live at Latitude59 in Nairobi, host Ssuna Ronald sits down with Mike Strano, Co-founder and COO of Yakwetu Online Limited. Dive into the ambitious mission to create a premier on-demand platform dedicated entirely to African storytelling. Mike reveals the shocking scale of the piracy crisis robbing African creatives of $803 million a year and how his company's proprietary technology is not just streaming content, but actively creating a legal, profitable ecosystem for filmmakers.We explore Yakwetu's unique four-product strategy, from the pay-per-view model of "My Movies Africa" to their groundbreaking encrypted screening tool that's being used by churches and events. Mike also shares his philosophy as a bootstrapped founder with a proven track record, why he believes his venture is a safe bet for investors, and his plan to legitimize 54,000 illegal movie shops across Kenya. If you're curious about the future of African media, entertainment tech, and resilient entrepreneurship, this conversation is a must-listen.(00:00:43) - The Big Idea: Mike introduces Yakwetu and its mission to empower African creatives.(00:01:10) - The Product Suite: A breakdown of Yakwetu's four key products, including "My Movies Africa."(00:02:16) - The $803M Piracy Problem: Mike reveals the staggering financial loss and their encrypted solution for screenings.(00:04:18) - Legitimizing an Illegal Market: The innovative plan to partner with 54,000 "movie shops" and split revenue three ways.(00:06:08) - Quality vs. Relatability: How Yakwetu curates content and the power of a good story.(00:07:48) - The Bootstrapped Journey: Mike discusses bootstrapping since 2014 and the current search for a $1M pre-seed round.(00:09:42) - The Future Vision: Yakwetu's next step as a marketplace for media, similar to Amazon's model.(00:11:53) - Global Ambitions: Patenting their anti-piracy tech for markets in Latin America, Eastern Europe, and beyond.Power Talks is your front-row seat to the conversations shaping the future of business and technology in Africa. Host Ssuna Ronald brings you face-to-face with the most dynamic founders, investors, and ecosystem builders driving progress across the continent. From deep-dive interviews with startup founders to insights from top VCs and event coverage from hubs like Nairobi and Kigali, we unpack the big ideas, the bigger opportunities, and the game-changing conversations you need to hear.Subscribe to stay updated on Africa's innovation revolution.Enjoyed this episode? Please subscribe, rate us, and share it with a friend, a founder, or anyone who believes in the power of African innovation.Executive Producer: Ssuna RonaldSound Engineer: Gumisiriza RichardArt Direction: Abdu Latif OkalangPowered By: Latitude 59
Connect via: ⁠⁠⁠LinkedIn⁠⁠⁠ & ⁠⁠⁠Instagram⁠⁠⁠For Inquiries: ⁠⁠⁠emailpowertalks@gmail.com⁠⁠⁠

Links: Outsourcing Security at Sea—The Return of Private Maritime-Security Companies and Their Role in Twenty-First-Century Maritime Security, Naval War College Review Irregular Warfare InitiativePieter W.G. Zhao is a PhD Researcher and Junior Lecturer at the Erasmus University in Rotterdam, the Netherlands, focusing on history and international relations in the maritime domain. He's also a Nonresident Fellow at the Irregular Warfare Initiative. His doctoral research analyzes the changing dynamics in the 21st-century maritime warfare and security environment from an applied historical perspective, focusing on non-state actors and irregular warfare at sea. He obtained his BA and MA in History from the Erasmus University Rotterdam, followed by a second Master's degree in International Security studies from Sciences Po, Paris, and the Johns Hopkins University's School of Advanced International Studies in Washington DC.LinkedInBlueSkyContact PageJ. Overton is co-host of the Sea Control podcast and edited the essay collection “Seapower by Other Means: Naval Contributions to National Objectives Beyond Sea Control, Power Projection, and Traditional Service Missions.”

As viral AI models like Openai's Sora 2 raise risks around Hollywood and copyright infringement, new tools like the anti-piracy startup SoundPatrol are emerging to protect intellectual property rights. Plus, AWS is still struggling to resolve its major outage after a six hour disruption this morning looked like it had been mitigated.  Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Rumors are intensifying that Target and Walmart are poised to remove Xbox Hardware from store shelves. An inventory search lends some smoke to the rumors around one of those stores. Could this be a potentially fatal blow to the hardware arm of one of the "big 3"? We discuss this and much more on another week of the longest running podcast about video games, Orange Lounge Radio.   OLR: The Final Episode will air on 23, November 2025.   Also in the News: * Switch Piracy Mod from Reddit Nintendo Legal Action * Taito Caught Using AI for Gaming History Photo * Halo Art Director Leaves * Battlefield 6 Launch   All this and more on the show where EVERY gamer has a voice-- Orange Lounge Radio! LIVE on the VOG Network, Sunday nights at 6 Pacific, 9 Eastern www.vognetwork.com Mailbag: participate (at) orangeloungeradio dot com

You can’t stop every pirate, but you can slow them down—and keep real customers smiling. Today we cover low-cost deterrents, “soft DRM,” and community perks that make stealing less attractive. Side Hustle School features a new episode EVERY DAY, featuring detailed case studies of people who earn extra money without quitting their job. This year, the show includes free guided lessons and listener Q&A several days each week. Show notes: SideHustleSchool.com Email: team@sidehustleschool.com Be on the show: SideHustleSchool.com/questions Connect on Instagram: @193countries Visit Chris's main site: ChrisGuillebeau.com Read A Year of Mental Health: yearofmentalhealth.com If you're enjoying the show, please pass it along! It's free and has been published every single day since January 1, 2017. We're also very grateful for your five-star ratings—it shows that people are listening and looking forward to new episodes.

Check out https://vessi.com/lmg to enter Vessi's October giveaway for a chance to win over $6,000 in prizes! You can also enjoy 20% off at checkout for this month only using our link! Giveaway Details: 7 Prizes. 7 Winners. Over $6,000 in Prizes, Ends Oct 31, 2025, Enter your email for a chance to win, no purchase necessary Check out Proton Mail for free at https://proton.me/wan or get up to 38% off their plans! Visit https://www.squarespace.com/WAN and use offer code WAN for 10% off Check out Ubiquiti at: https://lmg.gg/ubiquitilan Get a Circuit Board skin for your device so dbrand can keep messing with Linus at https://dbrand.com/pcb Check out Dell's powerful business laptops at: https://lmg.gg/dellprowan Pick up a Secretlab Titan Evo Ergonomic Gaming Chair today at: https://lmg.gg/secretlabwan Get a special deal on Private Internet Access VPN today at https://www.piavpn.com/LinusWan Purchases made through some store links may provide some compensation to Linus Media Group. Learn more about your ad choices. Visit megaphone.fm/adchoices

PREVIEW: ERIC JAY DOLIN'S LEFT FOR DEAD  D'Aranda's Treachery and the Semi-piracy of the Prize System Guest: Eric Jay Dolin The book focuses on the greed involved in the prize system during a minor 1812 incident in the Falkland Islands. Lieutenant D'Aranda of HMS Nancy arrived intending to be a hero by rescuing castaways. However, D'Aranda immediately ripped up the Americans' humanitarian deal, viewing the situation as an opportunity for personal financial gain. He claimed the American ship Nanina as a prize and the Americans as prisoners of war, highlighting how many interpreted the prize system as "semi-piracy." The British castaways did not oppose D'Aranda's decision. D'Aranda completed his villainous act by abandoning Charles Barnard and his party who were hunting ashore to secure necessary food provisions.

Popular anime streaming site HiAnime is listed as a "priority notorious streaming site" in a new list of piracy sites being targeted by the U.S. court system.As seen via Torrent Freak, the Motion Picture Association published a response for public comment dated Oct. 1, 2025, by the Office of the U.S. Trade Representative for "submissions from the public on notorious markets outside of the United States." Among these submissions is a list of "Priority Notorious Linking and Streaming Sites," which includes HiAnime along with platforms such as Myflixerz and Cuevana. HiAnime is still widely considered the world's largest anime piracy site, with its monthly views outstripping the likes of Disney+ in January this year.The official description for the platform from the MPA statement reads, "Hianime, formerly known as Zoro[.]to and Aniwatch[.]to, has a global ranking of 159 with 244.2 million visits from 17.54 million unique visitors in August 2025, according to SimilarWeb. The site provides access to a range of content, especially anime content. The hosting location is masked using Cloudflare's reverse proxy, but the site is currently believed to be operated from Vietnam." HiAnime is listed as a "priority" site on the new report, alongside Myflixerz/Sflix and Cuevana.biz/is, while additional new entries to the list include the likes of Anime-Sama and Kisskh.co/kisskh.ovh.Support The Podcast!⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://creators.spotify.com/pod/show/roose366/subscribe⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Follow For More Content &Streams!Science Podcast: ⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/5nFXe9dPeWrMpyObyAlrnF?si=7358d1cf32cb45b7⁠⁠⁠⁠⁠⁠Youtube Gaming: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@RooseJp/videos⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Tiktok: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.tiktok.com/@podcastonanime⁠

As it was in the Garden of Eden, where the serpent changed the biological makeup of God's creation, so it goes again with the Fallen Ones using mad science to create an abomination on Earth. Genomic technologies are driving a vast expansion in digitalized data, from gene sequences and entire genomes that link genes to specific functions and other types of metadata for humans, other animals, plants, and microbes. A prime example includes the development of customized bioweapons. America's adversaries can direct biological attacks, specifically at US livestock and crops, to create a food security crisis. Another way is for the harvesting and pirating of DNA for racial targeting. Humanity is at a crossroads. It has to avoid both biotechnological calamity and the reign of the Antichrist. Listen to Ground Zero with Clyde Lewis M-F from 7-10 pm, pacific time on groundzeroplus.com. Call in to the LIVE show at 503-225-0860. #groundzeroplus #clydelewis #genome #DNA #biological

Support us as we expand our challenge to our broken media here: https://www.patreon.com/owenjones84 or here: https://ko-fi.com/owenjonesSupport this show http://supporter.acast.com/the-owen-jones-podcast. Hosted on Acast. See acast.com/privacy for more information.

We recorded this episode in the knowledge that Israel's planned illegal interception of the Global Sumud Flotilla was imminent. Overnight, the abduction of its passengers begun, and at time of upload, it is still ongoing. Israeli military vessels attacked the humanitarian boats with water canons, before boarding vessels and capturing passengers. Captives are expected to be taken to Ketziot prison in the Negev desert. This was a forcible prevention of the flotilla's lawful aim to carry aid to Gaza as it endures a manmade famine and genocide. Under maritime law, it was an act of piracy. It was also enabled by international news media. Here's how. The episode is hosted by Mathilda Mallinson (⁠⁠⁠⁠⁠⁠⁠⁠⁠@mathildamall⁠⁠⁠⁠⁠⁠⁠⁠⁠) and Helena Wadia (⁠⁠⁠⁠⁠⁠⁠⁠⁠@helenawadia⁠⁠⁠⁠⁠⁠⁠⁠⁠)  The music is by⁠⁠⁠⁠⁠⁠⁠⁠⁠ @soundofsamfire⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow us on⁠⁠⁠⁠⁠⁠⁠⁠⁠ Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠,⁠⁠⁠⁠⁠⁠⁠⁠⁠ Bluesky⁠⁠⁠⁠⁠⁠⁠⁠⁠, and⁠⁠⁠⁠⁠⁠⁠⁠⁠ TikTok ⁠⁠⁠ Support us on⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠! Learn more about your ad choices. Visit podcastchoices.com/adchoices

The race between pirates and rights holders has entered a new era where algorithms call the shots. Across six countries on three continents, courts are embracing AI as the referee of intellectual property rights in sports broadcasting, delivering a game-changing shift in enforcement speed and effectiveness.From hockey arenas in Toronto to cricket grounds in Mumbai, sophisticated AI systems now fingerprint legitimate broadcasts, instantly detect unauthorized streams, and trigger court-ordered blocks in real-time. The result? Millions of viewers watching pirated streams suddenly find their screens going dark mid-match as algorithms blow the whistle on infringement.This episode takes you inside landmark cases where technology and law converge. In Canada, broadcasters secured dynamic blocking orders that update during live games. Spain's La Liga won the right to target entire server infrastructures. French courts ordered VPN providers to block pirate access. Ireland extended Premier League protections through 2027. And India's cricket authorities gained "dynamic plus" injunctions to shut down rogue apps and mirror sites as they appear.What makes these cases revolutionary is how they've normalized algorithm-driven enforcement. Courts now trust AI detection as reliable evidence and trigger for immediate action. Internet service providers publish their blocking obligations as routine notices. The technology that once seemed futuristic has become the everyday referee of digital rights.For pirates who once stayed ahead of enforcement by constantly shifting domains and servers, the game has fundamentally changed. They now face an opponent that moves at machine speed, identifying and blocking new infrastructure faster than humans can respond. It's a buzzer-beater for intellectual property that's reshaping the global sports streaming landscape.Ready to understand how AI is revolutionizing IP enforcement? Subscribe now and discover why the algorithm might be the most powerful player in today's sports broadcasting game.Want to develop your own IP protection strategy? Check out "Protection for the Inventive Mind" – available now on Amazon in print and Kindle formats.Get the book!Send us a textSupport the show

In this episode of Beyond the Code, Yitzy sits down with Steve Epstein — a distinguished systems/cybersecurity & AI engineer with roots at Bell Labs (alongside Peter Shor & Lov Grover), decades at NDS/Cisco/Synamedia, and currently working at Rafael, in Israel's defense sector.Steve explains, in plain English, why quantum computing threatens today's internet (RSA, ECDH, ECDSA), what Q-Day means, and when [it might be] coming, and how post-quantum cryptography (PQC) must be rolled out across clouds, hardware, supply chains, and especially blockchains.We cover the journey from satellite-TV smart cards and anti-piracy cat-and-mouse, to Netflix's cloud migration and account-sharing detection (one of Steve's 40–50 patents), to the stark reality of “harvest-now, decrypt-later”. Bottom line: crypto agility and PQC migration have to start now if we want banking, messaging, and crypto ledgers to survive the 2029–2035 Q-Day window.Topics & Timestamps00:00 Intro — who is Steven Epstein (Bell Labs → NDS/Cisco → Rafael; 40–50 patents)07:45 Smart cards, satellite TV security, and why hardware upgradability mattered12:20 Cloud era: Netflix, AWS, microservices — and the collapse of legacy pay-TV models18:45 Piracy at scale: finding and knocking down illegal streams (and why it barely works)23:30 Quantum 101: Shor's algorithm, RSA/ECDH/ECDSA risk, Q-Day timelines31:40 PQC overview: Kyber, Dilithium, Falcon, SPHINCS+, HQC; crypto-agility in practice36:50 Harvest-now/decrypt-later and why blockchains are uniquely exposed41:50 Migration realities: cars, routers, military systems, supply chains47:30 What to do now: prioritize PQC for wallets, ledgers, key exchanges, and messaging

In this episode, Rick Sanchez, Kakuzu, Moriarty, and Hidan collide in a wildly unfiltered roundtable that explores piracy across eras from the blood-soaked seas of history to the shadowy world of digital torrents and cybercrime today. Rick delivers drunken yet brilliant takes on intergalactic piracy, Kakuzu draws on centuries of experience to break down the ruthless economics behind it, Moriarty dissects the strategic genius that fuels both old world raiders and modern hackers, while Hidan rants about rituals, blood, and chaos in a way that somehow ties it all together. Blending sharp insight with dark humor, the crew dismantles the myths of piracy and shows how its spirit never truly dies it just changes form.---------------------------------Support Us----------------------------------------Support The Modern Akatsuki if you feel like it .(Read everything below carefully before sending us your donations)

On this episode of the Self-Publishing with ALLi podcast, Dan Holloway reports on the Anthropic class action hearing, where the judge will decide if the database of pirated titles is clear enough for authors to check their inclusion. He also highlights a new “Really Sensible Licensing” system for AI use of creative works, audiobook revenues overtaking e-books in monthly reports, and Disney Plus joining with Webtoon as graphic novels gain ground both online and in bookstores. Sponsor Self-Publishing News is proudly sponsored by PublishMe—helping indie authors succeed globally with expert translation, tailored marketing, and publishing support. From first draft to international launch, PublishMe ensures your book reaches readers everywhere. Visit publishme.me. Find more author advice, tips, and tools at our Self-publishing Author Advice Center, with a huge archive of nearly 2,000 blog posts and a handy search box to find key info on the topic you need. And, if you haven't already, we invite you to join our organization and become a self-publishing ally. About the Host Dan Holloway is a novelist, poet, and spoken word artist. He is the MC of the performance arts show The New Libertines, He competed at the National Poetry Slam final at the Royal Albert Hall. His latest collection, The Transparency of Sutures, is available on Kindle.

On today's episode  I speak about making poor parental decision making, but on my part. Mostly because i am not a parent, but parents felt ok with me watching their kids. I gave a bunch of kids soda, that had never had soda before, and their parents did not approve. From their I did not receive approval from restaurants i went to last week, I am the worst patron because I just go sit town and turn on the youtube or Netflix. Apparently it is frowned upon when going to upscale restaurants, but hey i say my money is still green correct. I also got to see a funny skit that was sent to me about a new zombie concept. What if zombies still had our flaws when undead, like i imagine a zombie being a narcissist, or a gas lighter, fun times right. PUT IT ON THE LINE- LYN COLLINS50 SHOT YA - 50 CENT (00:00 - 32:24)On the movie review section we talk about film movies and other things and give the worse takes. This week i speak about  “ SAVAGES' this movie has a sleeper case, and it is definitely with the watch. This is a true Disney film without the clean cast and with s3x, money, drugs, and violence. A movie about a lovers triangle gone wrong due to work complications, and 2 men trying to rectify pass grievances to move forward in their lovers quarrel. If you have seen this movie you're probably trying to figure out if we're talking about the same movie and yes we're.    (32:25 - 01:03:09)I then jump into The Cool Report  where we discuss a business owners bright plans to get right off segregation and it backfires terribly. Someone thought if they made an all women night club, that the money would come in pouring by the dozens but didn't do their due diligence to see they were in the wrong. From there China calculated a devious tactic, watching ads to be able to access toilet paper from public bathrooms, and what point in society did we lose our morals and charge for basic decency.  We don't even know how much reward is being given for ads, is it a tile an ad. Speaking of moral decency a man files a report with the police and receives justice when he was assaulted in front of people and no one helped him out. 2 floozies assaulted  him using twerk attack and almost succeeded draining him of his life force.(01:03:10 - 01:19:44)We then step into a segment where the listeners ask me 3 questions about myself or just randomness. A character wants to know why did i skip out on the ice topic last week and i assure him on this episode the i am with the mess. Another character want to know, what is the PH outdo sound like, and i don't think anyone knows that answer, and if they do, they're some wild wild boys or ladies.My cousin Chris sent me a clip of the next wave of streaming that isn't new but making a comeback. Piracy is back and i am not here for it, only because i am now the artist on the other end. If you bootleg my show, i am going to make you eat that iPod shuffle.   (01:19:45 - 01:34:53)Then we have 2 fans ask us a questions for PTL where we get asked the tough questions where we place ourselves in their shoes. A lover wants to know when is it okay to hide money from a partner. I say when you know the feds are coming, if that's the case. But why can't someone stash a little bit on money on the side, what if they really want something. Another lover wants to know, how to smooth things out with their lady over a misunderstanding. He meant phat, she heard fat. 2 huge differences, not really its a semantics game.(01:34:54  - 01:49:45)THE FINThanks to everyone that shows us love and wish y'all the best on the journey called life.(01:49:56 - 01:52:49)please continue to like, share, comment and subscribe.PEACE OUT!!!! For questions to be answered on Part time lover please email @nospecialcharacterspod@gmail.comTIME CODEINTRO/ WHAT'S NEW - 00:00MOVIE REVIEW - 32:35THE COOL REPORT - 01:03:10ASK ME A QUESTION - 01:19:45PART TIME LOVER - 01:34:54OUTRO - 01:49:56

ORIGINAL UNBELIEVABLE.  2/4: The Pirate King: The Strange Adventures of Henry Avery and the Birth of the Golden Age of Piracy Hardcover – April 2, 2024 by  Sean Kingsley  (Author), Rex Cowan  (Author) https://www.amazon.com/Pirate-King-Strange-Adventures-Golden/dp/1639365958/ref=tmm_hrd_swatch_0?_encoding=UTF8&qid=&sr= Henry Avery of Devon pillaged a fortune from a Mughal ship off the coast of India and then vanished into thin air—and into legend. More ballads, plays, biographies and books were written about Avery's adventures than any other pirate. His contemporaries crowned him "the pirate king" for pulling off the richest heist in pirate history and escaping with his head intact (unlike Blackbeard and his infamous Flying Gang). Avery was now the most wanted criminal on earth. To the authorities, Avery was the enemy of all mankind. To the people he was a hero. Rumors swirled about his disappearance. The only certainty is that Henry Avery became a ghost. 1841

.  PREVIEW.  AUTHORS: Sean Kingsley and Rex Cowan TITLE: The Pirate King: Lost Treasure, Piracy in the Indian Ocean, Spying, Spycraft for the King, Scottish Independence SUMMARY: Henry Avery, surviving pirate and strategist, was sent as Daniel Defoe's enforcer/wingman to manipulate opinion in Scotland (1706), fighting Jacobites threatening Scottish independence. Details: Henry Avery was one of the few pirates who survived to enjoy their ill-gotten gains, unlike Blackbeard, Stede Bonnet, and Calico Jack Rackham, who were hanged or died Avery was sent with master spy Daniel Defoe to Scotland in early 18th century to undermine the Scottish independence movement They traveled to Scotland in September 1706 Edinburgh was a hotbed of Catholics, known locally as Jacobites These Jacobites threatened to break away from the English Crown Daniel Defoe was sent by London to manipulate public opinion by controlling key figures (church leaders, lawyers, merchants) and the presses They established control within two months Henry Avery served as Defoe's wingman and enforcer Avery is characterized as an incredible strategist, very smart, ex-Royal Navy salt, "the thinking man's muscle"

ORIGINAL UNBELIEVABLE  1/4: The Pirate King: The Strange Adventures of Henry Avery and the Birth of the Golden Age of Piracy Hardcover – April 2, 2024 by  Sean Kingsley  (Author), Rex Cowan  (Author) https://www.amazon.com/Pirate-King-Strange-Adventures-Golden/dp/1639365958/ref=tmm_hrd_swatch_0?_encoding=UTF8&qid=&sr= Henry Avery of Devon pillaged a fortune from a Mughal ship off the coast of India and then vanished into thin air—and into legend. More ballads, plays, biographies and books were written about Avery's adventures than any other pirate. His contemporaries crowned him "the pirate king" for pulling off the richest heist in pirate history and escaping with his head intact (unlike Blackbeard and his infamous Flying Gang). Avery was now the most wanted criminal on earth. To the authorities, Avery was the enemy of all mankind. To the people he was a hero. Rumors swirled about his disappearance. The only certainty is that Henry Avery became a ghost.

ORIGINAL UNBELIEVABLE.  4/4: The Pirate King: The Strange Adventures of Henry Avery and the Birth of the Golden Age of Piracy Hardcover – April 2, 2024 by  Sean Kingsley  (Author), Rex Cowan  (Author) https://www.amazon.com/Pirate-King-Strange-Adventures-Golden/dp/1639365958/ref=tmm_hrd_swatch_0?_encoding=UTF8&qid=&sr= Henry Avery of Devon pillaged a fortune from a Mughal ship off the coast of India and then vanished into thin air—and into legend. More ballads, plays, biographies and books were written about Avery's adventures than any other pirate. His contemporaries crowned him "the pirate king" for pulling off the richest heist in pirate history and escaping with his head intact (unlike Blackbeard and his infamous Flying Gang). Avery was now the most wanted criminal on earth. To the authorities, Avery was the enemy of all mankind. To the people he was a hero. Rumors swirled about his disappearance. The only certainty is that Henry Avery became a ghost.

ORIGINAL UNBELIEVABLE.  3/4: The Pirate King: The Strange Adventures of Henry Avery and the Birth of the Golden Age of Piracy Hardcover – April 2, 2024 by  Sean Kingsley  (Author), Rex Cowan  (Author) https://www.amazon.com/Pirate-King-Strange-Adventures-Golden/dp/1639365958/ref=tmm_hrd_swatch_0?_encoding=UTF8&qid=&sr= Henry Avery of Devon pillaged a fortune from a Mughal ship off the coast of India and then vanished into thin air—and into legend. More ballads, plays, biographies and books were written about Avery's adventures than any other pirate. His contemporaries crowned him "the pirate king" for pulling off the richest heist in pirate history and escaping with his head intact (unlike Blackbeard and his infamous Flying Gang). Avery was now the most wanted criminal on earth. To the authorities, Avery was the enemy of all mankind. To the people he was a hero. Rumors swirled about his disappearance. The only certainty is that Henry Avery became a ghost. 1850

Send us a message!Charleston's pirate legacy is more than legend—it's a story of fear, spectacle, and transformation. In this episode of Shadowed Pasts, we uncover the darker truths behind Blackbeard's blockade, Bonnet's execution, and the myths that shaped a city built on shadow. Music is by Alexander Nakarada.Support the show

A short episode with just a dash of legalese about  trouble for an ISP not squashing piracy enough, and one last chance to guess the Mystery Sound from episode 315 before we reveal it next episode!  Keep it nerdy and we will see you next week Join the conversation with us LIVE every Monday on […]

The Blerds are back bringing you all of their thoughts on everything happening in nerd culture. This week, Shannon and Jaja talk about exciting announcements from the latest Nintendo Direct. We're also giving our thoughts on the highly anticipated Demon Slayer: Infinity Castle movie. Plus more nerd news! Make sure to subscribe to us on Youtube, Apple Podcasts, Spotify or your Podcast app of choice! 00:00-Introduction to Nerd Culture 02:47-Diving into Current Nerdy Activities 05:15-Nintendo Direct Highlights 08:21-Controversial Nintendo News 12:09-Legal Troubles in Gaming 16:08-The Consequences of Piracy 18:18-Upcoming Xbox Announcements 20:42-Sony's Anticipated Releases 22:35-James Gunn's Man of Tomorrow 30:50-HBO Max's Pricing Dilemma 35:08-Rising Costs of Streaming Services 38:02-Excitement for Upcoming Movies 40:59-Demon Slayer: Infinity Castle Review 48:59-Live Action Adaptations: A Mixed Bag   Follow Us!  https://linktr.ee/blerdsnerds National Resources List https://linktr.ee/NationalResourcesList Youtube  https://www.youtube.com/channel/UCK56I-TNUnhKhcWLZxoUTaw Email us: Blerdsnerds@gmail.com Follow Our Social: https://www.instagram.com/blerdsnerds/ https://twitter.com/BlerdsNerds https://www.facebook.com/blerdsnerds https://tiktok.com/blerdsnerds_pod Shannon: https://www.instagram.com/luv_shenanigans James: https://www.instagram.com/llsuavej  Jaja: https://www.instagram.com/jajasmith3 

Francois Daost is a W3C staff member and co-chair of the Web Developer Experience Community Group. We discuss the W3C's role and what it's like to go through the browser standardization process. Related links W3C TC39 Internet Engineering Task Force Web Hypertext Application Technology Working Group (WHATWG) Horizontal Groups Alliance for Open Media What is MPEG-DASH? | HLS vs. DASH Information about W3C and Encrypted Media Extensions (EME) Widevine PlayReady Media Source API Encrypted Media Extensions API requestVideoFrameCallback() Business Benefits of the W3C Patent Policy web.dev Baseline Portable Network Graphics Specification Internet Explorer 6 CSS Vendor Prefix WebRTC Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: today I'm talking to Francois Daoust. He's a staff member at the W3C. And we're gonna talk about the W3C and the recommendation process and discuss, Francois's experience with, with how these features end up in our browsers. [00:00:16] Jeremy: So, Francois, welcome [00:00:18] Francois: Thank you Jeremy and uh, many thanks for the invitation. I'm really thrilled to be part of this podcast. What's the W3C? [00:00:26] Jeremy: I think many of our listeners will have heard about the W3C, but they may not actually know what it is. So could you start by explaining what it is? [00:00:37] Francois: Sure. So W3C stands for the Worldwide Web Consortium. It's a standardization organization. I guess that's how people should think about W3C. it was created in 1994. I, by, uh, Tim Berners Lee, who was the inventor of the web. Tim Berners Lee was the, director of W3C for a long, long time. [00:01:00] Francois: He retired not long ago, a few years back. and W3C is, has, uh, a number of, uh. Properties, let's say first the goal is to produce royalty free standards, and that's very important. Uh, we want to make sure that, uh, the standard that get produced can be used and implemented without having to pay, fees to anyone. [00:01:23] Francois: We do web standards. I didn't mention it, but it's from the name. Standards that you find in your web browsers. But not only that, there are a number of other, uh, standards that got developed at W3C including, for example, XML. Data related standards. W3C as an organization is a consortium. [00:01:43] Francois: The, the C stands for consortium. Legally speaking, it's a, it's a 501c3 meaning in, so it's a US based, uh, legal entity not for profit. And the, the little three is important because it means it's public interest. That means we are a consortium, that means we have members, but at the same time, the goal, the mission is to the public. [00:02:05] Francois: So we're not only just, you know, doing what our members want. We are also making sure that what our members want is aligned with what end users in the end, need. and the W3C has a small team. And so I'm part of this, uh, of this team worldwide. Uh, 45 to 55 people, depending on how you count, mostly technical people and some, uh, admin, uh, as well, overseeing the, uh, the work, that we do, uh, at the W3C. Funding through membership fees [00:02:39] Jeremy: So you mentioned there's 45 to 55 people. How is this funded? Is this from governments or commercial companies? [00:02:47] Francois: The main source comes from membership fees. So the W3C has a, so members, uh, roughly 350 members, uh, at the W3C. And, in order to become a member, an organization needs to pay, uh, an annual membership fee. That's pretty common among, uh, standardization, uh, organizations. [00:03:07] Francois: And, we only have, uh, I guess three levels of membership, fees. Uh, well, you may find, uh, additional small levels, but three main ones. the goal is to make sure that, A big player will, not a big player or large company, will not have more rights than, uh, anything, anyone else. So we try to make sure that a member has the, you know, all members have equal, right? [00:03:30] Francois: if it's not perfect, but, uh, uh, that's how things are, are are set. So that's the main source of income for the W3C. And then we try to diversify just a little bit to get, uh, for example, we go to governments. We may go to governments in the u EU. We may, uh, take some, uh, grant for EU research projects that allow us, you know, to, study, explore topics. [00:03:54] Francois: Uh, in the US there, there used to be some, uh, some funding from coming from the government as well. So that, that's, uh, also, uh, a source. But the main one is, uh, membership fees. Relations to TC39, IETF, and WHATWG [00:04:04] Jeremy: And you mentioned that a lot of the W3C'S work is related to web standards. There's other groups like TC 39, which works on the JavaScript spec and the IETF, which I believe worked, with your group on WebRTC, I wonder if you could explain W3C'S connection to other groups like that. [00:04:28] Francois: sure. we try to collaborate with a, a number of, uh, standard other standardization organizations. So in general, everything goes well because you, you have, a clear separation of concerns. So you mentioned TC 39. Indeed. they are the ones who standardize, JavaScript. Proper name of JavaScript is the EcmaScript. [00:04:47] Francois: So that's tc. TC 39 is the technical committee at ecma. and so we have indeed interactions with them because their work directly impact the JavaScript that you're going to find in your, uh, run in your, in your web browser. And we develop a number of JavaScript APIs, uh, actually in W3C. [00:05:05] Francois: So we need to make sure that, the way we develop, uh, you know, these APIs align with the, the language itself. with IETF, the, the, the boundary is, uh, uh, is clear as well. It's a protocol and protocol for our network protocols for our, the IETF and application level. For W3C, that's usually how the distinction is made. [00:05:28] Francois: The boundaries are always a bit fuzzy, but that's how things work. And usually, uh, things work pretty well. Uh, there's also the WHATWG, uh, and the WHATWG is more the, the, the history was more complicated because, uh, t of a fork of the, uh, HTML specification, uh, at the time when it was developed by W3C, a long time ago. [00:05:49] Francois: And there was been some, uh, Well disagreement on the way things should have been done, and the WHATWG took over got created, took, took this the HTML spec and did it a different way. Went in another, another direction, and that other, other direction actually ended up being the direction. [00:06:06] Francois: So, that's a success, uh, from there. And so, W3C no longer works, no longer owns the, uh, HTML spec and the WHATWG has, uh, taken, uh, taken up a number of, uh, of different, core specifications for the web. Uh, doing a lot of work on the, uh, on interopoerability and making sure that, uh, the algorithm specified by the spec, were correct, which, which was something that historically we haven't been very good at at W3C. [00:06:35] Francois: And the way they've been working as a, has a lot of influence on the way we develop now, uh, the APIs, uh, from a W3C perspective. [00:06:44] Jeremy: So, just to make sure I understand correctly, you have TC 39, which is focused on the JavaScript or ECMAScript language itself, and you have APIs that are going to use JavaScript and interact with JavaScript. So you need to coordinate there. The, the have the specification for HTML. then the IATF, they are, I'm not sure if the right term would be, they, they would be one level lower perhaps, than the W3C. [00:07:17] Francois: That's how you, you can formulate it. Yes. The, the one layer, one layer layer in the ISO network in the ISO stack at the network level. How WebRTC spans the IETF and W3C [00:07:30] Jeremy: And so in that case, one place I've heard it mentioned is that webRTC, to, to use it, there is an IETF specification, and then perhaps there's a W3C recommendation and [00:07:43] Francois: Yes. so when we created the webRTC working group, that was in 2011, I think, it was created with a dual head. There was one RTC web, group that got created at IETF and a webRTC group that got created at W3C. And that was done on purpose. Of course, the goal was not to compete on the, on the solution, but actually to, have the two sides of the, uh, solution, be developed in parallel, the API, uh, the application front and the network front. [00:08:15] Francois: And there was a, and there's still a lot of overlap in, uh, participation between both groups, and that's what keep things successful. In the end. It's not, uh, you know, process or organization to organization, uh, relationships, coordination at the organization level. It's really the fact that you have participants that are essentially the same, on both sides of the equation. [00:08:36] Francois: That helps, uh, move things forward. Now, webRTC is, uh, is more complex than just one group at IETF. I mean, web, webRTC is a very complex set of, uh, of technologies, stack of technologies. So when you, when you. Pull a little, uh, protocol from IETFs. Suddenly you have the whole IETF that comes with you with it. [00:08:56] Francois: So you, it's the, you have the feeling that webRTC needs all of the, uh, internet protocols that got, uh, created to work Recommendations [00:09:04] Jeremy: And I think probably a lot of web developers, they may hear words like specification or standard, but I believe the, the official term, at least at the W3C, is this recommendation. And so I wonder if you can explain what that means. [00:09:24] Francois: Well. It means it means standard in the end. and that came from industry. That comes from a time where. As many standardization organizations. W3C was created not to be a standardization organization. It was felt that standard was not the right term because we were not a standardization organization. [00:09:45] Francois: So recommend IETF has the same thing. They call it RFC, request for comment, which, you know, stands for nothing in, and yet it's a standard. So W3C was created with the same kind of, uh thing. We needed some other terminology and we call that recommendation. But in the end, that's standard. It's really, uh, how you should see it. [00:10:08] Francois: And one thing I didn't mention when I, uh, introduced the W3C is there are two types of standards in the end, two main categories. There are, the de jure standards and defacto standards, two families. The de jure standards are the ones that are imposed by some kind of regulation. so it's really usually a standard you see imposed by governments, for example. [00:10:29] Francois: So when you look at your electric plug at home, there's some regulation there that says, this plug needs to have these properties. And that's a standard that gets imposed. It's a de jure standard. and then there are defacto standards which are really, uh, specifications that are out there and people agree to use it to implement it. [00:10:49] Francois: And by virtue of being used and implemented and used by everyone, they become standards. the, W3C really is in the, uh, second part. It's a defacto standard. IETF is the same thing. some of our standards are used in, uh, are referenced in regulations now, but, just a, a minority of them, most of them are defacto standards. [00:11:10] Francois: and that's important because that's in the end, it doesn't matter what the specific specification says, even though it's a bit confusing. What matters is that the, what the specifications says matches what implementations actually implement, and that these implementations are used, and are used interoperably across, you know, across browsers, for example, or across, uh, implementations, across users, across usages. [00:11:36] Francois: So, uh, standardization is a, is a lengthy process. The recommendation is the final stage in that, lengthy process. More and more we don't really reach recommendation anymore. If you look at, uh, at groups, uh, because we have another path, let's say we kind of, uh, we can stop at candidate recommendation, which is in theoretically a step before that. [00:12:02] Francois: But then you, you can stay there and, uh, stay there forever and publish new candidate recommendations. Um, uh, later on. What matters again is that, you know, you get this, virtuous feedback loop, uh, with implementers, and usage. [00:12:18] Jeremy: So if the candidate recommendation ends up being implemented by all the browsers, what's ends up being the distinction between a candidate and one that's a normal recommendation. [00:12:31] Francois: So, today it's mostly a process thing. Some groups actually decide to go to rec Some groups decide to stay at candidate rec and there's no formal difference between the, the two. we've made sure we've adopted, adjusted the process so that the important bits that, applied at the recommendation level now apply at the candidate rec level. Royalty free patent access [00:13:00] Francois: And by important things, I mean the patent commitments typically, uh, the patent policy fully applies at the candidate recommendation level so that you get your, protection, the royalty free patent protection that we, we were aiming at. [00:13:14] Francois: Some people do not care, you know, but most of the world still works with, uh, with patents, uh, for good, uh, or bad reasons. But, uh, uh, that's how things work. So we need to make, we're trying to make sure that we, we secure the right set of, um, of patent commitments from the right set of stakeholders. [00:13:35] Jeremy: Oh, so when someone implements a W3C recommendation or a candidate recommendation, the patent holders related to that recommendation, they basically agree to allow royalty-free use of that patent. [00:13:54] Francois: They do the one that were involved in the working group, of course, I mean, we can't say anything about the companies out there that may have patents and uh, are not part of this standardization process. So there's always, It's a remaining risk. but part of the goal when we create a working group is to make sure that, people understand the scope. [00:14:17] Francois: Lawyers look into it, and the, the legal teams that exist at the all the large companies, basically gave a green light saying, yeah, we, we we're pretty confident that we, we know where the patterns are on this particular, this particular area. And we are fine also, uh, letting go of the, the patterns we own ourselves. Implementations are built in parallel with standardization [00:14:39] Jeremy: And I think you had mentioned. What ends up being the most important is that the browser creators implement these recommendations. So it sounds like maybe the distinction between candidate recommendation and recommendation almost doesn't matter as long as you get the end result you want. [00:15:03] Francois: So, I mean, people will have different opinions, uh, in the, in standardization circles. And I mentioned also W3C is working on other kind of, uh, standards. So, uh, in some other areas, the nuance may be more important when we, but when, when you look at specification, that's target, web browsers. we've switched from a model where, specs were developed first and then implemented to a model where specs and implementing implementations are being, worked in parallel. [00:15:35] Francois: This actually relates to the evolution I was mentioning with the WHATWG taking over the HTML and, uh, focusing on the interoperability issues because the starting point was, yeah, we have an HTML 4.01 spec, uh, but it's not interoperable because it, it's not specified, are number of areas that are gray areas, you can implement them differently. [00:15:59] Francois: And so there are interoperable issues. Back to candidate rec actually, the, the, the, the stage was created, if I remember correctly. uh, if I'm, if I'm not wrong, the stage was created following the, uh, IE problem. In the CSS working group, IE6, uh, shipped with some, version of a CSS that was in the, as specified, you know, the spec was saying, you know, do that for the CSS box model. [00:16:27] Francois: And the IE6 was following that. And then the group decided to change, the box model and suddenly IE6 was no longer compliant. And that created a, a huge mess on the, in the history of, uh, of the web in a way. And so the, we, the, the, the, the candidate recommendation sta uh, stage was introduced following that to try to catch this kind of problems. [00:16:52] Francois: But nowadays, again, we, we switch to another model where it's more live. and so we, you, you'll find a number of specs that are not even at candidate rec level. They are at the, what we call a working draft, and they, they are being implemented, and if all goes well, the standardization process follows the implementation, and then you end up in a situation where you have your candidate rec when the, uh, spec ships. [00:17:18] Francois: a recent example would be a web GPU, for example. It, uh, it has shipped in, uh, in, in Chrome shortly before it transition to a candidate rec. But the, the, the spec was already stable. and now it's shipping uh, in, uh, in different browsers, uh, uh, safari, uh, and uh, and uh, and uh, Firefox. And so that's, uh, and that's a good example of something that follows, uh, things, uh, along pretty well. But then you have other specs such as, uh, in the media space, uh, request video frame back, uh, frame, call back, uh, requestVideoFrameCallback() is a short API that allows you to get, you know, a call back whenever the, the browser renders a video frame, essentially. [00:18:01] Francois: And that spec is implemented across browsers. But from a W3C specific, perspective, it does not even exist. It's not on the standardization track. It's still being incubated in what we call a community group, which is, you know, some something that, uh, usually exists before. we move to the, the standardization process. [00:18:21] Francois: So there, there are examples of things where some things fell through the cracks. All the standardization process, uh, is either too early or too late and things that are in spec are not exactly what what got implemented or implementations are too early in the process. We we're doing a better job, at, Not falling into a trap where someone ships, uh, you know, an implementation and then suddenly everything is frozen. You can no longer, change it because it's too late, it shipped. we've tried, different, path there. Um, mentioned CSS, the, there was this kind of vendor prefixed, uh, properties that used to be, uh, the way, uh, browsers were deploying new features without, you know, taking the final name. [00:19:06] Francois: We are trying also to move away from it because same thing. Then in the end, you end up with, uh, applications that have, uh, to duplicate all the properties, the CSS properties in the style sheets with, uh, the vendor prefixes and nuances in the, in what it does in, in the end. [00:19:23] Jeremy: Yeah, I, I think, is that in CSS where you'll see --mozilla or things like that? Why requestVideoFrameCallback doesn't have a formal specification [00:19:30] Jeremy: The example of the request video frame callback. I, I wonder if you have an opinion or, or, or know why that ended up the way it did, where the browsers all implemented it, even though it was still in the incubation stage. [00:19:49] Francois: On this one, I don't have a particular, uh, insights on whether there was a, you know, a strong reason to implement it,without doing the standardization work. [00:19:58] Francois: I mean, there are, it's not, uh, an IPR (Intellectual Property Rights) issue. It's not, uh, something that, uh, I don't think the, the, the spec triggers, uh, you know, problems that, uh, would be controversial or whatever. [00:20:10] Francois: Uh, so it's just a matter of, uh, there was no one's priority, and in the end, you end up with a, everyone's happy. it's, it has shipped. And so now doing the spec work is a bit,why spend time on something that's already shipped and so on, but the, it may still come back at some point with try to, you know, improve the situation. [00:20:26] Jeremy: Yeah, that's, that's interesting. It's a little counterintuitive because it sounds like you have the, the working group and it, it sounds like perhaps the companies or organizations involved, they maybe agreed on how it should work, and maybe that agreement almost made it so that they felt like they didn't need to move forward with the specification because they came to consensus even before going through that. [00:20:53] Francois: In this particular case, it's probably because it's really, again, it's a small, spec. It's just one function call, you know? I mean, they will definitely want a working group, uh, for larger specifications. by the way, actually now I know re request video frame call back. It's because the, the, the final goal now that it's, uh, shipped, is to merge it into, uh, HTML, uh, the HTML spec. [00:21:17] Francois: So there's a, there's an ongoing issue on the, the WHATWG side to integrate request video frame callback. And it's taking some time but see, it's, it's being, it, it caught up and, uh, someone is doing the, the work to, to do it. I had forgotten about this one. Um, [00:21:33] Jeremy: Tension from specification review (horizontal review) [00:21:33] Francois: so with larger specifications, organizations will want this kind of IPR regime they will want commit commitments from, uh, others, on the scope, on the process, on everything. So they will want, uh, a larger, a, a more formal setting, because that's part of how you ensure that things, uh, will get done properly. [00:21:53] Francois: I didn't mention it, but, uh, something we're really, uh, Pushy on, uh, W3C I mentioned we have principles, we have priorities, and we have, uh, specific several, uh, properties at W3C. And one of them is that we we're very strong on horizontal reviews of our specs. We really want them to be reviewed from an accessibility perspective, from an internationalization perspective, from a privacy and security, uh, perspective, and, and, and a technical architecture perspective as well. [00:22:23] Francois: And that's, these reviews are part of the formal process. So you, all specs need to undergo these reviews. And from time to time, that creates tension. Uh, from time to time. It just works, you know. Goes without problem. a recurring issue is that, privacy and security are hard. I mean, it's not an easy problem, something that can be, uh, solved, uh, easily. [00:22:48] Francois: Uh, so there's a, an ongoing tension and no easy way to resolve it, but there's an ongoing tension between, specifying powerful APIs and preserving privacy without meaning, not exposing too much information to applications in the media space. You can think of the media capabilities, API. So the media space is a complicated space. [00:23:13] Francois: Space because of codecs. codecs are typically not relative free. and so browsers decide which codecs they're going to support, which audio and video codecs they, they're going to support and doing that, that creates additional fragmentation, not in the sense that they're not interoperable, but in the sense that applications need to choose which connect they're going to ship to stream to the end user. [00:23:39] Francois: And, uh, it's all the more complicated that some codecs are going to be hardware supported. So you will have a hardware decoder in your, in your, in your laptop or smartphone. And so that's going to be efficient to decode some, uh, some stream, whereas some code are not, are going to be software, based, supported. [00:23:56] Francois: Uh, and that may consume a lot of CPU and a lot of power and a lot of energy in the end. So you, you want to avoid that if you can, uh, select another thing. Even more complex than, codecs have different profiles, uh, lower end profiles higher end profiles with different capabilities, different features, uh, depending on whether you're going to use this or that color space, for example, this or that resolution, whatever. [00:24:22] Francois: And so you want to surface that to web applications because otherwise, they can't. Select, they can't choose, the right codec and the right, stream that they're going to send to the, uh, client devices. And so they're not going to provide an efficient user experience first, and even a sustainable one in terms of energy because they, they're going to waste energy if they don't send the right stream. [00:24:45] Francois: So you want to surface that to application. That's what the media, media capabilities, APIs, provides. Privacy concerns [00:24:51] Francois: Uh, but at the same time, if you expose that information, you end up with ways to fingerprint the end user's device. And that in turn is often used to track users across, across sites, which is exactly what we don't want to have, uh, for privacy reasons, for obvious privacy reasons. [00:25:09] Francois: So you have to balance that and find ways to, uh, you know, to expose. Capabilities without, without necessarily exposing them too much. Uh, [00:25:21] Jeremy: Can you give an example of how some of those discussions went? Like within the working group? Who are the companies or who are the organizations that are arguing for We shouldn't have this capability because of the privacy concerns, or [00:25:40] Francois: In a way all of the companies, have a vision of, uh, of privacy. I mean, the, you will have a hard time finding, you know, members saying, I don't care about privacy. I just want the feature. Uh, they all have privacy in mind, but they may have a different approach to privacy. [00:25:57] Francois: so if you take, uh, let's say, uh, apple and Google would be the, the, I guess the perfect examples in that, uh, in that space, uh, Google will have a, an approach that is more open-ended thing. The, the user agents has this, uh, should check what the, the, uh, given site is doing. And then if it goes beyond, you know, some kind of threshold, they're going to say, well, okay, well, we'll stop exposing data to that, to that, uh, to that site. [00:26:25] Francois: So that application. So monitor and react in a way. apple has a more, uh, you know, has a stricter view on, uh, on privacy, let's say. And they will say, no, we, the, the, the feature must not exist in the first place. Or, but that's, I mean, I guess, um, it's not always that extreme. And, uh, from time to time it's the opposite. [00:26:45] Francois: You will have, uh, you know, apple arguing in one way, uh, which is more open-ended than the, uh, than, uh, than Google, for example. And they are not the only ones. So in working groups, uh, you will find the, usually the implementers. Uh, so when we talk about APIs that get implemented in browsers, you want the core browsers to be involved. [00:27:04] Francois: Uh, otherwise it's usually not a good sign for, uh, the success of the, uh, of the technology. So in practice, that means Apple, uh, Microsoft, Mozilla which one did I forget? [00:27:15] Jeremy: Google. [00:27:16] Francois: I forgot Google. Of course. Thank you. that's, uh, that the, the core, uh, list of participants you want to have in any, uh, group that develops web standards targeted at web browsers. Who participates in working groups and how much power do they have? [00:27:28] Francois: And then on top of that, you want, organizations and people who are directly going to use it, either because they, well the content providers. So in media, for example, if you look at the media working group, you'll see, uh, so browser vendors, the ones I mentioned, uh, content providers such as the BBC or Netflix. [00:27:46] Francois: Chip set vendors would, uh, would be there as well. Intel, uh, Nvidia again, because you know, there's a hardware decoding in there and encoding. So media is, touches on, on, uh, on hardware, uh, device manufacturer in general. You may, uh, I think, uh, I think Sony is involved in the, in the media working group, for example. [00:28:04] Francois: and these companies are usually less active in the spec development. It depends on the groups, but they're usually less active because the ones developing the specs are usually the browser again, because as I mentioned, we develop the specs in parallel to browsers implementing it. So they have the. [00:28:21] Francois: The feedback on how to formulate the, the algorithms. and so that's this collection of people who are going to discuss first within themselves. W3C pushes for consensual dis decisions. So we hardly take any votes in the working groups, but from time to time, that's not enough. [00:28:41] Francois: And there may be disagreements, but let's say there's agreement in the group, uh, when the spec matches. horizontal review groups will look at the specs. So these are groups I mentioned, accessibility one, uh, privacy, internationalization. And these groups, usually the participants are, it depends. [00:29:00] Francois: It can be anything. It can be, uh, the same companies. It can be, but usually different people from the same companies. But it the, maybe organizations with a that come from very, a very different angle. And that's a good thing because that means the, you know, you enlarge the, the perspectives on your, uh, on the, on the technology. [00:29:19] Francois: and you, that's when you have a discussion between groups, that takes place. And from time to time it goes well from time to time. Again, it can trigger issues that are hard to solve. and the W3C has a, an escalation process in case, uh, you know, in case things degenerate. Uh, starting with, uh, the notion of formal objection. [00:29:42] Jeremy: It makes sense that you would have the, the browser. Vendors and you have all the different companies that would use that browser. All the different horizontal groups like you mentioned, the internationalization, accessibility. I would imagine that you were talking about consensus and there are certain groups or certain companies that maybe have more say or more sway. [00:30:09] Jeremy: For example, if you're a browser, manufacturer, your Google. I'm kind of curious how that works out within the working group. [00:30:15] Francois: Yes, it's, I guess I would be lying if I were saying that, uh, you know, all companies are strictly equal in a, in a, in a group. they are from a process perspective, I mentioned, you know, different membership fees with were design, special specific ethos so that no one could say, I'm, I'm putting in a lot of money, so you, you need to re you need to respect me, uh, and you need to follow what I, what I want to, what I want to do. [00:30:41] Francois: at the same time, if you take a company like, uh, like Google for example, they send, hundreds of engineers to do standardization work. That's absolutely fantastic because that means work progresses and it's, uh, extremely smart people. So that's, uh, that's really a pleasure to work with, uh, with these, uh, people. [00:30:58] Francois: But you need to take a step back and say, well, the problem is. Defacto that gives them more power just by virtue of, uh, injecting more resources into it. So having always someone who can respond to an issue, having always someone, uh, editing a spec defacto that give them more, uh, um, more say on the, on the directions that, get forward. [00:31:22] Francois: And on top of that, of course, they have the, uh, I guess not surprisingly, the, the browser that is, uh, used the most, currently, on the market so there's a little bit of a, the, the, we, we, we, we try very hard to make sure that, uh, things are balanced. it's not a perfect world. [00:31:38] Francois: the the role of the team. I mean, I didn't talk about the role of the team, but part of it is to make sure that. Again, all perspectives are represented and that there's not, such a, such big imbalance that, uh, that something is wrong and that we really need to look into it. so making sure that anyone, if they have something to say, make making sure that they are heard by the rest of the group and not dismissed. [00:32:05] Francois: That usually goes well. There's no problem with that. And again, the escalation process I mentioned here doesn't make any, uh, it doesn't make any difference between, uh, a small player, a large player, a big player, and we have small companies raising formal objections against some of our aspects that happens, uh, all large ones. [00:32:24] Francois: But, uh, that happens too. There's no magical solution, I guess you can tell it by the way. I, uh, I don't know how to formulate the, the process more. It's a human process, and that's very important that it remains a human process as well. [00:32:41] Jeremy: I suppose the role of, of staff and someone in your position, for example, is to try and ensure that these different groups are, are heard and it isn't just one group taking control of it. [00:32:55] Francois: That's part of the role, again, is to make sure that, uh, the, the process is followed. So the, I, I mean, I don't want to give the impression that the process controls everything in the groups. I mean, the, the, the groups are bound by the process, but the process is there to catch problems when they arise. [00:33:14] Francois: most of the time there are no problems. It's just, you know, again, participants talking to each other, talking with the rest of the community. Most of the work happens in public nowadays, in any case. So the groups work in public essentially through asynchronous, uh, discussions on GitHub repositories. [00:33:32] Francois: There are contributions from, you know, non group participants and everything goes well. And so the process doesn't kick in. You just never say, eh, no, you didn't respect the process there. You, you closed the issue. You shouldn't have a, it's pretty rare that you have to do that. Uh, things just proceed naturally because they all, everyone understands where they are, why, what they're doing, and why they're doing it. [00:33:55] Francois: we still have a role, I guess in the, in the sense that from time to time that doesn't work and you have to intervene and you have to make sure that,the, uh, exception is caught and, uh, and processed, uh, in the right way. Discussions are public on github [00:34:10] Jeremy: And you said this process is asynchronous in public, so it sounds like someone, I, I mean, is this in GitHub issues or how, how would somebody go and, and see what the results of [00:34:22] Francois: Yes, there, there are basically a gazillion of, uh, GitHub repositories under the, uh, W3C, uh, organization on GitHub. Most groups are using GitHub. I mean, there's no, it's not mandatory. We don't manage any, uh, any tooling. But the factors that most, we, we've been transitioning to GitHub, uh, for a number of years already. [00:34:45] Francois: Uh, so that's where the work most of the work happens, through issues, through pool requests. Uh, that's where. people can go and raise issues against specifications. Uh, we usually, uh, also some from time to time get feedback from developers and countering, uh, a bug in a particular implementations, which we try to gently redirect to, uh, the actual bug trackers because we're not responsible for the respons implementations of the specs unless the spec is not clear. [00:35:14] Francois: We are responsible for the spec itself, making sure that the spec is clear and that implementers well, understand how they should implement something. Why the W3C doesn't specify a video or audio codec [00:35:25] Jeremy: I can see how people would make that mistake because they, they see it's the feature, but that's not the responsibility of the, the W3C to implement any of the specifications. Something you had mentioned there's the issue of intellectual property rights and how when you have a recommendation, you require the different organizations involved to make their patents available to use freely. [00:35:54] Jeremy: I wonder why there was never any kind of, recommendation for audio or video codecs in browsers since you have certain ones that are considered royalty free. But, I believe that's never been specified. [00:36:11] Francois: At W3C you mean? Yes. we, we've tried, I mean, it's not for lack of trying. Um, uh, we've had a number of discussions with, uh, various stakeholders saying, Hey, we, we really need, an audio or video code for our, for the web. the, uh, png PNG is an example of a, um, an image format which got standardized at W3C and it got standardized at W3C similar reasons. There had to be a royalty free image format for the web, and there was none at the time. of course, nowadays, uh, jpeg, uh, and gif or gif, whatever you call it, are well, you know, no problem with them. But, uh, um, that at the time P PNG was really, uh, meant to address this issue and it worked for PNG for audio and video. [00:37:01] Francois: We haven't managed to secure, commitments by stakeholders. So willingness to do it, so it's not, it's not lack of willingness. We would've loved to, uh, get, uh, a royalty free, uh, audio codec, a royalty free video codec again, audio and video code are extremely complicated because of this. [00:37:20] Francois: not only because of patterns, but also because of the entire business ecosystem that exists around them for good reasons. You, in order for a, a codec to be supported, deployed, effective, it really needs, uh, it needs to mature a lot. It needs to, be, uh, added to at a hardware level, to a number of devices, capturing devices, but also, um, uh, uh, of course players. [00:37:46] Francois: And that takes a hell of a lot of time and that's why you also enter a number of business considerations with business contracts between entities. so I'm personally, on a personal level, I'm, I'm pleased to see, for example, the Alliance for Open Media working on, uh, uh, AV1, uh, which is. At least they, uh, they wanted to be royalty free and they've been adopting actually the W3C patent policy to do this work. [00:38:11] Francois: So, uh, we're pleased to see that, you know, they've been adopting the same process and same thing. AV1 is not yet at the same, support stage, as other, codecs, in the world Yeah, I mean in devices. There's an open question as what, what are we going to do, uh, in the future uh, with that, it's, it's, it's doubtful that, uh, the W3C will be able to work on a, on a royalty free audio, codec or royalty free video codec itself because, uh, probably it's too late now in any case. [00:38:43] Francois: but It's one of these angles in the, in the web platform where we wish we had the, uh, the technology available for, for free. And, uh, it's not exactly, uh, how things work in practice.I mean, the way codecs are developed remains really patent oriented. [00:38:57] Francois: and you will find more codecs being developed. and that's where geopolitics can even enter the, the, uh, the play. Because, uh, if you go to China, you will find new codecs emerging, uh, that get developed within China also, because, the other codecs come mostly from the US so it's a bit of a problem and so on. [00:39:17] Francois: I'm not going to enter details and uh, I would probably say stupid things in any case. Uh, but that, uh, so we continue to see, uh, emerging codecs that are not royalty free, and it's probably going to remain the case for a number of years. unfortunately, unfortunately, from a W3C perspective and my perspective of course. [00:39:38] Jeremy: There's always these new, formats coming out and the, rate at which they get supported in the browser, even on a per browser basis is, is very, there can be a long time between, for example, WebP being released and a browser supporting it. So, seems like maybe we're gonna be in that situation for a while where the codecs will come out and maybe the browsers will support them. Maybe they won't, but the, the timeline is very uncertain. Digital Rights Management (DRM) and Media Source Extensions [00:40:08] Jeremy: Something you had, mentioned, maybe this was in your, email to me earlier, but you had mentioned that some of these specifications, there's, there's business considerations like with, digital rights management and, media source extensions. I wonder if you could talk a little bit about maybe what media source extensions is and encrypted media extensions and, and what the, the considerations or challenges are there. [00:40:33] Francois: I'm going to go very, very quickly over the history of a, video and audio support on the web. Initially it was supported through plugins. you are maybe too young to, remember that. But, uh, we had extensions, added to, uh, a realplayer. [00:40:46] Francois: This kind of things flash as well, uh, supporting, uh, uh, videos, in web pages, but it was not provided by the web browsers themselves. Uh, then HTML5 changed the, the situation. Adding these new tags, audio and video, but that these tags on this, by default, support, uh, you give them a resources, a resource, like an image as it's an audio or a video file. [00:41:10] Francois: They're going to download this, uh, uh, video file or audio file, and they're going to play it. That works well. But as soon as you want to do any kind of real streaming, files are too large and to stream, to, to get, you know, to get just a single fetch on, uh, on them. So you really want to stream them chunk by chunk, and you want to adapt the resolution at which you send the stream based on real time conditions of the user's network. [00:41:37] Francois: If there's plenty of bandwidth you want to send the user, the highest possible resolution. If there's a, some kind of hiccup temporary in the, in the network, you really want to lower the resolution, and that's called adaptive streaming. And to get adaptive streaming on the web, well, there are a number of protocols that exist. [00:41:54] Francois: Same thing. Some many of them are proprietary and actually they remain proprietary, uh, to some extent. and, uh, some of them are over http and they are the ones that are primarily used in, uh, in web contexts. So DASH comes to mind, DASH for Dynamic Adaptive streaming over http. HLS is another one. Uh, initially developed by Apple, I believe, and it's, uh, HTTP live streaming probably. Exactly. And, so there are different protocols that you can, uh, you can use. Uh, so the goal was not to standardize these protocols because again, there were some proprietary aspects to them. And, uh, same thing as with codecs. [00:42:32] Francois: There was no, well, at least people wanted to have the, uh, flexibility to tweak parameters, adaptive streaming parameters the way they wanted for different scenarios. You may want to tweak the parameters differently. So they, they needed to be more flexibility on top of protocols not being truly available for use directly and for implementation directly in browsers. [00:42:53] Francois: It was also about providing applications with, uh, the flexibility they would need to tweak parameters. So media source extensions comes into play for exactly that. Media source extensions is really about you. The application fetches chunks of its audio and video stream the way it wants, and with the parameters it wants, and it adjusts whatever it wants. [00:43:15] Francois: And then it feeds that into the, uh, video or audio tag. and the browser takes care of the rest. So it's really about, doing, you know, the adaptive streaming. let applications do it, and then, uh, let the user agent, uh, the browser takes, take care of the rendering itself. That's media source extensions. [00:43:32] Francois: Initially it was pushed by, uh, Netflix. They were not the only ones of course, but there, there was a, a ma, a major, uh, proponent of this, uh, technical solution, because they wanted, uh, they, uh, they were, expanding all over the world, uh, with, uh, plenty of native, applications on all sorts of, uh, of, uh, devices. [00:43:52] Francois: And they wanted to have a way to stream content on the web as well. both for both, I guess, to expand to, um, a new, um, ecosystem, the web, uh, providing new opportunities, let's say. But at the same time also to have a fallback, in case they, because for native support on different platforms, they sometimes had to enter business agreements with, uh, you know, the hardware manufacturers, the whatever, the, uh, service provider or whatever. [00:44:19] Francois: and so that was a way to have a full back. That kind of work is more open, in case, uh, things take some time and so on. So, and they probably had other reasons. I mean, I'm not, I can't speak on behalf of Netflix, uh, on others, but they were not the only ones of course, uh, supporting this, uh, me, uh, media source extension, uh, uh, specification. [00:44:42] Francois: and that went kind of, well, I think it was creating 2011. I mean, the, the work started in 2011 and the recommendation was published in 2016, which is not too bad from a standardization perspective. It means only five years, you know, it's a very short amount of time. Encrypted Media Extensions [00:44:59] Francois: At the same time, and in parallel and complement to the media source extension specifications, uh, there was work on the encrypted media extensions, and here it was pushed by the same proponent in a way because they wanted to get premium content on the web. [00:45:14] Francois: And by premium content, you think of movies and, uh. These kind of beasts. And the problem with the, I guess the basic issue with, uh, digital asset such as movies, is that they cost hundreds of millions to produce. I mean, some cost less of course. And yet it's super easy to copy them if you have a access to the digital, uh, file. [00:45:35] Francois: You just copy and, uh, and that's it. Piracy uh, is super easy, uh, to achieve. It's illegal of course, but it's super easy to do. And so that's where the different legislations come into play with digital right management. Then the fact is most countries allow system that, can encrypt content and, uh, through what we call DRM systems. [00:45:59] Francois: so content providers, uh, the, the ones that have movies, so the studios here more, more and more, and Netflix is one, uh, one of the studios nowadays. Um, but not only, not only them all major studios will, uh, would, uh, push for, wanted to have something that would allow them to stream encrypted content, encrypted audio and video, uh, mostly video, to, uh, to web applications so that, uh, you. [00:46:25] Francois: Provide the movies, otherwise, they, they are just basically saying, and sorry, but, uh, this premium content will never make it to the web because there's no way we're gonna, uh, send it in clear, to, uh, to the end user. So Encrypting media extensions is, uh, is an API that allows to interface with, uh, what's called the content decryption module, CDM, uh, which itself interacts with, uh, the DR DRM systems that, uh, the browser may, may or may not support. [00:46:52] Francois: And so it provides a way for an application to receive encrypted content, pass it over get the, the, the right keys, the right license keys from a whatever system actually. Pass that logic over to the, and to the user agent, which passes, passes it over to, uh, the CDM system, which is kind of black box in, uh, that does its magic to get the right, uh, decryption key and then the, and to decrypt the content that can be rendered. [00:47:21] Francois: The encrypted media extensions triggered a, a hell of a lot of, uh, controversy. because it's DRM and DRM systems, uh, many people, uh, uh, things should be banned, uh, especially on the web because the, the premise of the web is that the, the user has trusts, a user agent. The, the web browser is called the user agent in all our, all our specifications. [00:47:44] Francois: And that's, uh, that's the trust relationship. And then they interact with a, a content provider. And so whatever they do with the content is their, I guess, actually their problem. And DRM introduces a third party, which is, uh, there's, uh, the, the end user no longer has the control on the content. [00:48:03] Francois: It has to rely on something else that, Restricts what it can achieve with the content. So it's, uh, it's not only a trust relationship with its, uh, user agents, it's also with, uh, with something else, which is the content provider, uh, in the end, the one that has the, uh, the license where provides the license. [00:48:22] Francois: And so that's, that triggers, uh, a hell of a lot of, uh, of discussions in the W3C degenerated, uh, uh, into, uh, formal objections being raised against the specification. and that escalated to, to the, I mean, at all leverage it. It's, it's the, the story in, uh, W3C that, um, really, uh, divided the membership into, opposed camps in a way, if you, that's was not only year, it was not really 50 50 in the sense that not just a huge fights, but the, that's, that triggered a hell of a lot of discussions and a lot of, a lot of, uh, of formal objections at the time. [00:49:00] Francois: Uh, we were still, From a governance perspective, interestingly, um, the W3C used to be a dictatorship. It's not how you should formulate it, of course, and I hope it's not going to be public, this podcast. Uh, but the, uh, it was a benevolent dictatorship. You could see it this way in the sense that, uh, the whole process escalated to one single person was, Tim Burners Lee, who had the final say, on when, when none of the other layers, had managed to catch and to resolve, a conflict. [00:49:32] Francois: Uh, that has hardly ever happened in, uh, the history of the W3C, but that happened to the two for EME, for encrypted media extensions. It had to go to the, uh, director level who, uh, after due consideration, uh, decided to, allow the EME to proceed. and that's why we have a, an EME, uh, uh, standard right now, but still re it remains something on the side. [00:49:56] Francois: EME we're still, uh, it's still in the scope of the media working group, for example. but the scope, if you look at the charter of the working group, we try to scope the, the, the, the, the updates we can make to the specification, uh, to make sure that we don't reopen, reopen, uh, a can of worms, because, well, it's really a, a topic that triggers friction for good and bad reasons again. [00:50:20] Jeremy: And when you talk about the media source extensions, that is the ability to write custom code to stream video in whatever way you want. You mentioned, the MPEG-DASH and http live streaming. So in that case, would that be the developer gets to write that code in JavaScript that's executed by the browser? [00:50:43] Francois: Yep, that's, uh, that would be it. and then typically, I guess the approach nowadays is more and more to develop low level APIs into W3C or web in, in general, I guess. And to let, uh. Libraries emerge that are going to make lives of a, a developer, uh, easier. So for MPEG DASH, we have the DASH.js, which does a fantastic job at, uh, at implementing the complexity of, uh, of adaptive streaming. [00:51:13] Francois: And you just, you just hook it into your, your workflow. And that's, uh, and that's it. Encrypted Media Extensions are closed source [00:51:20] Jeremy: And with the encrypted media extensions I'm trying to picture how those work and how they work differently. [00:51:28] Francois: Well, it's because the, the, the, the key architecture is that the, the stream that you, the stream that you may assemble with a media source extensions, for example. 'cause typically they, they're used in collaboration. When you hook the, hook it into the video tag, you also. Call EME and actually the stream goes to EME. [00:51:49] Francois: And when it goes to EME, actually the user agent hands the encrypted stream. You're still encrypted at this time. Uh, encrypted, uh, stream goes to the CDM content decryption module, and that's a black box well, it has some black, black, uh, black box logic. So it's not, uh, even if you look at the chromium source code, for example, you won't see the implementation of the CDM because it's a, it's a black box, so it's not part of the browser se it's a sand, it's sandboxed, it's execution sandbox. [00:52:17] Francois: That's, uh, the, the EME is kind of unique in, in this way where the, the CDM is not allowed to make network requests, for example, again, for privacy reasons. so anyway, the, the CDM box has the logic to decrypt the content and it hands it over, and then it depends, it depends on the level of protection you. [00:52:37] Francois: You need or that the system supports. It can be against software based protection, in which case actually, a highly motivated, uh, uh, uh, attacker could, uh, actually get access to the decoded stream, or it can be more hardware protected, in which case actually the, it goes to the, uh, to your final screen. [00:52:58] Francois: But it goes, it, it goes through the hardware in a, in a mode that the US supports in a mode that even the user agent doesn't have access to it. So it doesn't, it can't even see the pixels that, uh, gets rendered on the screen. There are, uh, several other, uh, APIs that you could use, for example, to take a screenshot of your, of your application and so on. [00:53:16] Francois: And you cannot apply them to, uh, such content because they're just gonna return a black box. again, because the user agent itself does not see the, uh, the pixels, which is exactly what you want with encrypted content. [00:53:29] Jeremy: And the, the content decryption module, it's, if I understand correctly, it's something that's shipped with the browsers, but you were saying is if you were to look at the public source code of Chromium or of Firefox, you would not see that implementation. Content Decryption Module (Widevine, PlayReady) [00:53:47] Francois: True. I mean, the, the, um, the typical examples are, uh, uh, widevine, so wide Vine. So interestingly, uh, speaking in theory, these, uh, systems could have been provided by anyone in practice. They've been provided by the browser vendors themselves. So Google has Wide Vine. Uh, Microsoft has something called PlayReady. Apple uh, the name, uh, escapes my, uh, sorry. They don't have it on top of my mind. So they, that's basically what they support. So they, they also own that code, but in a way they don't have to. And Firefox actually, uh, they, uh, don't, don't remember which one, they support among these three. but, uh, they, they don't own that code typically. [00:54:29] Francois: They provide a wrapper around, around it. Yeah, that's, that's exactly the, the crux of the, uh, issue that, people have with, uh, with DRMs, right? It's, uh, the fact that, uh, suddenly you have a bit of code running there that is, uh, that, okay, you can send box, but, uh, you cannot inspect and you don't have, uh, access to its, uh, source code. [00:54:52] Jeremy: That's interesting. So the, almost the entire browser is open source, but if you wanna watch a Netflix movie for example, then you, you need to, run this, this CDM, in addition to just the browser code. I, I think, you know, we've kind of covered a lot. Documenting what's available in browsers for developers [00:55:13] Jeremy: I wonder if there's any other examples or anything else you thought would be important to mention in, in the context of the W3C. [00:55:23] Francois: There, there's one thing which, uh, relates to, uh, activities I'm doing also at W3C. Um. Here, we've been talking a lot about, uh, standards and, implementations in browsers, but there's also, uh, adoption of these browser, of these technology standards by developers in general and making sure that developers are aware of what exists, making sure that they understand what exists and one of the, key pain points that people, uh. [00:55:54] Francois: Uh, keep raising on, uh, the web platform is first. Well, the, the, the web platform is unique in the sense that there are different implementations. I mean, if you, [00:56:03] Francois: Uh, anyway, there are different, uh, context, different run times where there, there's just one provided by the company that owns the, uh, the, the, the system. The web platform is implemented by different, uh, organizations. and so you end up the system where no one, there's what's in the specs is not necessarily supported. [00:56:22] Francois: And of course, MDN tries, uh, to document what's what's supported, uh, thoroughly. But for MDN to work, there's a hell of a lot of needs for data that, tracks browser support. And this, uh, this data is typically in a project called the Browser Compat Data, BCD owned by, uh, MDN as well. But, the Open Web Docs collective is a, uh, is, uh, the one, maintaining that, uh, that data under the hoods. [00:56:50] Francois: anyway, all of that to say that, uh, to make sure that, we track things beyond work on technical specifications, because if you look at it from W3C perspective, life ends when the spec reaches standards, uh, you know, candidate rec or rec, you could just say, oh, done with my work. but that's not how things work. [00:57:10] Francois: There's always, you need the feedback loop and, in order to make sure that developers get the information and can provide the, the feedback that standardization can benefit from and browser vendors can benefit from. We've been working on a project called web Features with browser vendors mainly, and, uh, a few of the folks and MDN and can I use and different, uh, different people, to catalog, the web in terms of features that speak to developers and from that catalog. [00:57:40] Francois: So it's a set of, uh, it's a set of, uh, feature IDs with a feature name and feature description that say, you know, this is how developers would, uh, understand, uh, instead of going too fine grained in terms of, uh, there's this one function call that does this because that's where you, the, the kind of support data you may get from browser data and MDN initially, and having some kind of a coarser grained, uh, structure that says these are the, features that make sense. [00:58:09] Francois: They talk to developers. That's what developers talk about, and that's the info. So the, we need to have data on these particular features because that's how developers are going approach the specs. Uh. and from that we've derived the notion of baseline badges that you have, uh, are now, uh, shown on MDN on can I use and integrated in, uh, IDE tool, IDE Tools such as visual, visual studio, and, uh, uh, libraries, uh, linked, some linters have started to, um, to integrate that data. [00:58:41] Francois: Uh, so, the way it works is, uh, we've been mapping these coarser grained features to BCDs finer grained support data, and from there we've been deriving a kind of a, a batch that says, yeah, this, this feature is implemented well, has limited availability because it's only implemented in one or two browsers, for example. [00:59:07] Francois: It's, newly available because. It was implemented. It's been, it's implemented across the main browser vendor, um, across the main browsers that people use. But it's recent, and widely available, which we try to, uh, well, there's been lots of discussion in the, in the group to, uh, come up with a definition which essentially ends up being 30 months after, a feature become, became newly available. [00:59:34] Francois: And that's when, that's the time it takes for the, for the versions of the, the different versions of the browser to propagate. Uh, because you, it's not because there's a new version of a, of a browser that, uh, people just, Ima immediately, uh, get it. So it takes a while, to propagate, uh, across the, uh, the, the user, uh, user base. [00:59:56] Francois: And so the, the goal is to have a, a, a signal that. Developers can rely on saying, okay, well it's widely available so I can really use that feature. And of course, if that doesn't work, then we need to know about it. And so we are also working with, uh, people doing so developer surveys such as state of, uh, CSS, state of HTML, state of JavaScript. [01:00:15] Francois: That's I guess, the main ones. But also we are also running, uh, MDN short surveys with the MDN people to gather feedback on. On the, on these same features, and to feed the loop and to, uh, to complete the loop. and these data is also used by, internally, by browser vendors to inform, prioritization process, their prioritization process, and typically as part of the interop project that they're also running, uh, on the site [01:00:43] Francois: So a, a number of different, I've mentioned, uh, I guess a number of different projects, uh, coming along together. But that's the goal is to create links, across all of these, um, uh, ongoing projects with a view to integrating developers, more, and gathering feedback as early as possible and inform decision. [01:01:04] Francois: We take at the standardization level that can affect the, the lives of the developers and making sure that it's, uh, it affects them in a, in a positive way. [01:01:14] Jeremy: just trying to understand, 'cause you had mentioned that there's the web features and the baseline, and I was, I was trying to picture where developers would actually, um, see these things. And it sounds like from what you're saying is W3C comes up with what stage some of these features are at, and then developers would end up seeing it on MDN or, or some other site. [01:01:37] Francois: So, uh, I'm working on it, but that doesn't mean it's a W3C thing. It's a, it's a, again, it's a, we have different types of group. It's a community group, so it's the Web DX Community group at W3C, which means it's a community owned thing. so that's why I'm mentioning a working with a representative from, and people from MDN people, from open Web docs. [01:02:05] Francois: so that's the first point. The second point is, so it's, indeed this data is now being integrated. If you, and you look, uh, you'll, you'll see it in on top of the MDN pages on most of them. If you look at, uh, any kind of feature, you'll see a, a few logos, uh, a baseline banner. and then can I use, it's the same thing. [01:02:24] Francois: You're going to get a baseline, banner. It's more on, can I use, and it's meant to capture the fact that the feature is widely available or if you may need to pay attention to it. Of course, it's a simplification, and the goal is not to the way it's, the way the messaging is done to developers is meant to capture the fact that, they may want to look, uh, into more than just this, baseline status, because. [01:02:54] Francois: If you take a look at web platform tests, for example, and if you were to base your assessment of whether a feature is supported based on test results, you'll end up saying the web platform has no supported technology because there are absolutely no API that, uh, where browsers pass 100% of the, of the, of the test suite. [01:03:18] Francois: There may be a few of them, I don't know. But, there's a simplification in the, in the process when a feature is, uh, set to be baseline, there may be more things to look at nevertheless, but it's meant to provide a signal that, uh, still developers can rely on their day-to-day, uh, lives. [01:03:36] Francois: if they use the, the feature, let's say, as a reasonably intended and not, uh, using to advance the logic. [01:03:48] Jeremy: I see. Yeah. I'm looking at one of the pages on MDN right now, and I can see at the top there's the, the baseline and it, it mentions that this feature works across many browsers and devices, and then they say how long it's been available. And so that's a way that people at a glance can, can tell, which APIs they can use. [01:04:08] Francois: it also started, uh, out of a desire to summarize this, uh, browser compatibility table that you see at the end of the page of the, the bottom of the page in on MDN. but there are where developers were saying, well, it's, it's fine, but it's, it goes too much into detail. So we don't know in the end, can we, can we use that feature or can we, can we not use that feature? [01:04:28] Francois: So it's meant as a informed summary of, uh, of, of that it relies on the same data again. and more importantly, we're beyond MDN, we're working with tools providers to integrate that as well. So I mentioned the, uh, visual Studio is one of them. So recently they shipped a new version where when you use a feature, you can, you can have some contextual, uh. [01:04:53] Francois: A menu that tells you, yeah, uh, that's fine. You, this CSS property, you can, you can use it, it's widely available or be aware this one is limited Availability only, availability only available in Firefox or, or Chrome or Safari work kit, whatever. [01:05:08] Jeremy: I think that's a good place to wrap it up, if people want to learn more about the work you're doing or learn more about sort of this whole recommendations process, where, where should they head? [01:05:23] Francois: Generally speaking, we're extremely open to, uh, people contributing to the W3C. and where should they go if they, it depends on what they want. So I guess the, the in usually where, how things start for someone getting involved in the W3C is that they have some

Piracy in Great Qing surges to a "golden age" during the Qianlong & Jiaqing eras. Corsair Confederations like Zheng Yi Sao's vast-beyond-reckoning Red Flag Fleet, backed by the likes of Vietnam's Tay Son rebels, dominating the South China Sea through organized plunder and shadow economies. Jiaqing's shift to accomodation, while necessary, may expose Qing naval vulnerabilities, paving the way for foreign interventions and imperial decline... Time Period Covered: Prelude: ca. 15th-18th Cs. Main: ~1780-1810 CE Major Sources Cited: Antony, Robert J. Like Froth Floating on the Sea: The World of Pirates and Seafarers in Late Imperial South China. Andrade, Tonio. Lost Colony: The Untold Story of China's First Great Victory over the West. Murray, Dian H. Pirates of the South China Coast, 1790–1810. Perdue, Peter C. China Marches West: The Qing Conquest of Central Eurasia. Qing Shilu (Veritable Records of the Qing Dynasty). Spence, Jonathan D. The Search for Modern China. Woodside, Alexander. "The Ch'ien-lung Reign" in The Cambridge History of China Vol. 9, Pt. 1: The Ch'ing Empire to 1800. Learn more about your ad choices. Visit megaphone.fm/adchoices

Join Anthony and Joe for a brutally honest discussion about WWE's big move to Saudi Arabia, the spectacle of WrestleMania 43, and the wild world of pro wrestling and comedy. From the politics of international events to the parade of legendary (and not-so-legendary) wrestlers and comedians, nothing is off-limits. Expect sharp commentary, plenty of laughs, and a deep dive into the business, culture, and controversies surrounding wrestling's global expansion. Plus, hear their takes on streaming services, internet piracy, and the ever-changing landscape of entertainment.0:00:00 Monkey? & Opening Banter00:01:22 Avril Lavigne, Gigi Dolan, and Revisionist History00:05:05 Nepotism in Music & Wrestling00:10:00 Poppy, Amy Lee, and New Music Collabs00:14:00 WWE's Big Saudi Announcement00:19:00 WWE in Saudi Arabia: Fan Reactions00:23:00 Bianca Belair on Women's Progress00:27:00 Triple H, The Undertaker, and Ethics00:32:00 The Prince's Speech & WWE's Motives00:38:00 Will WrestleMania in Saudi Arabia Succeed?00:44:00 Comedians and the Saudi Comedy Festival00:50:00 Who Would Wrestle in Saudi Arabia?00:58:00 Streaming Services, Piracy, and Value01:06:00 Generational Differences in Piracy01:14:00 Closing Thoughts & Upcoming ShowsBecome a supporter of this podcast: https://www.spreaker.com/podcast/wrestling-soup--1425249/support.

Captain Silvo heralds the end of the Era of Piracy as he is the final Marquee to be released. We anticipate the imminent release of Hondo and the return of Mace. Presented by Radio Free Tatooine (https://www.radiofreetatooine.com) We love hearing from our Tatooiners. Join our Discord to share your thoughts, discuss strategies, and stay up […] The post Galactic War Report – Episode 443: Mr. Silvo is My Father’s Name appeared first on RADIO FREE TATOOINE.

Con's Piracy - Penelope by Rock Band Land

A judge rejected Anthropic's $1.5 billion piracy settlement, OpenAI refutes claims of a California exit due to regulatory issues, and the U.S. has ended agreements with European nations to counter disinformation from countries like Russia, China, and Iran. MP3 Please SUBSCRIBE HERE for free or get DTNS Live ad-free. A special thanks to all ourContinue reading "A Judge Rejected Anthropic's $1.5 Billion Piracy Settlement – DTH"

New malware phishing campaign hidden in SVG files Anthropic agrees to pay $1.5bn in book piracy lawsuit Qantas penalizes executives for cyberattack Huge thanks to our sponsor, Vanta Do you know the status of your compliance controls right now? Like...right now? We know that real-time visibility is critical for security, but when it comes to our GRC programs…we rely on point-in-time checks. But more than 9,000 companies have continuous visibility into their controls with Vanta. Vanta brings automation to evidence collection across over 35 frameworks, like SOC 2 and ISO 27001. They also centralize key workflows like policies, access reviews, and reporting, and helps you get security questionnaires done 5 times faster with AI. Now that's…a new way to GRC. Get started at Vanta.com/headlines. Find the stories behind the headlines at CISOseries.com.  

Check out our Patreon for a daily Lawrence Select™ Meme: https://www.patreon.com/insidegamesYTJoin the Inside Games notification Discord server for alerts when we publish new videos: http://discord.gg/ArvphbMPFJHosted by:Lawrence: http://twitch.tv/sirlarr | Bruce: http://twitch.tv/brucegreene Edited by: Shooklyn: https://linktr.ee/ShooklynSources --https://arstechnica.com/gaming/2025/08/todays-game-consoles-are-historically-overpriced/https://automaton-media.com/en/news/ps5s-steep-price-a-barrier-for-potential-monster-hunter-wilds-players-capcom-president-says/https://www.bbc.com/news/articles/ckgejpxzepkohttps://steamdb.info/app/1030300/charts/https://www.thegamer.com/hollow-knight-silksong-player-count-second-highest-indie-has-achieved/https://www.theverge.com/news/771772/hollow-knight-silksong-stardew-valley-eric-barone-concernedapehttps://www.reddit.com/r/Piracy/comments/1n6os6w/are_you_guys_pirating_silksong/https://insider-gaming.com/marvels-wolverine-trailer/https://x.com/2K/status/1963775457876406534https://insider-gaming.com/ea-sports-walks-away-from-developing-college-basketball/https://www.rockpapershotgun.com/civilization-7-developers-firaxis-have-laid-off-an-unspecified-number-of-workers-2k-confirmhttps://www.linkedin.com/feed/update/urn:li:activity:7369382797020463105/Music —Switch It Up - Silent Partner https://youtu.be/r_HRbXhOir8Funk Down - MK2 https://youtu.be/SPN_Ssgqlzc

France fines Google and Shein over cookie misconduct CISA adds more TP-Link routers flaws to its KEV catalog World's largest sports piracy site shut down Huge thanks to our sponsor, ThreatLocker ThreatLocker® is a global leader in Zero Trust endpoint security, offering cybersecurity controls to protect businesses from zero-day attacks and ransomware. ThreatLocker operates with a default deny approach to reduce the attack surface and mitigate potential cyber vulnerabilities. To learn more and start your free trial, visit ThreatLocker.com/CISO. Find the stories behind the headlines at CISOseries.com.

Click Here to ask your book writing and publishing questions!Copyright. Piracy. LibGen. AI scraping. If just reading that list makes you want to hide under your desk with a bottle of...something...you're not alone. Indie authors are being forced to navigate a landscape that feels murkier by the day, and most of us didn't exactly sign up to become copyright attorneys.Unfortunately, the “poor man's copyright” trick (mailing yourself a sealed copy of your manuscript) I used to suggest won't do a thing to protect you in 2025. What does matter? Understanding when and how to formally register your copyright, what that three-month filing window really means, and how to handle it when you discover your book has been pirated.In this episode, I break down:Whether copyright registration is worth the time and money for indie authorsWhat to do (and what not to do) if your book shows up on LibGen or other shady sitesThe difference between healthy protection and exhausting paranoiaI'll show you how to balance protecting your work with staying focused on what really matters—building genuine connections with readers who do want to support you.Want to go deeper? Check out Jenn Hansen-dePaula's conversation with attorney Olivia Maynes for a legal perspective here: https://jenndepaula.com/podcast/90

In today's MadTech Daily, we discuss Disney strengthening its European content slate with a ZDF deal, Anthropic settling its piracy case, and Perplexity's new revenue model rewarding publishers for AI articles used by its AI. 

Guest: Angela C. Sutton is an Assistant research professor at Vanderbilt University, where she has taught Seapower in History, the Golden Age of Piracy, and Comparative Slavery. She is the author of Pirates of the Slave Trade: The Battle of Cape Lopez and the Birth of an American Institution. The post The Pirates That Halted The Slave Trade appeared first on KPFA.

SpaceX has successfully launched the Starship for its 10th test flight after it was delayed a couple of times due to weather conditions and other issues. This time, the company was able to achieve its objectives without the vehicle and its booster exploding mid-test. In other tech news, Anthropic has settled a class-action lawsuit brought by a group of authors for an undisclosed sum. The move means the company will avoid a potentially more costly ruling if the case regarding its use of copyright materials to train artificial intelligence tools had moved forward. And, Meta is throwing its resources behind a new super PAC in California. According to Politico, the group will support state-level political candidates who espouse tech-friendly policies, particularly those with a loose approach to regulating artificial intelligence. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Keywordscybersecurity, product management, career development, market strategy, customer insights, hacking, music, team building, startup life, risk management  SummaryIn this episode of No Password Required, host Jack Clabby and co-host Kayleigh Melton engage in a lively conversation with John Shipp, a product strategist at Rapid7. They explore John's unique journey from a metalhead to a cybersecurity expert, discussing the importance of passion in career development, the intricacies of product management, and the significance of customer insights in shaping cybersecurity solutions. John shares his early experiences in hacking, the influence of music on his life, and the value of building strong teams and company culture. The episode concludes with a fun segment called the Lifestyle Polygraph, where John answers quirky questions about his ideal cyber team and his dream day with Ric Flair.  TakeawaysBeing a metalhead prepares you for the boardroom.You can follow your passion and thrive in your career.Product management involves understanding customer needs and market dynamics.Curiosity is a key driver in the tech field.Great teams are built on strong leadership and culture.Startup life requires a willingness to take risks.Networking and building relationships are crucial in cybersecurity.Understanding your risk appetite is important when considering career moves.Music can be a significant influence on personal and professional life.Mentorship and sharing knowledge are vital for growth in the industry. TitlesFrom Metal to Management: A Cybersecurity JourneyPassion and Profession: Finding Your Path in Cybersecurity Sound bites"You can follow your passion and thrive.""I learned security at scale.""Curiosity drives my passion for tech." Chapters00:00 Introduction to Cybersecurity and Personal Journeys02:49 The Role of Passion in Career Development05:21 Navigating Product Management and Market Strategy08:23 The Evolution of Cybersecurity Skills11:37 The Importance of Customer Insights in Product Development14:35 Early Experiences in Hacking and Cybersecurity17:24 The Influence of Music on Personal and Professional Life20:19 Building Teams and Company Culture23:10 Startup Life and Risk Management26:08 Lifestyle Polygraph: Fun Questions and Insights29:13 Final Thoughts and Connections 

G'day Folks, In this episode of the General Knowledge Podcast, Lee is joined by Ethan Nash from TOTT News for a deep dive into the state of digital freedom, media, and government control. The conversation opens with a look at the decline of streaming services and the resurgence of piracy, highlighting how rising subscription costs, intrusive ads, and restrictions on password sharing have pushed audiences back toward torrenting. This sets the stage for a broader discussion on ownership, control of media, and the erosion of consumer choice in the digital age. The core of the discussion centers on the looming implementation of digital ID systems and restrictions to internet access in Australia. Ethan outlines how governments worldwide, particularly in the UK and Australia, are pushing toward mandatory identification for basic online activity, including Google searches, social media, and streaming platforms. The hosts warn that this shift represents the death of anonymity online, with VPN use already being targeted for suppression. They connect these developments to global agendas promoted by the World Economic Forum and the growing influence of “China-style” surveillance models. The conversation then broadens into political and social consequences. Lee and Ethan examine how governments often justify surveillance and restrictions under the guise of “protecting children,” while in reality building infrastructure for full-spectrum control. They touch on the proposed laws in Australia, the role of the eSafety Commissioner, and moves toward centralised digital identity through platforms like MyGov. Drawing parallels to past authoritarian overreaches, they argue that citizens are losing both privacy and basic freedoms in ways that would have been unimaginable only a decade ago. Despite the bleak outlook, the hosts also highlight potential for resistance and innovation. From “anti-surveillance tech” like special clothing and peer-to-peer communication systems, to grassroots activism such as the UK's “Blade Runners” dismantling surveillance cameras, they suggest necessity will fuel inventive ways to fight back. They urge listeners to consider alternative systems, whether through new technologies, financial models, or community-driven solutions, stressing that individuals with resources and courage will be vital in shaping parallel networks of resilience. Finally, the episode closes by tying these issues back to Australia's political and economic landscape. They discuss weak leadership, controversial marches, immigration pressures, and proposed tax hikes, framing them as symptoms of a nation in decline. Yet, they emphasize that collective action and informed resistance can still make a difference. Whether through petitions, protests, or simply refusing to comply, they argue that Australians must recognise the stakes: protecting privacy, autonomy, and national integrity before these freedoms are permanently eroded. https://tottnews.com/2025/08/12/new-forever-chemicals-sydney-water/ https://senatorbabet.com.au/media-release-senator-babet-urges-australians-to-stand-against-digital-surveillance/ https://www.facebook.com/events/1476921229995080 Remember the Bonus Content shows are available now to all Patreon supporters for just AU$8 a month! Now 44 Bonus shows are available just for those who see value in what we do. Including a 5 part series on the Port Arthur Massacre, The Electric Universe with Physicist Wal Thornhill, The Moon Landing Hoax & The Titanic Conspiracy! PLUS!!!... every Patreon member gets a video version of every episode of the regular show too! Instead of donating money to a charity that most likely won't pass on your full donation to whomever needs it, why not sign up as a patron over at our Patreon account for all the bonus content and extra podcasts! https://www.patreon.com/RealNewsAustralia   PayPal donations can be made me here at RealNewsAustralia.com to help pay for costs associated with bringing you this show if you don't want any extra bonus content for your support.   As always make sure you subscribe and give us a 5 star rating on iTunes with a nice little review to help us out! Please consider sharing on social media to ensure we reach a bigger audience!    We're relying on YOU!   Links:  https://www.patreon.com/RealNewsAustralia - Join Today! BUY ME A COFFEE! https://www.buymeacoffee.com/GeneralMaddox/membership http://paypal.me/LeeMaddox79- Support today!  

Haashiraamaa Senju and Kisame Hoshikage along with Schumy Vanna kaviyangal's very own team members codenamed Space Monkeys come together in this episode to discuss about piracy and everything related to it in detail. Episode Director - Gaara the Kazakage Episode editor - Gaara the Kazakage & Spacemonkey69 Podcast Poster - Levi Ackerman Podcast quality control team -Levi Ackerman SpaceMonkey01 & SpaceMonkey21 Produced by Leaf Village (Konoha) Ninja Academy 13 families of the Illuminati. Schumy Vanna Kaviyangal is a company which consists of some hardcore Internet Artists, they are known for their memes, podcasts and their rationalist content, they are pro left and hanging out with them is a fun fest (we have no choice but to type this out for ourselves), let me add something else as well, we been Spotify podcast chart-toppers for many many weeks and we also have the longest podcast episode in Asia for 13 plus hours... So this is us.PS- Some say we are funded by the Illuminati but we wouldn't be opening a Patreon page for us if they were funding us right?. kbyethanks. SVK Brotherhood Form:⁠⁠⁠⁠⁠https://forms.gle/9RxFJnT3KtS8C85fA⁠⁠⁠⁠⁠UPI ID- ⁠schumyvannakaviyangal13@axlUPI ID- ⁠⁠schumyvannakaviyangal13@yblUPI ID -schumyvannakaviyangal13@iblFully Flimy X SVK Merchandise:-⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://fullyfilmy.in/collections/svk-collection⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠---------------------------------Support Us----------------------------------------Support Schumy Vanna Kaviyangal if you feel like it

Have an idea or tip? Send us a text!The intersection of copyright law and artificial intelligence represents one of the most challenging legal frontiers of our digital era. In this thought-provoking conversation, Dr. C. Daniel Miller (The Copyright Detective) unpacks the complex world of intellectual property rights when machines can generate content indistinguishable from human creation.From his unique background spanning higher education, NASA projects, and over a decade in copyright clearance, Dr. Miller offers a balanced perspective on AI as both an innovative tool and a potential legal minefield. He explains that while copyright fundamentally exists to encourage creativity by granting creators exclusive rights, AI systems have disrupted this framework by training on millions of works without permission or compensation.Perhaps most surprising is the current legal status of AI-generated content: images created solely through prompts remain uncopyrightable according to the US Copyright Office. Neither the user nor the AI can claim ownership, effectively placing such creations in the public domain. Meanwhile, major lawsuits loom large over the industry, with Disney and Universal Studios taking on Midjourney for creating near-perfect replicas of iconic characters, and potential damages in other cases potentially reaching billions.For creators concerned about protecting their work, Dr. Miller emphasizes the critical importance of copyright registration within 90 days of publication. Without registration, creators cannot sue for infringement and lose access to statutory damages that make legal action financially viable. He also warns about "AI hallucinations," noting studies showing up to 79% of content from newer AI platforms may contain factual errors, reinforcing his mantra: "Don't trust and always verify."Whether you're a photographer concerned MediaclipMediaclip strives to continuously enhance the user experience while dramatically increasing revenue.Independent Photo ImagersIPI is a member + trade association and a cooperative buying group in the photo + print industry.Buzzsprout - Let's get your podcast launched!Start for FREEVisual 1stVisual 1st is the premier global conference focused on the photo and video ecosystem. Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Support the showSign up for the Dead Pixels Society newsletter at http://bit.ly/DeadPixelsSignUp.Contact us at gary@thedeadpixelssociety.comVisit our LinkedIn group, Photo/Digital Imaging Network, and Facebook group, The Dead Pixels Society. Leave a review on Apple and Podchaser. Are you interested in being a guest? Click here for details.Hosted and produced by Gary PageauEdited by Olivia PageauAnnouncer: Erin Manning

As the Golden Age of Piracy drew to a close, the oceans turned into hunting grounds where pirates became prey. Dan tells the dramatic tale of the rise and fall of Bartholomew Roberts, or Black Bart, one of the most feared pirates of the age.From West Africa to South America, Roberts dominated the Atlantic. He captured over 400 ships before the British Navy, led by Captain Chaloner Ogle, finally caught up with him. His death in a blaze of cannon fire—and the mass hanging of his captured crew—marked the brutal end of piracy's golden era.Dan is joined by Sophie Nibbs, the curator of the new Pirates exhibition at the National Maritime Museum, Greenwich, to explore this final chapter of our Pirates series.You can discover more and book tickets for the 'Pirates' exhibition at the National Maritime Museum Greenwich here.Written by Dan Snow, produced by Mariana Des Forges and edited by Dougal PatmoreJoin Dan and the team for a special LIVE recording of Dan Snow's History Hit on Friday 12th September 2025! To celebrate 10 years of the podcast, Dan is putting on a special show of signature storytelling, never-before-heard anecdotes from his often stranger-than-fiction career as well as answering the burning questions you've always wanted to ask!Get tickets here, before they sell out: https://www.kingsplace.co.uk/whats-on/words/dan-snows-history-hit/You can now find Dan Snow's History Hit on YouTube! Watch episodes every Friday (including this one) here.Sign up to History Hit for hundreds of hours of original documentaries, with a new release every week and ad-free podcasts. Sign up at https://www.historyhit.com/subscribe.We'd love to hear your feedback - you can take part in our podcast survey here: https://insights.historyhit.com/history-hit-podcast-always-on.You can also email the podcast directly at ds.hh@historyhit.com.

• Intro• FBI Takes Down Switch Piracy Site• Switch 2 Owners Getting Banned for Using Pre-Owned Switch 1 Games• The Backlog• Krafton / Subnautica Debacle• Switch 2 Pro Controllers Have Poor Repairability• New 8BitDo Pro 3 Controller Announced• Nintendo Ending Game Vouchers• Xbox ASUS ROG Ally Prices Leak• VP of EU Parliament Supports Stop Killing Games Movement• Tony Hawk 3+4 Locks Easter Egg Behind Paywall• Tony Hawk 3+4 Has Guitar Hero Reference Pulled• Donkey Kong Performance Issues on Switch 2• John Wick Hex Being Delisted• Cyberpunk Coming to Mac• Analogue 3D Delayed to August• TWEET OF THE WEEKOriginally streamed on July 15, 2025

Piracy websites are being cracked down on by the American Government, but what are some of the reasons that drive people to pirate? We discuss this part of the industry that has an impact, even if it's something that's not openly discussed often. There's other news to get into as well, as our gaming backlogs grow this summer with all of the gaming sales and bundles. All this and much more make up another week of the longest running video game podcast, Orange Lounge Radio!   Also in the News:   * Romero Games was Not Closed by Microsoft * Digital Xbox Games Now with Accessibility Tags Expected for other Platforms * Ubisoft Still Laying Off after $1.25 Billion Investment * Nintendo Vouchers to End   All this and more on the show where EVERY gamer has a voice-- Orange Lounge Radio! LIVE on the VOG Network, Sunday nights at 6 Pacific, 9 Eastern www.vognetwork.com Mailbag: participate (at) orangeloungeradio dot com

SCOTUS Free Speech Coalition v. Paxton Adalytics finds 9,000+ pirated movies, including summer blockbusters, TV shows, and live sports on YouTube, amassing a collective 250M+ views from July to May SCOTUS granting cert to Cox v. Sony Bartz v. Anthropic AI copyright case Kadrey v. Meta AI copyright case Microsoft layoffs hit 9,000 employees in new wave of cuts Here are the letters that let Apple and Google ignore the TikTok ban Identities of More Than 80 Americans Stolen for North Korean IT Worker Scams Everyone in tech has an opinion about Soham Parekh | TechCrunch Elon Musk's Starlink Adds $750 Congestion Charge Mystery recall of iPhone engineers may be Chinese interference in Apple's plans Host: Leo Laporte Guests: Cathy Gellis and Nicholas De Leon Download or subscribe to This Week in Tech at https://twit.tv/shows/this-week-in-tech Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: storyblok.com/twittv-25 zscaler.com/security Miro.com/podcast oracle.com/twit canary.tools/twit - use code: TWIT

SCOTUS Free Speech Coalition v. Paxton Adalytics finds 9,000+ pirated movies, including summer blockbusters, TV shows, and live sports on YouTube, amassing a collective 250M+ views from July to May SCOTUS granting cert to Cox v. Sony Bartz v. Anthropic AI copyright case Kadrey v. Meta AI copyright case Microsoft layoffs hit 9,000 employees in new wave of cuts Here are the letters that let Apple and Google ignore the TikTok ban Identities of More Than 80 Americans Stolen for North Korean IT Worker Scams Everyone in tech has an opinion about Soham Parekh | TechCrunch Elon Musk's Starlink Adds $750 Congestion Charge Mystery recall of iPhone engineers may be Chinese interference in Apple's plans Host: Leo Laporte Guests: Cathy Gellis and Nicholas De Leon Download or subscribe to This Week in Tech at https://twit.tv/shows/this-week-in-tech Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: storyblok.com/twittv-25 zscaler.com/security Miro.com/podcast oracle.com/twit canary.tools/twit - use code: TWIT

Zheng Yi Sao was a pirate leader so formidable that she made Blackbeard and Captain Morgan look like amateurs. From humble beginnings as a sex worker in Canton, she rose to command a vast pirate fleet that wrought havoc in the South China Sea. She took on the Qing Dynasty, the Portuguese and the East India Company and still managed to walk away free.In the second episode of our 'Pirates' mini-series, Dan is joined by Andrew Choong, Curator of Historic Photographs & Ship Plans at the National Maritime Museum in Greenwich, to uncover the story of one of history's most successful buccaneers.You can discover more about the exhibition and book tickets here.Produced by Mariana Des Forges and edited by Dougal Patmore.Join Dan and the team for the first-ever LIVE recording of Dan Snow's History Hit on Friday 12th September 2025! To celebrate 10 years of the podcast, Dan is putting on a special show of signature storytelling, never-before-heard anecdotes from his often stranger-than-fiction career as well as answering the burning questions you've always wanted to ask! Get tickets here, before they sell out: https://www.kingsplace.co.uk/whats-on/words/dan-snows-history-hit/You can now find Dan Snow's History Hit on YouTube! Watch episodes every Friday here.Sign up to History Hit for hundreds of hours of original documentaries, with a new release every week and ad-free podcasts. Sign up at https://www.historyhit.com/subscribe.We'd love to hear your feedback - you can take part in our podcast survey here: https://insights.historyhit.com/history-hit-podcast-always-on.You can also email the podcast directly at ds.hh@historyhit.com.

Swashbuckling rogues with a disregard for authority surging across the oceans, the smell of salt and gunpowder in their nostrils... looking for treasure on desert islands. Just like Dan, we're sure you've also grown up reading pirate stories and watching adventure films.But, what if we told you that most of what you know about pirates isn't quite true?This July, Dan is teaming up with the National Maritime Museum Greenwich to unravel the fact from the fiction and tell you the extraordinary stories of the most formidable pirates in history. From the South China Seas to the Barbary Coast and the Caribbean, he'll be joined by leading experts to chart the rise and fall of Piracy across the 17th - 19th centuries.New episodes every Monday from 29th June to 21st July.Be sure to hit follow wherever you get your podcasts so you never miss an episode.Produced by Mariana Des Forges and edited by Dougal Patmore.You can email the podcast directly at ds.hh@historyhit.com.

Step confidently into daily life with the ultra-light Vessi Weekend Sneaker and their dry sock guarantee. They even come with a 1-year warranty with 30-days of worry-free returns. Get 15% off your first pair at https://vessi.com/wanshow at checkout! Check out the CORSAIR Platform:4 Elevate Desk at: https://lmg.gg/Platform4 Visit https://www.squarespace.com/WAN and use offer code WAN for 10% off Buy something from dbrand so they have an excuse to keep messing with Linus. Visit http://dbrand.com/WAN Check out Dell's powerful business laptops at: https://lmg.gg/dellprowan Pick up a Secretlab Titan Evo Ergonomic Gaming Chair today at: https://lmg.gg/secretlabwan Get a special deal on Private Internet Access VPN today at https://www.piavpn.com/LinusWan Purchases made through some store links may provide some compensation to Linus Media Group. Learn more about your ad choices. Visit megaphone.fm/adchoices