• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: September 9th, 2023

help-circle

  • pirat@lemmy.worldtoF-Droid@lemmy.mlShowly
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    The reason could be that Trakt integrates with media server apps like Jellyfin or Plex, or apps like Kodi, and that you can thereby bring your watch history with you across apps and you don’t lose it if your server crashes, library is corrupted or something… I have never used it, but I’d imagine that’d be a reason to use it. If I knew of a libre alternative, I’d actually consider using it for Jellyfin.


  • pirat@lemmy.worldtoF-Droid@lemmy.mlLauncher Kvaesitso
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    3 days ago

    No idea why, but I don’t see their comments anywhere in this thread. Thanks for confirming.

    EDIT:

    I found this metadata file, is that the one?

    https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/de.mm20.launcher2.release.yml

    From the file:

    MaintainerNotes: |- Kvaesitso uses several external APIs for search providers. Several of them require signing up to obtain a developer API key: gdrive search, openweathermap, HERE and Meteorologisk institutt. It’s not possible for users to provide these keys as explained here: https://github.com/MM2-0/Kvaesitso/issues/227#issuecomment-1366826219 If keys are not provided, these features are automatically disabled during the build.

    core/shared/build.gradle.kts and plugins/sdk/build.gradle.kts have configurations in them for publishing artifacts to maven repos. They are not used during the build, but detected by F-Droid scanner anyway. We patch it out from core/shared/build.gradle.kts, since this module itself is still used in compilation, and delete plugins/sdk/build.gradle.kts because it’s not used in app compilation.

    Kvaesitso depended on different libraries used for gdrive login in the past that pulled GMS dependency, however it’s not the case anymore:

    https://github.com/MM2-0/Kvaesitso/issues/583#issuecomment-1775268896 The new libraries pull OpenTelemetry though, but it’s unclear if it’s used (considering gdrive integration is disabled).

    Max heap size is reduced in gradle.properties to avoid gradle daemon being killed by OOM manager.

    Older versions of Kvaesitso had onedrive integration that depended on non-whitelisted maven repos, but it was removed.

    Upstream provides an fdroid flavor, however there’s no difference with default flavor except for different versionName.

    For some reason, F-Droid fails to pick up the correct gradle version from distributionUrl if subdir is used.

    It seems to be the case that F-Droid removes gdrive and onedrive in their build. Though, there seem to be no mentions of Wikipedia.



  • This app promotes or depends entirely on a non-free network service

    When viewing the app in F-Droid, the note below this part tells, that it uses a third-party service for currency exchange rates.

    I don’t know if the fact that it can show Wikipedia results, and that you can connect it to your Google account (to show cloud files from Drive and such in the search results) plays a role too, but it isn’t specifically mentioned under the anti-features… On a sidenote, searching your own Owncloud or Nextcloud is supported too.




  • I thought it was supposed to be an infinite amount of monkeys, since it’s known as “infinite monkey theorem”, but apparently, according to Wikipedia,

    The infinite monkey theorem states that a monkey hitting keys at random on a typewriter keyboard for an infinite amount of time will almost surely type any given text, including the complete works of William Shakespeare. […]

    […] can be generalized to state that any sequence of events that has a non-zero probability of happening will almost certainly occur an infinite number of times, given an infinite amount of time or a universe that is infinite in size.

    However, I think, as long as either the timeframe or monkey amount is infinite, it should lead to the same results. So, why even limit one of them on this theoretical level after all?

    The linked study even seems to limit both, so they’re not quite investigating the actual classic theorem of one monkey with infinite time, it seems.