Sync History
Manage and restore your bookmark history versions, ensuring data security and traceability
🚀 Sync History Overview
The sync history feature is a core data management function of Bookmark UniSync, providing you with:
- 📝 Automatic Recording - Every bookmark change automatically generates a history record
- 🔄 Version Tracking - View bookmark status of all historical versions
- 💾 Permanent Save - Mark important versions for permanent preservation
- ⏮️ One-Click Restore - Quickly restore to any historical version
📍 Feature Location
- Click the Bookmark UniSync extension icon in the upper right corner of the browser
- Find the "Sync History" option in the main interface
- Click to enter the history record management page
📋 Formation of History Records
🔄 Automatic Sync Records
Every time the following operations are performed, a history record is automatically generated:
| Operation Type | Trigger Condition | Record Content |
|---|---|---|
| 📝 Modify Bookmark | Edit existing bookmark title, URL or folder | Complete bookmark list before and after modification |
| ➕ Add Bookmark | Add new bookmark or folder | Complete bookmark list including new items |
| 🗑️ Delete Bookmark | Delete bookmark or folder | Complete bookmark list before deletion |
| 📁 Move Bookmark | Adjust bookmark position or belonging folder | Complete bookmark structure after moving |
🔧 Manual Upload Records
| Operation | Trigger Method | Record Characteristics |
|---|---|---|
| 📤 Manual Upload | Click "Upload" button | Marked as manual operation for easy identification |
| 🔄 Force Sync | Manually trigger sync | Ensure local and server consistency |
Automatic Sync Advantages
- Real-time Protection - Every change is immediately synced to the cloud
- Zero Operation Burden - No manual recording required, system handles automatically
- Complete Preservation - Each version contains complete bookmark structure
💾 Historical Version Operations
🔒 Permanent Save Function
Significance of Save Operation
- 🛡️ Prevent Automatic Cleanup - Permanently saved versions will not be automatically deleted by the system
- ⭐ Important Marking - Easy to identify bookmark status at key moments
- 📊 Long-term Backup - Provide guarantee for long-term data retention
⚠️ History Record Quantity Limitation
📊 Record Storage Rules
The system has clear limitations on history record storage:
- 🔢 Total Records - Keep only the most recent 10 history records
- 📋 Coverage Range - Includes both permanently saved and unsaved versions
- 🔄 Automatic Cleanup - When exceeding 10 records, the earliest records will be automatically deleted
Important Reminder
Only 10 permanent save history records!
- The most recent 10 history records include both permanently saved and unsaved versions
- Unsaved versions plus permanently saved versions total only 10
- When an 11th record is generated, the earliest non-permanently saved record will be automatically deleted
🎯 Impact and Strategy
| Impact Factor | Description | Response Strategy |
|---|---|---|
| 📅 Time Progression | New records automatically replace old ones | Save important versions promptly |
| 💾 Save Status | Permanent saves are not cleaned up | Regularly check and re-save |
| 🔢 Quantity Limitation | Server hardware condition limitations | Carefully choose save timing |
| 🔄 Automatic Override | Cannot prevent automatic cleanup | Save important versions promptly |
📋 Management Recommendations
- 🎯 Selective Saving - Only save truly important versions
- 🔄 Timely Operation - Save important nodes immediately to avoid being overwritten
When to Use Save Function
| Scenario | Recommended Action | Reason |
|---|---|---|
| 🎯 Important Nodes | After completing major project organization | Mark work milestones |
| 🔄 Before System Upgrade | Before browser or system updates | Prevent accidental data loss |
| 📱 Device Replacement | Before and after device changes | Ensure complete data migration |
| 🎉 Special Moments | After collecting important resources | Permanently save precious resources |
Save Operation Steps
-
📍 Enter Sync History Page
- Select "Sync History" in the extension main interface
-
👁️ Browse History Records
- View timestamps and change descriptions
- Find the version that needs to be saved
-
💾 Execute Save Operation
- Click the "Save" button of the target version
- Enter a meaningful tag name in the pop-up dialog box
- Confirm the save operation
- Check save status identifier
🏷️ Save Record Naming Function
📝 Importance of Naming
Adding meaningful names to saved history records can:
- 🎯 Quick Identification - See the characteristics and purpose of the version at a glance
- 📊 Classification Management - Organize versions by project, time or purpose
- 🔍 Easy Search - Quickly find specific versions through keywords
- 💡 Memory Assistance - Help recall the background when the version was created
🏷️ Naming Suggestions and Examples
| Naming Strategy | Example | Applicable Scenarios |
|---|---|---|
| 📅 Time + Event | "2024-11-29 Project Organization Complete" | Daily important nodes |
| 🎯 Project Name | "Q4 Financial Report Bookmark Collection" | Specific project resources |
| 📱 Device Identifier | "MacBook Work Environment Backup" | Multi-device management |
| 🔄 Status Description | "Safe Backup Before System Upgrade" | Save before changes |
| ⭐ Importance Marking | "[Important] Customer Resource Bookmarks" | Key resource marking |
📝 Naming Operation Steps
-
📍 Trigger Save Function
- Click the "Save" button in the history record list
-
💬 Enter Naming Information
- Enter a meaningful tag in the pop-up dialog box
- Recommend using concise and clear descriptions (10-30 characters)
- Can include time, project or status information
-
✅ Confirm Save
- Click "Confirm" to complete saving and naming
- System will display save success prompt
- New name will be displayed in the history record list
Naming Best Practices
- 🎯 Specific and Clear - Avoid vague names
- 📅 Include Time - Facilitate sorting and searching by time
- 🔤 Use Separators - Use spaces or hyphens to improve readability
- ⭐ Importance Marking - Use special marks for key versions
Advantages When Restoring
When needing to restore a specific version, meaningful names can help you:
- 🎯 Quickly identify target version
- 📊 Understand version creation background
- 💡 Avoid restoring wrong version
- 🔄 Improve work efficiency
⏮️ Version Restore Function
Effect of Restore Operation
- 🔄 Complete Replacement - Current bookmarks will be completely replaced by the selected historical version
- 📁 Structure Restoration - Including folder structure and bookmark positions
- ⚠️ Irreversible - The restore operation itself will also generate a new history record
Preparation Before Restore
| Check Item | Operation Description | Importance |
|---|---|---|
| 📋 Current Backup | Confirm current status has been automatically synced | 🔴 Required |
| 🎯 Target Confirmation | Carefully check target version content | 🔴 Required |
| 📱 Device Status | Confirm other devices have synced | 🟡 Recommended |
| 🔌 Network Connection | Ensure stable network | 🟡 Recommended |
Restore Operation Steps
-
📍 Select Target Version
- Find the version to restore in the history list
- Can quickly identify through custom names
-
⏮️ Execute Restore Operation
- Click the "Restore" button
- Confirm restore operation
- Wait for system processing to complete
-
✅ Verify Restore Result
- Check current bookmark status
Quick Restore Based on Name
If the version is named, you can quickly find the target version through the following methods:
- 🏷️ Tag Identification - View naming of corresponding version by hovering over description
Restore Notes
- ⚠️ Current Status Lost - Restore will overwrite current bookmark status
- 📱 All Device Impact - All logged-in devices will sync to restore status
📊 History Record Management
📈 Record List Information
Each history record contains the following information:
| Information Item | Description | Purpose |
|---|---|---|
| 🕐 Timestamp | Record time accurate to the second | Sort and search by time |
| 🏷️ Custom Name | Tag name set when saving | Quickly identify version purpose |
| 💾 Save Status | Whether permanently saved | Identify important versions |
🛡️ Data Security Best Practices
💾 Important Version Save Strategy
| Scenario Type | Save Frequency | Save Standard |
|---|---|---|
| 📊 Daily Work | Save once a week | Select the most complete organized version |
| 🎯 Project Period | Save once a day | Save阶段性成果 |
| 🔄 System Changes | Save before and after changes | Ensure safe data transition |
| 📱 Device Management | Save when switching devices | Mark device status nodes |
⚠️ Restore Operation Safety Guide
Restore Checklist
- 📋 Confirm current status has been synced
- 🎯 Verify target version content is correct
- 📱 Notify other device users
- 💾 Consider saving current status first
- 🌐 Ensure stable network connection
Emergency Handling
| Emergency Situation | Handling Method | Preventive Measures |
|---|---|---|
| 🚫 Restored Wrong Version | Immediately find correct version and restore again | Carefully preview before restoring |
| 🔄 Some Devices Not Synced | Manually trigger sync or restart extension | Regularly check device status |
| 💾 Important Version Not Saved | Find recent history record to save | Develop regular saving habits |
| 📱 Device Lost | Restore latest save from any device | Regular multi-device backup |
❓ Frequently Asked Questions
| Question | Solution |
|---|---|
| 📅 Too many history records | System will automatically clean up unnecessary records |
| ⏰ Can't find records for specific time point | Hover over saved records to view naming when saved |
| 💾 Is there a limit to the number of saved versions | Maximum 10 history records, including both permanently saved and unsaved versions |
| 🔄 Other devices not updated after restore | Check network connection, manually trigger sync |
| 📱 Will simultaneous operations on multiple devices cause conflicts | System automatically handles conflicts, later operations form new records |
| 💾 Accidentally saved unimportant version | Can ignore, or delete and re-save correct version |
| 🔢 Important history records automatically deleted | System only keeps most recent 10 records, recommend regularly backing up important versions |
🔗 Related Links
- 📖 Installation Guide - How to install extension
- 📝 Registration Guide - Create account
- 📤 Upload Function - Manual bookmark upload
- 🗑️ Delete Local Bookmarks - Clean up local data
- 📧 Contact Us - Get technical support
Professional Tip
Rational use of sync history function can make your bookmark management more secure and orderly. It is recommended to develop the habit of regularly saving important versions, so you can quickly restore to the ideal state when needed.