Displaying all 3 Episode of Coder Radio with the tag “surveillance”.
-
588: Hulk Smash “PUNY DEVS”
September 18th, 2024 | 59 mins 32 secs
ai cameras, anthropic, california ai bill, coder radio, crowdstrike incident, demand decline, developers, development podcast, drones, google, iphone 16 pre-orders, kernel access, larry ellison, liability, microsoft, open-source ai, openai, oracle, police oversight, regulation, safety committee, safety protocols, sam altman, surveillance, windows security
The insidious undercurrents threatening to crush open-source AI projects, plus our thoughts on Microsoft's "big changes" to Windows post-CrowdStrike.
-
540: Sherlockin All Over the Place
October 18th, 2023 | 1 hr 12 mins
4k nintendo 64, 90/10 rule, ai features, analogue, apple, big tech, c#, chat control 2.0, coder radio, dev retention rates, developers, development podcast, drew houston, dropbox, email, employee retention, end-to-end encryption, eu commission, mandatory chat control, messenger, n64 cartridges, openai, private messaging, remote work, scanning reports, secure encryption, sherlocked, surveillance, telephony, third-party developers, trust, videoconferencing, virtual-first company
We're about to see a wave of big tech AI features "inspired" by third-party developers at a scale that makes the Sherlocking on Apple's platform seem like chump change. Plus, how Dropbox turned around their dev retention rates, and more.
-
529: This API is Not for You
August 2nd, 2023 | 39 mins 35 secs
api, app store, app store mafia, apple, capitalism, coder radio, contractors, developers, development podcast, drm, encryption, floss transition, geolocation, google web integrity api, lack of transparency, landmark geolocation tool, language models, linux distribution, nso group spyware, privacy concerns, riva networks, security concerns, smartcards, surveillance, tech industry, twitter ios app store, us internet, userdefaults, white house policy
Microsoft's dirty old API games, the new, even more restrictive rules Apple developers will now have to follow, and why Google's "Web Integrity API" seems gross.