1
00:00:00,020 --> 00:00:04,300
it's catastrophic. It's completely incompatible with the way that F-Droid works. So it's,

2
00:00:05,160 --> 00:00:07,100
you know, it's more or less an extinction event for us.

3
00:00:08,920 --> 00:00:14,300
It is an absolute honor to have Mark from F-Droid join me on Techlore Talks. Today,

4
00:00:14,460 --> 00:00:19,480
we talk about some super important things that impact the entire digital rights ecosystem that

5
00:00:19,480 --> 00:00:25,100
are being fought right now as we speak. We talk about F-Droid versus the Google Play Store and the

6
00:00:25,200 --> 00:00:29,980
key differences for what that means to you. We talk about Google's new policies and how this can

7
00:00:30,000 --> 00:00:34,920
FDroid and other open source app stores on the market. We talk about how you can take action

8
00:00:35,200 --> 00:00:39,900
against Google Play service changes. We talk about the implications of centralized app distribution

9
00:00:40,200 --> 00:00:44,980
and also some speculation on why Google might be even doing this in the first place. If you care

10
00:00:45,010 --> 00:00:48,920
about stepping up to big tech and doing the right thing and fighting for open source projects,

11
00:00:49,240 --> 00:00:55,199
this is the podcast for you. We recorded this on November 6th, so please keep that context in mind

12
00:00:55,220 --> 00:00:57,200
for when we're talking about current events.

13
00:00:57,540 --> 00:01:01,140
Okay. I want to welcome Mark from F-Droid on the team.

14
00:01:01,190 --> 00:01:04,239
Do you want to say a few words about yourself and what you work on?

15
00:01:05,160 --> 00:01:06,640
Hi, my name is Mark Perdemo.

16
00:01:07,260 --> 00:01:12,600
I've been a software developer for a very long time, 30-odd years.

17
00:01:13,420 --> 00:01:17,900
I've been developing mobile applications in both the major ecosystems

18
00:01:18,070 --> 00:01:22,820
for the Apple iPhone and for Google Android devices ever since 2008.

19
00:01:23,660 --> 00:01:33,000
And I've worked in a variety of roles and a variety of apps, some very big name brand apps, some very small indie apps, a lot of free and open source applications.

20
00:01:34,020 --> 00:01:44,280
And since last year, I've been a member of the board of directors for the F-Droid project, which is a free and open source mobile app distribution environment.

21
00:01:45,440 --> 00:01:55,020
So how did you go from working, it sounds like more on the mainstream side of things, and then kind of pivoting over to this open source, still somewhat niche app store?

22
00:01:56,200 --> 00:01:58,180
Yeah, well, I mean, it's been a long journey.

23
00:01:59,180 --> 00:02:13,660
Earlier in my career as actually a server side Java developer, and when mobile phones first came out, both when the Android preview was released and then the iPhone app store first went into beta,

24
00:02:14,040 --> 00:02:18,760
very fascinated with the whole you know idea of that and I developed along with

25
00:02:19,480 --> 00:02:23,740
another developer an app called Stanza which was the first electronic book

26
00:02:23,860 --> 00:02:28,720
reader for the iPhone that wound up being very popular so we formed sort of a

27
00:02:28,880 --> 00:02:34,220
startup around that and we worked on that for a while and yeah that was really

28
00:02:34,250 --> 00:02:38,459
sort of my entrance into the environment and ever since you know I first started I

29
00:02:38,560 --> 00:02:45,080
I just loved the idea of being able to have this magical little rectangle that you could put software on.

30
00:02:45,680 --> 00:02:48,960
Anyone could develop software for and anyone could distribute software through.

31
00:02:50,300 --> 00:02:56,680
And then as sort of my career progressed, you know, I joined some larger companies and then I went back to doing smaller projects,

32
00:02:57,200 --> 00:02:58,920
doing some consulting and contracting.

33
00:03:00,280 --> 00:03:07,300
I just came back again and again to how the current constrained distribution environment,

34
00:03:07,970 --> 00:03:14,800
both for the iPhone and the main distribution channel on Android devices, which is the Google

35
00:03:14,850 --> 00:03:20,940
Play Store, were very constraining and very stifling. And that was really what sort of sparked

36
00:03:21,030 --> 00:03:29,019
my interest in like, can there be another way? What is the potential avenue for having

37
00:03:29,120 --> 00:03:33,240
sort of a really free and open app development and distribution environment.

38
00:03:33,930 --> 00:03:36,800
And that was really how I sort of started getting interested in it.

39
00:03:37,490 --> 00:03:44,980
And then, you know, over the years, I sort of developed some ideas around creating my own project,

40
00:03:45,820 --> 00:03:50,280
which would facilitate distribution, the development distribution of these applications.

41
00:03:51,300 --> 00:03:53,540
That's the project I'm still working on called the AppFair project.

42
00:03:54,570 --> 00:03:57,100
And one of those channels would be going through the F-Droid project.

43
00:03:57,260 --> 00:04:02,480
So I started collaborating with them in sort of a lightweight manner at first, and then

44
00:04:02,510 --> 00:04:10,220
got more and more interested in the project until I got to a point where I felt like it

45
00:04:10,320 --> 00:04:18,340
would be beneficial to the project if they sort of had the advantage of kind of an outside

46
00:04:18,579 --> 00:04:23,979
voice like mine who is generally more familiar with industry and things like that, and less

47
00:04:24,000 --> 00:04:29,020
someone who came really from the ground up from inside the free and open source software movement.

48
00:04:29,840 --> 00:04:32,680
And just for timelines, when did you join the board?

49
00:04:33,560 --> 00:04:40,860
The board, I believe I applied late last year and then the election I think was in February of this

50
00:04:40,880 --> 00:04:48,939
year, February or March. Got it. Okay. And then, so, you know, it sounds like you almost have an iOS

51
00:04:49,460 --> 00:04:54,780
background at first. Did I get that correct? Yeah, actually I simultaneously started developing for

52
00:04:54,920 --> 00:05:02,480
both platforms, but it was really the iOS side that kind of took off. And as a small development group,

53
00:05:02,620 --> 00:05:07,380
it's really hard to have more than one platform you're supporting. So yeah, that was sort of how

54
00:05:07,380 --> 00:05:13,660
I kind of fell into the iOS side initially. But actually, I originally started developing for

55
00:05:13,900 --> 00:05:17,740
Android. It was just that that side did not advance as quickly as the iOS side.

56
00:05:18,720 --> 00:05:22,340
Got it. And so if someone's listening to this right now and they're going, okay, you know,

57
00:05:22,470 --> 00:05:26,900
maybe I use an iPhone, maybe I just use a regular Pixel that I buy from Google or a Samsung device,

58
00:05:27,270 --> 00:05:32,180
et cetera, how do you kind of break down this overall concept of app stores? Because,

59
00:05:34,540 --> 00:05:38,420
yeah, people seem to get it on desktop, but not fully on mobile devices yet. So how do you

60
00:05:38,490 --> 00:05:45,339
normally approach this conversation? Yeah. So do you mean, you know, what the app store provides

61
00:05:45,340 --> 00:05:48,520
and how the infrastructure works?

62
00:05:49,580 --> 00:05:52,500
Just expectations over, I guess, software installation

63
00:05:52,900 --> 00:05:53,940
between mobile and desktop.

64
00:05:54,760 --> 00:05:55,160
Right, right.

65
00:05:55,680 --> 00:05:58,840
Yeah, so historically, with desktop computers,

66
00:05:59,760 --> 00:06:01,280
there was no app store.

67
00:06:01,340 --> 00:06:03,800
You would download an application to your desktop

68
00:06:04,000 --> 00:06:05,480
and you would typically run it

69
00:06:06,100 --> 00:06:07,820
sort of in the bad old days of,

70
00:06:08,020 --> 00:06:10,360
or good old days of computing.

71
00:06:10,460 --> 00:06:12,280
And you still do in a lot of environments.

72
00:06:14,000 --> 00:06:19,100
know, there have always been hazards around that. You know, there has always

73
00:06:19,300 --> 00:06:24,080
been malware that can be distributed, viruses and things like that. But for the

74
00:06:24,140 --> 00:06:28,580
most part, it's, you know, worked great. There's a thriving desktop world. Mobile

75
00:06:28,780 --> 00:06:34,460
devices really since they first started, started bundling with them these app

76
00:06:34,680 --> 00:06:43,960
stores, these app marketplaces, and they provide a lot of useful features. They

77
00:06:44,680 --> 00:06:48,500
information about the app. You can you know look at screenshots, you can often

78
00:06:48,580 --> 00:06:52,800
read reviews and things like that. And then you have a sort of an easy way to

79
00:06:53,100 --> 00:06:58,500
obtain the app, you know just by clicking a get button or something. And then if it

80
00:06:58,560 --> 00:07:03,140
is a paid app then you know there's built-in infrastructure being able to

81
00:07:03,260 --> 00:07:08,360
handle that. And then critically it also supports being able to update existing

82
00:07:08,380 --> 00:07:14,720
applications. You know applications always have bugs that need to be fixed. They very often have

83
00:07:15,000 --> 00:07:19,760
security defects that need to be addressed. They have you know new features and improvements that

84
00:07:19,880 --> 00:07:25,080
they want to roll out. And in the days of the desktop you would sort of need to know like oh

85
00:07:25,090 --> 00:07:30,000
you need to go and check to see if there's an update online or even before that you would need

86
00:07:30,000 --> 00:07:35,319
to get a new CD with a new version of say Microsoft Word or something. And app stores really help

87
00:07:35,900 --> 00:07:40,860
remove the friction from that process. You know, you can often configure them to just automatically

88
00:07:41,160 --> 00:07:47,440
install updates for you, which comes with its own set of perils, unfortunately, but that's a really

89
00:07:47,520 --> 00:07:54,240
low friction way to sort of always be up to date with your applications. And it's, you know, it's a

90
00:07:54,320 --> 00:08:00,660
really popular, you know, way to manage it. You know, I don't believe it should be the only way,

91
00:08:01,280 --> 00:08:04,080
But on the iPhone, it is the only way to do it.

92
00:08:04,860 --> 00:08:07,320
And on Android, it is definitely the path of least resistance,

93
00:08:07,990 --> 00:08:11,080
either to use first-party app store, which is typically

94
00:08:11,130 --> 00:08:14,160
the Google Play Store, or maybe the Samsung App Store,

95
00:08:15,080 --> 00:08:19,480
or to use a free and open source alternative like FDroid.

96
00:08:20,880 --> 00:08:24,860
And then can you give me the fundamental differences

97
00:08:25,050 --> 00:08:27,140
between something like FDroid and the Google Play Store?

98
00:08:27,250 --> 00:08:28,660
If somebody hasn't heard of FDroid before,

99
00:08:29,240 --> 00:08:30,460
how do you break that down?

