Repository navigation
Focus HistoryHub on history collection - #91
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HistoryHub provides Bilibili history collection, Chrome history synchronization, and searchable paginated history views. The interface has three destinations: Bilibili history, browser history, and connection/login settings.
Collection saves Bilibili results to the existing JSON and SQLite stores. One sync action handles initial retrieval and subsequent updates, while local records remain readable without an active Bilibili login. Chrome synchronization and its token boundary are unchanged.
Download, media, interaction, analysis, notification, scheduling and MCP code and dependencies are removed. README and packaging describe and build the retained history functionality. Existing history databases and deletion markers are preserved.
Validation: Python, JavaScript, Vue, configuration and import-reference static checks passed. CI validates backend module loading, the frontend production build and both container builds. No real platform account or browser history is used for validation.