mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #148] New permissions in v3 #139
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#139
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bodograumann on GitHub (Aug 23, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/148
I'm on Firefox 61.02 and floccus (currently 2.2.9) is requesting permissions to “Access my data for all websites”.
In recent times many addons have been subverted to grab users browsing data, so I have made a habbit of verifying that any new permissions are legitimate.
Unfortunately in this case the description of the requested permissions is pretty unclear. Also I could not find any information on new permission requirements in the Readme.
Could you please check whether these permissions are really needed and if that is the case, add an explanation to the readme?
@marcelklehr commented on GitHub (Aug 23, 2018):
Ah, yes. I'll update the README.
@marcelklehr commented on GitHub (Aug 23, 2018):
Here you go: https://github.com/marcelklehr/floccus#permissions
Thanks for the feedback :)
@marcelklehr commented on GitHub (Aug 23, 2018):
The "new" permission is not actually new, but it was added to allow accessing http servers as well, not just https servers.
@bodograumann commented on GitHub (Aug 23, 2018):
Thank you for the quick resolution :-)
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.