100
00:08:31,600 --> 00:08:36,539
The big, the major difference is that F-Droid is a non-commercial app store.

101
00:08:37,289 --> 00:08:39,340
You wouldn't even really call it a store because we don't sell anything.

102
00:08:40,270 --> 00:08:44,480
There is no, there's no registration, you don't have to sign up, you don't have to

103
00:08:44,590 --> 00:08:47,660
enter your email address, there's no personal information you provide. It's

104
00:08:47,740 --> 00:08:53,200
really just, you know, an app that you can use to browse vetted free and open

105
00:08:53,400 --> 00:08:58,099
source applications. You know, if you sort of look at, you know, look at it in the

106
00:08:58,120 --> 00:09:02,760
simplest way, an App Store is really just an app that installs apps. You know,

107
00:09:02,920 --> 00:09:05,440
unless you browse and search and update and things like that, but it's really just

108
00:09:05,680 --> 00:09:11,960
an app that installs other applications. And so F-Droid essentially takes out the

109
00:09:12,260 --> 00:09:17,560
commercial aspect of the App Store and puts in a requirement that all

110
00:09:17,820 --> 00:09:23,859
applications be free and open source, meaning that 100% of the source code

111
00:09:23,880 --> 00:09:30,980
needed to build that application is publicly available. And that's really the

112
00:09:31,120 --> 00:09:37,760
vetting that we provide, is that we offer trustworthiness because the app

113
00:09:37,960 --> 00:09:42,740
can't sort of hide what it's doing. It can't hide any of its features or

114
00:09:42,940 --> 00:09:47,939
misfeatures. And so people really like to use F-Droid for a lot of different

115
00:09:47,960 --> 00:09:55,400
reasons, but one major reason is for concern over privacy and surveillance. You're pretty much

116
00:09:55,640 --> 00:10:02,440
guaranteed that none of these apps are embedding any of these sort of telemetry spyware kind of

117
00:10:02,600 --> 00:10:07,300
libraries that are tracking what you're doing and then uploading this information to third-party

118
00:10:07,360 --> 00:10:12,699
data brokers and things like that. You really know you can trust what you get from an app store like

119
00:10:12,720 --> 00:10:18,560
F-Droid. And the fact that we don't have any commercial incentive to support things like

120
00:10:19,210 --> 00:10:25,940
in-app purchases, upselling advertisements, and things like that means that when you see that an

121
00:10:26,080 --> 00:10:31,940
app is advertising itself as free, it really is free. It's not some marketing ploy to trick you

122
00:10:32,220 --> 00:10:37,220
into upselling or a free-to-play game where you have to buy gems or something like that.

123
00:10:38,700 --> 00:10:59,740
Yeah, and one of the things that might come to mind, and this is still an ongoing debate because we hear it from Apple, we hear it from Google, is that they are keeping us safe and secure because they are going through and any app developer, let's say they want to install malware on their audience's devices, they're going to upload a malicious version of the app.

124
00:10:59,900 --> 00:11:04,360
and naturally Apple and Google, if they're doing their job correctly, will catch that and prevent it from happening.

125
00:11:04,480 --> 00:11:08,000
So what kind of safety assurances can you offer through Afterroid?

126
00:11:08,000 --> 00:11:11,080
And how's your approach different from that?

127
00:11:11,940 --> 00:11:13,580
Yeah, well, it is fundamentally different.

128
00:11:14,660 --> 00:11:17,180
You know, on one hand, we have it a lot easier.

129
00:11:17,760 --> 00:11:22,220
Because we have a prerequisite in the Afterroid inclusion policies that it be 100% open source,

130
00:11:22,700 --> 00:11:26,280
it's pretty easy to spot when an app is trying to do something bad.

131
00:11:27,120 --> 00:11:32,880
either undermining the security of your operating system or acting as scamware or something,

132
00:11:33,160 --> 00:11:34,700
like trying to intercept your banking credentials,

133
00:11:36,120 --> 00:11:40,860
or just clandestinely surveilling you and uploading that information without your consent.

134
00:11:41,800 --> 00:11:45,800
It's a lot easier for us to identify those scenarios than it is for Apple and Google,

135
00:11:45,920 --> 00:11:50,680
which don't have any requirement that you reveal the source code of the applications you're uploading.

136
00:11:52,660 --> 00:12:04,340
And furthermore, even the developers who are creating the applications that they submit to the Apple App Store and the Google Play Store, they themselves don't always know everything that's going into their applications.

137
00:12:04,400 --> 00:12:07,860
because very often they're using third-party libraries

138
00:12:08,160 --> 00:12:10,660
that purport to be providing useful services.

139
00:12:11,190 --> 00:12:15,420
And really what it's doing is it's gathering telemetry on the user,

140
00:12:15,600 --> 00:12:18,460
uploading it to this third-party service

141
00:12:18,880 --> 00:12:21,500
so that they can profit from it either immediately

142
00:12:21,760 --> 00:12:23,740
or down the road when they can resell your data.

143
00:12:25,639 --> 00:12:29,199
So we really have it a lot easier than they do

144
00:12:29,220 --> 00:12:35,680
in order to provide these sort of security assurances, these security guarantees.

145
00:12:37,920 --> 00:12:44,240
But furthermore, we're not conflicted in what we identify as being malware versus not malware.

146
00:12:45,560 --> 00:12:52,420
There are plenty of people that identify any form of advertising, any form of telemetry as a sort of malware.

147
00:12:53,080 --> 00:12:58,900
But obviously, these are the things that these first-party platform providers themselves profit from.

148
00:13:00,500 --> 00:13:05,940
or, you know, say in-app purchases where you have this sort of casino mentality where, you know, you

149
00:13:06,920 --> 00:13:11,560
pay to win, you pay to get, you know, gems, you, you know, these, these gotcha games and things like

150
00:13:11,760 --> 00:13:17,020
that, you know, they're all skimming a cut off of it. So they are disincentivized from even

151
00:13:17,380 --> 00:13:23,240
considering that that might be a form of malware, whereas we don't have that commercial, you know,

152
00:13:23,400 --> 00:13:29,300
conflict of interest. And so we can just across the board say that these things are not suitable

153
00:13:29,640 --> 00:13:35,060
for our particular marketplace. I appreciate how you bring up this inconsistency of the term malware.

154
00:13:36,000 --> 00:13:40,440
I was in Cyprus just a couple weeks ago with the ad filtering dev summit, where you have some

155
00:13:40,660 --> 00:13:45,940
engineers, you know, from Brave, DuckDuckGo, Firefox, etc. And they're building really cool

156
00:13:46,140 --> 00:13:52,439
stuff. And one of the researchers talked about these insane workarounds that Meta and other social

157
00:13:52,460 --> 00:13:58,580
media apps use to pretty much track users across different applications. And it uses

158
00:14:00,140 --> 00:14:06,580
the Facebook Pixel. So it's so interesting because I don't think most people would consider the

159
00:14:06,770 --> 00:14:11,020
Facebook app on their phone malware because they're like, well, this is a useful tool. But just because

160
00:14:11,160 --> 00:14:15,640
something's a useful tool doesn't mean it doesn't function in a way that's quite exploitive to the

161
00:14:15,810 --> 00:14:21,460
user. And I just wanted to kind of shout that out as a good talking point that you brought up.

162
00:14:22,100 --> 00:14:39,120
Absolutely. I mean, that is a fundamental concern. These services that they provide, these applications, and like in the example of Facebook, this social network that lets you connect with the world, both your friends and local community, as well as broader interest groups.

163
00:14:40,240 --> 00:14:47,620
Those are really valuable and it's pretty amazing that it's provided to you for free in the sense that you do not need to pay any cash directly to them.

164
00:14:48,900 --> 00:14:51,600
But, you know, obviously that is being paid for somehow.

165
00:14:51,760 --> 00:14:52,820
How is that being paid for?

166
00:14:53,240 --> 00:15:02,520
It is gathering as much information and whatever is possible on you so that they can build a profile and advertise to you, have targeted advertisements.

167
00:15:03,080 --> 00:15:13,700
I mean, that's really the one and only reason why they're able to make these, you know, and I will say amazing services, be able to be offered at, you know, zero cost to people.

168
00:15:14,960 --> 00:15:19,440
And that is a fundamental conflict that the creators of these applications have.

169
00:15:19,670 --> 00:15:27,480
And it's a fundamental dilemma for anyone who wants to provide an app store and app distribution service

170
00:15:29,360 --> 00:15:33,340
that authentically works in support of the user's interests

171
00:15:33,390 --> 00:15:38,940
and not in the interests of the individuals or corporations who are developing and creating the application.

172
00:15:40,400 --> 00:15:42,160
Yeah, it's a good stance to take.

173
00:15:42,200 --> 00:15:52,740
And one thing, one little minor question I had, you brought up how some developers don't even know that they are including third-party libraries that include malicious things in them.

174
00:15:52,860 --> 00:15:54,200
And I've heard this quite a lot, actually.

175
00:15:54,800 --> 00:15:59,220
Do you have a ballpark educated guess on what percentage that is?

176
00:15:59,500 --> 00:16:01,480
Like, do you think it's 50-50?

177
00:16:01,820 --> 00:16:03,600
Do you think most developers don't know?

178
00:16:03,880 --> 00:16:05,400
Just kind of prying a little bit there.

179
00:16:06,240 --> 00:16:18,440
Well, so whether or not they are fully aware of every dependency that they have, I'd say the larger the application gets, the less likely they are to really understand every nook and cranny and corner of it.

180
00:16:20,600 --> 00:16:47,280
And I would say any developer who's been around for a while who is including any, you know, third party, you know, telemetry analytics gathering utility probably has a pretty good sense that they are essentially selling out their users, you know, private and intimate information subject to however much the app itself is able to gather, which is contention on how many, you know, entitlements and permissions has been granted.

181
00:16:48,740 --> 00:16:55,240
So I would say, you know, most developers can't really, with a straight face, say that they don't know what they are including.

182
00:16:56,620 --> 00:17:02,340
But they could have plausible deniability in the sense that if something gets eventually, you know,

183
00:17:02,420 --> 00:17:09,920
these frameworks sometimes get marked as malware by the first-party app store owners, you know, by the Google Play Store or the Apple App Store.

184
00:17:10,760 --> 00:17:13,860
And then they're able to identify those applications that use it.

185
00:17:14,300 --> 00:17:19,939
Typically what the done do is they'll warn the application developer that they need to have a new version that removes it.

186
00:17:21,720 --> 00:17:29,180
But, you know, I would say most developers are at least tangentially aware of when they are, you know,

187
00:17:29,340 --> 00:17:33,320
including something that could, at least in theory, be acting against the interests of their users.

188
00:17:34,740 --> 00:17:39,400
Got it. And then the last question I have before we dive into more of the situation going on with Google.

