WEBVTT 00:00.000 --> 00:00.560 Hi, everyone. 00:00.560 --> 00:03.960 This is going to be a quick demo of Pollen, the prototype browser extension 00:03.960 --> 00:05.120 we built for Bluesky. 00:05.120 --> 00:06.960 The idea behind Pollen is to showcase what's 00:06.960 --> 00:10.640 possible with our Nectar API, which is a new API 00:10.640 --> 00:14.120 we built that allows you to do image search across AT Protocol. 00:14.120 --> 00:17.640 So let's just jump in and show what's possible with Pollen and Nectar. 00:17.640 --> 00:19.360 So here, I have an example account that's 00:19.360 --> 00:21.880 going to be a news account for the purpose of this demo. 00:21.880 --> 00:25.600 And they're going to post a new news story that's developed. 00:25.600 --> 00:28.740 So in this case, the news story is the Chicago River being 00:28.740 --> 00:30.460 dyed green for St. Patrick's Day. 00:30.460 --> 00:32.040 And they're also going to attach an image, 00:32.040 --> 00:33.460 because that's what Pollen is all about 00:33.460 --> 00:36.380 and what Nectar is all about, being able to search images. 00:36.380 --> 00:38.940 So they're going to attach this image right here, 00:38.940 --> 00:42.220 a picture of the Chicago River being dyed green. 00:42.220 --> 00:43.620 And they're going to post that. 00:43.620 --> 00:46.260 And once that post is done, because we have the Pollen browser 00:46.260 --> 00:48.580 extension loaded, we're going to see this little claim 00:48.580 --> 00:50.060 button in the corner of the image. 00:50.060 --> 00:52.940 And so Pollen operates on claims, which 00:52.940 --> 00:54.060 could be any sort of information. 00:54.060 --> 00:55.580 In this case, it's going to be text. 00:55.580 --> 00:57.300 And so we can add some text that describes 00:57.300 --> 00:58.740 something about the image. 00:58.740 --> 01:00.900 And that claim is made on the image content itself, 01:00.900 --> 01:01.660 not on the post. 01:01.660 --> 01:03.820 And so this is what makes it different from just adding 01:03.820 --> 01:05.700 a comment or a repost. 01:05.700 --> 01:08.140 Here, still as the news, logged in as the news organization 01:08.140 --> 01:11.300 account, the news org is going to add a claim to the image 01:11.300 --> 01:13.180 that they took and they published. 01:13.180 --> 01:14.260 They could add geolocation. 01:14.260 --> 01:16.260 They could add like a timestamp, a caption, 01:16.260 --> 01:17.140 anything they want. 01:17.140 --> 01:17.900 In this case, they're just going 01:17.900 --> 01:19.660 to add some extra information here. 01:19.660 --> 01:21.660 Chicago River dyed for St. Patrick's Day, 01:21.660 --> 01:23.460 here's just where the photo was taken, 01:23.460 --> 01:25.340 and it was taken by us by News123. 01:25.340 --> 01:27.540 So they're going to submit this claim. 01:27.540 --> 01:29.100 And we see it immediately that's added. 01:29.100 --> 01:30.660 So this is all done through the extension. 01:30.660 --> 01:32.220 And when we click the claim, we get this drawer 01:32.220 --> 01:33.500 that shows us what happened. 01:33.500 --> 01:35.780 So it's already adding some context to the image. 01:35.780 --> 01:38.220 This claim is made, of course, in the news organization's 01:38.220 --> 01:38.720 PDS. 01:38.720 --> 01:40.340 We can take a look at it. 01:40.340 --> 01:43.180 And we'll see the text that was there. 01:43.180 --> 01:44.260 It's got this type. 01:44.260 --> 01:46.700 It's also got the perceptual hash of the actual image, 01:46.700 --> 01:48.200 which will become important later. 01:48.200 --> 01:50.140 And it links to the original post that was made. 01:50.140 --> 01:50.660 OK, great. 01:50.660 --> 01:51.940 And anyone can make these sorts of claims. 01:51.940 --> 01:53.140 In this case, the news organization 01:53.140 --> 01:55.700 is doing it to their own story to add context 01:55.700 --> 01:56.940 to their own images. 01:56.940 --> 02:01.940 Now we switch accounts here to Mallory, another demo account 02:01.940 --> 02:02.700 I've created. 02:02.700 --> 02:04.980 Mallory maybe saw this image from Facebook 02:04.980 --> 02:07.180 or from somewhere else in a different news organization. 02:07.180 --> 02:10.980 Maybe she wants to maliciously misinform people. 02:10.980 --> 02:12.780 In any case, she has her own idea about what 02:12.780 --> 02:14.060 this image describes. 02:14.060 --> 02:15.420 And so she's posting it. 02:15.420 --> 02:17.620 Toxic spill turns river neon green in London. 02:17.620 --> 02:19.620 So she's just making her own posts. 02:19.620 --> 02:21.980 And for her own post, she's going to attach her own image. 02:21.980 --> 02:24.340 This is a different image, different bytes. 02:24.340 --> 02:26.540 If you look closely, it's got more JPEG compression. 02:26.540 --> 02:28.300 It's a smaller image. 02:28.300 --> 02:31.020 Here, it's a little bit more compressed on the side. 02:31.020 --> 02:32.480 She got this from some other site. 02:32.480 --> 02:35.780 But it's the same image, same content, just different bytes. 02:35.780 --> 02:37.340 And now she's going to post that. 02:39.660 --> 02:42.180 And immediately, we see, thanks to the Pollen extension, 02:42.180 --> 02:43.580 oh, someone somewhere on the network 02:43.580 --> 02:44.980 has made a claim about this post. 02:44.980 --> 02:47.540 Let's click it and get some more context. 02:47.540 --> 02:50.060 And we see the claim from News123. 02:50.060 --> 02:52.780 Oh, this is the Chicago River dyed for St. Patrick's Day. 02:52.780 --> 02:55.180 It's a contradiction to what Mallory said. 02:55.180 --> 02:57.380 And so if we trust News123 more, we 02:57.380 --> 03:00.060 can get extra context and the false information 03:00.060 --> 03:02.620 can be disproved or at least better sourced. 03:02.620 --> 03:04.180 We can also see the image matching 03:04.180 --> 03:05.820 that's being done through the Nectar API 03:05.820 --> 03:06.740 by perceptual hashing. 03:06.740 --> 03:10.300 We see it's a 95% match on the original image. 03:10.300 --> 03:12.140 And if we want to see the original image, 03:12.140 --> 03:14.540 we just click this view claimed post. 03:14.540 --> 03:17.860 And we get taken to the original post 03:17.860 --> 03:18.940 that this claim was made on. 03:18.940 --> 03:22.460 If we click it here, it says claim on this post now. 03:22.460 --> 03:26.300 And as before, we can open this in a viewer, 03:26.300 --> 03:28.700 see when the claim was made, everything like that. 03:28.700 --> 03:31.380 So that's a super simple demo, of Pollen that 03:31.380 --> 03:33.220 allows image provenance, image claims, 03:33.220 --> 03:35.060 to move with the images themselves, 03:35.060 --> 03:37.020 even when they've been changed and altered. 03:37.020 --> 03:39.820 And this is what the Nectar API allows.