WEBVTT

1
00:00:00.000 --> 00:00:04.400
Now we're joined by Jair Miller.

2
00:00:04.400 --> 00:00:13.120
The future of open source is social and also Bluesky board member, but also a builder?

3
00:00:13.120 --> 00:00:14.120
Amazing.

4
00:00:14.120 --> 00:00:18.880
Take it away, Jair.

5
00:00:18.880 --> 00:00:21.880
Okay.

6
00:00:21.880 --> 00:00:25.240
Here we go.

7
00:00:25.240 --> 00:00:32.800
I had the good fortune, which is maybe apparent by the gray beard, to be around almost 30

8
00:00:32.800 --> 00:00:39.540
years ago and was invited by Tim O'Reilly to the first kind of gathering of people where

9
00:00:39.540 --> 00:00:46.920
he wanted to gather momentum behind this term called open source as something of its own

10
00:00:46.920 --> 00:00:49.280
meaning and definition.

11
00:00:49.280 --> 00:00:54.120
And the first open source conference is I fell in love with protocols and built Jabber

12
00:00:54.120 --> 00:00:58.040
XMPP back in the 90s, again, almost 30 years ago.

13
00:00:58.040 --> 00:01:00.840
Thank you.

14
00:01:00.840 --> 00:01:06.640
And so I've seen this whole arc of open source from the very beginning and how it's changed

15
00:01:06.640 --> 00:01:11.560
over the years and really what it's become with the kind of GitHub architecture where

16
00:01:11.560 --> 00:01:12.840
we're at today.

17
00:01:12.840 --> 00:01:15.880
And we're facing something new now.

18
00:01:15.880 --> 00:01:19.360
And I've been telling people code is tap water.

19
00:01:19.360 --> 00:01:20.620
It is that available.

20
00:01:20.620 --> 00:01:22.480
It is that common.

21
00:01:22.480 --> 00:01:24.560
Common is going to have access to it.

22
00:01:24.560 --> 00:01:32.840
So I am putting forth an idea that I had last fall that the future of open source is social.

23
00:01:32.840 --> 00:01:37.000
And of course, it's built on atproto.

24
00:01:37.000 --> 00:01:42.480
Today when you look at most open source activity, it is forks and clones.

25
00:01:42.480 --> 00:01:44.360
It goes through PRs and there's issues.

26
00:01:44.360 --> 00:01:46.240
It all goes to upstream.

27
00:01:46.240 --> 00:01:49.100
There's a maintainer, a group of maintainers.

28
00:01:49.100 --> 00:01:56.880
And while the ESR's original cathedral and bazaar, there's a lot of, you know, this looks

29
00:01:56.880 --> 00:02:01.800
like a cathedral again, even though there's just a lot of little cathedrals.

30
00:02:01.800 --> 00:02:08.640
And I believe that we can actually build on atproto something that is a true bazaar where

31
00:02:08.640 --> 00:02:13.080
the features and capabilities that people are developing and creating are moving between

32
00:02:13.080 --> 00:02:14.800
each other peer to peer.

33
00:02:14.800 --> 00:02:19.760
No gatekeepers, no upstream, no waiting for releases or merging.

34
00:02:19.760 --> 00:02:22.240
You just have capabilities that flow.

35
00:02:22.240 --> 00:02:23.920
Every repo becomes alive.

36
00:02:23.920 --> 00:02:26.420
Every copy of the repo becomes alive.

37
00:02:26.420 --> 00:02:27.540
And there's no upstream.

38
00:02:27.540 --> 00:02:30.140
It's all sideways.

39
00:02:30.140 --> 00:02:36.180
Today when you think about software development, people have features they want created.

40
00:02:36.180 --> 00:02:42.360
It often goes to like an architect or designer or, you know, a developer who is planning

41
00:02:42.360 --> 00:02:47.100
those features and creates maybe a requirements document or a scope of what they're going

42
00:02:47.100 --> 00:02:48.440
to implement.

43
00:02:48.440 --> 00:02:51.840
And then it goes into a developer who is actually like doing the engineering and the code and

44
00:02:51.840 --> 00:02:56.480
they output code and it gets distributed using Git.

45
00:02:56.480 --> 00:03:04.160
So I thought what if we've got these coding agents that make everything different?

46
00:03:04.160 --> 00:03:09.440
What if when people now are using coding agents directly, they don't have to be developers

47
00:03:09.440 --> 00:03:11.280
anymore?

48
00:03:11.320 --> 00:03:15.480
They create a new feature or capability on top of an open source project.

49
00:03:15.480 --> 00:03:20.760
They can just tell the coding agent package up and describe this feature, how you implemented

50
00:03:20.760 --> 00:03:21.760
it.

51
00:03:21.760 --> 00:03:24.220
Not the code, the description of the feature.

52
00:03:24.220 --> 00:03:27.720
This capability, that is what we share.

53
00:03:27.720 --> 00:03:32.040
That is the new form of open source peer to peer sharing.

54
00:03:32.040 --> 00:03:33.960
And that is what I called fit.

55
00:03:33.960 --> 00:03:38.560
Short for vitality, thinking that every code can be alive and be vital.

56
00:03:38.560 --> 00:03:39.820
Every repo.

57
00:03:39.820 --> 00:03:46.860
And so now any open source project with a coding agent can take a description of a capability

58
00:03:46.860 --> 00:03:50.100
or a feature and it can implement it for that person.

59
00:03:50.100 --> 00:03:52.920
You never need to pull a release or an upstream again.

60
00:03:52.920 --> 00:04:00.360
It becomes yours and it lives in your features and capabilities coming from other people.

61
00:04:00.360 --> 00:04:05.940
So the things that you can share socially, you can capture up skills, right?

