this repo has no description
atmosphereconf-vods.wisp.place/
1WEBVTT
2
31
400:00:00.000 --> 00:00:05.000
5Please say hi if you see them in the conference.
6
72
800:00:05.000 --> 00:00:07.000
9Thank you.
10
113
1200:00:30.000 --> 00:00:59.000
13Thank you.
14
154
1600:01:00.000 --> 00:01:01.000
17Hey, I'm Glenn.
18
195
2000:01:01.000 --> 00:01:07.960
21I'm going to talk to you about Oklog, which is a cooperative experiment that we've started
22
236
2400:01:07.960 --> 00:01:15.800
25in the Oakland Bay Area to build a community calendar, so a kind of commons for event data.
26
277
2800:01:15.800 --> 00:01:21.000
29And for a little context for approach, I have some scar tissue from crypto.
30
318
3200:01:21.000 --> 00:01:26.240
33And so one of the things that I really like this term is sewer socialism and I think Zoron
34
359
3600:01:26.240 --> 00:01:31.200
37in New York is one of the folks that exemplifies this, which is you win someone's trust over
38
3910
4000:01:31.200 --> 00:01:33.160
41through an outcome rather than ideologies.
42
4311
4400:01:33.160 --> 00:01:37.520
45So I think as we've gone through this project, even though I think about it as like digital
46
4712
4800:01:37.520 --> 00:01:39.960
49public media infrastructure, I try to really ground it in.
50
5113
5200:01:39.960 --> 00:01:44.640
53We are helping Oaklanders and other Bay Area folk find and go to local events, and we happen
54
5514
5600:01:44.640 --> 00:01:47.480
57to be using that protocol.
58
5915
6000:01:47.480 --> 00:01:52.040
61This all starts with the Oakland Review of Books, which is a new alt weekly that helped
62
6316
6400:01:52.040 --> 00:01:54.160
65us start last year.
66
6717
6800:01:54.160 --> 00:01:58.920
69And as part of the Oakland Review of Books, we started to publish a community calendar
70
7118
7200:01:58.920 --> 00:02:04.520
73of literary events, of cultural events, of protests, and it got some real great pickup.
74
7519
7600:02:04.520 --> 00:02:08.120
77And so one of the things I saw, this is Martina who does a lot of this work for us, and it
78
7920
8000:02:08.120 --> 00:02:11.360
81was a huge pain for her to do this work.
82
8321
8400:02:11.360 --> 00:02:14.880
85All of these events are fragmented all over the place, so getting all that data in one
86
8722
8800:02:14.880 --> 00:02:16.040
89place was a real pain.
90
9123
9200:02:16.040 --> 00:02:18.960
93And then the part that she actually really liked to do that was also really valuable
94
9524
9600:02:18.960 --> 00:02:25.400
97for our audience, which is that curation, the taste, telling people why this might be
98
9925
10000:02:25.400 --> 00:02:28.120
101an interesting thing to go to.
102
10326
10400:02:28.120 --> 00:02:31.240
105That was a tiny portion of the work that she actually got to do.
106
10727
10800:02:31.240 --> 00:02:38.800
109So we built some tools, Discord Bot and some other CMS tools just to help us manage this.
110
11128
11200:02:38.800 --> 00:02:42.640
113And one of the things we started realizing as we talked to lots of other people around
114
11529
11600:02:42.640 --> 00:02:47.920
117the Bay is that there's tons, there's dozens of folks that are doing this same thing, putting
118
11930
12000:02:47.920 --> 00:02:50.800
121together these kind of curated calendars.
122
12331
12400:02:50.800 --> 00:02:54.400
125And so what we decided to do is just get them all in one room.
126
12732
12800:02:54.400 --> 00:03:00.360
129So we invited all of the folks, the public media station, their neighborhood calendar
130
13133
13200:03:00.360 --> 00:03:05.480
133makers, there's lots of folks, alt-weeklys, newsrooms, all that are doing the same thing
134
13534
13600:03:05.480 --> 00:03:09.100
137of managing calendars and helping people find events.
138
13935
14000:03:09.100 --> 00:03:13.600
141So we got everybody together and we talked about how might we share practices, share
142
14336
14400:03:13.600 --> 00:03:16.260
145tools, share data, what would that look like.
146
14737
14800:03:16.260 --> 00:03:20.580
149And one thing that came out of that is everyone had the same sense of how do we do this thing
150
15138
15200:03:20.580 --> 00:03:21.580
153together.
154
15539
15600:03:21.580 --> 00:03:24.820
157We need a mega calendar but not dystopian.
158
15940
16000:03:24.820 --> 00:03:27.820
161And so we can just do things.
162
16341
16400:03:27.820 --> 00:03:33.620
165And so we started to talk about what it might look like to do this together on an open protocol.
166
16742
16800:03:33.620 --> 00:03:37.260
169So we kind of walked through, and I think these are some of the lessons of how we've
170
17143
17200:03:37.260 --> 00:03:42.020
173talked about this, is starting with something like on Instagram Reels where you have a venue
174
17544
17600:03:42.020 --> 00:03:44.340
177publishing their data in this form.
178
17945
18000:03:44.340 --> 00:03:49.380
181We've moved that out now into a database that each of our individual organizations are using,
182
18346
18400:03:49.380 --> 00:03:52.140
185whether it's Grist or Airtable or Excel, what have you.
186
18747
18800:03:52.140 --> 00:03:55.700
189And the next step is can we do this in a shared database.
190
19148
19200:03:55.700 --> 00:04:01.300
193Then here's the at-proto record of a calendar event.
194
19549
19600:04:01.300 --> 00:04:05.780
197And so one of the helpful points here is can you start wherever you get to your events,
198
19950
20000:04:05.780 --> 00:04:10.260
201much like wherever you get to your podcasts, and actually have that event data that venues
202
20351
20400:04:10.260 --> 00:04:14.660
205want out there anyways actually be available, and then there's a lot more we can start doing
206
20752
20800:04:14.660 --> 00:04:16.340
209with it.
210
21153
21200:04:16.340 --> 00:04:20.460
213And some of the advantages that were really attractive to the publishers is one is how
214
21554
21600:04:20.460 --> 00:04:22.440
217do we start sharing these workflow tools.
218
21955
22000:04:22.440 --> 00:04:24.260
221So we have our Discord bot.
222
22356
22400:04:24.260 --> 00:04:27.700
225There are others who have been building tools that are scraping venue sites or big event
226
22757
22800:04:27.700 --> 00:04:28.900
229sites.
230
23158
23200:04:28.900 --> 00:04:33.540
233And tons of folks were just how does the venue actually create their own event or submit
234
23559
23600:04:33.540 --> 00:04:40.220
237it to publishers, all going into the same lexicon, the same data that we can then use.
238
23960
24000:04:40.260 --> 00:04:44.500
241And on the other end, we start being able to do a lot more with that data now that we've
242
24361
24400:04:44.500 --> 00:04:47.500
245all collaborated on that shared element.
246
24762
24800:04:47.500 --> 00:04:50.260
249So one is we can still maintain editorial control.
250
25163
25200:04:50.260 --> 00:04:57.220
253We can still curate what is showing up in our individual publications and the commentary
254
25564
25600:04:57.220 --> 00:04:58.220
257they've put around it.
258
25965
26000:04:58.220 --> 00:04:59.420
261But we can also collaborate.
262
26366
26400:04:59.420 --> 00:05:05.820
265So if we add an event, then or add something, then Coyote or same page SF can use that same
266
26767
26800:05:05.820 --> 00:05:08.220
269data.
270
27168
27200:05:08.220 --> 00:05:12.180
273We can play with whatever format we like, whether it's in a post or in a calendar.
274
27569
27600:05:12.180 --> 00:05:16.540
277And really excited to start exploring more of the social functionality of can we see
278
27970
28000:05:16.540 --> 00:05:21.940
281what folks in your social network are interested in attending or going and not have it be specific
282
28371
28400:05:21.940 --> 00:05:23.380
285to Luma or EventBread or others.
286
28772
28800:05:23.380 --> 00:05:28.220
289I think it starts getting much more attractive from the user perspective.
290
29173
29200:05:28.220 --> 00:05:32.340
293So focusing a little bit more on the publisher control piece.
294
29574
29600:05:32.340 --> 00:05:35.580
297So we can still publish as we do in a newsletter.
298
29975
30000:05:35.580 --> 00:05:37.800
301But I think there's some other interesting examples here.
302
30376
30400:05:38.080 --> 00:05:41.600
305This middle one is from Roundabout at New Public.
306
30777
30800:05:41.600 --> 00:05:46.520
309And one of the things that they're really focused on is how do you moderate, have a
310
31178
31200:05:46.520 --> 00:05:49.600
313local neighborhood steward actually be able to moderate what goes on there.
314
31579
31600:05:49.600 --> 00:05:52.560
317I think they're using the same schema that we are.
318
31980
32000:05:52.560 --> 00:05:57.160
321I think there's going to be some really interesting ways to interoperate there.
322
32381
32400:05:57.160 --> 00:05:58.400
325Another really interesting example.
326
32782
32800:05:58.400 --> 00:06:01.960
329This is a group down in the Bay called the Relational Tech Project.
330
33183
33200:06:02.440 --> 00:06:08.640
333What they're doing is enabling neighborhood stewards to use AI tools to build their own
334
33584
33600:06:08.640 --> 00:06:11.120
337applications, including things like calendar apps.
338
33985
34000:06:11.120 --> 00:06:15.640
341And allow that to be much more situated and fit for what that community needs.
342
34386
34400:06:15.640 --> 00:06:20.640
345So the community of the outer sunset, for instance, in San Francisco, also wants to see
346
34787
34800:06:20.640 --> 00:06:24.200
349how the waves are, for instance, and incorporate things that make sense for that community.
350
35188
35200:06:26.400 --> 00:06:31.760
353So what's next from here is after our community calendar conference, we had not only a
354
35589
35600:06:31.800 --> 00:06:34.800
357bunch of these media organizations excited, we have a bunch of people who really want
358
35990
36000:06:34.800 --> 00:06:36.400
361to collaborate on the tech side.
362
36391
36400:06:36.400 --> 00:06:41.920
365And one in particular that's really interesting is KQED, which is our big local NPR station
366
36792
36800:06:41.920 --> 00:06:44.920
369that is really interested in anchoring and supporting this.
370
37193
37200:06:44.920 --> 00:06:48.440
373And so we're starting to go down the path of what might it look like to create a community
374
37594
37600:06:48.440 --> 00:06:54.160
377PDS for the Oakland Bay Area and specifically starting with events.
378
37995
38000:06:54.160 --> 00:06:59.760
381We're also starting to explore new local applications that actually take advantage of this collaboration.
382
38396
38400:06:59.760 --> 00:07:04.960
385So one organization is thinking about doing a pop up calendar that's kind of poorly suited
386
38797
38800:07:04.960 --> 00:07:07.640
389for existing things like Yelp and others.
390
39198
39200:07:07.640 --> 00:07:09.120
393So that's one thing we're looking into.
394
39599
39600:07:09.120 --> 00:07:13.120
397Others are things more like a TV guide ish, like what's happening right now in Oakland,
398
399100
40000:07:13.120 --> 00:07:14.120
401the Bay Area.
402
403101
40400:07:14.120 --> 00:07:17.760
405So I think there's going to be a lot of things that we can start building on top of this.
406
407102
40800:07:17.760 --> 00:07:22.680
409We're starting with the media curators that are already trusted, that already have audience,
410
411103
41200:07:22.680 --> 00:07:24.320
413that already have attention.
414
415104
41600:07:24.320 --> 00:07:28.560
417But from there, we're really excited to expand that participation and get more venues involved
418
419105
42000:07:28.560 --> 00:07:31.040
421and ultimately more residents.
422
423106
42400:07:31.040 --> 00:07:35.800
425And then we're also looking at beyond what this group can do together just on events,
426
427107
42800:07:35.800 --> 00:07:39.600
429but thinking more generally about what does the local community API look like?
430
431108
43200:07:39.600 --> 00:07:42.080
433What does all the public data that we could share?
434
435109
43600:07:42.080 --> 00:07:46.920
437I think there's lots of other use cases of things like buy nothing groups or lending
438
439110
44000:07:46.920 --> 00:07:52.960
441libraries or lots of things that exist on the margins of existing social platforms that
442
443111
44400:07:52.960 --> 00:07:57.800
445if we had more of a public spectrum for the open social web, we can see really different
446
447112
44800:07:57.800 --> 00:07:59.600
449applications develop.
450
451113
45200:07:59.600 --> 00:08:04.360
453Much like in the US, the kind of content you see on PBS or NPR is quite a bit different
454
455114
45600:08:04.360 --> 00:08:06.760
457than the way you see commercially.
458
459115
46000:08:06.760 --> 00:08:11.880
461And then ideally, this all feeds into, hey, if this works in Oakland and the Bay Area
462
463116
46400:08:11.880 --> 00:08:16.560
465and works for this NPR station or this Alt Weekly, how do we create this playbook that
466
467117
46800:08:16.560 --> 00:08:21.240
469allows other geographies to do similar things of building for themselves?
470
471118
47200:08:21.240 --> 00:08:23.640
473Yeah, so that's where we are.
474
475119
47600:08:23.640 --> 00:08:24.640
477It's all kind of emergent.
478
479120
48000:08:24.800 --> 00:08:29.200
481But I think what I really love about it is it feels like a great demonstration of what
482
483121
48400:08:29.200 --> 00:08:34.360
485I think is the promise of these applications on that protocol, which is really by collaborating
486
487122
48800:08:34.360 --> 00:08:38.360
489across organization, can we actually build something that has a better experience for
490
491123
49200:08:38.360 --> 00:08:39.360
493the users?
494
495124
49600:08:39.360 --> 00:08:43.640
497You don't need to know anything about how this is built other than everybody has collaborated
498
499125
50000:08:43.640 --> 00:08:44.640
501to make it better.
502
503126
50400:08:44.640 --> 00:08:45.640
505And that's what you see.
506
507127
50800:08:45.640 --> 00:08:49.200
509And so we can just do things together is the point.
510
511128
51200:08:49.200 --> 00:08:52.200
513So let's hope wrong.
514
515129
51600:08:54.840 --> 00:08:55.840
517Thank you so much.
518
519130
52000:08:55.840 --> 00:08:59.080
521What a great phrase to end on.
522
523131
52400:08:59.080 --> 00:09:00.640
525And you know what, folks?
526
527132
52800:09:00.640 --> 00:09:01.640
529We did it.
530
531133
53200:09:01.640 --> 00:09:02.640
533It's 4.40.
534
535134
53600:09:02.640 --> 00:09:07.680
537We ran four 10-minute lightning talks and we ended on time.
538
539135
54000:09:07.680 --> 00:09:12.440
541Breaking an atmosphere of tradition of running late all the time.
542
543136
54400:09:12.440 --> 00:09:14.080
545We did it, folks, and we did it together.
546
547137
54800:09:14.080 --> 00:09:15.080
549So thank you very much.
550