Closed dmwyatt closed 1 year ago
Hi, thanks for asking about this.
The need to access the 3rd website is because as stated on the extension's download page & the notion site, the token issued by Notion isn't stored locally for long-term because it could be compromised. It is stored on a remote server for which you'll find the source code in another branch of this repo. Maybe I should also add this info in the README.md of the repo?
As for the 4th website, this is because the auth process for Notion redirects the user on another website (choosen by the integration's maker) when it's done. The extension needs to access said website to fetch the response from Notion which is url-encoded. In the case of this extension I choose a Notion page with some additionnal information & a link to the FAQ as the redirect page. This is a little more difficult to explain in a concise way but I'll work on it and will at the very least add this explanation to the FAQ.
I think it'd be good in the README and the FAQ. In fact, I've always appreciated it when extensions included this info in the extension description.
Hi, I've updated the README and FAQ, the extension's description on Chrome is also on it's way to be updated, it's currently waiting for approval by Google (should take less than 24hrs)
It'd be good to get an explanation of why the extension needs to access the websites it says it does.
Currently, the extension says it needs access to:
The first two are self-explanatory...