62
00:04:05.940 --> 00:04:08.920
Today you can take those skills and share them and just post them.

63
00:04:08.920 --> 00:04:12.940
And they can come from your network, the people that you follow.

64
00:04:12.940 --> 00:04:20.040
And more importantly, you can take the capabilities, the structure change instructions, these improvements,

65
00:04:20.040 --> 00:04:24.740
and the people that you trust can actually publish these and you can go follow them and

66
00:04:24.740 --> 00:04:27.880
then you can post and share things back.

67
00:04:27.880 --> 00:04:33.360
The capabilities are what really grow a code base to adapt to your what things that you

68
00:04:33.360 --> 00:04:37.900
want and both and the skills teach agents new things and they both flow through the

69
00:04:37.900 --> 00:04:40.260
same trust network.

70
00:04:40.260 --> 00:04:43.020
It is a human and agent collaboration process.

71
00:04:43.020 --> 00:04:45.760
As a human, you're still logging into Bluesky.

72
00:04:45.760 --> 00:04:50.700
You still have to vet that to make sure that this is something safe for it to implement.

73
00:04:50.700 --> 00:04:55.060
And if you believe in it and you've used it, you can vouch for it too, right?

74
00:04:55.060 --> 00:05:00.580
And those signals go into the network very similar to likes and reposts.

75
00:05:00.580 --> 00:05:06.620
Your agent actually does the work to skim the network, to look at what is available

76
00:05:06.700 --> 00:05:12.340
and maybe look at what capabilities it thinks you might like and present to you things that

77
00:05:12.340 --> 00:05:15.260
it could implement on your behalf.

78
00:05:15.260 --> 00:05:18.480
You can tell it to remix those into your code base.

79
00:05:18.480 --> 00:05:22.580
Then you can package it up and say ship this new thing that I did back into the network

80
00:05:22.580 --> 00:05:27.460
and other agents out there using VIT will be able to see those capabilities.

81
00:05:27.460 --> 00:05:31.260
And you can tell it to learn a new skill, like go look for other people that I'm following

82
00:05:31.260 --> 00:05:35.220
and skills that they've published and go learn that skill.

83
00:05:35.220 --> 00:05:36.820
It's all built in that proto.

84
00:05:36.820 --> 00:05:41.620
These are just lexicons that live in your PDS with posts.

85
00:05:41.620 --> 00:05:43.340
It is your trust graph.

86
00:05:43.340 --> 00:05:47.060
It is your agents that work the network on your behalf.

87
00:05:47.060 --> 00:05:52.860
And everybody can build, share, build, share, build, share.

88
00:05:52.860 --> 00:05:54.140
That is VIT.

89
00:05:54.140 --> 00:05:58.380
And it is as easy to get started as NPM install, VIT.

90
00:05:58.380 --> 00:06:00.020
And you can VIT login.

91
00:06:00.020 --> 00:06:05.140
And you can go initialize any open source project to use VIT and use your coding agent.

92
00:06:05.140 --> 00:06:06.380
It will know how to do everything.

93
00:06:06.380 --> 00:06:08.180
It comes with a skill.

94
00:06:08.180 --> 00:06:13.340
And we can make the world of open source social in the future.

95
00:06:13.340 --> 00:06:15.340
That's it.

96
00:06:15.340 --> 00:06:21.300
So there's a whole other day to this conference now.

97
00:06:21.300 --> 00:06:22.500
You actually went super fast.

98
00:06:22.500 --> 00:06:24.140
We do have time for questions.

99
00:06:24.140 --> 00:06:27.740
How do we follow you?

100
00:06:27.740 --> 00:06:28.740
At Jeremy.

101
00:06:28.740 --> 00:06:29.740
I'm Bluesky.

102
00:06:29.740 --> 00:06:30.740
At Jeremy.com.

103
00:06:31.740 --> 00:06:34.740
I think it autocompletes if you do at JAR.

104
00:06:34.740 --> 00:06:35.740
At JAR.

105
00:06:35.740 --> 00:06:36.740
Yeah.

106
00:06:36.740 --> 00:06:38.740
This is super cool.

107
00:06:38.740 --> 00:06:44.460
And I just want to say from the, like, my history with Jabber, the first Jabber conferences

108
00:06:44.460 --> 00:06:50.020
we had, we had people show up from all over the world doing really interesting, bizarre

109
00:06:50.020 --> 00:06:52.180
things extending in interesting ways.

110
00:06:52.180 --> 00:06:54.860
And that is a permissionless protocol.

111
00:06:54.860 --> 00:06:58.980
And this conference is that same, like, vitality.

112
00:06:58.980 --> 00:07:03.180
It is that same nature of creatives building things because they don't need permission

113
00:07:03.180 --> 00:07:04.260
to build.

114
00:07:04.260 --> 00:07:05.260
And I'm here for it.

115
00:07:05.260 --> 00:07:06.340
This feels amazing.

116
00:07:06.340 --> 00:07:07.340
So thank you all.

117
00:07:07.340 --> 00:07:08.340
Awesome.

118
00:07:08.340 --> 00:07:09.340
Thank you, Jer.

119
00:07:09.340 --> 00:07:10.340
Stephen.

120
00:07:11.340 --> 00:07:12.340
Stephen.

121
00:07:35.340 --> 00:07:37.340
I would recommend extending.

122
00:07:37.340 --> 00:07:38.340
Extend.

123
00:07:38.340 --> 00:07:44.340
can extend. So you should see your...

124
00:07:44.340 --> 00:07:46.340
Perfect. Awesome. Yeah.

125
00:07:46.340 --> 00:07:53.340
Okay, cool.