mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #942] Permissions gone too far! #742
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#742
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 @bytesandbuds on GitHub (Mar 1, 2019).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/942
It just popped up on my phone.
The app is asking to read, compose, send and permanently delete all your email from Gmail persmission. I don't remember agreeing to this before. Why is this here? Is this accurate?
@euh2 commented on GitHub (Mar 13, 2019):
This is a generic permission the app must have to save SMS to Gmail. The wording Google uses here is somewhat dramatic.
@eflister commented on GitHub (May 16, 2019):
i am also freaked out by this. why don't you just ask for permission to send? at https://github.com/jberkel/sms-backup-plus/issues/928 they speculate that it's because IMAP doesn't have fine grained control -- in that case, how about not using IMAP, just send an email!??!
@zetaomegagon commented on GitHub (May 19, 2019):
@eflister
One reason is that IMAP can tell you what messages are already on the server or not. With email you'd have to find a way to mark backed up messages as backed up...so a local database. Otherwise, you'd be backing up the same messages in separate emails over and over again.
Probably if you are just sending an email, it would have to come from an address you own. All backups would have come from the same address. If you went to restore things wouldn't work out properly. Spoofing sender addresses doesn't always work out, so probably not an option.
I'm sure there are many more reasons where IMAP has taken some of the complexity out of the solution.
@kurahaupo commented on GitHub (Nov 9, 2019):
Sending an email to oneself would lose several important features:
INBOXYou may care to read the privacy policy for this project.
If you do not care about these features (and the privacy policy does not assuage your concerns), there are other apps you could use.
PS: you should redact (blur) your personal information when posting screenshots.