unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "W. Greenhouse" via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs android port has 124 permissions? privacy implications?
Date: Sat, 21 Dec 2024 16:15:26 +0000	[thread overview]
Message-ID: <s0ra5cp1081.fsf@tilde.club> (raw)
In-Reply-To: a4cf1412-6793-433b-96dc-c84c929af25d@disroot.org

జిందం వాఐి <jindam.vani@disroot.org> writes:

> * emacs android port was announced! [ 1 ]
> * it will be available in 30 [2]
> * release covered on lwn also [3]
> * available in f-droid repo [4]
> * just discovered thread which was
> created on independence day. ironic. [5]
> * there are few reasons for writing here
> * dont have inner workings of android apps
> * insufficient knowledge about android os
> * without having valid reason or concern,
> cannot post on emacs-devel
> * just hoping for some discussion or
> insight related to impact of permissions
> on privacy.
>
> [1] https://lists.gnu.org/archive/html/emacs-devel/2022-12/msg01358.html
> [2] https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS.30#n36
> [3] https://lwn.net/Articles/959931/
> [4] https://f-droid.org/en/packages/org.gnu.emacs/
> [5] https://forum.f-droid.org/t/emacs-excessive-permissions/27019

If you don't trust free software to do what you expect, don't install
it.

Permissions are needed to interact with the host (Android) system.

"Excessive" is a value judgment based on what you expect the software to
be able to do.




  reply	other threads:[~2024-12-21 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21 14:49 emacs android port has 124 permissions? privacy implications? జిందం వాఐి
2024-12-21 16:15 ` W. Greenhouse via Users list for the GNU Emacs text editor [this message]
2024-12-22  0:30 ` Po Lu
2024-12-24  6:03 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-24  8:31   ` జిందం వాఐి

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s0ra5cp1081.fsf@tilde.club \
    --to=help-gnu-emacs@gnu.org \
    --cc=wgreenhouse@tilde.club \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).