Option to disable Facebook SDK integration

I have a suggestion related to HTML5 builds. Amidst the whole Facebook controversy thing, would it be possible to include a toggle (or detect whether the game is making use of FB APIs) that disables the part of dmloader.js which links to Facebook’s SDK? It’s not a big issue as I imagine most privacy-conscious people probably run add-ons that disable such scripts regardless, but I feel it would be a welcome addition. :slight_smile:

1 Like

You should be able to use an app.manifest file to exclude Facebook and other parts of the engine that you don’t use.

# App manifest generated Fri Apr 13 2018 23:22:07 GMT-0700 (Pacific Daylight Time)
# Settings: Facebook,Release
platforms:
    x86_64-osx:
        context:
            excludeLibs: ["engine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["engine_release"]

    x86_64-linux:
        context:
            excludeLibs: ["engine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["engine_release"]

    js-web:
        context:
            excludeLibs: ["engine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["engine_release"]

    x86-win32:
        context:
            excludeLibs: ["libengine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["libengine_release.lib"]

    x86_64-win32:
        context:
            excludeLibs: ["libengine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["libengine_release.lib"]

    armv7-android:
        context:
            excludeLibs: ["engine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["engine_release"]

    armv7-ios:
        context:
            excludeLibs: ["engine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["engine_release"]

    arm64-ios:
        context:
            excludeLibs: ["engine"]
            excludeSymbols: ["FacebookExt"]
            libs: ["engine_release"]


https://britzl.github.io/manifestation/

3 Likes

Thanks for the workaround!

Are there plans to make Facebook opt-in, rather than opt-out if/once it becomes a native extension?

The system with app manifest files could and probably will be much more refined in the future. You could imagine something like a set of checkboxes in game.project or similar. We are also discussing how to lift out certain parts of the engine such as IAP, push and Facebook into public native extensions.

4 Likes