1
00:00:00,000 --> 00:00:29,000
Welcome to today's episode of Solarcast!

2
00:00:29,000 --> 00:00:34,000
Today we have Matthias Judd with us from call.

3
00:00:34,000 --> 00:00:42,000
And call is a long-term running, mesh and peer-to-peer communication application.

4
00:00:42,000 --> 00:00:46,000
And it has quite an interesting start of its story.

5
00:00:46,000 --> 00:00:53,000
So with no further ado, let's dive in.

6
00:00:53,000 --> 00:00:56,000
Awesome!

7
00:00:56,000 --> 00:01:01,000
Hello Matthias!

8
00:01:01,000 --> 00:01:02,000
Hello, Santa!

9
00:01:02,000 --> 00:01:04,000
How are you?

10
00:01:04,000 --> 00:01:09,000
We've been chatting away a little bit already, but I didn't actually ask you this yet.

11
00:01:09,000 --> 00:01:11,000
Oh, I'm doing great.

12
00:01:11,000 --> 00:01:12,000
Thank you, Salah.

13
00:01:12,000 --> 00:01:17,000
I'm really happy to be here and talk to you, like always.

14
00:01:17,000 --> 00:01:18,000
Likewise!

15
00:01:19,000 --> 00:01:23,000
So, as mentioned, we've been chatting away quite a lot.

16
00:01:23,000 --> 00:01:30,000
And before we dive into exciting stuff that's been happening recently, and you've been traveling a lot,

17
00:01:30,000 --> 00:01:34,000
let's go back in time a little bit.

18
00:01:34,000 --> 00:01:44,000
Because you are part of a project, a big part of a call, which is qal.net.

19
00:01:45,000 --> 00:01:57,000
And it's one of the longest running offline-first mesh networking peer-to-peer communication apps in the scene.

20
00:01:57,000 --> 00:02:03,000
And it has a very interesting start of its story.

21
00:02:03,000 --> 00:02:09,000
So I'm curious if you could tell us a bit about why call started and when it started.

22
00:02:09,000 --> 00:02:12,000
We've talked a bit about this in the past, but...

23
00:02:12,000 --> 00:02:16,000
Yeah, I mean...

24
00:02:16,000 --> 00:02:26,000
I'm a contemporary artist and we always ask ourselves how could we interconnect and how could we communicate.

25
00:02:26,000 --> 00:02:36,000
And in 2011, when the spring was happening, these movements were often described as social media revolutions.

26
00:02:36,000 --> 00:02:39,000
But at the same time, the internet was switched off.

27
00:02:40,000 --> 00:02:46,000
So, to contradict this narrative and to explore our interconnection possibilities,

28
00:02:46,000 --> 00:02:55,000
and to check how we can build our own networks and how we can build truly participatory communication options we created call.

29
00:02:55,000 --> 00:03:03,000
And you're also mentioning something that I think is really interesting and some background story that I don't know if everyone knows about.

30
00:03:04,000 --> 00:03:12,000
But you're a contemporary artist and you have done a very interesting project.

31
00:03:12,000 --> 00:03:16,000
Was it called Spying Back on...

32
00:03:16,000 --> 00:03:20,000
Do you want to tell us a little bit about it?

33
00:03:20,000 --> 00:03:25,000
Yeah, it's called Can You Hear Me?

34
00:03:26,000 --> 00:03:27,000
So...

35
00:03:27,000 --> 00:03:34,000
Yeah, there is also a nice video recording about the entire story.

36
00:03:34,000 --> 00:03:37,000
So, how to talk back to NSA.

37
00:03:37,000 --> 00:03:49,000
But the story behind that is that we were invited as artists to the Swiss Embassy in 2014 to present our work.

38
00:03:50,000 --> 00:03:58,000
And the Swiss Embassy is in the center of the government district in Berlin.

39
00:03:58,000 --> 00:04:04,000
So, it's right next to the chancellery and to the German Parliament.

40
00:04:04,000 --> 00:04:13,000
And when you look a bit further next to the German Parliament, there is the US Embassy and behind that the British Embassy.

41
00:04:14,000 --> 00:04:23,000
And around this time we learned that from the roofs of this embassy, they were spying the entire government district.

42
00:04:23,000 --> 00:04:30,000
So, even the cell phone of the then-chancellor Angela Merkel was spied upon.

43
00:04:30,000 --> 00:04:38,000
And so, we suggested to the Swiss Embassy to actually also put antennas onto their roofs.

44
00:04:38,000 --> 00:04:47,000
And so, but it was our own makeshift cannon-tenas and we did not.

45
00:04:47,000 --> 00:04:58,000
Spying people, but we were kind of creating a participatory network in which everyone could freely send messages and talk to each other.

46
00:04:59,000 --> 00:05:08,000
And one of the really interesting things about spying on people and listening to these frequencies is that when you spied on people,

47
00:05:08,000 --> 00:05:11,000
then you also need to listen on what they are saying.

48
00:05:11,000 --> 00:05:14,000
So, that's why we called this installation.

49
00:05:14,000 --> 00:05:21,000
Can you hear me? And invited everyone to participate and people really did participate and over.

50
00:05:21,000 --> 00:05:27,000
I don't remember how many thousand messages were written over these networks.

51
00:05:28,000 --> 00:05:31,000
That's amazing and hilarious.

52
00:05:31,000 --> 00:05:38,000
I also can't imagine, I would have loved to see the conversation between you and the Swiss Embassy.

53
00:05:38,000 --> 00:05:43,000
Do you have them actually agree to do this project? It's brilliant.