189
00:17:40,520 --> 00:17:42,340
Why does FDroid only exist on Android?

190
00:17:42,610 --> 00:17:46,340
I know it's maybe an obvious question for a lot of our audience members, but if anybody's

191
00:17:46,390 --> 00:17:49,120
new, why is there currently no FDroid for iOS?

192
00:17:49,370 --> 00:17:51,200
And do you think that could change in the future?

193
00:17:51,960 --> 00:17:57,440
Yeah, so it really goes back to the beginnings of both of these ecosystems.

194
00:17:58,310 --> 00:18:04,180
From the very beginning, the iPhone was designed to be a locked down, walled garden environment.

195
00:18:04,260 --> 00:18:10,720
It was only ever really designed to have a single first-party application distribution mechanism,

196
00:18:11,000 --> 00:18:12,100
which is the Apple App Store.

197
00:18:14,300 --> 00:18:19,700
In contrast, from the very beginning of Android, it runs on the Linux kernel.

198
00:18:20,290 --> 00:18:25,600
It comes from a more or less open source foundation, the Android Open Source Project.

199
00:18:26,800 --> 00:18:32,220
And from the very beginning, they had APIs that allow anyone to build an application distribution environment.

200
00:18:33,640 --> 00:18:36,000
Because the Google Play Store was not there from day one.

201
00:18:36,340 --> 00:18:41,720
They wanted independent carriers to be able to develop their own software

202
00:18:42,440 --> 00:18:45,940
and distribute applications in whatever way they see fit.

203
00:18:46,900 --> 00:18:49,360
And it has been wildly successful.

204
00:18:49,580 --> 00:18:53,320
There are dozens of app stores available, especially in China.

205
00:18:53,560 --> 00:18:56,400
There's at least half a dozen major ones with millions of users.

206
00:18:57,700 --> 00:19:02,760
And on other Android environments, there's Samsung, as I mentioned.

207
00:19:02,880 --> 00:19:05,120
Amazon had one up until recently.

208
00:19:06,140 --> 00:19:08,620
There's the Epic Games store and things like that.

209
00:19:09,100 --> 00:19:11,860
So it's really baked pretty deeply into Android

210
00:19:12,520 --> 00:19:16,880
that they have the ability to have anyone

211
00:19:17,100 --> 00:19:19,520
create this application distribution mechanism

212
00:19:19,880 --> 00:19:23,860
because those APIs are just a fundamental part

213
00:19:23,860 --> 00:19:24,580
of the operating system.

214
00:19:26,440 --> 00:19:26,660
Got it.

215
00:19:26,660 --> 00:19:28,860
And so do you want to maybe, it's a good segue,

216
00:19:30,020 --> 00:19:31,939
into how that might be changing

217
00:19:32,120 --> 00:19:34,220
and what Google has announced their plans are.

218
00:19:34,340 --> 00:19:36,220
And so I'd love to kind of hear from you

219
00:19:36,800 --> 00:19:37,900
maybe a summary of what's happening

220
00:19:38,080 --> 00:19:39,180
for people who aren't in the loop.

221
00:19:40,600 --> 00:19:41,880
Just kind of start that conversation.

222
00:19:43,040 --> 00:19:43,560
Yeah, yeah.

223
00:19:43,720 --> 00:19:44,920
So to talk about that,

224
00:19:44,980 --> 00:19:46,880
I'll lead up to it a little bit

225
00:19:46,980 --> 00:19:49,040
by talking about what we term side loading.

226
00:19:50,200 --> 00:19:52,480
So, you know, we've been talking about application stores

227
00:19:52,880 --> 00:19:54,780
and, you know, apps that install other apps.

228
00:19:56,540 --> 00:19:57,480
There's also, you know,

229
00:19:57,480 --> 00:19:59,580
a way of just directly installing applications

230
00:19:59,940 --> 00:20:00,500
on your device.

231
00:20:00,640 --> 00:20:08,700
You can just download an application, you know, usually ends with the suffix APK from any website,

232
00:20:09,120 --> 00:20:12,100
and then, you know, pop up a little screen and say, "Do you want to trust this developer?"

233
00:20:12,100 --> 00:20:14,600
and you say, "Okay," and then installs that app and runs it.

234
00:20:15,340 --> 00:20:17,080
That's actually how you install F-Droid.

235
00:20:17,380 --> 00:20:21,760
You know, you go to the F-Droid website and you click on this and you install it and it starts up.

236
00:20:22,700 --> 00:20:27,519
And then once you've trusted that developer, in the sense that you trust the signing certificate

237
00:20:27,540 --> 00:20:29,800
that the developer has used to sign that application,

238
00:20:31,200 --> 00:20:33,840
then you will be able to automatically install updates

239
00:20:34,020 --> 00:20:36,260
from that same developer without needing to, you know,

240
00:20:36,460 --> 00:20:37,040
re-trust them.

241
00:20:37,840 --> 00:20:39,620
And similarly, if that signature changes,

242
00:20:40,020 --> 00:20:41,140
then the system will warn you,

243
00:20:41,180 --> 00:20:42,900
it's like this was not signed by the same person.

244
00:20:42,980 --> 00:20:46,180
So it's a way of establishing direct sort of consumer

245
00:20:46,480 --> 00:20:50,540
to developer trust without necessarily relying on any middleman,

246
00:20:50,840 --> 00:20:52,500
any app store, you know, in between.

247
00:20:54,780 --> 00:20:58,040
And so that's also a fundamental part of Android.

248
00:20:58,180 --> 00:20:59,720
It's been around since the beginning.

249
00:21:01,080 --> 00:21:04,620
And there are thousands, not tens of thousands,

250
00:21:04,730 --> 00:21:06,200
of applications, popular applications,

251
00:21:06,390 --> 00:21:07,480
that are distributed that way,

252
00:21:08,280 --> 00:21:11,840
including the Apple Music application for Android.

253
00:21:12,580 --> 00:21:14,260
They have their own dedicated page to say,

254
00:21:14,460 --> 00:21:16,960
this is how you can sideload our application.

255
00:21:17,170 --> 00:21:18,440
They have step-by-step instructions.

256
00:21:19,610 --> 00:21:21,100
Yeah, I know it's been around for a long time.

257
00:21:21,130 --> 00:21:23,219
I think it's, you know, Google Play Store is not available

258
00:21:23,240 --> 00:21:27,960
in all markets. And so I think it's a mechanism for them to provide it, you know, largely to these

259
00:21:28,100 --> 00:21:33,920
markets. So yeah, so you know, it's been around forever. And it's been very hands off. None of this

260
00:21:34,060 --> 00:21:39,120
goes through, you know, Google in any way. And so that leads up to a couple of months ago in August,

261
00:21:39,620 --> 00:21:44,580
Google sort of out of the blue, announced they are starting what's called the developer registration

262
00:21:44,780 --> 00:21:54,420
program. And what this program does is it will require all developers everywhere in the world

263
00:21:54,840 --> 00:22:00,660
to register centrally with Google in order to be able to distribute these applications that they

264
00:22:00,780 --> 00:22:06,480
make. So that means that you need to, no matter what country you're in, no matter what jurisdiction,

265
00:22:06,550 --> 00:22:11,460
you need to go to Google, register with your personal information, provide government identification,

266
00:22:12,140 --> 00:22:14,300
pay them a fee, agree to terms and conditions,

267
00:22:15,200 --> 00:22:18,780
and then upload evidence of your signing key.

268
00:22:19,460 --> 00:22:20,960
So essentially you don't need to upload

269
00:22:21,020 --> 00:22:21,840
your private key itself,

270
00:22:22,080 --> 00:22:25,920
but you need to sign a sort of mini app that they send you

271
00:22:26,220 --> 00:22:27,540
to prove that you are the person

272
00:22:27,580 --> 00:22:28,980
who is able to sign applications.

273
00:22:29,780 --> 00:22:33,000
And if you don't do this, then starting next year,

274
00:22:33,900 --> 00:22:35,800
Android itself, all Android devices,

275
00:22:36,020 --> 00:22:39,899
all Android certified devices, will block applications

276
00:22:39,920 --> 00:22:42,360
that have not been verified by Google.

277
00:22:44,820 --> 00:22:48,220
- And so, yeah, do you mind,

278
00:22:49,600 --> 00:22:51,920
like, is this kind of bad?

279
00:22:51,970 --> 00:22:52,720
Is this really bad?

280
00:22:53,190 --> 00:22:55,020
You know, like, what are kind of your stances

281
00:22:55,260 --> 00:22:56,760
on like this kind of proposal?

282
00:22:57,580 --> 00:23:00,940
- I mean, it's catastrophic, especially for F-Droid.

283
00:23:01,030 --> 00:23:02,660
I mean, it's completely incompatible

284
00:23:02,690 --> 00:23:03,920
with the way that F-Droid works

285
00:23:04,170 --> 00:23:05,760
because we don't require that our developers

286
00:23:06,540 --> 00:23:07,720
will be registering with Google

287
00:23:07,940 --> 00:23:09,880
and many have already said straight up

288
00:23:09,900 --> 00:23:16,660
not going to do it. So it's more or less an extinction event for us, which is one of the

289
00:23:16,780 --> 00:23:24,500
reasons why we are so full-throated in our opposition to it. So yeah, it's terrible for

290
00:23:24,500 --> 00:23:30,820
us. It's terrible for anyone who just wants to be able to develop an app and share it directly with

291
00:23:30,880 --> 00:23:35,880
their friends or their family or their community or their church group or anything like that.

292
00:23:36,400 --> 00:23:49,140
It all of a sudden turns it, you know, takes it from a thing where an individual hobbyist can just, you know, spend a weekend developing this neat and useful application to something where you need to go through all of these steps.

293
00:23:49,270 --> 00:23:55,180
You need to provide all this, you know, personal intimate information that you might not be comfortable with sharing with Google.

294
00:23:56,420 --> 00:24:05,600
And you need to register with them all of the identifiers for every application you ever intend to distribute, which might not be something that you're interested in sharing with them.

295
00:24:06,300 --> 00:24:08,680
So it's a massive change.

296
00:24:09,160 --> 00:24:14,660
It completely changes the openness of the platform

297
00:24:15,540 --> 00:24:18,360
from what has always been for the past 18 years.

298
00:24:19,980 --> 00:24:24,520
Yeah, and what are some of the reasons that Google is using

299
00:24:24,660 --> 00:24:25,740
to justify this decision?

300
00:24:26,580 --> 00:24:30,700
And then how do you agree or disagree with some of those

301
00:24:32,380 --> 00:24:33,600
kind of decisions that they're making?

302
00:24:33,760 --> 00:24:50,700
Yes. So, you know, you can look on their web page at the developer registration program. They have a recent blog entry and a YouTube video developers roundtable that, you know, pretty much goes over their rationale, both about how they're going to be implementing it and why.

