I want a Import browser history plugin, and a robot plugin to auto import daily

#1

I have this usage in mind: Sometimes I put a keyword in the search box of the browser, and i found I have visited this before in the browser history, like this:

截屏2023-02-23 15.29.39
截屏2023-02-23 15.29.39934×411 24 KB

So if i want to trait TW as my single source of truth, I have to import the history from browser to tw. Maybe as JSON tiddler, one tiddler for a month of history.

This is easy because I have written a GitHub - linonetwo/zazu-firefox-bookmarks: Firefox bookmark searcher for Zazu. before. I just would like to know if someone had done this before.

One tricy thing is run this daily, maybe based on cronjob “0 0 * * *” , I don’t know if there is existed plugin for this. And if my wiki is not opened in browser, how to resume task once I open the wiki.

#2

I can use $:/tags/StartupAction/PostRender to build a task runner, that can auto import data to tw after wiki starts. [IDEA] Delay the backlink indexer · Issue #7277 · Jermolene/TiddlyWiki5 · GitHub

#3

We did remove the $:/HistoryList tiddler because it can be huge, if users do not close the browser for several months. Which caused the initial problem, why we removed it.

There are 3 tiddlers that use a filter to prevent the $:/HistoryList from saving.

  1. $:/config/SaverFilter
  2. $:/config/SyncFilter
  3. $:/core/save/all
  1. is responsible for the wiki dirty-status
  2. Will be of interest for you with Node.js
  3. Is the configuration to save a single file wiki
#4

Ok, You mean this imported browser history can be more huge than $:/HistoryList tiddler and cause problem.

This can be part of the tiddler 10k (or even 100k) problem that awaits for me to solve…

#5

It’s the same thing. I was just lazy to type the system prefix $:/ for the second tiddler title again. Sorry if that caused confusion.

It did cause problems so it was removed in beta-14 … You can search around in the commit history … There may be some issues around this time in 2014.

#6

A task runner plugin already exists, GitHub - inmysocks/TW5-TriggerActions: A background process (daemon) that will listen for changes in tiddlers returned by a filter/a set of filters and perform a set of actions whenever a change happens. , but not based on corn job.

#7

Is this relevant? I think @linonetwo is asking about importing the browsing history from the browser, and is not related to $:/HistoryList.

#8

A Slightly different approach to History is collecting the URLS we visit, a not time/date view of history. I make use of the “One Tab” browser extension in both Chrome and FireFox. It is populated when you close tabs with One Tab.

  • The reason I mention this is One Tab is an example of how much of this information can be easily collected and imported into TiddlyWiki.
  • I could see an extension making this all much easier, including for History.
  • Perhaps closing tabs, you would like the history for, or closing the browser are better triggers for capturing content for you wiki to import. Eg One Tab allows you to publish a set of tab URL’s online any other wiki (and person) could see.

The following hints at the One Tab features;

Snag_5b8fced

Snag_5b9219b

Background
@linonetwo I also have being looking more closely at the valuable information within the browser that we can make use of alongside tiddlywiki, including but not limited to Browser History, saved and pinned tabs, bookmarks/bookmarlets and cross browser (Chrome/Firefox) interactions.

  • TiddlyWikis handling of the data available from all these sources can be quite sophisticated and I think this means we could be at the leading edge of making more use of this information and as a result the resources are not thorough.
  • The main prior art is TiddlyClip
  • I think this is a motivation to use One Tabs approach or Maintain these externally to tiddlywiki and include/iframe etc… with selective import.
1 Like
#9

I currently have a workflow to transfer a folder hierarchy of bookmarklets from FireFox to Chrome. I observe you can export your history in a similar way to a bookmarks HTML, however the backup mechanism generates a JSON file with all the history information.

  • The JSON file is not recognised by TiddlyWiki, you may need to paste it into a JSON tiddler.
  • The JSON Mangler Plugin goes someway to making use of this JSON including views and generating a schema for the content.