Commit 34040740 authored by ByteHamster's avatar ByteHamster

Mention @slinger in my blog post

parent e20f7cdb
......@@ -15,7 +15,7 @@ This is a known problem, so Google published a library called `ProviderInstaller
This sounds too good to be true, doesn't it? Well, Google's `ProviderInstaller` has a pretty big drawback. The library is closed-source, so it can not be used for apps published on F-Droid. AntennaPod currently builds with two different flavors: one that is 100% free software for F-Droid and one with the `ProviderInstaller` library for the Google Play Store. This means that the F-Droid users are left behind. They still experience connection problems to some servers and consider this a bug in AntennaPod.
An alternative that works with F-Droid is to include the open-source library [`Conscrypt`](https://github.com/google/conscrypt/). Bundling `Conscrypt` with an app is just as easy as using Google's `ProviderInstaller` but it has two major disadvantages:
An alternative that works with F-Droid is to include the open-source library [`Conscrypt`](https://github.com/google/conscrypt/). Bundling the library in AntennaPod was first proposed by @Slinger in a [pull request for AntennaPod](https://github.com/AntennaPod/AntennaPod/pull/4077). While bundling `Conscrypt` with an app is just as easy as using Google's `ProviderInstaller`, it has two major disadvantages:
* App developers are forced to update the provider regularly. This is additional work for the maintainers and might cause trouble with apps that have a slow development cycle.
* Bundling `Conscrypt` increases the apk size. In case of AntennaPod, this means that the app gets around 4 MB bigger, which is a 40% increase just for this mostly invisible change. Now consider that every app would have to do that in order to get an updated TLS stack. If every app on F-Droid that deals with networking needs to bundle additional 4 MB of TLS libraries, this would increase storage usage noticeably.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment