violentmonkey / violentmonkey/violentmonkey

[Feature] Sync in current Firefox container

Open
#1,658 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement sync
Dominant language
JavaScript
Stars
8.9k
Forks
759
Avg merge
1d 2h
Merged PRs (30d)
3

Description

Motivation
Syncing to Google / DropBox / any online service never worked for me and never will because I use containers for sessions separation and it's impossible (I think) to tell Violentmonkey which container to use when making a backup. When I hit "authorize" button it always opens a sign-in page in the default container where I'm never logged in (and can't be for security reasons).

Proposed Solution
It'd be awesome if Violentmonkey just synced scripts and settings to Firefox Sync like some other Firefox plugins do. Firefox Sync doesn't share its session with websites so it's cross-site attack immune by definition and doesn't care for containers. Implementation might not be trivial because it seems not every aspect of it is properly documented, as stated in Mozilla wiki:

Build a Sync engine (if you need to sync more than just preferences). If you need this, please drop by the #sync channel in IRC so you can chat with a Sync developer (there are some important details not currently captured formally in any docs).

Use Cases
Because of the above, as a user who was making ZIP backups manually (actually by a cron-triggered JS script) and lost them today due to carelessly executed bleaching/privacy software (same would happen if a local ZIP file became unreadable for whatever reason), I'd like Violentmonkey to keep a backup in the cloud (preferably by default) making such cases less of a disaster.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing authorize flow mentioned in the issue and read Mozilla's Add-on Sync documentation linked there. Determine the scope of scripts and settings that must sync through Firefox Sync, then define how successful backup, restoration, and Firefox container behavior would be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.