54
00:05:44,000 --> 00:05:53,000
And maybe I'll put the links to the project in the show notes so whoever's curious can have a deeper look.

55
00:05:54,000 --> 00:06:01,000
And to not distract too much from the conversation that we initiated,

56
00:06:01,000 --> 00:06:07,000
you mentioned that calls started during the Arab Spring.

57
00:06:07,000 --> 00:06:14,000
I know that this has kind of had a long lasting impact on call as a project and also your engagement.

58
00:06:14,000 --> 00:06:20,000
Because one thing that call has done a lot of, which not all projects do, unfortunately,

59
00:06:20,000 --> 00:06:27,000
is actually engage with real communities and have these conversations about what's needed on the ground.

60
00:06:27,000 --> 00:06:32,000
Do you want to talk a little bit about that process for you?

61
00:06:32,000 --> 00:06:45,000
Yeah, I mean, as artists we mainly explore space and write experiments that everybody can participate in.

62
00:06:46,000 --> 00:06:56,000
And for years we had been using Wi-Fi Mesh Networks and always thought the setup of it is really complicated.

63
00:06:56,000 --> 00:07:05,000
And we always thought somebody should build a simple option to just interconnect and communicate.

64
00:07:05,000 --> 00:07:07,000
No, that's really needed.

65
00:07:07,000 --> 00:07:14,000
And as there was no project at the time, we then started it ourselves.

66
00:07:14,000 --> 00:07:25,000
And it created with the first off-grid zero-conf user devised by the Wi-Fi Mesh Communication Tool.

67
00:07:25,000 --> 00:07:36,000
And soon after releasing our first version, we got contacted by activists basically around the world who used call to communicate.

68
00:07:36,000 --> 00:07:41,000
And quite a few were joining our team and our development.

69
00:07:41,000 --> 00:07:46,000
And since then this project is ongoing.

70
00:07:46,000 --> 00:07:53,000
Yeah. And now it's been 2011. Was that when it started?

71
00:07:53,000 --> 00:07:57,000
Yeah, it's now 15 years.

72
00:07:57,000 --> 00:08:03,000
That's amazing. You can have a little 15-year celebration.

73
00:08:04,000 --> 00:08:22,000
But how I also remember that in one conversation we had at some point in the past, you had mentioned that you weren't quite like when you started this project, you didn't know that much about Mesh Communication Networks or technologies.

74
00:08:23,000 --> 00:08:29,000
And now it's been 15 years of being in this field and learning and also networking.

75
00:08:29,000 --> 00:08:34,000
And you have quite a vast network all over the place.

76
00:08:34,000 --> 00:08:39,000
I'm not going to mention any specific countries unless you bring them up yourself.

77
00:08:39,000 --> 00:08:42,000
So just a notice.

78
00:08:43,000 --> 00:08:50,000
But in that regard, like where...

79
00:08:50,000 --> 00:09:02,000
What do you see has been like a development from when you started in 2011 of the scene where as you mentioned there was no other project like this at the time.

80
00:09:02,000 --> 00:09:08,000
I know Briar was maybe starting them, but they didn't release until 2018.

81
00:09:08,000 --> 00:09:17,000
What's been the shift in the scene from 15 years ago until now?

82
00:09:19,000 --> 00:09:27,000
I think there have been many shifts and I think they're still...

83
00:09:27,000 --> 00:09:30,000
The development is not over.

84
00:09:30,000 --> 00:09:41,000
So our goal was always to have an end user device to actively communicate with others.

85
00:09:41,000 --> 00:09:48,000
And at that time, kind of Android was pretty new.

86
00:09:48,000 --> 00:09:53,000
I think it was 2.4 or something where we wrote the first version on it and so on.

87
00:09:53,000 --> 00:09:56,000
And also iPhone was not that.

88
00:09:56,000 --> 00:09:59,000
And it was all nowadays.

89
00:09:59,000 --> 00:10:17,000
So there was a specific mode that we were able to use, which was called IPSS mode, that was used by all the community networks to interconnect devices directly into a mesh network.

90
00:10:17,000 --> 00:10:19,000
It was a hack.

91
00:10:19,000 --> 00:10:20,000
It was a hack.

92
00:10:20,000 --> 00:10:33,000
One needs to say for the mobile platforms, because already then you did not have all the possibilities that you have on a laptop or on a normal computers.

93
00:10:33,000 --> 00:10:36,000
You don't have administrative access.

94
00:10:36,000 --> 00:10:57,000
And what we did is that we created a solution where people needed basically to route their Android device and to to jailbreak their iPhone in order to have access to the routing table and write our own kind of routing entries via the routing protocol.

95
00:10:58,000 --> 00:11:06,000
And also to kind of have access to the Wi-Fi driver and start up this IPSS mesh network on iPhone.

96
00:11:06,000 --> 00:11:10,000
We even used kind of private undocumented APIs.

97
00:11:10,000 --> 00:11:14,000
So it was really hacky.

98
00:11:14,000 --> 00:11:22,000
And this mode became basically not usable anymore, even not on the laptop.

99
00:11:22,000 --> 00:11:34,000
So the modern chips, although it is an official Wi-Fi standard, the modern chips, many of them claim to still support it, but they don't.

100
00:11:34,000 --> 00:11:36,000
The drivers are not there.

101
00:11:36,000 --> 00:11:43,000
Google kind of actively removed it from the kernel.

102
00:11:43,000 --> 00:12:01,000
So to be able to kind of do this hack, although they had been from the community, even patches to make this an official thing for that you don't need root access and so on.

103
00:12:01,000 --> 00:12:07,000
And also, what do you think was the motivation to remove it from Google?

