Hey @ariel.risky, does this plugin store general feed information as json?
If so would it possible to sync this plugin with thunderbird?
I’ve found out that I can set the location of where the feed information is stored there.
The Json file structure may be different though?..
If an example of the feed structure used for thunderbird would help, i could send mine.
The plugin doesn’t store feed information as JSON. Instead, it stores it in the browser’s Bookmark library as bookmark links. This allows feed synchronization across devices via Firefox Sync.
I believe Thunderbird supports importing feeds through an OPML file. You can export all Sage-Like feeds to an OPML file from the plugin’s settings page.
But I fail to see how this issue can be resolved without a third party.
If I try to read your mind, I assume you mean to modify the extension to use a local JSON file that could also be accessed by Thunderbird.
However, the browser will not allow a WebExtension to access local files without user interaction via the upload/download mechanisms. It’s a security issue.
You will need to send the feed info to some remote server and an add-on in Thunderbird to handle it.
However, the browser will not allow a WebExtension to access local files without user interaction via the upload/download mechanisms.
I’ve read that Extension can write to the Firefox user Profile folder.
You can set where Thunderbird reads the .json file, so if one were to set it to the Firefoxuser profile folder, in theory it should be able to access it.
Can you find it? I couldn’t find any indication of the ability to write to the file system without user interaction. To the user profile folder or any folder.
It sounds dangerous. A malicious WebExtension could potentially override existing files or write a file large enough to overwhelm the file system.
The first login dialog is triggered by the extension itself. The second one, however, is not.
The second dialog is displayed by the browser when the extension initiates a feed request, and the browser determines that an authentication is required. To minimize interruptions, the browser may eventually stop showing this dialog.
If the user still wants to access the feed manually, they can do so by selecting the “Sign in…” option from the feed’s context menu.