Alert for my #TKCompanionApp: a user has found an unauthorised copy on Google Play: play.google.com/store/apps/det…
That is NOT my app!! It's could be modifidd from the original in an unknown way, and surely a #FOSS #copyright #violation!
My app is _only_ available through @fdroidorg at f-droid.org/en/packages/name.b… or you can download F-Droid-signed APKs from @Codeberg (codeberg.org/marco.bresciani/T…) or the GitHub mirror: github.com/marcoXbresciani/TKC… and nowhere else.
BE CAREFUL!!
in reply to dorotaC

@dcz Sure the GPL would allow them publishing without credits and without mentioning the license? And if you say "that could have been inside the app", I tend to disagree (IANAL, though) as those facts should be clear WITHOUT having to run the software. Just look at the screenshots they post along with their listing. Or as Google asks for screenshots, I'd send the very same just made from the original app, @AAMfP
in reply to Marco Bresciani

Quick check via Appbrain's interface (appbrain.com/app/name.brescian…):

* APK is smaller than yours (22 MB vs. 25 MB)
* no permissions; if that's true certainly no ads/trackers added
* list of used frameworks/libraries available so you can compare
* a look at their other apps: seems they publish a lot of other FOSS apps which are (like Mucke) either at F-Droid or in my repo

Unfortunately only a Gmail contact given. Maybe ask what they're up to and whether they'd give credits in descs?

@dcz

in reply to Marco Bresciani

@dcz from the list I got the impression they added FOSS apps which intentionally were not present at Play – just because they wanted them there. Well, we could notify the other authors with your findings and experience so they could take action if they wanted.

There are reasons why one chooses NOT to put an app into that walled garden. And I somehow doubt that support requests to the address specified their would be processed – but who knows…

in reply to IzzyOnDroid ✅

From github.com/marcoXbresciani/TKC…

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;

- - -

The app listing is not a copy. You can write anything you want there. Plus, if they modified it, then they are the authors, too.

in reply to dorotaC

@dcz Also read section 6 (codeberg.org/marco.bresciani/T…). a+b do not apply here as it's no "physical copy", which leaves c-e as options – which all require to include a copy of the code or to tell where it is, separately from the "object code". That's at least as I would read it 🤷‍♂️ IMHO e) would apply here, which includes "provided you inform … where the object code and Corresponding Source of the work are being offered".
in reply to dorotaC

@dcz And I don't have a Google account, nor any Google stuff on my devices (for years I run as Google-free as I can).

But that said, first thing I'd do is take a look at the size. Just had it recently with another app: size at Play was twice the original. Usually those plagiators add some trackers & ad modules. Also compare permissions, which give a clue on the same line (changes being made) @AAMfP