104
00:12:08,000 --> 00:12:18,000
Well, there is the official talk is a battery saving and b security.

105
00:12:18,000 --> 00:12:24,000
I think both are valid things.

106
00:12:24,000 --> 00:12:36,000
But at the same time, there was also the talk in the community that the big providers kind of like the big mobile OS builders that are not there.

107
00:12:36,000 --> 00:12:57,000
They are the biggest vendor of phones and these operating systems were the mobile network providers, which means they had, if you were not supported by them, you would not sell your phones.

108
00:12:58,000 --> 00:13:04,000
And they were afraid that they could be less favored.

109
00:13:04,000 --> 00:13:06,000
At least this was the talk in the community.

110
00:13:06,000 --> 00:13:14,000
If there was an option to actually circumvent their minutes and data plans.

111
00:13:14,000 --> 00:13:25,000
And as a direct peer-to-peer connection, obviously, it's so convinced that they were maybe afraid of that.

112
00:13:26,000 --> 00:13:33,000
So I believe there is most probably some truth in that too.

113
00:13:33,000 --> 00:13:34,000
Yeah.

114
00:13:34,000 --> 00:13:37,000
Market incentives by big telecom companies.

115
00:13:37,000 --> 00:13:40,000
But sorry, I interrupted you as my question.

116
00:13:40,000 --> 00:13:48,000
You were mentioning that Google had removed the ability to access these APIs.

117
00:13:48,000 --> 00:13:54,000
And it's okay, we can fast forward as well.

118
00:13:54,000 --> 00:13:59,000
So we were on the topic of what's changed in the scene.

119
00:13:59,000 --> 00:14:13,000
And I think one thing that's changed and very clearly in that regards is that now the EU is becoming more vested into digital sovereignty.

120
00:14:13,000 --> 00:14:21,000
And that might also tie in with the sovereign phone operating systems and similar.

121
00:14:21,000 --> 00:14:30,000
And actually, I'm getting a little bit ahead of myself because I want to talk a little bit about insights and two challenges.

122
00:14:30,000 --> 00:14:40,000
But before we talk about that, just to map it out for whoever is listening and also for myself because this is not my expertise.

123
00:14:41,000 --> 00:14:49,000
What are the contemporary building blocks for an application like call?

124
00:14:49,000 --> 00:15:01,000
How do you get delay tolerant networking and meshing via Bluetooth and phone connections and applications to work?

125
00:15:01,000 --> 00:15:02,000
Yeah, exactly.

126
00:15:02,000 --> 00:15:05,000
I think this is also one of the changes that has happened.

127
00:15:05,000 --> 00:15:09,000
So we need to find a new way to interconnect.

128
00:15:09,000 --> 00:15:27,000
There is until today nothing that replaces this IBSS mode that have been Wi-Fi direct, which is cumbersome because you still need kind of a user, okay, to manual interaction to connect to someone.

129
00:15:27,000 --> 00:15:29,000
You cannot really match them.

130
00:15:30,000 --> 00:15:52,000
And there is now also kind of the so-called neighborhood of their networking, which is a new Wi-Fi standard but is not so widely supported and mostly on really expensive phones.

131
00:15:52,000 --> 00:15:56,000
So maybe this will become a possibility to directly interconnect.

132
00:15:56,000 --> 00:16:01,000
Our goal is to always use whatever there is to actually interconnect.

133
00:16:01,000 --> 00:16:21,000
So we are using, for example, LAN mode where you can interconnect when you are in the same local area network, like in the same Wi-Fi network, for example, this can be over your home router or when you are in a coffee

134
00:16:21,000 --> 00:16:28,000
or and connect to the Wi-Fi there or when you are in a wireless community network.

135
00:16:28,000 --> 00:16:35,000
And of course you can also open the hotspot on your mobile phone and let people directly connect via phone.

136
00:16:35,000 --> 00:16:47,000
We also use Bluetooth Low Energy, which also is an option to directly kind of interconnect to devices.

137
00:16:48,000 --> 00:16:55,000
And we also have an internet overlay possibility for that you can interconnect communities.

138
00:16:55,000 --> 00:17:04,000
The call app itself should really be installable for everyone on what every device you have.

139
00:17:04,000 --> 00:17:13,000
So we built it for the five big operating systems like Android, iOS, Linux, Windows, Mac OS.

140
00:17:13,000 --> 00:17:21,000
And there are also some command line binaries for that you can run it on headless devices such as servers or Raspberry Pi.

141
00:17:21,000 --> 00:17:29,000
And the core of the app is written in Rust, for whom is interested.

142
00:17:29,000 --> 00:17:36,000
This is one of the newer programming languages which was built for security and speed.

143
00:17:37,000 --> 00:17:43,000
And we have a beautiful cross-platform graphic user interface which is written in Flutter.

144
00:17:43,000 --> 00:17:48,000
That is also something that works on all of those devices.

145
00:17:48,000 --> 00:18:02,000
Maybe some building blocks on going further is when you are interconnected kind of directly to someone, it's nice you can talk to them.

146
00:18:02,000 --> 00:18:08,000
But we have a user discovery which means you see with whom you are actually connected.

147
00:18:08,000 --> 00:18:16,000
And we also have our own routing protocol that is making sure that when you are interconnected to someone,

148
00:18:16,000 --> 00:18:22,000
this someone is interconnected to someone else, you can talk to everyone somehow interconnected to someone.

149
00:18:22,000 --> 00:18:36,000
And also we have a chat messenger so where we have fully and to end encrypted chats,

150
00:18:36,000 --> 00:18:46,000
where you can have a one-to-one communication or a group chat communication with text chats, images, files and voice messages.

151
00:18:46,000 --> 00:18:54,000
And on top of that we also have a public channel where you can send messages to everyone in the network.

152
00:18:54,000 --> 00:19:01,000
It's amazing to hear this because this is so many projects in one in some ways,

153
00:19:01,000 --> 00:19:09,000
because there's all these peer-to-peer networks and local-first networks that are building parts of these puzzles.

154
00:19:10,000 --> 00:19:15,000
And I think that ties into a conversation that's been reoccurring here as well.

155
00:19:15,000 --> 00:19:25,000
And that's the aspect of you as call have built so many parts of this puzzle.

156
00:19:25,000 --> 00:19:32,000
How much are you building from scratch and how much are you interacting with pre-existing puzzle pieces?

157
00:19:32,000 --> 00:19:34,000
And how modular is this design?

158
00:19:34,000 --> 00:19:43,000
Because in conversations I've had with Breyer for example, there's been a call in Breyer often like grouped into the same kind of category, right?

159
00:19:43,000 --> 00:19:51,000
You're both very early on doing these kind of offline-first communication networks or applications.

160
00:19:51,000 --> 00:19:58,000
And with Bramble, their protocol, it's very intertwined.

161
00:19:59,000 --> 00:20:08,000
How modular is the design and how much can you take different pieces of the puzzle and connect it to other parts,

162
00:20:08,000 --> 00:20:16,000
like another kind of gossip in protocol maybe for networking or discovery or something like that?

163
00:20:17,000 --> 00:20:25,000
So what we try to do is to provide the best overall solution for users.

164
00:20:25,000 --> 00:20:36,000
As an off-the-grid messenger, this means of course many decisions on what you can do or how you do it actually.

165
00:20:37,000 --> 00:20:46,000
We try to build as little as possible ourselves, however we end up building quite a few things.

166
00:20:46,000 --> 00:20:56,000
For example, we have the transports in the background that we did not build ourselves most of them.

167
00:20:57,000 --> 00:21:09,000
We have for example, Lipier to Pier as a transport for the local area, network connection and also for Internet overlay.

168
00:21:09,000 --> 00:21:16,000
We built the Bluetooth Low Energy however because this did not exist completely ourselves.

169
00:21:16,000 --> 00:21:20,000
And this is very modular at the moment.

170
00:21:20,000 --> 00:21:28,000
So you can add new transports or we could add new transports in the future if we would love to.

171
00:21:28,000 --> 00:21:34,000
We also need to say we have rewritten everything after 2019.

172
00:21:34,000 --> 00:21:38,000
So it's now a day something completely different than what we had before.

173
00:21:39,000 --> 00:21:51,000
And we also wrote our own mesh networking protocol because we saw that we have very specific needs

174
00:21:51,000 --> 00:21:57,000
that kind of all the other mesh networking protocols that we used before did not have.

175
00:21:57,000 --> 00:22:05,000
And also that nowadays we have of course self-souvern cryptographic identity.

176
00:22:05,000 --> 00:22:11,000
So everybody, every user in the network has such a cryptographic identity.

177
00:22:11,000 --> 00:22:24,000
This is needed to identify yourself in the network to do the routing but also as a possibility to directly encrypt something for someone else.

178
00:22:24,000 --> 00:22:29,000
Self-souvern is the identity because there is no central registration.

179
00:22:29,000 --> 00:22:36,000
You build it yourself. Nobody else knows that this identity is you.

180
00:22:36,000 --> 00:22:42,000
So you then choose your username on top of it. You can also change your username.

181
00:22:42,000 --> 00:22:52,000
And you have this possibility to build up this persona or several personas for this communication space.

182
00:22:53,000 --> 00:23:00,000
Amazing. I'm sitting here thinking about a lot of different things I would like to ask.

183
00:23:00,000 --> 00:23:09,000
But to start off, if we wind back a little bit, we talked a bit about those challenges that exist.

184
00:23:09,000 --> 00:23:14,000
As you mentioned previously, some of these challenges.

185
00:23:15,000 --> 00:23:24,000
And is it so that each phone has a different Bluetooth connection pathway or how does it work?

186
00:23:24,000 --> 00:23:30,000
What makes it so challenging to do Bluetooth Low Energy connections?

187
00:23:30,000 --> 00:23:38,000
You mentioned something about the vendors being different. What is it actually?

188
00:23:39,000 --> 00:23:49,000
When doing Bluetooth Low Energy, you have many different variants on how to do it.

189
00:23:49,000 --> 00:23:52,000
You have many different protocol versions.

190
00:23:52,000 --> 00:23:58,000
And on top of that, you have different chip manufacturers.

191
00:23:58,000 --> 00:24:07,000
You have different firmware, which cannot do stuff.

192
00:24:07,000 --> 00:24:13,000
And you have then the mobile phone vendors, which allow you to do something or not.

193
00:24:13,000 --> 00:24:20,000
And all of this gives you a strange subset of what you can do.

194
00:24:20,000 --> 00:24:33,000
Sometimes also the mobile phones lie to you and claim to be able to do something, but then they can't.

195
00:24:33,000 --> 00:24:41,000
So this makes it a bit difficult. The stacks were really for a long time, very unstable.

196
00:24:41,000 --> 00:24:49,000
So it could be that the stack trashes and you need to reboot your phone in order to have access to Bluetooth again.

197
00:24:49,000 --> 00:24:54,000
There are many things that can go wrong in this regard.

198
00:24:54,000 --> 00:25:03,000
I would say we are there that we can master that.

199
00:25:03,000 --> 00:25:10,000
And that we will have a stable communication.

200
00:25:10,000 --> 00:25:26,000
So we are currently writing that. We have already an experimental thing, but soon, within the next month, we will have a very stable connection there.

201
00:25:26,000 --> 00:25:40,000
And then Bluetooth Low Energy also gives you a different possibility to advertise a device, to connect to a device, to send stuff to a device to read from a device.

202
00:25:40,000 --> 00:25:53,000
And all of this requires you to interact with this multiple possibilities, whatever you can do.

203
00:25:53,000 --> 00:26:07,000
And to put this into a nice protocol where you need to have a lot of reflection of what you need to do when something is going wrong or is not happening the way you want to.

204
00:26:07,000 --> 00:26:16,000
So I think we will see within the next month, the really stable implementation where you can well communicate.

205
00:26:16,000 --> 00:26:22,000
But it's then also difficult to say how far this connection will go.

206
00:26:23,000 --> 00:26:31,000
Also, this depends on your device class, which is often not that transparent to someone who buys it.

207
00:26:31,000 --> 00:26:50,000
And unfortunately, usually the more expensive your device is, the better it is also, which is also a bit problematic because we try, of course, to make it work for the really cheap devices.

208
00:26:50,000 --> 00:26:55,000
Yeah, that's often where it's the most needed, I would assume.

209
00:26:55,000 --> 00:27:01,000
But increasingly, it's becoming more and more needed all over the place.

210
00:27:01,000 --> 00:27:06,000
A authoritarian takeover of the West.

211
00:27:06,000 --> 00:27:17,000
But you talk a bit about these challenges, and you also mentioned that you're now, it sounds like you're finding a bit of a solution.

212
00:27:17,000 --> 00:27:25,000
And you'll soon have an experimental version coming out, or you have an experimental version already and a stable version in the making.

213
00:27:25,000 --> 00:27:34,000
How are you navigating this challenge of because Bluetooth low energy sounds really complex to take on?

214
00:27:35,000 --> 00:27:45,000
Well, call was for many years a grassroots open source project.

215
00:27:45,000 --> 00:27:51,000
And so kind of only with volunteers who produce code for it.

216
00:27:51,000 --> 00:27:57,000
And the requests from the communities through over the years.

217
00:27:57,000 --> 00:28:06,000
A lot. And in 2018, our Syrian partners and friends wanted to use call in the IDP and refugee camps in Syria.

218
00:28:06,000 --> 00:28:09,000
And we needed to change our development model.

219
00:28:09,000 --> 00:28:18,000
So we created an association, which is in charge of the source code and organizes the funding and supervisors also the development.

220
00:28:19,000 --> 00:28:38,000
And I would say this has made our development much more stable and predictable because now we can also invest a lot of time into specific solutions, which we are currently doing.

221
00:28:39,000 --> 00:28:47,000
Needless to say, all the development is still open source and it's on GitHub and everyone can download call for freely.

222
00:28:47,000 --> 00:28:51,000
And everyone is also invited to join our development.

223
00:28:51,000 --> 00:28:58,000
That's awesome. I'll get to that at the end. That's always the last part of how people connect with you.

224
00:28:58,000 --> 00:29:09,000
But in the meantime, what are the next steps? You mentioned the stable solution for Bluetooth low energy.

225
00:29:09,000 --> 00:29:15,000
And what in general are you working on? What's in the pipeline for you all?

226
00:29:16,000 --> 00:29:24,000
Well, we currently do a lot of testing for scalability.

227
00:29:24,000 --> 00:29:36,000
We want call to work provably great on several thousand users.

228
00:29:37,000 --> 00:29:41,000
We optimize our routing protocol for it.

229
00:29:41,000 --> 00:29:54,000
We optimize all the transports and everything and make everything as stable as possible.

230
00:29:54,000 --> 00:30:06,000
And also develop all the user features for the user interface that someone nowadays expects from such an application.

231
00:30:06,000 --> 00:30:14,000
And so that's what we are currently really occupied with.

232
00:30:14,000 --> 00:30:26,000
And it's really exciting actually to do all of that and see its scale and invest on that.

233
00:30:26,000 --> 00:30:31,000
Definitely. I can't imagine.

234
00:30:31,000 --> 00:30:43,000
I'm thinking here, since you're here and you have this long time engagement in the communities around offline first communication.

235
00:30:43,000 --> 00:30:49,000
What do you prefer calling it? Because I've heard a lot of people being a bit conflicted about the offline first communication.

236
00:30:49,000 --> 00:30:52,000
What do you prefer as a term?

237
00:30:52,000 --> 00:31:05,000
I would say we either call it Internet independent communication or off-degree communication offline first.

238
00:31:05,000 --> 00:31:15,000
It's also quite nice. Actually, the offline first term is coming from the IoT, so from the Internet of the Things.

239
00:31:15,000 --> 00:31:22,000
And it helped a lot because for years when talking about direct communication between devices, people always say,

240
00:31:22,000 --> 00:31:26,000
hey, well, I don't need it because we have the Internet and so on.

241
00:31:26,000 --> 00:31:36,000
And with this Internet of the Things, our entire factories basically need to, the devices need to talk to each other.

242
00:31:36,000 --> 00:31:43,000
They learned that because first everything was also connected to the Internet and they learned that when the Internet connection fails,

243
00:31:43,000 --> 00:31:47,000
it's really bad because actually nothing works anymore.

244
00:31:47,000 --> 00:32:00,000
So offline first also created a value for many more people and many more people are reflecting at the moment about solutions.

