Giving users the option to export their data to an HTML file (most likely) **ensures that their data is not lost should they need or want to uninstall or move the app on their device. This can be frustrating for users who have important saved to Brave but either had to or tried (unknowingly) uninstalling the app to fix an issue, change devices, or any other relevant reason. If Brave is uninstalled, all associated data is cleared along with it. This is _particularly_ relevant when un/re-installing the app: **The ability to export bookmarks/browsing data also solves the issue of "backing up" your data as well** - something Brave Sync doesn't offer. **This option allows users to try/switch over to Brave without having to sacrifice their data** - which, after import, can now be Synced across all their devices. **Many users are "blocked" from switching over to Brave due to the inability to import their browsing data** (any/call data, but primary concern seems to be bookmarks) **into Brave from another browser.** Many users have several years worth of saved (a la 2000+ bookmarks from 2011 - present!) and manually re-entering/saving all this data is unrealistic. This started by building a simple web server using Fastify._This issue was originally created a couple years ago (#150) but I felt requires a bit of a bump and update given how frequently it's requested._ I recently did this at a company hackathon where I built a Slackbot that could respond with company bookmarks. You can also import Bookworms like a normal npm module and then use it programmatically. You can see an example here: Ĭurrently you need to run the npx command after each update to the YAML file, check in the the changes and then reimport browsers.html, however this is something I’m working on automating. You can also fetch bookmarks from a remote location and output the exports into a different directory: npx bookworms get -d="./output"įor storing your bookmarks I recommend having a repository that contains the YAML, README.md and browsers.html files together, here people can view, import or contribute to your bookmarks. Select Import and Backup > Export Bookmarks to HTML. Mozilla Firefox Open the Firefox Library with the shortcut Ctrl-Shift-b or by tapping on Alt and selecting Bookmarks > Show all Bookmarks. This will generate the files README.md and a browsers.html in the same directory it’s run. Select Import and export > Export to a file from the menu to save the bookmarks to a file. With a few lines in NodeJS I was able to convert the bookmarks YAML into a README.md.īookworms is the tool I wrote that allows, people, teams or a company to store, share, update and centralize their important links while giving multiple useful outputs.Ĭurrently you need to have Node and npm installed on your machine once this is done you can use it with the following command: npx bookworms get. If you have your bookmarks stored as YAML this is a pretty straight forward transformation. Something very common in the industry is people maintaining a list of useful links and storing them in Github as a README.md. Having spent the last few years of my career working in infrastructure there was only one solution in my mind… YAML! label: Bookworms description: These are sample bookmarks folders: - label: folder 1 description: This is to describe the folder structure folders: - label: sub folder 1 description: This is to describe the sub folder structure bookmarks: - label: sample url 1 description: this is used to describe the bookmark href: ' ' - label: folder 2 folders: - label: sub folder 2 bookmarks: - label: sample url 2 description: this is used to describe the bookmark href: ' ' - label: sample url 3 description: this is used to describe the bookmark href: ' ' - label: sub folder 3 bookmarks: - label: sample url 4 description: this is used to describe the bookmark href: ' 'Ĭreating a standardised structure for URLs based on bookmarks and folders would allow people to easily contribute and add the ability to transform this data into different formats. I again started thinking about a way to centralise bookmarks while still allowing you to use your existing tools. The idea of crowdsourcing URLs and their authority of truth would run through mind for a while.Īt the start of this year I moved to a start up and while there are a lot less URLs they were still distributed in different tools and not always up-to date. If you were lucky someone might have already set up a bot to respond, if you were unlucky it might start a flamewar about how bad the latest HR platform was. The only real authority of truth was crowdsourced by asking in Slack what the URL was for a certain service. New tools are often introduced, old ones decommissioned or hostnames changed, I often joked that if I cleared my internet history I wouldn’t be able to do my job. How I centralize and distribute my bookmarksĪt a large company there are thousands of different internal URLs, from multiple development environments, workflow tools and HR systems.
0 Comments
Leave a Reply. |