303
00:24:51,380 --> 00:25:02,520
The one and only reason that they have stated is to prevent repeat malware offenders from being able to operate.

304
00:25:03,540 --> 00:25:14,880
The scenario, somewhat far-fetched scenario, that they lay out is the case where some group develops some sort of malware scam app.

305
00:25:15,760 --> 00:25:23,320
You know, like I said, it may be an app that pretends to be, you know, your bank and intercepts your credentials and then uses it to, you know, to take all your money or something.

306
00:25:25,700 --> 00:25:34,300
Prevent, it won't prevent that because obviously they can just register, you know, like anyone else with, you know, falsified credentials or whatever and develop the app.

307
00:25:34,380 --> 00:25:54,380
What it will prevent is if that app winds up getting identified and zapped by the Google Play Protect services, which is a complete separate service that runs on-device, scans for malware, and then when it identifies it, either warns the user or moves it altogether, depending on the parity.

308
00:25:55,360 --> 00:26:07,080
It will prevent the developers who come up with an app like that from simply being able to turn around and redistribute the same application with a brand new signing key that they didn't have to register anywhere.

309
00:26:08,760 --> 00:26:20,580
So that's really the very narrow hypothetical malware distribution scenario that this particular registration program would potentially be able to mitigate.

310
00:26:21,400 --> 00:26:24,260
And why is that catastrophic for F2WD?

311
00:26:25,080 --> 00:26:26,540
because you said it would be a disaster.

312
00:26:26,740 --> 00:26:29,980
So how does this impact you guys?

313
00:26:31,040 --> 00:26:33,120
Well, so as I mentioned, you know, we don't...

314
00:26:33,120 --> 00:26:36,920
So FDroid has a couple of different modes of operating.

315
00:26:37,700 --> 00:26:40,180
Historically, what would happen would be, you know,

316
00:26:40,220 --> 00:26:42,480
a developer creates a free and open source application.

317
00:26:42,760 --> 00:26:44,080
They host the source code somewhere,

318
00:26:44,980 --> 00:26:47,460
maybe on, you know, GitHub or GitLab or Codeberg

319
00:26:48,060 --> 00:26:48,700
or just on their website.

320
00:26:49,500 --> 00:26:57,440
And then they, you know, they submit to FDroid, essentially a request for inclusion.

321
00:26:58,660 --> 00:27:02,020
And then, you know, we go through and we say, okay, is this really open source?

322
00:27:02,600 --> 00:27:07,580
Is this a kind of application that we want to have on the platform?

323
00:27:08,260 --> 00:27:15,240
And then historically, we would just download that and we would build it and we would sign it with, you know, our own signing key and distribute it.

324
00:27:16,920 --> 00:27:22,260
Trying to move away from that to a much more secure and modern approach,

325
00:27:22,480 --> 00:27:24,040
which is called reproducible builds,

326
00:27:24,620 --> 00:27:28,660
which is that the developer themselves can build their application,

327
00:27:29,440 --> 00:27:33,420
essentially publishing their own APK that someone could download

328
00:27:33,560 --> 00:27:36,900
either directly from your website or through a service like AppDroid.

329
00:27:38,060 --> 00:27:42,620
And what we do is we validate that by essentially just rebuilding that application

330
00:27:43,160 --> 00:27:45,760
and comparing the two and making sure that they match identically.

331
00:27:46,380 --> 00:27:52,720
And what that enables is it enables the developer to use their own signing key to distribute that application,

332
00:27:54,000 --> 00:27:59,880
which is what really permits the trust relationship to be from the user directly with the developer,

333
00:28:00,230 --> 00:28:02,980
and not necessarily just trusting the intermediary App Store.

334
00:28:05,340 --> 00:28:10,760
And we cannot require that our developers register with Google.

335
00:28:11,440 --> 00:28:15,180
There's no mechanism for us to even check that or verify that.

336
00:28:15,660 --> 00:28:29,960
So, you know, if this were to go into effect today, you know, not only would the F-Droid itself stop launching, but all of the apps that we distribute through F-Droid would also just, you know, stop launching and would go dark overnight.

337
00:28:31,500 --> 00:28:36,980
And that's really the fundamental reason that it just doesn't work with the F-Droid model.

338
00:28:37,900 --> 00:29:01,760
Yeah, so I guess what would, and maybe I'm missing something, but with like a web-based F-Droid where you somehow were able to confirm that each developer went through Google's verification successfully, and then you'd have to, there would be no like automatic updates, you'd have to do it one by one.

339
00:29:01,890 --> 00:29:04,360
Is that maybe the best you could even do in that situation?

340
00:29:04,960 --> 00:29:05,520
Best case scenario?

341
00:29:06,420 --> 00:29:13,660
In theory, I mean, if we were not philosophically opposed to this program as well, in theory,

342
00:29:13,800 --> 00:29:19,580
we might be able to do something like that where we would mandate that developers do this.

343
00:29:20,180 --> 00:29:21,060
But we're not going to do that.

344
00:29:21,920 --> 00:29:23,220
Yeah, but still a bad situation.

345
00:29:25,080 --> 00:29:28,920
And the philosophy is definitely something that I think is important that you guys are

346
00:29:29,040 --> 00:29:29,400
sticking to.

347
00:29:29,400 --> 00:29:33,759
I'm just kind of seeing what even a best case scenario would look like for someone who maybe

348
00:29:33,780 --> 00:29:37,380
wanted to even, like if someone didn't have a philosophical issue with this and they were like,

349
00:29:37,520 --> 00:29:42,900
I'll still try to do that. Yeah, I mean, we're not necessarily going to prevent our developers from

350
00:29:43,360 --> 00:29:48,760
doing this as well. Like we essentially, it's up to the developer whether or not they sign on to it.

351
00:29:49,980 --> 00:29:56,280
We recommend against it for right now, at least. But we, you know, nothing stops developers from

352
00:29:56,400 --> 00:30:00,599
doing it, in which case these would just work. It's just we have no way of knowing whether or not

353
00:30:00,800 --> 00:30:04,040
the applications that we distribute are registered or not with Google.

354
00:30:05,360 --> 00:30:09,260
Got it. And then so how does this impact other app stores? Is it the same situation for all other

355
00:30:09,290 --> 00:30:15,320
app stores? Yeah, essentially, which is why we're a little surprised that there's not been more

356
00:30:15,700 --> 00:30:22,320
outcry from other commercial app stores, you know, because, you know, this, you know, as well as being

357
00:30:22,480 --> 00:30:28,459
sort of concerning from privacy reasons and, you know, raising barriers of entry, obviously there's

358
00:30:28,480 --> 00:30:30,940
the fee that they charge for doing this and things like that.

359
00:30:32,380 --> 00:30:36,560
But also, for a commercial competitor to the Play Store,

360
00:30:37,800 --> 00:30:40,640
it ought to be extremely unsettling because all of a sudden,

361
00:30:41,460 --> 00:30:43,560
you need to register with your direct competitor.

362
00:30:43,980 --> 00:30:47,160
You need to have all your app developers register with their direct competitor

363
00:30:47,500 --> 00:30:49,760
in order to be able to distribute through your own app store.

364
00:30:51,840 --> 00:30:55,460
I think that aspect of it maybe has not completely sunk in

365
00:30:56,060 --> 00:30:57,620
with the broader industry.

366
00:30:59,160 --> 00:31:03,940
about this because it ought to be seen as being sort of blatantly competitive. It's a little bit

367
00:31:04,040 --> 00:31:10,140
like if I have a car dealership and I want to sell, you know, my Ford model, I need to require

368
00:31:10,520 --> 00:31:15,920
that everyone first go get approval from Chevrolet in order to be allowed to do it. There's no,

369
00:31:16,840 --> 00:31:21,600
you know, there's no real precedent for anything like this, you know, ever, ever, you know,

370
00:31:21,720 --> 00:31:28,660
happening before in my experience in software. Yeah, and you know, I always dislike asking this

371
00:31:28,800 --> 00:31:33,500
question, but it's something I do have to ask because I don't know. I care. I'm sure a lot of

372
00:31:33,500 --> 00:31:37,940
our audience cares, but let's say someone's just using an iPhone. They just use the Google Play

373
00:31:38,120 --> 00:31:45,000
Store. Let's just call them a typical regular user. Why should they care about this? Yeah, well,

374
00:31:45,660 --> 00:31:50,839
you know, we think that people in general should care about their privacy. People should be more

375
00:31:50,860 --> 00:31:55,500
aware of what these applications are doing, how these applications

376
00:31:58,260 --> 00:32:02,360
impact the information that is being collected from you, often

377
00:32:02,600 --> 00:32:07,800
clandestinely. And in order to provide a check on that, we think it's essential

378
00:32:08,040 --> 00:32:12,840
that there be a open ecosystem, that it should not be monopolized by a single

379
00:32:13,060 --> 00:32:20,820
player, that things should not be gatekept by one single global entity. To

380
00:32:20,840 --> 00:32:28,020
actual useful service that F-Droid has provided is that there was a while ago, there was a

381
00:32:28,550 --> 00:32:32,280
suite of applications, very popular, called Simple Mobile Tools on Android.

382
00:32:32,990 --> 00:32:36,240
And they provided pretty much run-of-the-mill applications.

383
00:32:36,370 --> 00:32:42,760
They have a calendar, they have a camera app, they have scheduling applications, an email

384
00:32:43,020 --> 00:32:49,759
client, sort of a whole mini-suite that you could use to replace the existing pre-installed

385
00:32:49,780 --> 00:32:56,340
sometimes, you know, crapware that comes with your phone with some nice, clean, simple open-source applications.

386
00:32:57,680 --> 00:33:02,400
That was distributed because they were free and open-source on both the Google Play Store and on F-Droid.

387
00:33:03,860 --> 00:33:12,600
And then what happens, as has so often happened with a lot of applications, both in the iOS and in the, you know, Android ecosystem,

388
00:33:13,120 --> 00:33:18,980
is that this app developer wound up getting acquired by a company and all their apps getting acquired.

389
00:33:19,580 --> 00:33:22,680
And then almost immediately, these apps wound up getting,

390
00:33:23,300 --> 00:33:24,860
their source code got closed down,

391
00:33:24,930 --> 00:33:27,460
they started injecting advertisements everywhere,

392
00:33:27,610 --> 00:33:30,660
they started adding in-app purchases that take away features

393
00:33:30,830 --> 00:33:32,240
and put them behind paywalls,

394
00:33:32,480 --> 00:33:36,060
they started adding telemetry and surveillance and things like that.

395
00:33:36,530 --> 00:33:41,400
And so this implied contract that you had with this app developer,

396
00:33:41,810 --> 00:33:44,000
that just vanished overnight, non-consensually.

397
00:33:44,510 --> 00:33:47,100
And since almost everyone has these automatic updates turned on,

398
00:33:47,620 --> 00:33:51,100
the next day, these apps that were formerly ones that you trusted,

399
00:33:51,520 --> 00:33:53,560
suddenly became something that you cannot trust the next day.

400
00:33:55,480 --> 00:33:58,980
However, on the F-Droid side, what happened is because the source code before it had gotten

401
00:33:59,160 --> 00:34:03,540
acquired was still free and open source, an organization called Fossify just took them,

402
00:34:04,060 --> 00:34:09,060
forked them, and then started releasing them, continuing to be these sort of honest, simple,

403
00:34:09,419 --> 00:34:13,879
authentic, free tools, first through F-Droid and then again through the Play Store.

404
00:34:15,159 --> 00:34:22,780
And the identification and the calling out of that was really something,

405
00:34:23,290 --> 00:34:28,220
a lot of, until FDroid removed those applications from the original applications from our App Store,

406
00:34:28,379 --> 00:34:34,560
because they no longer complied with the open source requirement, as well as breaking a lot of other inclusion policy rules,

407
00:34:35,200 --> 00:34:39,800
a lot of users maybe never would have been aware of what had happened and how it had happened.

408
00:34:41,000 --> 00:34:45,220
But instead, a lot of people were like, "Why did these tools suddenly become crummy overnight?"

409
00:34:46,060 --> 00:34:51,280
A lot of forums were saying, "Oh, here's how you get the real ones back. You go and you get this open source one."

410
00:34:52,060 --> 00:34:57,840
If something like FDroid didn't exist, that broader service might not have ever been made available to the rest of the world,

411
00:34:58,120 --> 00:35:01,460
and even had a knock-on effect of being available through the Play Store.

412
00:35:02,160 --> 00:35:09,119
So that's sort of one real and concrete example of a service that having a competitive marketplace like FDroid

413
00:35:09,140 --> 00:35:10,360
has provided for the community.

414
00:35:11,690 --> 00:35:12,560
Yeah, it's quite frustrating.

415
00:35:12,820 --> 00:35:15,520
I mean, there's two things that I see happen all the time.

416
00:35:15,700 --> 00:35:19,280
One, these massive companies steal open source code,

417
00:35:20,500 --> 00:35:23,220
oftentimes not even attributing that code.

418
00:35:23,320 --> 00:35:24,640
I mean, a lot of people to this day,

419
00:35:24,690 --> 00:35:29,840
and I know this is totally a political thing that I'm saying.

420
00:35:29,960 --> 00:35:31,180
It's just the one that came to mind.

421
00:35:31,420 --> 00:35:34,460
But TrueSocial was a complete Mastodon clone.

422
00:35:35,120 --> 00:35:37,220
They totally stole the Mastodon code.

423
00:35:37,380 --> 00:35:39,280
There was references to the Mastodon code.

424
00:35:39,520 --> 00:35:40,720
They kind of sloppily stole it.

425
00:35:41,120 --> 00:35:41,960
Now they do reference it.

426
00:35:41,960 --> 00:35:44,480
I actually went to the website yesterday to confirm that.

427
00:35:44,800 --> 00:35:47,660
And now they say, oh, open source on the bottom, and it links to that.

428
00:35:47,860 --> 00:35:52,620
But all these big tech companies use open source code for different things, and it's very frustrating.

429
00:35:52,860 --> 00:35:54,040
So that's issue one.

430
00:35:54,160 --> 00:36:00,480
But issue two is that even if you use these platforms, people go, well, I've never used Linux, so why do I care?

431
00:36:00,700 --> 00:36:04,840
but if the only two options that existed were macOS and Windows,

432
00:36:05,140 --> 00:36:08,320
they might look very different if Linux wasn't there as that alternative.

433
00:36:08,430 --> 00:36:10,880
And I feel like you guys are in a very similar boat,

434
00:36:11,020 --> 00:36:12,980
that without you checking the Play Store,

435
00:36:13,550 --> 00:36:15,280
the Play Store could look very different for people.

436
00:36:16,150 --> 00:36:18,780
So, yeah, just a bit of a rant on my end.

437
00:36:20,180 --> 00:36:21,960
But yeah, I mean, you're absolutely right.

438
00:36:22,120 --> 00:36:25,900
I mean, even if people are not interested in using Ftroid, you know, directly,

439
00:36:26,340 --> 00:36:30,560
we do have a broader check on the ecosystem,

440
00:36:30,860 --> 00:36:35,440
especially as it pertains to keeping open source players honest.

441
00:36:37,440 --> 00:36:42,300
If something turns bad, if the rug gets pulled, as it so often does,

442
00:36:43,440 --> 00:36:47,020
then we're sort of there to help provide alternatives

443
00:36:47,560 --> 00:36:52,160
and provide sort of a guaranteed safe place that will never be possible in.

444
00:36:55,140 --> 00:37:04,220
So one thing that I did want to also ask about this, this is tied to the Google Play services, as far as I'm aware.

445
00:37:04,600 --> 00:37:08,880
So if you're just using a regular Android device, then this is something that's going to impact you.

446
00:37:10,620 --> 00:37:15,520
However, I got a bajillion comments about this, because I've been doing coverage about this F2OID stuff.

447
00:37:15,650 --> 00:37:20,140
People are like, well, this is why I'm using Lineage OS, which doesn't come with Google Play services.

448
00:37:21,230 --> 00:37:22,800
And, you know, maybe it uses MicroG.

449
00:37:23,360 --> 00:37:28,500
I've seen people using Graphene who go, "Well, I'm using sandbox play services," or "I'm not using any at all."

450
00:37:29,040 --> 00:37:31,200
So why should these people still care about what's going on?

451
00:37:31,500 --> 00:37:36,300
Because there seems to be this idea that, "Oh, I'm not using Google Play services, so I'm unaffected by this."

452
00:37:36,980 --> 00:37:42,180
Yeah, right. So, you know, this does only affect what they call Android-certified devices,

453
00:37:43,320 --> 00:37:48,400
which is devices that are essentially approved by Google.

454
00:37:49,360 --> 00:37:58,720
The requirements for that are that you use Google Play services, that you have the Google Play store at least available as an option on your device.

455
00:38:00,360 --> 00:38:07,500
But as a benefit, you get to use Google Mobile Services, which makes it easier for people to use.

456
00:38:08,100 --> 00:38:14,540
So outside of China, these Android certified devices are well over 95% of all installed devices.

457
00:38:14,820 --> 00:38:21,740
I mean, this is really like the entire universe of Android devices in the world outside of China.

458
00:38:23,080 --> 00:38:25,900
You know, the rest are non-Android certified devices.

459
00:38:25,980 --> 00:38:27,280
They might be custom ROMs.

460
00:38:27,280 --> 00:38:28,380
They might be Lineage OS.

461
00:38:28,620 --> 00:38:30,000
They might be Graphene.

462
00:38:30,160 --> 00:38:31,460
They might, you know, be Calyx.

463
00:38:32,320 --> 00:38:33,800
They could be, you know, PinePhone.

464
00:38:34,040 --> 00:38:40,280
There's, you know, quite a wide variety and thriving, you know, ecosystem that we fully support.

465
00:38:41,680 --> 00:38:47,700
But these are really, you know, one to two percent of all users.

466
00:38:47,870 --> 00:38:51,720
It's not, you're not going to really be installing this on your grandmother's phone,

467
00:38:52,980 --> 00:38:55,280
you know, unless you have a really interesting grandmother.

468
00:38:57,619 --> 00:39:01,100
And, you know, it's, they are right.

469
00:39:01,650 --> 00:39:06,400
And I do see a lot of, you know, kind of crowing from that crowd saying like,

470
00:39:06,580 --> 00:39:08,680
"Yeah, see, this is why I chose this."

471
00:39:08,830 --> 00:39:11,760
And we fully support them, and FDroid is often

472
00:39:12,170 --> 00:39:16,540
the primary app distribution environment for those devices.

473
00:39:18,319 --> 00:39:24,620
But do we really want to sacrifice 95% of the Android users out there

474
00:39:24,920 --> 00:39:26,260
to be subject to this?

475
00:39:29,440 --> 00:39:32,800
I think it's a little bit narrow-sided to say,

476
00:39:32,920 --> 00:39:35,120
"Oh, your solution is just to install Lineage.

477
00:39:35,140 --> 00:39:37,960
That's not a solution for billions of people in the world.

478
00:39:38,480 --> 00:39:41,380
Yeah, and I think something I was thinking about as well,

479
00:39:41,460 --> 00:39:43,520
and maybe I don't know if this is fully true,

480
00:39:43,700 --> 00:39:45,420
so you're a perfect person to ask here.

481
00:39:46,420 --> 00:39:47,520
My understanding, so of course,

482
00:39:47,620 --> 00:39:51,260
this is really only directly going after developers.

483
00:39:51,960 --> 00:39:54,180
This isn't directly going after users at all.

484
00:39:54,800 --> 00:39:58,100
And so what's the downstream effect of the developers

485
00:39:58,200 --> 00:40:00,140
who don't want to continue developing apps

486
00:40:00,300 --> 00:40:01,100
away from the Play Store?

487
00:40:02,400 --> 00:40:10,080
Like that that still will impact those custom ROMs if the developers developing those open source apps they're using aren't able to like

488
00:40:11,340 --> 00:40:13,640
Like will they still develop for that small subset of users?

489
00:40:15,540 --> 00:40:20,380
That's yeah, I mean question. Yeah, I mean I think it remains to be seen we have seen

490
00:40:21,060 --> 00:40:25,400
We have seen a number of developers who you know, I've already said never signing up for this

491
00:40:26,400 --> 00:40:30,220
And I'll probably just stop developing altogether and you know go go do something else

492
00:40:31,120 --> 00:40:31,940
woodworking or something.

493
00:40:33,360 --> 00:40:35,540
You know, I don't know if that is gonna, you know,

494
00:40:36,460 --> 00:40:38,460
be a very widespread protest,

495
00:40:39,180 --> 00:40:40,840
but I think the world is the worst place for it

496
00:40:40,920 --> 00:40:44,560
because those are often the developers who have the most interesting application ideas,

497
00:40:45,280 --> 00:40:49,480
applications that might not fit perfectly well with the Google Play Store's own,

498
00:40:49,880 --> 00:40:50,960
you know, inclusion policies,

499
00:40:51,840 --> 00:40:53,860
that might only be able to be distributed,

500
00:40:55,060 --> 00:40:56,440
you know, through direct download.

501
00:40:57,120 --> 00:41:07,240
You know, sometimes very niche apps, sometimes, you know, apps that they just don't think have commercial viability or not interested in the Play Store.

502
00:41:09,200 --> 00:41:17,460
I'm sure there'll be plenty of people who continue to develop them and are happy to drastically reduce the number of people who are able to install them.

