Add Recent Releases to homepage / FAQ

[Hyacinthe Cartiaux]

It would be great to have gpg signed releases hosted on eff.org in the same way as https everywhere.

In example, for https everywhere, we can use the following URLs and signatures in the Archlinux PKGBUILD on AUR:

source=("${_pkgname}-${pkgver}.xpi::https://www.eff.org/files/https-everywhere-${pkgver}-eff.xpi"
        "${_pkgname}-${pkgver}.xpi.sig::https://www.eff.org/files/https-everywhere-${pkgver}-eff.xpi.sig")
validpgpkeys=('1073E74EB38BD6D19476CBF8EA9DBF9FB761A677') # William Budington

Do you think it will be possible in the future or is it already done ?

Thank you very much

[Alexei]

This should be already be the case ... For example:

• https://www.eff.org/files/privacy-badger-eff-2017.11.20.xpi.sig
• https://www.eff.org/files/privacy-badger-eff-2017.11.20.xpi

Regarding valid PGP keys: I've been signing releases for a few months now; older releases are signed by other keys.

Let me know if you have any other questions.

[Eli Schwartz]

Thanks, it wasn't immediately apparent that the naming pattern differed from https-everywhere by having "eff" before the version rather than after. And the only file linked from https://www.eff.org/privacybadger is a "latest" file that doesn't redirect to the stable filename, so it doesn't seem to be very discoverable. 😄

[Alexei]

I suppose we could have a "recent releases" section somewhere on Privacy Badger's homepage, similar to the one on HTTPS Everywhere's page.

[Alexei]

Previously, from a user email:

On the page, like HTTPS Everywhere has download links. For sysadmin
deployment from a local repository, for technicians supporting multiple
browsers, and for unsupported browsers to download them to install in
supported browsers.

Add version number to extension and provide a few older versions for
compatibility.

[Alexei]

We could just add a note about older versions to the FAQ, maybe to https://privacybadger.org/#Can-I-download-Privacy-Badger-directly-from-eff.org