Eu.faircode.email contains BugSnag, needs TRACKING antifeature

11

I sent him an email when I opened this topic (he has no issue tracker on github).

1 Like
12

If it’s opt-in (and FOSS of course), and it’s clear to the user what toggling it on means (so no “tricking-in” or “you must turn this on or feature X will stay disabled” – not that I would expect such from Marcel, so take this as “speaking generally”) it should be fine. That would be a clear declaration of consent.

13

This too https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-faq104

14

Did this now: Bugsnag is analytics by licaon-kter · Pull Request #159 · M66B/FairEmail · GitHub

15

Bugsnag is disabled by default and you’ll be asked if you want to enable it on first run. There is an info button which leads to this FAQ with detailed information about what Bugsnag does.

You could see error reporting as a form of Analytics, but in my interpretation it should be used for marketing to be called Analytics, which it isn’t. Tracking is in my idea even a step further and requires data to be sent not anonymously.

Bugsnag is disabled by default and explicitly opt-in, so there is no analytics and no tracking by default.

I like to be 100 % transparent, so I have changed the description to this:

Is this okay for everybody?

5 Likes
16

@M66B If you want to “appear” in F-Droid client “kiosk/new” opening screen, you need a /metadata in your repo root/ ; check simplified https://github.com/y20k/trackbook/tree/master/metadata ; there are other advanced metadata: check Auto-generate an app website based on Fastlane/F-Droid metadata

17

@oF2pks can you please check if this is correct?

GitHub

1024×500 186 KB

M66B/FairEmail

Open source, privacy friendly email app for Android - M66B/FairEmail

In particular, I am not sure if it is possible to use markdown in " *.txt files in the old, custom, F-Droid text-based format" (Build Metadata Reference | F-Droid - Free and Open Source Android App Repository)

Am I right that a pull request needs to be done to make this work?

18

Yes, to remove the current Description from the metadata, so it gets picked up, on the next app update, from your repo.

1 Like
19

Any chance to add screenshots as well?

20

Can you please take care of this?

21

Let’s first get this to work. I will add screenshots later.

22

Will do, asap. Thanks

23

I have just added images and screenshots as well.
I am curious how this is going to look!

2 Likes
24

FYI: FairEmail - use fastlane (0048cf3b) · Commits · F-Droid / Data · GitLab

25

Thanks!

I guess the meta data will be pulled on the next build?

The only doubt I have: is markdown supported in meta data?

26

IIRC, next index update, as 615 was already build.

Not quite, more like a subset of HTML, kinda like Google Play store, eg. Simple-Gallery/fastlane/metadata/android/en-US/full_description.txt at master · SimpleMobileTools/Simple-Gallery · GitHub → https://f-droid.org/en/packages/com.simplemobiletools.gallery.pro/

27

I have just removed all markdown from the full description.

28

But why not leave the links?

29

I like to keep the description the same as the Play store description.
At the bottom there is a link to the full GitHub description (with links).

30

You still miss metadata/en-US/ changelogs / to comply with new fdroid selection Files · master · F-Droid / Client · GitLab

@dosse91 , seems you can now soften your thread primary description ? If you have time, I have a running list of fdroid apks with so-called trackers or similar : CLI tool to check F-Droid apps with Exodus - #7 by oF2pks