245
00:32:00,000 --> 00:32:02,000
Yeah.

246
00:32:02,000 --> 00:32:08,000
So a little add-on here.

247
00:32:08,000 --> 00:32:15,000
Matthias remembered in hindsight that there's another term that is often used here, which is delay tolerant networking.

248
00:32:15,000 --> 00:32:24,000
And it refers to a field in academia, but in general towards these networks that can function on their very low bandwidth,

249
00:32:24,000 --> 00:32:31,000
but also function when the network is experiencing delays, unlike traditional Internet as we know it.

250
00:32:31,000 --> 00:32:36,000
Awesome.

251
00:32:36,000 --> 00:32:52,000
Now, what I started asking before, and what I'm curious about, but I also don't want to put you on the spot, but I do want answers.

252
00:32:52,000 --> 00:32:57,000
So you can answer this as diplomatically as you'd like.

253
00:32:57,000 --> 00:33:07,000
But I'm really curious because there's been a lot of talk about mesh core, mesh task, there's also a reticulum out now.

254
00:33:07,000 --> 00:33:22,000
And I would love to hear your expert take on these different projects and the differences and how you would navigate engaging with them.

255
00:33:23,000 --> 00:33:27,000
Could that be okay?

256
00:33:27,000 --> 00:33:33,000
Yeah, of course. This is really a different domain, I would say.

257
00:33:33,000 --> 00:33:50,000
So when you talk about mesh task, mesh core, these are both projects that build up on radio protocol, which is called LORA.

258
00:33:50,000 --> 00:33:55,000
Long range.

259
00:33:55,000 --> 00:34:04,000
And this is actually a really great protocol because it can interconnect you over kilometers.

260
00:34:04,000 --> 00:34:10,000
And there is a really cheap hardware for that.

261
00:34:10,000 --> 00:34:19,000
So for basically, I don't know how it is nowadays, but a year ago you could buy for 20 bucks a communication device.

262
00:34:19,000 --> 00:34:27,000
And so the two projects you mentioned, they make use of these communication devices.

263
00:34:27,000 --> 00:34:41,000
So it's a hardware device and they interconnect it with a mobile app, over which you can talk to your hardware device.

264
00:34:42,000 --> 00:34:44,000
And you can send messages.

265
00:34:44,000 --> 00:34:54,000
So saying this is that the messages over LORA, the message size is really, really small.

266
00:34:54,000 --> 00:34:58,000
So it's about 140 bytes or something.

267
00:34:59,000 --> 00:35:07,000
And so it's great for all the Internet of the things stuff.

268
00:35:07,000 --> 00:35:18,000
So where you want to read, for example, the value of a little sensor somewhere.

269
00:35:18,000 --> 00:35:24,000
So what is the temperature nowadays or whatever?

270
00:35:25,000 --> 00:35:34,000
And it's not so great for otherwise if you think of, let's say, replacing Internet communication.

271
00:35:34,000 --> 00:35:39,000
Because there we are used to much higher data traffic.

272
00:35:39,000 --> 00:35:45,000
So I would say it's probably two different domains of communication.

273
00:35:46,000 --> 00:36:01,000
So what we are doing with call, for example, is really high traffic where you send longer messages and with LORA, you are rather using very small messages.

274
00:36:01,000 --> 00:36:05,000
So but you have a communication possibilities.

275
00:36:05,000 --> 00:36:10,000
In there, the models are a bit different.

276
00:36:10,000 --> 00:36:15,000
So with MeshTastic you have every device is the same.

277
00:36:15,000 --> 00:36:19,000
And you can send messages to every device around.

278
00:36:19,000 --> 00:36:29,000
However, the routing protocol, at least when we built up these networks here, we also tested it one and a half year ago.

279
00:36:30,000 --> 00:36:33,000
There was not really a routing protocol.

280
00:36:33,000 --> 00:36:39,000
It was just sending messages around and repeating them.

281
00:36:39,000 --> 00:36:42,000
So not giving you real feedback.

282
00:36:42,000 --> 00:36:47,000
So you didn't really knew whether the message arrived or not and so on.

283
00:36:47,000 --> 00:36:49,000
So it was very confusing.

284
00:36:49,000 --> 00:36:52,000
What were we saying then?

285
00:36:52,000 --> 00:36:53,000
MeshTastic.

286
00:36:53,000 --> 00:36:57,000
And MeshCore does it a bit better, but it has a different model.

287
00:36:57,000 --> 00:37:02,000
It has the model that you have kind of relays and you have clients.

288
00:37:02,000 --> 00:37:05,000
And a device cannot be both.

289
00:37:05,000 --> 00:37:21,000
So basically the idea is that the device you run around with is your client and then you need your client needs to send something to a relay and this relays then kind of send the messages around.

290
00:37:22,000 --> 00:37:29,000
So I think both models have their pros and cons with MeshCore.

291
00:37:29,000 --> 00:37:32,000
You know better whether a message arrived and so on.

292
00:37:32,000 --> 00:37:34,000
And it works generally better.

293
00:37:34,000 --> 00:37:43,000
But I think thinking of Mesh networks, I would say it would be great if a device could do both.

294
00:37:43,000 --> 00:37:46,000
So I think we will in the future see that.

295
00:37:47,000 --> 00:37:52,000
And of course many other protocols also try to get into this Lara stuff.

296
00:37:52,000 --> 00:37:55,000
You mentioned Reticulum for example.

297
00:37:55,000 --> 00:38:01,000
And then there is always the thing, yeah, well we could bridge everything together.

