WEBVTT - Tech News: Google I/O Highlights 0:00:04.400 --> 0:00:07.800 Welcome to tech Stuff, a production from I Heart Radio. 0:00:12.080 --> 0:00:14.960 Hey there, and welcome to tech Stuff. I'm your host, 0:00:15.080 --> 0:00:18.200 Jonathan Strickland. I'm an executive producer with iHeart Radio and 0:00:18.239 --> 0:00:21.560 I love all things tech. And this is the tech 0:00:21.680 --> 0:00:27.560 news for Thursday May one, and we're gonna concentrate a 0:00:27.560 --> 0:00:31.480 lot on Google for much of this episode. So, last year, 0:00:31.880 --> 0:00:36.239 Google canceled its annual io event for developers because of 0:00:36.280 --> 0:00:39.760 the pandemic. This year, the company held a virtual event 0:00:40.080 --> 0:00:42.920 in which presenters appeared on camera in front of a 0:00:42.960 --> 0:00:47.880 small audience of Googlers at the Google Plex in Mountain View, California. 0:00:48.159 --> 0:00:50.600 So we're going to go over some of the announcements 0:00:50.760 --> 0:00:55.120 from that event. And first up is Android twelve. There 0:00:55.160 --> 0:00:58.280 were a lot of updates to Android's operating system that 0:00:58.320 --> 0:01:01.760 we're announced and it is now public beta, but it 0:01:01.800 --> 0:01:04.760 will launch for real zs this fall. Some of the 0:01:04.880 --> 0:01:08.720 changes are to use your interface and they're largely cosmetic. 0:01:08.959 --> 0:01:12.200 For example, the color palette of the operating system is 0:01:12.200 --> 0:01:15.960 more customizable in Android twelve, and you can set the 0:01:15.959 --> 0:01:19.240 OS so that it will choose a color palette sourced 0:01:19.319 --> 0:01:23.200 from whatever image you choose as your background wallpaper. So 0:01:23.560 --> 0:01:25.679 on my phone. I've got a picture of my doggie 0:01:25.680 --> 0:01:30.120 Tibolt as my wallpaper, and presumably if I run Android 0:01:30.200 --> 0:01:33.959 twelve on my phone, then my notifications and stuff will 0:01:34.319 --> 0:01:37.960 have a color scheme that reflects the colors in that photo, 0:01:38.160 --> 0:01:40.880 which is kind of neat. There are tons of other 0:01:41.000 --> 0:01:44.840 updates besides the cosmetic, however. One is that there's a 0:01:44.880 --> 0:01:48.680 new privacy dashboard and Android twelve, which lets you see 0:01:48.680 --> 0:01:52.920 which apps are accessing your phone's various features and how 0:01:52.920 --> 0:01:56.000 frequently they do so, so you can check to see 0:01:56.480 --> 0:01:59.880 which apps are checking on the your location, you know, 0:02:00.040 --> 0:02:03.280 really frequently, or making use of your camera or your 0:02:03.280 --> 0:02:06.960 microphone or whatever. And you can also use the dashboard 0:02:07.000 --> 0:02:10.280 to revoke access to those features should you wish. So 0:02:10.320 --> 0:02:13.840 if you look and say, oh, this app is pinging 0:02:14.040 --> 0:02:17.480 my location, you know, twenty times a day, you can 0:02:17.480 --> 0:02:21.160 revoke access from that dashboard. It's Google's way to give 0:02:21.280 --> 0:02:25.120 users more insight into how their phones are harvesting data 0:02:25.400 --> 0:02:28.560 with these various apps. And don't get me wrong, Google 0:02:28.680 --> 0:02:32.200 does this as much or more than anyone else, but 0:02:32.280 --> 0:02:35.040 I do think this is a really nice feature. Other 0:02:35.160 --> 0:02:37.600 updates to the OS include a feature in which the 0:02:37.680 --> 0:02:41.400 clock on the screen saver screen will change size depending 0:02:41.480 --> 0:02:44.560 upon how many notifications you have, so as you clear 0:02:44.560 --> 0:02:47.880 out notifications, the clock gets bigger. That's a pretty handy 0:02:47.919 --> 0:02:50.880 way to see if you've got messages waiting on you 0:02:51.000 --> 0:02:54.560 on your phone. One of the cool technologies Google showed 0:02:54.560 --> 0:02:58.000 off at the event was projects star Line, which is 0:02:58.000 --> 0:03:01.920 a sort of three D video conferencing technology. In the 0:03:02.000 --> 0:03:05.080 version we saw at the event, there were examples of 0:03:05.160 --> 0:03:08.400 two people each sitting down in front of a large screen, 0:03:08.960 --> 0:03:11.880 and there wasn't really any indication as to how far 0:03:11.919 --> 0:03:15.160 apart these people were in real space. I mean, maybe 0:03:15.240 --> 0:03:17.960 they were across the country from each other, or maybe 0:03:18.040 --> 0:03:20.280 they were in different parts of the same building, but 0:03:20.360 --> 0:03:24.359 either way, the setup included depth sensing cameras that could 0:03:24.400 --> 0:03:27.639 capture light fields and then send that data over to 0:03:27.760 --> 0:03:30.960 the other screen while doing the same thing for the 0:03:31.000 --> 0:03:34.560 other side. So the effect was that the image you 0:03:34.600 --> 0:03:38.040 saw on screen appeared to have real depth to it, 0:03:38.480 --> 0:03:41.480 almost as if the person you're talking to on screen 0:03:41.920 --> 0:03:44.640 is actually sitting right in front of you in person. 0:03:45.120 --> 0:03:48.200 Which is pretty nifty stuff all by itself. But what 0:03:48.320 --> 0:03:52.480 I found particularly fascinating is that Google developed a compression 0:03:52.520 --> 0:03:55.240 algorithm that can handle this kind of application in the 0:03:55.280 --> 0:04:00.120 first place. High definition camera with depth sensing capabilities is 0:04:00.160 --> 0:04:03.880 going to generate a lot of data and transmitting that 0:04:03.960 --> 0:04:06.960 data in real time so that you can have a 0:04:07.080 --> 0:04:11.119 video chat with no perceptible lag time. That's a big challenge. 0:04:11.640 --> 0:04:14.120 Google says it developed a way to compress the data 0:04:14.160 --> 0:04:17.720 stream down to a factor of one hundred, so one 0:04:17.800 --> 0:04:23.119 hundred times smaller than the uncompressed size. The demonstration was cool. 0:04:23.360 --> 0:04:26.479 It was also prerecorded, I should add, but there's no 0:04:26.600 --> 0:04:29.080 word on whether Google is going to roll this out 0:04:29.120 --> 0:04:32.320 on any sort of meaningful scale, or if this will 0:04:32.360 --> 0:04:35.760 remain more as a demonstration of really neat technologies that 0:04:35.839 --> 0:04:39.279 might find their way into other applications in the future. 0:04:39.920 --> 0:04:43.599 Something that is rolling out is another collaborative work tool 0:04:43.800 --> 0:04:48.479 called smart Canvas. Google's demo showed team members working on 0:04:48.520 --> 0:04:51.920 a project together in real time on a Google platform 0:04:51.960 --> 0:04:56.119 that incorporates stuff like Google Docs and Google Sheets. Also 0:04:56.120 --> 0:04:58.599 allowed users to have a video chat going at the 0:04:58.640 --> 0:05:01.279 same time, so that people can talk with one another 0:05:01.320 --> 0:05:05.359 while collaborating in real time, and the tool incorporates some 0:05:05.520 --> 0:05:09.400 of Google's AI features as well to to help communicate 0:05:09.480 --> 0:05:13.039 clearly and avoid pitfalls. So the example they had in 0:05:13.080 --> 0:05:17.400 their video was using the word chairman in part of 0:05:17.400 --> 0:05:20.640 a presentation and the AI suggest changing it to chair 0:05:20.720 --> 0:05:26.480 person to avoid using a gender specific noun. So that 0:05:26.560 --> 0:05:29.800 was one example they gave. Google isn't a stranger to 0:05:29.880 --> 0:05:33.880 creating collaborative tools. I still remember the old Google Wave product, 0:05:34.160 --> 0:05:38.440 which was interesting but somewhat confusing way back in the day, 0:05:38.720 --> 0:05:40.880 and that would allow multiple people to work in the 0:05:40.920 --> 0:05:45.240 same virtual workspace simultaneously. At the time, it was kind 0:05:45.240 --> 0:05:48.200 of hard to imagine use cases for Google Wave beyond 0:05:48.240 --> 0:05:50.320 how I was using it, which was to build out 0:05:50.320 --> 0:05:54.159 a rundown for live shows. But smart Canvas has a 0:05:54.200 --> 0:05:57.840 more straightforward approach to collaboration that I think is pretty 0:05:57.920 --> 0:06:02.200 easy to understand. I wasn't super impressed with the interface 0:06:02.200 --> 0:06:05.240 when I saw it, but um, it was, you know, 0:06:05.320 --> 0:06:08.239 kind of stripped down. It wasn't like flashy or anything, 0:06:08.560 --> 0:06:11.799 so maybe simpler is better. I don't know. I'm also 0:06:12.000 --> 0:06:16.320 notoriously bad about using collaborative tools, so maybe I'm not 0:06:16.360 --> 0:06:19.640 the right one to comment on it. In addition, Google 0:06:19.680 --> 0:06:24.640 showed off an AI app called lamb DA that was odd. 0:06:24.920 --> 0:06:29.400 So this AI uses things like voice recognition, and natural 0:06:29.520 --> 0:06:34.960 language processing to interpret language. Then it generates responses and 0:06:35.080 --> 0:06:39.200 makes it very conversational, and moreover, it can generate responses 0:06:39.240 --> 0:06:43.280 as if it were something else, as opposed to you know, 0:06:43.360 --> 0:06:46.719 the Google Assistant, which is just this kind of ephemeral 0:06:47.160 --> 0:06:50.520 AI assistant. In the demos that Google showed off, they 0:06:50.560 --> 0:06:54.240 had Lambda answering questions as if Lambda were a paper 0:06:54.279 --> 0:06:58.560 airplane or the dwarf planet Pluto. And this makes me 0:06:58.600 --> 0:07:01.360 wonder if you had Lamb a pose as a chicken, 0:07:01.839 --> 0:07:05.800 would it finally explain why it crossed the road, Because 0:07:05.880 --> 0:07:10.360 a lot of people have been asking about that. It 0:07:10.440 --> 0:07:13.080 really was interesting to think of an app that could 0:07:13.080 --> 0:07:17.200 presumably put itself in the role of different things and 0:07:17.240 --> 0:07:20.960 then answer questions about it, including bits in which the 0:07:21.040 --> 0:07:24.400 AI would make the equivalent of small talk only as 0:07:24.440 --> 0:07:27.360 if the AI were you know, the dwarf planet Pluto 0:07:27.640 --> 0:07:30.560 or whatever it was neat and it really shows how 0:07:30.560 --> 0:07:34.200 far we've come with natural language processing and the ability 0:07:34.280 --> 0:07:38.880 to create AI programs that can seemingly converse fairly well. 0:07:39.040 --> 0:07:42.840 Though Google does say that this is far from perfect, 0:07:42.920 --> 0:07:46.320 it's still a pretty early build. It feels like another 0:07:46.320 --> 0:07:48.920 big step forward from the demo we saw a couple 0:07:48.960 --> 0:07:52.360 of years ago in which a Google assistant program made 0:07:52.400 --> 0:07:56.120 reservations on the behalf of a user, and it seemed 0:07:56.200 --> 0:07:59.000 to be an actual assistant, like it called up a 0:07:59.080 --> 0:08:02.720 restaurant to make reservations, and it was impossible to tell 0:08:03.120 --> 0:08:06.480 that it was an automated program. It sounded like it 0:08:06.560 --> 0:08:09.720 was a person, which is pretty nifty. Google also had 0:08:09.760 --> 0:08:13.480 some announcements about where os that's w E A R. 0:08:14.240 --> 0:08:17.520 Now it's just known as where, and didn't really talk 0:08:17.560 --> 0:08:21.040 about the Pixel Watch. In fact, Google also didn't talk 0:08:21.080 --> 0:08:25.280 about pixel phones. Really. There was a distinct lack of 0:08:25.320 --> 0:08:28.960 talk about hardware at all. They didn't mention anything about 0:08:29.000 --> 0:08:33.240 the rumored Google design chips that are codenamed Whitechapel. You know, 0:08:33.280 --> 0:08:36.640 like Apple, Google is apparently moving toward developing its own 0:08:36.800 --> 0:08:40.760 processors rather than relying on stuff that's made by other companies. 0:08:41.360 --> 0:08:43.640 None of that was brought up in the IO event, 0:08:43.679 --> 0:08:46.160 at least not as of the recording of this episode. 0:08:46.880 --> 0:08:49.640 Other stuff Google showed off included phone apps that are 0:08:50.040 --> 0:08:53.000 better at working with different skin tones for stuff like 0:08:53.040 --> 0:08:56.160 white balance that has traditionally been one of the big 0:08:56.200 --> 0:08:59.560 problems with Google photo apps. They simply didn't work as 0:08:59.640 --> 0:09:01.880 well for people of color, which is one of the 0:09:01.920 --> 0:09:04.080 many ways tech can turn out to have a bias 0:09:04.280 --> 0:09:08.480 against certain groups. And Google demonstrated a cool technology that 0:09:08.480 --> 0:09:11.760 could create an animation from two different photos of the 0:09:11.840 --> 0:09:15.520 same scene. So let's say you take a picture of 0:09:15.520 --> 0:09:19.120 someone who's standing in a particular pose and they're standing 0:09:19.160 --> 0:09:21.720 in front of like a landmark of some sort, and 0:09:21.760 --> 0:09:23.880 then they make a different pose and you take a 0:09:23.920 --> 0:09:28.520 second photo. With this new feature, Google could create interpretative 0:09:28.720 --> 0:09:32.640 frames between those two photos and create a short animation 0:09:32.960 --> 0:09:35.960 moving from one pose to the other. It's kind of 0:09:36.000 --> 0:09:39.080 creepy in a way because Google is literally creating new 0:09:39.120 --> 0:09:42.520 images based off the input of the two reference frames 0:09:42.760 --> 0:09:45.800 and then joining them together. So it's creepy and cool 0:09:46.000 --> 0:09:48.840 at the same time, kinda like most of my friends. 0:09:49.600 --> 0:09:52.520 And Google showed off updates two maps which will now 0:09:52.559 --> 0:09:56.440 include more relevant information as you move through areas. For example, 0:09:56.840 --> 0:09:59.520 the new maps will show you restaurants that happened to 0:09:59.559 --> 0:10:02.120 be open as you pass through town, so you're not 0:10:02.160 --> 0:10:05.679 getting a notification about, you know, Billy Bob's Best b 0:10:05.760 --> 0:10:09.040 b Q when Billy Bob's happens to be closed. That 0:10:09.040 --> 0:10:11.800 wouldn't do you much good, and maps will alert you 0:10:11.800 --> 0:10:15.040 when areas are getting busy and help you plan routes better. 0:10:15.720 --> 0:10:17.760 Maybe it's best to stay at the office for another 0:10:17.760 --> 0:10:20.200 twenty minutes and that will end up saving you forty 0:10:20.240 --> 0:10:23.600 five minutes of sitting in traffic, for example. And there 0:10:23.640 --> 0:10:26.000 are some cool a R features in Google Maps that 0:10:26.040 --> 0:10:28.760 they showed off, like virtual signs that can pop up 0:10:28.760 --> 0:10:31.920 in your view that tell you where certain landmarks are 0:10:31.960 --> 0:10:34.480 in relation to where you are. Oh and they will 0:10:34.480 --> 0:10:38.120 also help drivers pick the most eco friendly routes, routes 0:10:38.160 --> 0:10:40.800 that will have fewer stops and starts to them, or 0:10:40.840 --> 0:10:43.640 fewer locations where you know you might have to break 0:10:43.720 --> 0:10:46.600 suddenly or drive up a steep hill, which is kind 0:10:46.640 --> 0:10:48.760 of a neat feature. So it may not be the 0:10:48.840 --> 0:10:52.280 fastest route to your destination, but it would be at least, 0:10:52.280 --> 0:10:55.359 in theory, a route that would generate fewer carbon emissions 0:10:55.400 --> 0:10:57.719 because of the nature of the drive, which sounds kind 0:10:57.720 --> 0:10:59.320 of chill to me. Oh and if you have a 0:10:59.360 --> 0:11:02.520 BM double you you might be able to unlock and 0:11:02.600 --> 0:11:06.280 start your car using your phone as a digital key. 0:11:06.400 --> 0:11:10.679 Android twelve will support digital key operations over u w 0:11:10.880 --> 0:11:14.960 B and NFC protocols. But so far, BMW is the 0:11:15.000 --> 0:11:19.480 only automaker confirmed to offer compatible car models with this technology. 0:11:19.880 --> 0:11:22.679 It is another example of how smart devices are replacing 0:11:23.280 --> 0:11:26.640 various other things we typically use, from payments to car keys. 0:11:27.400 --> 0:11:31.480 But in non Google news, the cryptocurrency world has seen 0:11:31.520 --> 0:11:35.240 a dramatic drop in value over the last two weeks. 0:11:35.240 --> 0:11:39.160 Since May twelve, the overall market, which includes cryptocurrencies like 0:11:39.240 --> 0:11:43.160 Bitcoin and ethereum, as well as doge coin, the joke 0:11:43.280 --> 0:11:46.600 that really got out of hand, and numerous others, the 0:11:46.679 --> 0:11:49.600 market has dropped in value to the tune around eight 0:11:49.720 --> 0:11:54.280 hundred billion dollars as I record this. Many cryptocurrencies are 0:11:54.320 --> 0:11:57.600 experiencing a brief climate value as I record this episode, 0:11:57.640 --> 0:12:00.160 So it could be that we just saw ma of 0:12:00.240 --> 0:12:03.120 drop and now the market is recovering. Or it could 0:12:03.200 --> 0:12:05.480 be that what I'm seeing is just a blip and 0:12:05.520 --> 0:12:08.359 we're going to have a bear market in which valuation 0:12:08.400 --> 0:12:11.520 will continue to drop further. No one is really sure, 0:12:11.880 --> 0:12:13.800 and the big part of that is that the value 0:12:13.880 --> 0:12:17.640 of many of these currencies largely depends on whether people 0:12:17.679 --> 0:12:22.720 are buying into them or selling them off. Buying cryptocurrencies 0:12:22.760 --> 0:12:28.199 decreases the supply, at least for most cryptocurrencies, which in turn, 0:12:28.320 --> 0:12:31.760 you know, drives up the value of the remaining cryptocurrencies 0:12:31.760 --> 0:12:36.240 that are in circulation. Selling off cryptocurrencies to convert them 0:12:36.240 --> 0:12:41.359 into cash, that increases the supply and thus the value decreases. 0:12:41.760 --> 0:12:44.360 Now it's a bit more complicated than that, but those 0:12:44.400 --> 0:12:46.959 are the basics. So does this mean you should rush 0:12:47.000 --> 0:12:50.079 in and buy up cryptocurrencies while they are still relatively 0:12:50.160 --> 0:12:53.040 low or at least, you know, lower than they were 0:12:53.400 --> 0:12:57.200 two weeks ago. I have no idea. We might see 0:12:57.200 --> 0:13:00.000 the market plunge again. Heck, this could be the big 0:13:00.040 --> 0:13:04.200 getting of a relatively long bear market where values dropped 0:13:04.360 --> 0:13:08.600 week after week before they recover. Or we might already 0:13:08.640 --> 0:13:11.640 be in another upswing. It's really hard to tell, and 0:13:11.720 --> 0:13:14.880 chances are anyone who is giving you hard and firm 0:13:14.920 --> 0:13:18.800 advice has a vested interest in the outcome. So if 0:13:18.800 --> 0:13:21.920 someone you know is stressing that, hey, now is the 0:13:21.920 --> 0:13:25.080 time to buy, a good follow up question for that 0:13:25.120 --> 0:13:28.280 person is how much money do you have wrapped up 0:13:28.280 --> 0:13:32.720 in cryptocurrency? Because it could be that the person telling 0:13:32.760 --> 0:13:35.840 you to buy is desperate to see those values go 0:13:35.960 --> 0:13:38.320 up so that they can recapture some of the wealth 0:13:38.480 --> 0:13:42.880 they had been accumulating prior to the market downturn. Just 0:13:43.040 --> 0:13:45.880 be careful, is all I'm saying. I mentioned in the 0:13:45.880 --> 0:13:48.840 Google Stories about how Google's photo app is getting tweaks 0:13:48.880 --> 0:13:52.240 to address negative biases and the app has with regard 0:13:52.280 --> 0:13:56.000 to people of color. Twitter is doing something similar. Twitter 0:13:56.080 --> 0:13:59.840 had been using a tool to auto crop photos, using 0:14:00.120 --> 0:14:02.760 I to identify the subject of a photograph and then 0:14:02.800 --> 0:14:05.200 to crop the image so that it would better fit 0:14:05.280 --> 0:14:09.720 within Twitter feeds, particularly on mobile devices. But in use 0:14:09.800 --> 0:14:12.520 it was shown to work best with pictures of white people, 0:14:13.000 --> 0:14:16.160 and it would crop those images fairly effectively, but it 0:14:16.240 --> 0:14:20.400 worked much less well for people who weren't white. Not great, 0:14:20.800 --> 0:14:24.480 So now Twitter is abandoning the auto crop feature. The 0:14:24.520 --> 0:14:28.440 company tested the algorithm for gender and race biases and 0:14:28.520 --> 0:14:32.120 concluded that in fact, the algorithm does have problems. Now 0:14:32.120 --> 0:14:34.920 Twitter's mobile app will show full images in the Twitter 0:14:35.000 --> 0:14:38.120 feed and will only crop photos if the pictures are 0:14:38.120 --> 0:14:40.920 just too tall or too wide to fit on screen, 0:14:41.400 --> 0:14:43.760 and then only doing that in a pretty standard way 0:14:43.840 --> 0:14:47.000 as opposed to trying to auto identify the subject of 0:14:47.040 --> 0:14:50.680 the photo. Once again we see how bias can work 0:14:50.680 --> 0:14:53.920 its way into code, even unintentionally, and I think Twitter 0:14:54.000 --> 0:14:57.280 made the right move here. Perhaps in the future the 0:14:57.280 --> 0:15:00.200 company will have an improved auto cropping tool that won't 0:15:00.240 --> 0:15:03.240 show the same tendencies towards bias, But in the meantime, 0:15:03.400 --> 0:15:05.840 it's better to have nothing than to have a tool 0:15:05.880 --> 0:15:09.000 that works really well for one demographic and not so 0:15:09.040 --> 0:15:13.520 well for all the others. Finally, byte Dance, the parent 0:15:13.600 --> 0:15:17.120 company that owns TikTok, has announced a change in leadership 0:15:17.440 --> 0:15:21.720 that I find interesting and fairly refreshing. Co founder jeng 0:15:21.840 --> 0:15:25.360 Yi Ming says he will step down as CEO to 0:15:25.480 --> 0:15:28.880 take on some other role in the company. So in 0:15:28.920 --> 0:15:31.480 a message to employees, he explained that he felt his 0:15:31.520 --> 0:15:36.920 strengths were in areas outside of managing people, including ideation 0:15:37.240 --> 0:15:39.960 and data analysis and that kind of thing. He also 0:15:40.000 --> 0:15:42.320 said he's not a very social person and that he 0:15:42.360 --> 0:15:45.040 felt that byte Dance needed a leader who would be 0:15:45.080 --> 0:15:47.600 able to take the company to new places. So, in 0:15:47.600 --> 0:15:49.840 other words, he was saying, I might have been the 0:15:49.920 --> 0:15:52.520 right person to get things moving to where they are, 0:15:52.720 --> 0:15:55.280 but I'm not the right person to evolve the company 0:15:55.320 --> 0:15:59.520 from here. Co founder Liang Rubo will take over as 0:15:59.640 --> 0:16:01.960 ce oh, and I've seen this sort of thing happen 0:16:02.000 --> 0:16:04.920 with a few companies here in the States. There are 0:16:05.000 --> 0:16:09.280 some entrepreneurs who absolutely love the experience of launching a 0:16:09.320 --> 0:16:12.920 new company and then having it grow to a certain point, 0:16:13.600 --> 0:16:17.640 but beyond that they tend to lose interest. Their strengths 0:16:17.720 --> 0:16:20.560 lie in those early phases of getting a company off 0:16:20.600 --> 0:16:24.480 the ground and establishing a presence. But once these companies 0:16:24.520 --> 0:16:28.120 reach a certain scale, the entrepreneurs find it less interesting 0:16:28.400 --> 0:16:31.760 or outside of their wheelhouse of skills, and so they 0:16:31.800 --> 0:16:34.760 look for ways to move into other roles. And I 0:16:34.800 --> 0:16:37.920 think that's a healthy thing. Not everyone is made to 0:16:38.080 --> 0:16:41.760 grow into these leadership positions while the company itself is 0:16:41.800 --> 0:16:46.720 also scaling up, and a transparent transition of leadership tends 0:16:46.800 --> 0:16:49.560 to be a sign of a healthy company as opposed 0:16:49.600 --> 0:16:52.400 to some of the revolving door situations we've seen with 0:16:52.440 --> 0:16:55.840 companies in the past. Analysts don't expect this change in 0:16:55.920 --> 0:17:00.200 leadership to have massive consequences for daily operations of either 0:17:00.280 --> 0:17:04.440 Byte Dance or TikTok. And that's it. That's the tech 0:17:04.520 --> 0:17:08.560 news for Thursday, May one. I hope all of you 0:17:08.600 --> 0:17:11.280 are well. If you have any suggestions for topics I 0:17:11.280 --> 0:17:14.119 should cover in tech stuff, reach out to me on Twitter. 0:17:14.320 --> 0:17:16.920 The handle for the show is tech Stuff hs W 0:17:17.640 --> 0:17:26.840 and I'll talk to you again really soon. Tech Stuff 0:17:26.920 --> 0:17:30.120 is an I Heart Radio production. For more podcasts from 0:17:30.119 --> 0:17:33.880 my heart Radio, visit the i heart Radio app, Apple Podcasts, 0:17:34.000 --> 0:17:36.000 or wherever you listen to your favorite shows.