🤖 Hey, it's an update: Save My Chatbot v3.7.2

[github-actions[bot]]

What's Changed

• Refactor: Complete code restructuration to separate core logic from features implementation by @Hugo-COLLIN in Refactor: Complete code restructuration to separate core logic from features implementation #231
• Refactor: Moving logic from tab.ts ; Moving the scraper's domain check and output generation to background by @Hugo-COLLIN in Refactor: Moving logic from tab.ts ; Moving the scraper's domain check and output generation to background #232
• Feat: Send file to custom webhook by @dgruano in Feat: Send file to custom webhook #228
• Fix: Manage background download for Firefox and Chrome ; Modals shadowroot error ; Allow www.chatgpt.com scrap as a signed-out user by @Hugo-COLLIN in Fix: Manage background download for Firefox and Chrome ; Modals shadowroot error ; Allow www.chatgpt.com scrap as a signed-out user #233

Full Changelog: v3.6.1...v3.7.2

[przemoc]

This new version of Save My Chatbot added new permission: downloads.
(via #232 via innocently titled b4bba3f)

This leads to browsers generating notifications like below:

Save my Chatbot - AI Conversation Exporter is turned off

To turn on this extension, please accept the new permissions.

• Manage your downloads

Changing web extension permissions is usually a red flag. It should be properly documented and well explained so that users could understand it was really justified action. I don't see any of that in PR, release notes, extension's page.

For developers "why" may be often bread and butter, but it's not necessarily so for users, so it's good to take time and write it down. Sometimes it may help self-realize that some justifications are weak and there could or even should be different solution to investigate. Problem with particular permissions is that they are often wider than what extension needs to do, and that's why it is important to convey what capabilities from permission will be used (and sometimes even emphasizing what capabilities will NOT be used).

[Some actions require permissions that developers do not agree with, so there are even issues raised against browsers to improve that, and it's good to track and link to such discussions if they are relevant. Users may not always understand technical details, but they may understand that you'd like to avoid some permission but it may be feasibly impossible at current time.]

BTW Good open source extensions practice is to list on your extension page all required permissions and provide justification for each of them. Extension stores have limited description size IIRC, so it may potentially not have enough space to do that, but you have your own extension page where you don't have such limitations.

[przemoc]

It looks that downloads permission requirement have been thankfully removed from manifest.json in commit c2e1090, i.e. starting from v3.7.5.

Applying suggested documentation improvements would be still nice to see.