298
00:38:01,000 --> 00:38:04,000
I would say in theory yes.

299
00:38:04,000 --> 00:38:12,000
In practice you then only can send very small messages for that it makes sense.

300
00:38:12,000 --> 00:38:19,000
So I guess it would make sense just to bridge the Lara messages to the rest of the network.

301
00:38:19,000 --> 00:38:21,000
That's also what Lara is for.

302
00:38:21,000 --> 00:38:25,000
The idea is then that you take them up and you can use many projects for that.

303
00:38:25,000 --> 00:38:32,000
Not only those mentioned and send them over the Internet and so on and spread them further.

304
00:38:32,000 --> 00:38:41,000
It's a bit more problematic when you have high traffic content from the Internet.

305
00:38:41,000 --> 00:38:45,000
The Internet which was not optimized for this protocol.

306
00:38:45,000 --> 00:38:55,000
So you actually just created the segue for me because the next question I wanted to ask about is now that we're talking about projects.

307
00:38:55,000 --> 00:38:59,000
And you mentioned that there are a lot of other projects out there.

308
00:38:59,000 --> 00:39:04,000
Not only in this regard but if you want to mention in this regard as well.

309
00:39:04,000 --> 00:39:09,000
But what are projects that are out there that are kind of exciting to you right now.

310
00:39:09,000 --> 00:39:17,000
What are things that are happening that are inspiring from a community perspective or technological perspective.

311
00:39:17,000 --> 00:39:22,000
What got your eyes to open up so to speak.

312
00:39:22,000 --> 00:39:35,000
Well with call we are a messenger which is basically ready to communicate over community Wi-Fi networks.

313
00:39:35,000 --> 00:39:43,000
And especially those Wi-Fi networks we saw them appear in the early 2000s.

314
00:39:43,000 --> 00:39:48,000
Many of them maybe slept in here in Germany.

315
00:39:48,000 --> 00:39:52,000
We have a huge community which is still doing it.

316
00:39:52,000 --> 00:40:02,000
But nowadays we see a peer community Wi-Fi networks especially in the global south in numbers.

317
00:40:02,000 --> 00:40:09,000
And that's really exciting because it can solve the problem of the last mile.

318
00:40:09,000 --> 00:40:16,000
I'm also myself in this community mesh network community.

319
00:40:16,000 --> 00:40:20,000
So I'm trying to push that.

320
00:40:20,000 --> 00:40:30,000
We created a special interest group for community network infrastructure for example at the Internet Society that tries to support and interconnect.

321
00:40:30,000 --> 00:40:50,000
And I hope and I'm looking forward to see many more community networks around the world and people building up their own infrastructure and interconnecting themselves over various means and measures.

322
00:40:50,000 --> 00:40:53,000
Yeah definitely.

323
00:40:54,000 --> 00:41:06,000
So looking ahead into the future if there was a genie in the bottle that swooshed in and said you have three wishes.

324
00:41:06,000 --> 00:41:14,000
What would you like to solve for communication networks in your domain right now?

325
00:41:14,000 --> 00:41:24,000
What would be like the biggest hurdles the biggest challenges that are currently facing the scene?

326
00:41:24,000 --> 00:41:34,000
So one of the things I'm solving with other projects is for example the service discovery layer for community networks.

327
00:41:34,000 --> 00:41:40,000
And I hope we will see good solutions within this year.

328
00:41:40,000 --> 00:41:55,000
Another thing which is of course keeping us up at night for call net is that there should really be a good way to interconnect our end user devices with each other.

329
00:41:55,000 --> 00:42:18,000
I mean stable connections with high traffic throughput which is not which we don't do not need to access in a hacky way but is already built in into our end user devices and which is cross operating system and cross platform compatible.

330
00:42:19,000 --> 00:42:23,000
So I really hope that this will happen in the future.

331
00:42:23,000 --> 00:42:31,000
I don't have high hopes I need to say but I hope this will be finally be built.

332
00:42:31,000 --> 00:42:39,000
Yeah that's a complex one because as you mentioned before there's so many different factors to enable that.

333
00:42:40,000 --> 00:42:50,000
But yeah we just handed in an application to the EU a month ago where we could have had one possible solution for that.

334
00:42:50,000 --> 00:42:53,000
Shout out to the EU get us funded.

335
00:42:57,000 --> 00:42:58,000
I wish a good luck.

336
00:42:58,000 --> 00:42:59,000
Thank you very much.

337
00:43:00,000 --> 00:43:14,000
But you have let's dive back and circle back to the beginning of this conversation because before we started the recording we talked a little bit.

338
00:43:14,000 --> 00:43:21,000
You've been very active and you travel a lot almost every time we talk you're in a different place.

339
00:43:22,000 --> 00:43:30,000
Whether it's Switzerland, visiting family or back in Berlin and recently you were also in Prague.

340
00:43:30,000 --> 00:43:43,000
But what's going on and what's recent happenings that have have piqued your interests?

341
00:43:44,000 --> 00:43:51,000
Or what's something that you recently visited or what's something that's recent coming up soon?

342
00:43:51,000 --> 00:43:55,000
You mentioned there was a global gathering for example.

343
00:43:57,000 --> 00:44:12,000
Yeah I mean there are many many many events around the world where people are meeting that are interested in the future.

344
00:44:12,000 --> 00:44:31,000
But in building up their own communication, their community networks and reflecting on how we are communicating in our society and how we can build up tools.

345
00:44:32,000 --> 00:44:42,000
I could not really select one thing over in Arthur here.

346
00:44:42,000 --> 00:44:52,000
But if you will definitely be at a devep camp this summer so you can also meet me at global gathering.