503
00:41:18,640 --> 00:41:21,400
But what that number is, I think only time will tell.

504
00:41:22,920 --> 00:41:25,620
Yeah, and that's something we want to leave up to chance.

505
00:41:27,660 --> 00:41:33,540
So, you know, if someone's hearing this, what is kind of, what are the next steps here?

506
00:41:33,580 --> 00:41:36,100
Like, what are the timelines that Google has proposed?

507
00:41:37,520 --> 00:41:42,240
What can people do that is actionable, that can make a real difference, whether or not

508
00:41:42,260 --> 00:41:43,660
they even use FDroid right now?

509
00:41:44,480 --> 00:41:45,940
What are you kind of sharing with people?

510
00:41:46,900 --> 00:41:52,060
So there's a website that I worked with people on called keepandroidopen.org.

511
00:41:52,500 --> 00:41:57,380
And that essentially lists the call to actions that we think are the most viable.

512
00:41:58,700 --> 00:42:01,400
This is not a direct F-Droid project.

513
00:42:01,510 --> 00:42:04,500
This is actually a project that I just sort of undertook on my own.

514
00:42:04,760 --> 00:42:08,260
And then it turned into about 20 contributors now.

515
00:42:08,390 --> 00:42:10,060
They translated it into five different languages.

516
00:42:11,340 --> 00:42:16,600
Essentially, the calls to action there are based on three target audience groups.

517
00:42:17,360 --> 00:42:21,980
It's consumers, developers, and the state regulators.

518
00:42:23,220 --> 00:42:27,280
people who are the governing bodies around these things.

519
00:42:28,540 --> 00:42:35,820
In terms of consumers, really the most effective thing that you can do is contact your local jurisdictions regulators

520
00:42:36,320 --> 00:42:42,760
and make them aware of your objection to it, why you think that it is problematic.

521
00:42:43,460 --> 00:42:50,300
This will be most effective in areas that have a strong regulatory environment, especially the European Union.

522
00:42:50,560 --> 00:42:56,540
You know, this particular act is in direct contravention of the requirements imposed by the Digital Markets Act.

523
00:42:57,720 --> 00:43:00,240
And I think, you know, regulators need to be made aware of that.

524
00:43:00,920 --> 00:43:05,860
Also, plenty of other countries are looking into, you know, App Store monopolies and regulation around there,

525
00:43:06,300 --> 00:43:12,440
namely Brazil, Japan, the United Kingdom, South Korea are some of the more advanced ones around that.

526
00:43:13,400 --> 00:43:15,700
And then, you know, other ones are sort of following suit, Australia.

527
00:43:17,880 --> 00:43:25,980
But yeah, reaching out directly to regulators, making your own individual voice heard, I think that's really the most powerful thing that consumers can do right now.

528
00:43:27,020 --> 00:43:33,820
Other options are looking into alternative ecosystems, not just installing Ftroid, which by the way, I think everyone should do.

529
00:43:34,680 --> 00:43:40,440
It's just great to have as a backup and a place that you can really go to really trust the applications you get.

530
00:43:41,260 --> 00:43:46,780
But also looking into different ecosystem options for custom ROMs or installing lineage OS.

531
00:43:48,620 --> 00:43:53,920
You might stumble upon a really interesting setup for yourself that works really well for you.

532
00:43:55,130 --> 00:44:00,020
But yeah, the most effective thing that a consumer can do really is to try to make your voice heard.

533
00:44:01,540 --> 00:44:05,600
From developers, the most effective thing you can do right now is do nothing.

534
00:44:06,390 --> 00:44:07,300
Do not sign up for this.

535
00:44:08,680 --> 00:44:13,720
It's in early access right now, but they're going to be opening up developer registration early next year.

536
00:44:14,640 --> 00:44:16,240
Do not add your name to this list.

537
00:44:16,290 --> 00:44:17,820
Do not upload your information.

538
00:44:17,950 --> 00:44:20,500
Do not pay them money for the privilege.

539
00:44:21,480 --> 00:44:22,680
How much money is it, by the way?

540
00:44:22,820 --> 00:44:23,480
It's not much.

541
00:44:23,870 --> 00:44:25,820
I think they have it set right now at $25.

542
00:44:27,050 --> 00:44:28,820
But it's just like, come on.

543
00:44:29,220 --> 00:44:31,380
You're really adding insult to injury.

544
00:44:33,480 --> 00:44:34,760
Don't do any of it.

545
00:44:35,030 --> 00:44:35,640
Just opt out.

546
00:44:36,840 --> 00:44:42,000
There'll always be time later. If it comes down to it on the day, it's going to come into effect.

547
00:44:42,260 --> 00:44:43,980
You can always do it later, but don't do it now.

548
00:44:44,700 --> 00:44:46,980
Is that annual or is that a one-time?

549
00:44:47,580 --> 00:44:53,340
I believe it is one-time, but I don't know if that is set in stone yet.

550
00:44:54,880 --> 00:44:58,820
All their documentation is sort of like subject to change and things like that.

551
00:44:59,560 --> 00:45:00,700
Same with the terms and conditions.

552
00:45:01,060 --> 00:45:06,040
One of the really alarming things about it is that they say,

553
00:45:06,140 --> 00:45:07,640
oh, you just have to sign their terms and conditions.

554
00:45:07,880 --> 00:45:12,260
Of course, they're 100 pages long, and they have all sorts of clauses in them,

555
00:45:12,920 --> 00:45:14,980
especially some really alarming stuff.

556
00:45:16,100 --> 00:45:18,320
But the thing is that these are always changing.

557
00:45:19,000 --> 00:45:21,400
Coming from developing for these commercial app stores,

558
00:45:21,580 --> 00:45:22,980
the Apple App Store and the Play Store,

559
00:45:23,940 --> 00:45:26,180
every month or so you get these updates.

560
00:45:26,320 --> 00:45:29,060
And if you don't click OK, your apps get nuked.

561
00:45:30,160 --> 00:45:31,340
You're pulled from the store.

562
00:45:31,440 --> 00:45:35,180
So everyone is just sort of conditioned in this Pavlovian way to be like,

563
00:45:35,220 --> 00:45:37,140
oh, terms and conditions have updated, click OK.

564
00:45:37,860 --> 00:45:40,140
And if those terms and conditions contain things like,

565
00:45:40,520 --> 00:45:45,900
thou shalt not compete with YouTube services,

566
00:45:46,120 --> 00:45:47,840
or thou shalt not compete with Apple Music,

567
00:45:49,020 --> 00:45:51,300
well, all of a sudden you've just clicked yourself out of business.

568
00:45:52,560 --> 00:45:55,140
So, I mean, that's really the alarming thing about these terms and conditions,

569
00:45:55,360 --> 00:45:57,800
that it's not a one-time thing, but it's a rolling thing,

570
00:45:57,960 --> 00:46:00,520
They can update over time to say anything that they want.

571
00:46:02,540 --> 00:46:05,340
So yeah, so for developers, summary is don't sign up for it.

572
00:46:05,500 --> 00:46:06,740
It's just a bad idea.

573
00:46:07,700 --> 00:46:09,980
And tell your other developer friends not to sign up for it.

574
00:46:10,700 --> 00:46:14,740
And then third is for the state themselves, for governments and regulators.

575
00:46:15,700 --> 00:46:21,580
Look really closely at this, considering how it affects your own country's digital sovereignty.

576
00:46:22,880 --> 00:46:28,880
you are essentially ceding the rights of your developers and your businesses and your governments

577
00:46:29,830 --> 00:46:34,920
to be able to speak directly to your consumers through technology.

578
00:46:35,880 --> 00:46:39,460
I really regard software development and app development as a form of speech.

579
00:46:39,880 --> 00:46:46,200
You're not just providing a tool, you're providing a mode of expression.

580
00:46:47,040 --> 00:46:54,740
And just like the printing press has been a force for advancing the Enlightenment centuries over centuries,

581
00:46:55,700 --> 00:47:02,280
app development is a way of facilitating people to communicate with their environment.

582
00:47:02,960 --> 00:47:09,040
And any time you are allowing essentially a foreign, a distant entity,

583
00:47:09,320 --> 00:47:13,780
especially a for-profit entity that might be competing with their own businesses,

584
00:47:14,360 --> 00:47:22,880
To have a single global kill switch for this, to have a single point of gatekeeping, you're

585
00:47:23,020 --> 00:47:28,100
really, you're giving up a lot for your businesses, for your defense.

586
00:47:29,620 --> 00:47:39,020
To cite one particular example is back in 2021, back when there was a parliamentary election

587
00:47:39,080 --> 00:47:47,280
in Russia and Alexei Naglevi was running against Vladimir Putin, he had an election app that

588
00:47:47,480 --> 00:47:50,060
was available on both the Play Store and the App Store.

589
00:47:51,250 --> 00:47:58,340
And shortly before the election, the Kremlin essentially strong-armed both Google and Apple

590
00:47:58,600 --> 00:48:00,160
to pull that app from their App Store.

591
00:48:01,110 --> 00:48:03,080
And that app disappeared.

592
00:48:04,020 --> 00:48:07,040
The results of the election were probably a foregone conclusion anyway.

593
00:48:07,600 --> 00:48:11,100
But obviously, you know, the current regime won.

594
00:48:12,980 --> 00:48:14,340
Alexei Nikolavi is now dead.

595
00:48:15,180 --> 00:48:19,580
Russia has invaded Ukraine and is on, you know, on the border of the rest of Europe.

596
00:48:19,680 --> 00:48:25,900
So these are not like sort of, you know, hypothetical, you know, out there ideas.

597
00:48:26,380 --> 00:48:31,780
But having a single centralized control to all app distribution focused in, you know,

598
00:48:31,960 --> 00:48:38,080
two companies that are located 10 miles away from each other, it just seems like it ought

599
00:48:38,080 --> 00:48:40,740
to be extremely alarming to every government out there.

600
00:48:42,120 --> 00:48:48,580
And every person. I mean, yeah, when you put it very well there, I think, to really drill the

601
00:48:48,680 --> 00:48:58,540
message home. So I guess an initial question here, why? Like, yes, Google is saying malware,

602
00:48:58,760 --> 00:49:04,340
they're saying security. It's easy to point at it and this is what I've been doing and just say,

603
00:49:04,520 --> 00:49:11,540
oh it's for more control over the platform. Is that kind of the most that you're able to really

604
00:49:11,880 --> 00:49:17,200
attribute this to? Do you think there's any other motives behind it? I know it's all speculative,

605
00:49:17,730 --> 00:49:22,819
you don't know, but do you have any ideas on maybe like what they're actually trying to accomplish

606
00:49:22,820 --> 00:49:28,740
from this? Yeah, I mean, it would be speculation. There's obviously a lot of speculation floating

