mintycactus,
@mintycactus@lemmy.world avatar

deleted_by_author

  • Loading...
  • Retiring,
    @Retiring@lemmy.ml avatar

    This says it only detects chrome extensions, so I am not surprised it doesn’t detect your Firefox extensions. Why do you say that Firefox won’t leak extensions at all? Do you have a source for that?

    mintycactus,
    @mintycactus@lemmy.world avatar

    deleted_by_author

  • Loading...
  • Atemu, (edited )
    @Atemu@lemmy.ml avatar

    The way it’s written doesn’t say whether it simply isn’t made to work for Firefox or whether it couldn’t be made to work for Firefox. Fortunately, the latter appears to be the case.

    ReveredOxygen,
    @ReveredOxygen@sh.itjust.works avatar

    if you click read more, it mentions that it can’t be made to work with firefox

    Atemu,
    @Atemu@lemmy.ml avatar

    Detecting extensions using web accessible resources is not possible on Firefox as Firefox extension ID’s are unique for every browser instance. Therefore the URL of the extension resources cannot be known by third parties.

    and also for Chrome:

    in manifest v3 extensions will be able to enable ‘use_dynamic_url’ option, which will change the resource URL for each session (browser restart). This will render this detection method unusable.

    Though it should be noted that this method isn’t the only way to detect extensions.

    TCB13,
    @TCB13@lemmy.world avatar

    But there is no easy way to detect all extensions, instead most popular ones

    It doesn’t really matter if its easy or hard, I’m sure Google already has automated processes in-place to detect all extensions published to the store and fingerprint browsers. They might even have the same for Firefox extensions, who knows.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • privacy@lemmy.ml
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #