Skip to content

xBrowsersync disabled due to lack of statement on use of user data #506

Open

Description

@PhilaBurger

Describe the issue you are experiencing
Chrome has disabled the xBrowsersync extension. The Chrome store lists it as non supported because "This extension is no longer available because it doesn't follow best practices for Chrome extensions." and recommends its removal.

How can the issue be reproduced?

1.Open up the extension manager and see that the extension is disabled and can not be enabled.

Screenshots

Image Image

Desktop browser
Please complete the following information for all affected desktop browsers:

  • OS: Mac Sonoma 14.7.4
  • Browser Chrome
  • Version 133.0.6943.142 (Official Build) (x86_64)

Application log
No log available, as the application won't start.

Activity

  1. joel-bd commented on Mar 7, 2025

    @joel-bd

    I ran into this, too. I believe that it's not a problem with a statement on userdata so much as chrome dropping support for manifest v2 and pushing everyone to switch to manifest v3.

  2. PhilaBurger commented on Mar 7, 2025

    @PhilaBurger
    Author

    Hopefully, the devs can get that migrated and republish the app, so we can start using it, again?

  3. clecap commented on Mar 7, 2025

    @clecap

    Me too...

  4. DawidKrysiak commented on Mar 10, 2025

    @DawidKrysiak

    you can very easily use it now.
    Download the latest zip file, unzip it, in chrome's extensions manager select 'Load Unpacked'.
    Yes, google will warn you all the time and even try to disable the extension every now and then, but it is, quite frankly, hilarious for a company like Google to release a warning about other people's behaviours.

  5. PhilaBurger commented on Mar 10, 2025

    @PhilaBurger
    Author

    Per

    you can very easily use it now. Download the latest zip file, unzip it, in chrome's extensions manager select 'Load Unpacked'.

    Perhaps...but it's a wee bit of a hassle

    Yes, google will warn you all the time and even try to disable the extension every now and then, but it is, quite frankly, hilarious for a company like Google to release a warning about other people's behaviours.

    Perhaps, but if one is going to write apps for a platform and accept that platform's terms of service, one must continue to abide by those terms of service if they wish to continue to work in that platforrm, yes?

  6. DawidKrysiak commented on Mar 10, 2025

    @DawidKrysiak

    @PhilaBurger , I am not telling you what to do, I am just giving you a solution that requires 1 minute of your time to resolve the issue , until it's resolved (if at all) in the chrome web store. You do you, I have no problem with unzipping a file. My biggest issue is with google now, as they keep switching off the plugin.

    update: the reason I said "if at all" is because this plugin was flagged by Google for a very long time, now they try to remove it from our browsers for days and I see no movement from the project.

  7. malins commented on Mar 28, 2025

    @malins

    This whole project looks unmaintained as of now. Last commit 3 years ago.

  8. DawidKrysiak commented on Mar 28, 2025

    @DawidKrysiak

    This whole project looks unmaintained as of now. Last commit 3 years ago.

    yes. I am tempted to fork this and start working on AWS integration - I wish to use my own, secure storage for the bookmarks. AWS is cheap as dirt.

  9. paschalis-mpeis commented on May 16, 2025

    @paschalis-mpeis

    Unfortunately the project seems to be dead. I've switched to floccusaddon/floccus, which seems to do a quite good job.

  10. PhilaBurger commented on May 23, 2025

    @PhilaBurger
    Author
  11. natpicone commented on Mar 18, 2026

    @natpicone
    Collaborator

    👋 Hi! I wanted to let the community know that I'm actively working on resuming maintenance of this project.

    xBrowserSync is one of the few simple, privacy-respecting, open-source tools for syncing bookmarks across different browsers — and I think it's worth keeping alive.

    My current priorities are:

    1. Manifest V3 migration — to restore the Chrome extension
    2. Critical data-loss bugs — sync overwriting / deleting bookmarks
    3. Other open issues — based on community votes and impact

    Thank you for your patience and continued interest. Your reports are not going unheard. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugprivacyPrivacy or security concern

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions