Floccus

Configuration

• On Firefox, always choose the root of synchronization to be equal to the Bookmarks Toolbar folder. Else it won't work - Firefox does not have permission to create subfolders in the "actual" root folder.
• For a new device, it's much safer to choose a manual synchronization and only the pull option (no merge synchronization; data on Google drive remains untouched).

Profiles

• Floccus supports different types of backend storage profiles: for instance the Nextcloud Bookmarks API, WebDAV (can be used with Nextcloud), or Google Drive.
• The Nextcloud Bookmarks profile will store your bookmarks in the Nextcloud database (usually MySQL). The implementation of the synchronization is very slow and buggy (especially with a locking feature that does not work correctly). See the troubleshooting section for information on how to debug issues with this profile, but it's recommended to not use it at all.
• The Google Drive profile is not recommended either.
• So the best choice appears to be the Nextcloud WebDAV profile. In short, it will create a .xbel file on your shared files space in Nextcloud. Devices will read this file, merge it with local bookmarks and potentially reupload the resulting file to the server.

Troubleshooting

• Often, if you run into issues (a browser not able to synchronize correctly), the easiest way is just to remove all bookmarks on the target device/browser, then reissue a pull which will recreate all bookmarks from the latest version on the server. This seems to happen a lot, especially with Firefox.
• This method is quick and if you don't have any bookmarks on the target browser that might be not saved in the main instance, this is perfectly safe.
• To debug what happens when Floccus runs a synchronization, you can inspect the worker of the extension. It will open a developer console / developer tools, where you can check network requests for instance. Look out for 423 HTTP return codes, failed POST/PUT requests, etc.