Import from Firefox

[zecamigo]

Describe the solution you'd like
Being able to import bookmarks exported from Firefox.

Describe alternatives you've considered
LinkHub is a potential sweetspot between offline readers like Wallabag and continue to rely on browsers bookmark managers.

[AmrDeveloper]

Hi @zecamigo,

I like the idea of importing popular browsers files, but we need to check how stable those files are, and how often the structure is changed

[DevKingofEarth]

HTML works welll, but if you need to to look into the .json, the problem is either you need create a logic to make it work in your app without renders or you need to implement rendering according to that what's available in the bookmarks .json file.

Better follow with HTML, as all browsers support HTML.

The problem with your app I found is lack of logic for Subfolders

Since HTML is supported. I would also request you to avoid duplicating Bookmarks, say if I use syncthing to sync, I had to import bookmarks everytime, then it gets doubled, say if 325 bookmarks I imported it at first, then it becomes 650 if I do it later.

[DevKingofEarth]

So make something aligned/related to syncing and versioning in local system folder(I'm internal storage) like where the user like to choose a directory and use any cloud or syncing service without the intervention of app. Then the app might be more useful. Also please look for the subfolder stuff as well.

[AmrDeveloper]

Hello @DevKingofEarth,

It can be a good option, and maybe to be explicit, "Import from Firefox".

For the nested folders, currently i am working on redesign to be similar and to make it easy to add sub folders without breaking anything, but it's on TODO to support it with good UI

[DevKingofEarth]

My idea for you is, instead of worrying about browsers, just rely on HTML itself, and make it available to backup and restore locally in desired directory. By doing that, you allowing users freedom to however and wherever they store and/or sync their bookmarks. E.g., Syncthing, NextCloud, WebDAV, etc.

You can either make a logic to manipulate changes in HTML,

say for e.g., if I did something in Firefox or any browser, like I added a new bookmark, export it to the location wherever I use it to sync, that export would replace the old Bookmarks.html with new link or added links, which also gets into phone local storage, and if you add a new link or changes through the app, then through auto saving feature it updates that HTML file.

Or we should simply export and keep replacing the HTML file from both the ends

If you think we need to eliminate the manual process of exporting bookmarks from browser, then an extension/browser add-on has to be made.

That is why I believe the first choice is good for starting. Just play with HTML, it is universal, it will have all simple bookmark properties like folder and subfolders, just import and auto save as usual, but not allowing duplicate of the same file.

[AmrDeveloper]

That is why I believe the first choice is good for starting. Just play with HTML, it is universal, it will have all simple bookmark properties like folder and subfolders, just import and auto save as usual, but not allowing duplicate of the same file.

It makes sense to use HTML., I think the UI for import/export should be modified to allow more options and maybe to allow parse other apps' exported files, I will refactor the UI first with current features and taking into account the new features then i will add them,