Proprietary components

[IzzySoft]

Proprietary components

[IzzySoft]

I think opt-in is coming. Should be easy to implement.

I guess so. Once it's there in a new release, please let me know and I drop the Tracking AF.

As for the other part: 🤞

[alessioC42]

This is a pretty cool tool.

Edit: you might wish to mention the opt-in with the app description in the "Data protection" ("Datenschutz") section.

Gonna do that.

Thanks for your help!

[alessioC42]

Yes, that is the plan. Crashlytics is not necessary for the app to run, but it is very necessary for the development, as it is an app for a reverse-engineered website with SSR. I will be adding a "non-crashlytics" build soon.

[alessioC42]

@IzzySoft
As you already saw on the Gitlab RFP issue I am changing to an self hosted version of Countly, since my server is not able to handle an Sentry instance. Naming conversion will stay the same.

[IzzySoft]

And in the long run you might evaluate a (self-hosted) Sentry I've heard. LK already linked you to my snippet for that. Glad to read, so my decision to keep it up was right. Though I was considering just to switch back to the previous release and disable updates until solved. Might have been better, so nobody gets Crashlytics in "by accident" and feel annoyed…

Please give me a ping then when the new variant is available, and let me know what naming patterns you intend to keep the two apart – so I can tell my updater which one to grab and which one to ignore. Wish you easy implementation of that!

[IzzySoft]

Will Countly be opt-in – or is it enabled by default? I see Crashlytics is gone with the latest release, congrats! GMS and Firebase are still there. Overlooked – or is there a reason they must remain?

[alessioC42]

Countly is enabled by default in the application.
GMS and Firebase are still there?
I think the Countly SDK might be the problem. (doc);
Apparently Countly also supports push notifications via Firebase and GMS. I do not use these features in my application and would like to remove them if possible. I am not sure if this is possible with the Countly SDK yet. I will have to check tomorrow.

[IzzySoft]

Ah, I see – yeah, I was suspecting something along those lines but wasn't sure what library it might be. There might be some tricks along these lines, using gradle's excludeGroup, but not being an Android dev myself I cannot tell.

Oh, and mind making analytics opt-in? You could e.g. initialize it with NULL – and when it's NULL ask in the onboarding activity. Plus give an option in settings to re-decide. With that, I could drop the Tracking anti-feature then.

[alessioC42]

I think opt-in is coming. Should be easy to implement.

I have no idea how Gradle works. I have to find out. But I think it should be possible too.

[alessioC42]

It turns out that Countly has a Flutter SDK without GMS and Firebase. On pub.dev it is listed way below the normal package list, and I did not find anything about it in the docs. Long story short: GMS and Firebase are out.

Also Countly is now opt-in.

I guess since Countly is also not in your snippet as "approved" that I leave the issue closed for the Gitlab RFP repo?

Another question just out of interest: How did you find the project? Do you have a web crawler that lists potential projects for you, or did someone contact you?

[IzzySoft]

Confirming all offenders gone – anti-features are removed (effective with the next sync in less than an hour), thanks & congrats!

Edit: you might wish to mention the opt-in with the app description in the "Data protection" ("Datenschutz") section.

Snippet updated as suggested: Countly now is in the "approved" section with a footnote for the details.

Do you have a web crawler that lists potential projects for you

Also one for GitLab and one for Codeberg. And there's always my issue tracker where people can suggest apps to be included. Those who cannot do so on GitLab sometimes send me suggestions via mail or DM to my Fediverse account at floss.social.