607
00:49:28,920 --> 00:49:36,480
around. You know, most of it is mostly unsupported. You know, I would say, I think it's fair to say

608
00:49:37,320 --> 00:49:42,900
it's for control, right? They've seen that Apple gets away with this, that Apple gets away with it,

609
00:49:43,020 --> 00:49:48,719
even in areas where it's blatantly illegal, like in the European Union, under the Digital Markets

610
00:49:48,800 --> 00:49:54,040
Act. They see that they've been, you know, flouting that with impunity. And they think that now is

611
00:49:54,160 --> 00:49:58,240
probably the time where they can get away with it. We're obviously in the United States in a pretty

612
00:49:58,880 --> 00:50:05,020
light touch regulatory environment. And so there's not going to be, you know, any serious investigations

613
00:50:05,440 --> 00:50:09,700
on the part of the Federal Trade Commission or the Department of Consumer Affairs, the Justice

614
00:50:09,940 --> 00:50:16,099
Department. That's just not going to be happening. And so, you know, I think they're thinking the time

615
00:50:16,120 --> 00:50:22,660
is now to do it. And not only because of legislation that follows following the Digital

616
00:50:22,780 --> 00:50:28,260
Markets Act in these other countries, but also because of new requirements as a result

617
00:50:28,400 --> 00:50:34,740
of the settlement with Epic Games that is going to mandate that they be able to distribute

618
00:50:34,860 --> 00:50:41,900
third party marketplaces from their own Google Play Store. They want to be able to lock down

619
00:50:41,920 --> 00:50:45,460
as much as possible the potential kinds of applications

620
00:50:45,820 --> 00:50:47,760
that are going to get distributed through there.

621
00:50:48,500 --> 00:50:51,100
And this is the obvious route to being able to do it.

622
00:50:52,340 --> 00:50:54,080
It's funny you brought up Epic Games right now.

623
00:50:55,500 --> 00:50:57,880
I'll take random bullet points as you say certain things.

624
00:50:58,140 --> 00:51:00,020
And my next one that I wanted to ask about,

625
00:51:00,360 --> 00:51:01,780
because I just have to quickly type things out.

626
00:51:02,460 --> 00:51:04,680
Epic Games, LOL, question mark.

627
00:51:05,500 --> 00:51:08,260
And the reason why, I just think it's almost,

628
00:51:08,920 --> 00:51:20,360
I can't find a better word right now other than unhinged of Google to be kind of taking these L's against Epic over this exact thing.

629
00:51:20,730 --> 00:51:26,520
And Google is now simultaneously doing something that's in some ways 10x more extreme than they ever did against Epic.

630
00:51:26,840 --> 00:51:31,080
So, yeah, it's just I don't know if that's a question.

631
00:51:31,290 --> 00:51:32,460
I just find it a bit crazy.

632
00:51:33,540 --> 00:51:39,760
Yeah, no, I mean, it's definitely a crazy time, you know, with the outcome of the lawsuits,

633
00:51:41,070 --> 00:51:47,060
you know, and how different it is between, you know, the lawsuit between Epic and Google

634
00:51:47,390 --> 00:51:52,420
and the one between Epic and Apple, where the outcomes were so wildly divergent.

635
00:51:53,380 --> 00:51:58,240
You know, I'm sure Google has some, you know, very bitter feelings about that and feel like,

636
00:51:58,700 --> 00:52:02,780
you know, why did we get, you know, kind of shafted on this and Apple didn't.

637
00:52:03,480 --> 00:52:07,760
But that was the outcome that happened and was going to be sticking with us for a long time.

638
00:52:09,080 --> 00:52:12,820
But they had to come to some sort of settlement, right?

639
00:52:13,100 --> 00:52:20,960
Like Epic totally won out in the debate about distribution.

640
00:52:23,440 --> 00:52:29,620
And yeah, I think they're doing this to sort of get in front of it, lock things down as much as they can get away with.

641
00:52:30,800 --> 00:52:33,540
which from a commercial, you know, they're not being irrational.

642
00:52:33,800 --> 00:52:36,540
They are a profit-seeking entity,

643
00:52:37,280 --> 00:52:40,040
and they're looking to protect their profits as much as possible.

644
00:52:40,200 --> 00:52:46,980
I don't see it as like, you know, there's no real, like, humanity involved with it.

645
00:52:47,060 --> 00:52:50,500
It's just that they're trying to do what corporations do.

646
00:52:52,100 --> 00:52:56,180
Yeah, so, you know, through this, I'm sure it's very stressful for you all at F-Droid

647
00:52:56,360 --> 00:52:58,180
and a lot of the people that you're close with.

648
00:52:59,280 --> 00:53:07,640
Who else have you kind of seen step up? And, you know, have there been any surprises behind the scenes or like people that you think are doing really good work right now?

649
00:53:08,840 --> 00:53:20,280
Yeah. So, you know, both as FDroid, we obviously communicate with the community, you know, civil society groups, government regulators and things like that.

650
00:53:21,540 --> 00:53:27,340
Also on the keepandroidopen.org site, we are putting up an open letter for people to sign.

651
00:53:28,450 --> 00:53:33,900
And we have quite a lot of people, of signatories that have committed to the open letter,

652
00:53:34,140 --> 00:53:36,980
essentially asking Google to just reverse this policy and not do it.

653
00:53:39,040 --> 00:53:45,780
I mean, opposition has been almost universal, both among the individual groups that we've encountered,

654
00:53:46,400 --> 00:53:53,520
among consumers who are sort of cognizant of the technologies around there, and developers.

655
00:53:53,960 --> 00:53:58,540
I mean, we really haven't seen anyone speaking up in support of this policy

656
00:53:59,440 --> 00:54:03,800
that has at least communicated through any forum whatsoever to us.

657
00:54:04,920 --> 00:54:05,980
I was actually a little bit surprised.

658
00:54:06,100 --> 00:54:10,080
I figured there would be at least someone, some industry group or something,

659
00:54:10,080 --> 00:54:12,100
who was like, no, we actually fully support this.

660
00:54:12,560 --> 00:54:18,880
know, we make banking apps or something and we think it'll be great and prevent scams and stuff.

661
00:54:19,560 --> 00:54:23,540
It's been dead silence. It's really only been Google themselves that has been trying to defend

662
00:54:23,680 --> 00:54:33,220
this and, you know, not very effectively in my view. Yeah. So, you know, what is still kind of,

663
00:54:34,200 --> 00:54:39,140
what still drives you, you know, day to day, given, you know, there is a lot of uncertainty

664
00:54:39,160 --> 00:54:46,660
perhaps in the next year or two. So is there anything that still excites you about this crisis,

665
00:54:47,520 --> 00:54:51,180
maybe outside of this crisis, just kind of how are you grappling with this personally?

666
00:54:52,560 --> 00:54:56,620
Yeah, well, I think a lot of excitement is that there's a lot more awareness than there had been,

667
00:54:56,860 --> 00:55:02,640
even a month or two ago about this. People who had not really even thought about ways of installing

668
00:55:02,660 --> 00:55:07,520
applications you know through the non first-party default you know promoted

669
00:55:07,580 --> 00:55:12,320
app stores are suddenly aware of you know not just F-Droid but of you know

670
00:55:12,400 --> 00:55:16,720
being able to just get apps directly you know it's really popular for things

671
00:55:16,880 --> 00:55:21,100
you know especially things like ad blocking which you know obviously is you

672
00:55:21,100 --> 00:55:27,860
know pretty pretty reduced in its presence in commercial app stores so

673
00:55:27,860 --> 00:55:31,620
that's been there's sort of been a surge of excitement you know around F-Droid

674
00:55:31,640 --> 00:55:33,600
and AlturaVap marketplaces.

675
00:55:34,120 --> 00:55:35,920
It's kind of like what they call the Streisand effect, right?

676
00:55:36,010 --> 00:55:41,340
It was only through, you know, coming out and attacking the project

677
00:55:42,060 --> 00:55:44,020
that, you know, we got, we started getting a lot of attention.

678
00:55:44,780 --> 00:55:45,740
So that's exciting.

679
00:55:45,850 --> 00:55:48,920
And the other exciting thing, I think, is that there's been, you know,

680
00:55:48,930 --> 00:55:51,800
a little more tension on the Apple side of things.

681
00:55:52,780 --> 00:55:55,540
As sort of a separate thing, separate from F-Droid,

682
00:55:56,240 --> 00:55:58,540
I've, over the past year or so,

683
00:55:58,740 --> 00:56:06,160
I've been consulting with various regulatory groups in Europe around the Digital Markets Act and how it should apply to Apple.

684
00:56:07,280 --> 00:56:14,400
And they are saying, well, it really isn't consistently applied between Google and Apple, and it ought not be because they are both designated gatekeepers.

685
00:56:15,400 --> 00:56:24,520
So, you know, I think, I hope that this will maybe open the opportunity for making a case that the Apple ecosystem should be opened up a little bit more,

686
00:56:25,020 --> 00:56:26,900
that there should be an F-troyd for Apple,

687
00:56:27,410 --> 00:56:29,820
and it should not just be constrained to, you know,

688
00:56:30,020 --> 00:56:32,580
one of the duopoly of mobile platforms out there.

689
00:56:34,380 --> 00:56:37,680
Yeah, and, you know, where do you see this potentially going?

690
00:56:37,860 --> 00:56:39,100
Like, do you think the fight's lost?

691
00:56:39,190 --> 00:56:39,900
Do you think it's won?

692
00:56:40,320 --> 00:56:41,440
What's kind of next?

693
00:56:43,199 --> 00:56:45,460
And assuming, you know, worst-case scenarios,

694
00:56:46,200 --> 00:56:47,980
I've seen this, I know this is a lot of questions,

695
00:56:48,350 --> 00:56:49,280
so I'll do my best.

696
00:56:51,600 --> 00:56:54,040
I've seen a lot of people talk about how this is actually

697
00:56:54,760 --> 00:56:57,920
a result of having only two operating systems.

698
00:56:58,260 --> 00:57:00,460
Kind of how I mentioned earlier, Linux just existing

699
00:57:00,790 --> 00:57:03,680
probably has a lot of indirect influence on the other ones.

700
00:57:03,770 --> 00:57:06,300
But there is no real Linux phone.

701
00:57:06,600 --> 00:57:07,720
You know, I know there's PinePhone.

702
00:57:07,770 --> 00:57:09,200
I know there's Librem 5.

703
00:57:09,350 --> 00:57:12,320
I know PostMarketOS.

704
00:57:12,400 --> 00:57:13,480
I know these things exist,

705
00:57:13,800 --> 00:57:15,340
but you already talked about the small percentage

706
00:57:15,620 --> 00:57:17,580
of these, like, alternative Android users.

707
00:57:18,040 --> 00:57:21,000
That's, you know, tiny, tiny, tiny, tiny, tiny.

708
00:57:21,520 --> 00:57:29,520
So do you think that's really something that needs to happen to be fully prevented in the future, for there to be a full ecosystem alternative?

709
00:57:31,740 --> 00:57:35,080
I don't know if that's a cohesive question, but I'll just let you.

710
00:57:36,080 --> 00:57:37,200
Yeah, I mean, definitely.

711
00:57:37,400 --> 00:57:40,100
I mean, the duopoly is essentially a monopoly right now.

712
00:57:40,680 --> 00:57:46,080
You know, you have two different corporate players located, you know, 10 miles from each other with essentially identical policies.

713
00:57:47,060 --> 00:57:51,860
And, you know, we're seeing a shrinking in the difference between these two platforms.

714
00:57:52,860 --> 00:57:55,140
And I think it is really, really harmful.

715
00:57:55,360 --> 00:58:01,380
There is no equivalent to, you know, Linux as a counterweight to the Windows and Mac OS, you know, desktop world.

716
00:58:03,220 --> 00:58:06,660
And, you know, we once upon a time, this was a thriving ecosystem.

717
00:58:06,860 --> 00:58:12,100
You know, you had Nokia, you had Symbian, you know, you had Palm OS and Windows Phone and BlackBerry.

718
00:58:12,360 --> 00:58:14,760
And, you know, you had all sorts of competitors.

719
00:58:15,300 --> 00:58:22,980
And, you know, I don't know if that was necessarily always considered to be a wonderful time, but it was at least a competitive and thriving, you know, marketplace.

720
00:58:23,820 --> 00:58:27,880
And now you have a system where basically the two entities have carved up the market.

721
00:58:28,140 --> 00:58:35,540
You know, Apple more or less takes a 30 percent high, you know, high margin ground and Google takes a 70 percent, you know, rest of it.

722
00:58:35,940 --> 00:58:39,380
And that's pretty much how it has been for the past, you know, five to 10 years.

723
00:58:41,200 --> 00:58:43,660
I do think that competitors need to emerge.

724
00:58:43,960 --> 00:58:47,180
And there are, you know, very interesting potential competitors.

725
00:58:47,360 --> 00:58:49,640
You know, there's, you know, do you even list some more?

726
00:58:49,780 --> 00:58:54,020
There's, you know, Sailfish OS, which is, you know, which is interesting.

727
00:58:55,420 --> 00:59:00,980
You know, there's a lot of potential, but to, you know, these are trillion dollar companies.

728
00:59:01,300 --> 00:59:08,500
And to go up against them, I really think you would need sort of a Manhattan project in order to really create and promote it.

729
00:59:09,040 --> 00:59:11,040
And there is one in China.

730
00:59:11,420 --> 00:59:12,460
It's called HarmonyOS.

731
00:59:13,380 --> 00:59:16,280
And they are, you know, forging forward with it.

732
00:59:17,480 --> 00:59:19,900
Unfortunately, it's just as locked down as those other platforms.

733
00:59:20,760 --> 00:59:26,100
And, you know, I doubt it's going to be seen as a great liberator for, you know, for the world.

734
00:59:26,700 --> 00:59:31,840
But they do provide an example of how with enough, you know, will and state sponsorship,

735
00:59:32,420 --> 00:59:38,660
you can essentially force through a, you know, third option, which is, you know, at least in China,

736
00:59:39,540 --> 00:59:40,780
I think is going to be an emerging

737
00:59:41,640 --> 00:59:41,740
competitor.

738
00:59:42,900 --> 00:59:44,220
Wow. Yeah.

739
00:59:45,780 --> 00:59:47,000
Well, that's the end of all my questions.

740
00:59:47,840 --> 00:59:49,060
The last thing, I just wanted

741
00:59:49,060 --> 00:59:51,160
to say this. It's not a question. It's just a statement.

742
00:59:51,500 --> 00:59:52,980
But this is something

743
00:59:53,140 --> 00:59:55,080
I've heard ever since

744
00:59:55,080 --> 00:59:57,100
I started using FDroid and Android

745
00:59:59,080 --> 01:00:00,900
way back in like 2017,

746
01:00:01,400 --> 01:00:02,820
2018. It's been forever now.

747
01:00:05,460 --> 01:00:07,240
But anytime I pick up

748
01:00:07,260 --> 01:00:11,840
an iPhone or I'm using an iPhone for work because I have to use different devices for different things.

749
01:00:12,540 --> 01:00:16,020
And I hear this from other people I know who have also gotten used to F-Droid.

750
01:00:17,220 --> 01:00:23,920
They say they love their iPhones, but the only thing that's missing is F-Droid. And yeah, so that's

751
01:00:24,180 --> 01:00:28,180
kind of a high praise that I think that I feel and a lot of people feel in my life. And I see it in

752
01:00:28,180 --> 01:00:33,880
our community all the time because there is no really open source ecosystem on the iOS side of

753
01:00:33,900 --> 01:00:39,040
things like there is on the Android side of things. So I just wanted to share a lot of appreciation

754
01:00:39,640 --> 01:00:44,180
that I have for you guys. Oh, great. Well, thank you so much. You know, it really is, we do this

755
01:00:44,480 --> 01:00:48,560
for the users, right? We're not getting paid. There's no money going through the project. It's

756
01:00:49,040 --> 01:00:54,620
really a labor of love and really comes from a belief that like, you know, when you bought a

757
01:00:54,800 --> 01:00:59,620
smartphone, you own it. It's your computer and you should be allowed to put whatever you want on it.

758
01:00:59,920 --> 01:01:02,540
It's just like any other, you know, owning anything else.

759
01:01:03,460 --> 01:01:09,380
And to be able to, you know, act as a counterweight to the forces that are trying to make you think otherwise,

760
01:01:09,840 --> 01:01:16,320
that, you know, are trying to assert that they actually own your device and they are able to reach down into it and do whatever they want.

761
01:01:17,220 --> 01:01:19,380
But, yeah, really, it's for the end users.

762
01:01:19,730 --> 01:01:26,780
And there are not that many other voices out there that are so purely oriented towards the consumer side of the marketplace.

763
01:01:28,120 --> 01:01:32,480
So, yeah, so hearing that, you know, always puts a tickle in my heart.

764
01:01:33,760 --> 01:01:33,900
Yeah.

765
01:01:34,090 --> 01:01:39,040
So, I mean, do you have anything else that you want to share with people before we log off?

766
01:01:40,540 --> 01:01:44,700
And how can people keep up with what's going on in a clean way?

767
01:01:45,200 --> 01:01:48,340
And then also if they want to follow you or F-Troid, what's the best way to do that?

768
01:01:49,300 --> 01:01:49,700
Yeah, definitely.

769
01:01:49,950 --> 01:01:54,660
So, you know, number one, I would say visit, you know, the F-Troid website, follow the blog.

770
01:01:55,100 --> 01:01:58,480
We have RSS feeds and, of course, social media, primarily on Mastodon.

771
01:01:59,720 --> 01:02:02,500
That's a great way to just sort of get in touch with the community.

772
01:02:03,420 --> 01:02:06,600
Obviously, installing F-Droid is a great thing to do if you have an Android phone.

773
01:02:07,320 --> 01:02:09,120
Look around and see if there's anything interesting.

774
01:02:10,020 --> 01:02:15,920
It's not exclusive to other app stores, so you can have it side by side with Google Play or the Samsung App Store or anything like that.

775
01:02:17,060 --> 01:02:22,560
That really helps because the more people that are aware of it, the more they spread the word,

776
01:02:23,100 --> 01:02:26,060
the more we can sort of, you know, fight back against some of these policies.

777
01:02:27,740 --> 01:02:28,820
So, yeah, so that would be the main thing.

778
01:02:28,930 --> 01:02:31,760
And then the other thing that you might want to consider is visiting, you know,

779
01:02:32,539 --> 01:02:36,680
keepandroidopen.org that has, you know, a variety of sort of concrete action items

780
01:02:37,300 --> 01:02:40,780
that people can take, and that will be updated with information about, you know,

781
01:02:40,920 --> 01:02:44,200
sort of the progress of this movement as time evolves.

782
01:02:45,200 --> 01:02:46,840
But I am actually optimistic.

783
01:02:47,030 --> 01:02:50,280
You know, I think, you know, as I said, overwhelming response,

784
01:02:52,320 --> 01:02:55,360
universal response in support of, you know,

785
01:02:55,500 --> 01:02:56,580
keeping this platform open.

786
01:02:57,180 --> 01:02:58,600
I think people are becoming more aware

787
01:02:58,650 --> 01:02:59,560
of why it's important.

788
01:03:00,260 --> 01:03:01,980
And so I have a good feeling

789
01:03:02,180 --> 01:03:03,520
that I think we'll have a good outcome.

790
01:03:05,040 --> 01:03:05,200
Awesome.

791
01:03:05,290 --> 01:03:06,360
Well, thank you for your time, Mark.

792
01:03:06,580 --> 01:03:07,800
I super appreciate it.

793
01:03:08,140 --> 01:03:10,380
And definitely go check out the links.

794
01:03:10,450 --> 01:03:12,140
I'll leave them down in the show notes for all of you.

795
01:03:12,780 --> 01:03:13,780
And I want to thank you for your time.

796
01:03:14,720 --> 01:03:15,620
Thank you so much for having me.

797
01:03:15,720 --> 01:03:16,020
It was great.

798
01:03:16,050 --> 01:03:16,620
It was great chatting.

799
01:03:17,280 --> 01:03:18,780
And that is Mark, everybody.

800
01:03:19,220 --> 01:03:21,020
I really liked this interview

801
01:03:21,020 --> 01:03:25,420
And I left feeling really inspired and I hope that you all felt the same way.

802
01:03:25,860 --> 01:03:29,700
If you want to take action, please go in the description and check out the sources that

803
01:03:29,700 --> 01:03:32,080
we have down there so that you can also help in the fight.

804
01:03:32,420 --> 01:03:36,380
And if you aren't going to do any of that, I at least hope that you all left this a bit

805
01:03:36,460 --> 01:03:41,120
more educated on the systems that kind of make up what your phone actually allows you

806
01:03:41,120 --> 01:03:41,540
to do.

807
01:03:41,780 --> 01:03:46,140
If you enjoy Techlor talks, it wouldn't be possible without our Techlorians who get access

808
01:03:46,160 --> 01:03:47,800
to exclusive perks and communities

809
01:03:48,300 --> 01:03:50,460
and also make it so that we can do this podcast

810
01:03:50,810 --> 01:03:52,800
free for the world and keep it growing

811
01:03:53,020 --> 01:03:54,780
so that it reaches more and more people.

812
01:03:54,990 --> 01:03:57,060
So check out how you can support us down below

813
01:03:57,610 --> 01:03:59,660
and I'll see you all next time on Techlore Talks.