FairEmail stopping development after Google falsely flags app as spyware

Re:FairEmail stopping development after Google falsely flags... by bilekas on Thursday May 19, 2022 @12:03PM (#31436418)

> this is the sending of information off each user's contact list (the email address domains) to those remote servers. As such, it requires a disclosure to the user.

That's really interesting.. Honestly, I wouldn't have even picked up on that reading the code, as it's only the domain of the email itself. Not any identifiable information.

Feels a little but harsh but fair enough.

I wonder is there an identifiable marker which could say `"User X has a contact list containing gmail, yahoo and protonmail accounts."`

You don't know who the user is at all but you know "A" user has that contact list.

Very harsh.

[ Parent | on HN ]

Re:FairEmail stopping development after Google falsely flags... by CodesInChaos on Thursday May 19, 2022 @12:10PM (#31436516)

Some of those contacts might use personal domains, or company addresses, not just big freemailers.

[ Parent | on HN ]

Re:FairEmail stopping development after Google falsely flags... by wander_homer on Thursday May 19, 2022 @04:09PM (#31439541)

I still don't see the issue. So the application then asks the personal domain for a favicon, how is that an issue? Especially when you consider that this feature is off by default and has a red warning label next to it, that this comes at a privacy risk.

[ Parent | on HN ]

Re:FairEmail stopping development after Google falsely flags... by bilekas on Thursday May 19, 2022 @02:59PM (#31438642)

That's actually a really good point I hadn't considered, from the documentation it mentions only suppoorting standard formats and not those such as MS exchange etc. But you're right, there are personalized which are standard.

[ Parent | on HN ]