<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/942a5077d5f64bbf9a09e7b54ce8be10&quot; frameborder=&quot;0&quot; width=&quot;1152&quot; height=&quot;864&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>864</height><width>1152</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>864</thumbnail_height><thumbnail_width>1152</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/942a5077d5f64bbf9a09e7b54ce8be10-1689188170998.gif</thumbnail_url><duration>277.9000000000001</duration><title>CS+Community: Week 1 Lesson 2: Private Information </title><description>Welcome back programmers! In this video, we&apos;ll be going through the Scratch project and understanding what information should be kept private. I&apos;ll explain the TIP strategy, which stands for Title, Instructions, Purpose, and Play. We&apos;ll fix the project where Lionel shared private information and learn how to keep information safe. We&apos;ll explore the C strategy, which stands for Sprites, Events, and Explore, to make the project more private. I&apos;ll guide you through each sprite and show you how to modify the information. Your task is to make the other sprites more private too. Remember, keeping some information private is important. Good luck, programmers!</description></oembed>