347
00:44:53,000 --> 00:45:09,000
In autumn there are many small community based conferences and conferences where I'm involved with for example the battle match where all the mass networking people meet.

348
00:45:10,000 --> 00:45:25,000
Of course there are also many communities that don't have a technical focus but have a human interest in a community interest focus.

349
00:45:26,000 --> 00:45:53,000
And as a society interest focus one thing maybe is the collapse camp which will be happening in about one and a half month near Berlin where people are meeting who reflect on how to get into a more sustainable society and what to do and how to keep up

350
00:45:54,000 --> 00:45:57,000
if things are collapsing.

351
00:45:57,000 --> 00:46:13,000
And of course there are many people from a mercipitorial movement who like to communicate and build up their own communication structures for their movements.

352
00:46:14,000 --> 00:46:24,000
That's so amazing and I feel like it's a global kind of in Swedish it would be Sperdland.

353
00:46:24,000 --> 00:46:32,000
But I'm not sure what the English word would be but it's bubbling everywhere and things are popping up in a lot of different places.

354
00:46:33,000 --> 00:46:40,000
Local municipalities are picking up on the need for communication post collapse.

355
00:46:40,000 --> 00:46:53,000
So it's very exciting times in some ways and also tragic but perhaps both can be at the same time.

356
00:46:54,000 --> 00:47:05,000
But we're reaching the final stages of this conversation and I'm sure there will be many more to come.

357
00:47:05,000 --> 00:47:12,000
I'll see you at D-web camp at least soon and we just planned a little session we're going to host there together.

358
00:47:12,000 --> 00:47:14,000
So that's exciting.

359
00:47:15,000 --> 00:47:25,000
And how does one engage with call or actually before we go there because that's the final question.

360
00:47:25,000 --> 00:47:35,000
How is call funded because that's something I always ask because it's always a question for anyone who's doing open source.

361
00:47:35,000 --> 00:47:37,000
Oh my gosh.

362
00:47:37,000 --> 00:47:41,000
How do you navigate that as call?

363
00:47:42,000 --> 00:47:56,000
Yeah, as I already quickly told before we created an association that is looking for funding for such projects.

364
00:47:56,000 --> 00:48:08,000
And then also is running the development and is coordinating the development.

365
00:48:09,000 --> 00:48:26,000
So we would say we have everything from community participation to also developers who luckily can get paid for bigger contributions to the network.

366
00:48:26,000 --> 00:48:32,000
And this also lets us build exciting new features.

367
00:48:33,000 --> 00:48:44,000
So for example, we will right now build multiple communication channels and also an enhanced community manageable network safety and span protection option.

368
00:48:44,000 --> 00:48:52,000
This was for example one thing that was funded by a European founder called NLNet.

369
00:48:52,000 --> 00:48:54,000
Shout out to NLNet.

370
00:48:54,000 --> 00:49:01,000
Y'all have done a lot for the European open source communities but also globally.

371
00:49:01,000 --> 00:49:07,000
This podcast is being released on castopod which was also funded by NLNet actually.

372
00:49:07,000 --> 00:49:16,000
Which is federating with over activity pub which was also funded by NLNet and the European Union.

373
00:49:16,000 --> 00:49:24,000
So I gotta say the EU has stepped up their game and they're really starting to deliver.

374
00:49:24,000 --> 00:49:28,000
I hope they can keep it up because the momentum is on.

375
00:49:28,000 --> 00:49:39,000
And speaking of momentum to tap into this momentum and all the activities that are happening with call, how does one connect with you?

376
00:49:40,000 --> 00:49:45,000
Just saying that maybe then I should also mention some other founders.

377
00:49:45,000 --> 00:49:53,000
So we have multiple luckily and a big founder is also the open technology fund from the US or the National Democratic Institute.

378
00:49:53,000 --> 00:49:59,000
So and hopefully there will be more and we will see.

379
00:49:59,000 --> 00:50:21,000
So to connect to our project there is a website which is call.net so qaul.net and on this website you can find all the links to download our projects and to access the information how to connect.

380
00:50:22,000 --> 00:50:25,000
For example have a public matrix channel.

381
00:50:25,000 --> 00:50:42,000
We have a GitHub repository of course and we have various documentation tutorials, user documentation, developer documentation and we also have a web-laid account for UI translation.

382
00:50:43,000 --> 00:50:57,000
Because we have already many many different languages in which the user interface is in but there are always new possibilities for community to translate to UI.

383
00:50:57,000 --> 00:50:59,000
Absolutely.

384
00:50:59,000 --> 00:51:02,000
And thank you so much for joining today.

385
00:51:03,000 --> 00:51:09,000
I am very curious about the upcoming releases and I can't wait to try out call again.

386
00:51:09,000 --> 00:51:16,000
It's been a while since last time but I tried to try it out frequently and see what's up.

387
00:51:16,000 --> 00:51:20,000
So super excited for that.

388
00:51:20,000 --> 00:51:25,000
Let us know when the new releases and I can make a little shout out potentially.

389
00:51:25,000 --> 00:51:28,000
That would be really nice.

390
00:51:29,000 --> 00:51:37,000
And in general thank you for joining today and looking forward to seeing you in person again.

391
00:51:37,000 --> 00:51:42,000
Yeah thanks a lot for inviting me and I'm really looking forward to meeting you again.

392
00:51:42,000 --> 00:51:44,000
Likewise.

393
00:51:44,000 --> 00:51:46,000
Take tea later.

394
00:51:46,000 --> 00:51:47,000
Bye.