Generative AI 101

Flock cameras may sit in your town, but the data they collect can travel far beyond it. Host Emily Laird follows the network behind automated license plate readers, from National Lookup and cross-agency sharing to hundreds of thousands of searches conducted by departments that local communities never directly approved. The episode examines cases in California, Illinois, and Wisconsin where settings, access controls, public records laws, and basic account security collided with the promise of local oversight. The reality check is simple: you can turn off a camera, but you cannot easily pull back data that has already entered the network.

❓HAVE YOU BEEN FLOCKED?
https://haveibeenflocked.com/

 

🎯 JOIN THE AI WEEKLY MEETUPS

https://www.uwstout.edu/ai-weekly-meetup

 

📩 EMAIL REMINDERS FOR THE MEETUPS

https://app.e2ma.net/app2/audience/signup/2101263/1779703/

 

💬 CONNECT WITH EMILY LAIRD ON LINKEDIN

http://www.linkedin.com/in/meet-emily-laird

In this episode, host Emily Laird examines who gets access to Flock's massive license plate database, what police can search, and what happens when that access is abused. From officers allegedly tracking ex-partners to warrantless searches, immigration lookups, and millions of vehicle records, the real issue is not whether the camera reads your plate correctly, but who gets to pull up the history afterward. Flock has audit logs, new safeguards, and a growing list of policy changes, but the documented misuse raises a harder question: who is actually watching the people doing the searching?

❓HAVE YOU BEEN FLOCKED?
https://haveibeenflocked.com/

 

🎯 JOIN THE AI WEEKLY MEETUPS

https://www.uwstout.edu/ai-weekly-meetup

 

📩 EMAIL REMINDERS FOR THE MEETUPS

https://app.e2ma.net/app2/audience/signup/2101263/1779703/

 

💬 CONNECT WITH EMILY LAIRD ON LINKEDIN

http://www.linkedin.com/in/meet-emily-laird

Flock Safety built an 8.3 billion dollar business on a simple idea: a photograph isn't very useful until software can search it. In this episode, host Emily Laird traces the path from one Atlanta neighborhood's break-ins to a sensor network across more than 5,000 communities, and explains what changes when a passing car becomes a database record with fields for plate, color, body type, and bumper stickers. She also walks through the partial plate match that got an innocent driver stopped by police, a case where the matching software did exactly what it was designed to do and the result was still wrong. The takeaway isn't that AI makes mistakes; it's that AI moves bad data and bad process faster than they could travel on their own.

 

🎯 JOIN THE AI WEEKLY MEETUPS

https://www.uwstout.edu/ai-weekly-meetup

 

📩 EMAIL REMINDERS FOR THE MEETUPS

https://app.e2ma.net/app2/audience/signup/2101263/1779703/

 

💬 CONNECT WITH EMILY LAIRD ON LINKEDIN

http://www.linkedin.com/in/meet-emily-laird

The most dangerous AI output isn't the ridiculous one; it's the polished answer with one critical error hiding in plain sight. In this episode, host Emily Laird puts generative AI evaluation on trial, from OpenAI's GDPval and Anthropic's TASTE study to the uncomfortable fact that automated AI judges still can't match experienced human reviewers. She breaks down metamorphic testing (a terrible name for a very useful idea) and explains how every caught mistake can become a test your systems have to survive. If you can no longer evaluate your own work, you haven't bought a productivity tool; you've built a dependency.

 

🎯 JOIN THE AI WEEKLY MEETUPS

https://www.uwstout.edu/ai-weekly-meetup

 

📩 EMAIL REMINDERS FOR THE MEETUPS

https://app.e2ma.net/app2/audience/signup/2101263/1779703/

 

💬 CONNECT WITH EMILY LAIRD ON LINKEDIN

http://www.linkedin.com/in/meet-emily-laird

Somebody got your company chatbot to break a rule, and now they are calling it a hack. Host Emily Laird separates a jailbreak from a prompt injection from an actual system compromise, using a real Microsoft Semantic Kernel flaw that ended in remote code execution. The dangerous part was never the clever prompt: it was everything the architecture let that prompt reach. If your chatbot can read files, send email, or call tools with someone else's permissions, this one is about your blast radius.

 

🎯 JOIN THE AI WEEKLY MEETUPS

https://www.uwstout.edu/ai-weekly-meetup

 

📩 EMAIL REMINDERS FOR THE MEETUPS

https://app.e2ma.net/app2/audience/signup/2101263/1779703/

 

💬 CONNECT WITH EMILY LAIRD ON LINKEDIN

http://www.linkedin.com/in/meet-emily-laird