News for hackers. Stuff that matters.
Re:How Google is forcing us to make our open source VoIP app... by secretsatan on Thursday October 20, 2022 @01:05PM (#33277614)
I kinda sorta see google’s side. There are just too many shady operators out there who will swear blind they’re completely honest, and maybe they are, but they also employed a third party to write code or maybe just imported a 3rd party lib (i am in no way saying this is the case)

As to, why don’t they look at the code? bugger that being standard practise, i’m not handing over my code to google or apple.

Even if they did, how to check final the uploaded binary?

I’m not doubting the article, but the mobile app world is flooded with shady operators at all levels, and i don’t really buy the real paranoid arguments here

Re:How Google is forcing us to make our open source VoIP app... by asdff on Thursday October 20, 2022 @01:31PM (#33277965)
At the same time, why not just release at least one phone that is developer friendly? People can handle it. All these issues are present on computers that are able to run unsigned code, have sensitive personal info stored on them, etc. Yet the sky is not falling with all this going on with everyone's computer on earth, like how people fear the sky will fall if we opened up the mobile phone.
Re:How Google is forcing us to make our open source VoIP app... by secretsatan on Thursday October 20, 2022 @01:40PM (#33278068)
They keep making them but they keep failing, because people want phones that work without needing a computer science degree to understand what is safe and what isn’t.

And myself being an apple guy with a dev account, i can install pretty much what i want

Re:How Google is forcing us to make our open source VoIP app... by ipaddr on Thursday October 20, 2022 @02:38PM (#33278833)
The initial barrier of getting grandma on an iphone is over and the need to dumb down devices to the lowest iq to gain marketshare should be over. It is time to raise the collect iq and at least offer a way to drop the training wheels
Re:How Google is forcing us to make our open source VoIP app... by jtvjan on Thursday October 20, 2022 @01:38PM (#33278041)
It's easy to install unsigned apps on Android, but not being on the Play Store severely limits your reach, since many people only check there for apps instead of searching on the open web.
Re:How Google is forcing us to make our open source VoIP app... by ericlnu on Friday October 21, 2022 @09:38AM (#33287876)
FDroid
Re:How Google is forcing us to make our open source VoIP app... by nemothekid on Thursday October 20, 2022 @01:55PM (#33278293)
>Yet the sky is not falling with all this going on with everyone's computer on earth, like how people fear the sky will fall if we opened up the mobile phone.

This is because everything was moved to the web and users were beaten over the head with a hammer to never install anything on their computers. The sky was falling and subsequently the desktop software platform hardly exists today.

Re:How Google is forcing us to make our open source VoIP app... by TillE on Thursday October 20, 2022 @02:20PM (#33278616)
I expect Microsoft's built-in antivirus helped a lot too, but yeah, the Windows XP era (c. 2001-2010 probably) was an absolute disaster of malware.
Re:How Google is forcing us to make our open source VoIP app... by anikom15 on Thursday October 20, 2022 @07:08PM (#33282009)
How exactly was the sky falling?
Re:How Google is forcing us to make our open source VoIP app... by aasasd on Friday October 21, 2022 @09:11AM (#33287641)
Re:How Google is forcing us to make our open source VoIP app... by anikom15 on Wednesday October 26, 2022 @11:06PM (#33352592)
This is funny, but in practice there would be maybe one or two of these bars. Many didn’t work together. These toolbars didn’t stop people from being able to work, eat, or pay their bills. I know. I lived through this era.
Re:How Google is forcing us to make our open source VoIP app... by fsflover on Thursday October 20, 2022 @01:56PM (#33278301)
>why not just release at least one phone that is developer friendly?

Google and Apple want to control their users, they don't want to give you an open phone. Instead have a look at Librem 5 and Pinephone, which run GNU/Linux.

Re:How Google is forcing us to make our open source VoIP app... by secretsatan on Thursday October 20, 2022 @02:20PM (#33278624)
In a way, but not for your reasons, they want to create mass market devices that if you give one to your grandma, little nephew can twist their arm for the root password to install this totally harmless fun app

Apple realised that far more than google imho

Re:How Google is forcing us to make our open source VoIP app... by datavirtue on Friday October 21, 2022 @09:49AM (#33287970)
So include a button that rolls back the OS to yesterday? You are inventing a dire issue that does not exist or has a clear, proven solution.
Re:How Google is forcing us to make our open source VoIP app... by jonas21 on Thursday October 20, 2022 @02:00PM (#33278347)
On most (if not all) Android phones, you can tap the version 8 times to put it into developer mode and then install whatever you want.
Re:How Google is forcing us to make our open source VoIP app... by ericlnu on Friday October 21, 2022 @09:37AM (#33287864)
All
Re:How Google is forcing us to make our open source VoIP app... by kk6mrp on Friday October 21, 2022 @10:10AM (#33288163)
Not all, some have this option locked out.
Re:How Google is forcing us to make our open source VoIP app... by secretsatan on Thursday October 20, 2022 @02:02PM (#33278371)
Depends what you mean by “sky falling on heads” They’re definitely aren’t concerted efforts in companies to not just open any email attachments

No data breaches occur to insecure passwords

Phishing, let alone spear phishing isn’t a thing

No popular app has ever found to be doing naughty things

We’ll not to the oss crowd anyway, if it does happen, it’s coz they aren’t using open source and checking every line of code

Re:How Google is forcing us to make our open source VoIP app... by tsimionescu on Thursday October 20, 2022 @01:56PM (#33278308)
Not to mention, given their cookie policy, they claim that they are "very privacy conscious" is dubious at best (no button to directly reject all non-necessary cookies, navigation to a different page to configure cookie preferences, claiming that analytics cookies are required).

I'm going to go ahead and say that probably they are misrepresenting what is happening.

Re:How Google is forcing us to make our open source VoIP app... by TheCapeGreek on Thursday October 20, 2022 @02:27PM (#33278705)
To give the benefit of the doubt, knowing nothing else about this company:

This is clearly a South African based company. GDPR and cookie may be important compliance but it's not top of the totem pole - the local South African equivalent law (POPI) is more about data processing than cookies. Plenty of sites have not updated their cookie UX for the newer regulations.

I've even noticed some sites serve different forms of cookie consent depending on where you're accessing from. I only started seeing the ability to reject cookies entirely when I travelled to EU recently - before it was always hidden in dark pattern UX.

Re:How Google is forcing us to make our open source VoIP app... by Nextgrid on Thursday October 20, 2022 @03:05PM (#33279199)
> the local South African equivalent law (POPI) is more about data processing than cookies. Plenty of sites have not updated their cookie UX for the newer regulations.

The GDPR is exactly the same. Even the ePrivacy Directive (the so-called "cookie law") actually covers more than just cookies - any method of storage in a user's terminal (whether browser local storage, or an app's own database) is also in scope.

Re:How Google is forcing us to make our open source VoIP app... by happymellon on Thursday October 20, 2022 @03:38PM (#33279616)
Indeed, and you can also use cookies without requesting permission.
Re:How Google is forcing us to make our open source VoIP app... by colejohnson66 on Thursday October 20, 2022 @05:01PM (#33280643)
For example, a login cookie is “essential” and does not require consent
Re:How Google is forcing us to make our open source VoIP app... by someweirdperson on Thursday October 20, 2022 @08:20PM (#33282617)
But don't start that php session (which sets the session cookie) before the user sends login credentials.
Re:How Google is forcing us to make our open source VoIP app... by happymellon on Friday October 21, 2022 @12:38AM (#33284573)
You are allowed a session cookie if it is for the operation of a website.

You don't need to ask permission to store a shopping cart or anything like that as a cookie.

Re:How Google is forcing us to make our open source VoIP app... by someweirdperson on Friday October 21, 2022 @03:45AM (#33285561)
I agree, it's not necessarily only login credentials, but could be a shopping cart. However, no shopping cart is needed until the user adds an item to it. Watching the shopping window doesn't need a cookie.

The typical practice seems to be to set a session-cookie unconditionally, to be able to store user-related data within that session, even if the user has not provided any such information.

Re:How Google is forcing us to make our open source VoIP app... by happymellon on Friday October 21, 2022 @04:23AM (#33285807)
Are you using that cookie for tracking or analytics?

If not then that's fine.

Re:How Google is forcing us to make our open source VoIP app... by happymellon on Thursday October 20, 2022 @03:37PM (#33279606)
GDPR is also nothing about cookies. It is about collecting tracking and marketing data about someone without their permission.

If you do any tracking and you don't use cookies, you still need permission and if you use cookies but you aren't using them for data mining then you do not need to ask for permission.

Re:How Google is forcing us to make our open source VoIP app... by maxboone on Thursday October 20, 2022 @04:51PM (#33280521)
It's not, it's a Dutch company
Re:How Google is forcing us to make our open source VoIP app... by moffkalast on Thursday October 20, 2022 @05:13PM (#33280794)
The Dutch colonized South Africa again eh? Old habits die hard.
Re:How Google is forcing us to make our open source VoIP app... by _djo_ on Thursday October 20, 2022 @06:04PM (#33281415)
No it’s not, why would you claim it was? The domain TLD is South African (.co.za), the phone number listed is in Cape Town, and it’s a South African registered company.

> Voys Telecom SA (Pty) Ltd A company with limited liability duly incorporated in terms of the Companies Act of South Africa, 71 of 2008, with registration number: 2013/114285/07, hereinafter referred to as “the Service Provider”;

Re:How Google is forcing us to make our open source VoIP app... by prvit on Thursday October 20, 2022 @06:14PM (#33281501)
Re:How Google is forcing us to make our open source VoIP app... by _djo_ on Thursday October 20, 2022 @06:26PM (#33281613)
Ah, got it. Yup, the Dutch office is the original one, there are a bunch of others around the world.

As far as I can tell though each different country office operates largely independently, almost as a franchise. So it might still be that the South African branch, with a registered local entity and no EU-based customers is more focused on POPI than the GDPR.

Re:How Google is forcing us to make our open source VoIP app... by chooma on Friday October 21, 2022 @05:19AM (#33286154)
We're an international telco, with two separate local entities & local teams, that are governed by different laws. The voys.nl website most certainly has the cookie consent screen.
Re:How Google is forcing us to make our open source VoIP app... by yieldcrv on Thursday October 20, 2022 @02:14PM (#33278539)
I noticed that too
Re:How Google is forcing us to make our open source VoIP app... by nedt on Friday October 21, 2022 @07:02AM (#33286726)
Not only are they tracking without consent. They are also missing very basic settings, like IP anonymization.
Re:How Google is forcing us to make our open source VoIP app... by veeti on Thursday October 20, 2022 @02:18PM (#33278579)
This line of reasoning can be used to reject and remove access to literally any app or API. Why offer a contacts API if you're not allowed to use it? Who is trustworthy enough to have this privilege?

They should just remove all third party API's to access any user data. Then we can be certain of privacy, with only non-shady actors like Google, Samsung, Facebook, etc. accessing saved contacts.

Re:How Google is forcing us to make our open source VoIP app... by bakugo on Thursday October 20, 2022 @02:41PM (#33278860)
So why not just remove the Contacts API entirely then? If it exists, "shady operators" can misuse it. Oh and, camera apps made by "shady operators" could be sending your pictures to questionable places so why not remove the Camera API as well? And we can't forget that "shady operators" could be snooping through your files so let's remove the filesystem API too.

Actually now that I think about it, any app could be malware, so let's just deal with the root of the problems and remove support for installing third party apps entirely. Everyone should just use apps made by google and nothing else, that way you know there aren't any spooky shady operators hiding under your bed.

Re:How Google is forcing us to make our open source VoIP app... by pjmlp on Thursday October 20, 2022 @05:06PM (#33280693)
They already removed filesystem API for quite some time now, you're only allowed to read inside the application directory, anywhere else on the device requires SAF.

https://developer.android.com/about/versions/11/privacy/stor...

Re:How Google is forcing us to make our open source VoIP app... by gizmo686 on Friday October 21, 2022 @12:41PM (#33290059)
Android still has an API to allow access to all files that were previously allowed. It just requires an explicit opt in from the user.

https://developer.android.com/training/data-storage/manage-a...

Re:How Google is forcing us to make our open source VoIP app... by pjmlp on Friday October 21, 2022 @02:07PM (#33291144)
Read the fine print,

>To limit broad access to shared storage, the Google Play store has updated its policy to evaluate apps that target Android 11 (API level 30) or higher and request "All files access" through the MANAGE_EXTERNAL_STORAGE permission. This policy takes effect in May 2021.

Re:How Google is forcing us to make our open source VoIP app... by forgetbook on Thursday October 20, 2022 @05:26PM (#33280995)
Slippery slope--There's a reasonable middle ground between "disallow all api access" and "allow all api access"
Re:How Google is forcing us to make our open source VoIP app... by mplewis on Thursday October 20, 2022 @05:38PM (#33281151)
Sure, but the entire problem is that Google does not seem to be able to manage the middle ground and proper use of it.
Re:How Google is forcing us to make our open source VoIP app... by hn_go_brrrrr on Thursday October 20, 2022 @08:16PM (#33282596)
There is such a reasonable middle ground, but Android is falling down that slope at an alarming rate.
Re:How Google is forcing us to make our open source VoIP app... by pydry on Thursday October 20, 2022 @06:07PM (#33281436)
They could just make the contacts API use an inbuilt contact picker than just supplies to the app the contact the user selects each time they make a call.

I assume they want google apps to have access to the whole phonebook without looking too suss though.

Re:How Google is forcing us to make our open source VoIP app... by saagarjha on Friday October 21, 2022 @02:36AM (#33285181)
This doesn’t work when you get an incoming call, and it’s annoying for outgoing ones too.
Re:How Google is forcing us to make our open source VoIP app... by pydry on Friday October 21, 2022 @12:17PM (#33289694)
It absolutely could. You could have a permission to do a lookup on the contacts list. These lookups could then be logged and tracked.
Re:How Google is forcing us to make our open source VoIP app... by utucuro on Friday October 21, 2022 @06:56AM (#33286689)
> I assume they want google apps to have access to the whole phonebook without looking too suss though. This is why I hope Google and Apple both get forced to give up control of either the OS or the app marketplaces. No company should own both the platform and have a privileged place on that platform like they do today. MS didn't even have this level of control on Windows and they still got an antitrust lawsuit...
Re:How Google is forcing us to make our open source VoIP app... by mcfedr on Saturday October 22, 2022 @10:09AM (#33298443)
This is a horrible user experience, ends up like iOS where there are great apple apps, and everything else is second class. The great thing of android is that you can choose a different dialer or different sms app, and it can be as good as the preinstalled one
Re:How Google is forcing us to make our open source VoIP app... by pydry on Saturday October 22, 2022 @11:40AM (#33299199)
Being able to install an anime themed dialer that will exfiltrate your address book isnt making android better.

Neither are the slew of apps that simply fucking break if they dont get access to every last one of your contacts.

Granular permissions intelligently designed do not make for a worse experience they make for a better one.

Re:How Google is forcing us to make our open source VoIP app... by sgc on Thursday October 20, 2022 @06:26PM (#33281618)
They won't let you call anything but their crappy camera app by intent already, for supposed privacy reasons. As you intimate, what is the point of allowing mobile apps, if they can't access any of the features of the device? Because that is where they are heading, fast. A few crappy google apps that require 24/7 spying to work, and then they "protect you" from everyone else. Sounds like an old school mafia street racket.
Re:How Google is forcing us to make our open source VoIP app... by esprehn on Thursday October 20, 2022 @07:54PM (#33282431)
That sounds like iOS? Only Apple apps have access to all the system level capabilities and you can't replace any of the system apps, not even the browser.
Re:How Google is forcing us to make our open source VoIP app... by sgc on Friday October 21, 2022 @12:05AM (#33284383)
It would be fair if one were to conclude that I don't like iOS. But my comment made a few different points, including about google's app quality, not only forcing default apps but also disallowing user choice where it should exist in a pervasive, hard to see way (for the end user), and invasive tracking.

Frankly, over the last week I have been looking into whether there is a relatively straightforward way to write an app for a mobile linux, because I am at the point I am willing to get rid of several common apps, such as banking apps, to get off this nauseating hamster wheel.

Re:How Google is forcing us to make our open source VoIP app... by fragmede on Friday October 21, 2022 @03:16PM (#33291971)
We have the technology for virtual machines, and phones are pretty beefy these days. where's my Linux phone hypervisor with android guest?
Re:How Google is forcing us to make our open source VoIP app... by sgc on Friday October 21, 2022 @06:24PM (#33293628)
There is Anbox, which just uses the same kernel for Linux and Android. But it is incomplete and not very active. Basically, we don't even need a hypervisor, but apparently it's still not easy.

https://github.com/anbox/anbox

Re:How Google is forcing us to make our open source VoIP app... by aruggirello on Saturday October 22, 2022 @12:48PM (#33299902)
Did you know about Waydroid? It's still at a relatively early stage, but it rocks!

https://waydro.id/

Re:How Google is forcing us to make our open source VoIP app... by jdmg94 on Friday October 21, 2022 @10:58AM (#33288677)
no forum about Android is complete without somebody blaming Apple
Re:How Google is forcing us to make our open source VoIP app... by LocalH on Thursday October 20, 2022 @09:25PM (#33283096)
Welcome to iOS 1
Re:How Google is forcing us to make our open source VoIP app... by fencepost on Thursday October 20, 2022 @10:05PM (#33283510)
Everyone should just use apps made by google and nothing else, that way you know there aren't any spooky shady operators hiding under your bed.

You left out 'other'.

Notable because Google long ago left behind 'don't be evil' and now is failing at 'FFS, at least try to not be f*cking creepy.'

Re:How Google is forcing us to make our open source VoIP app... by getcrunk on Thursday October 20, 2022 @05:53PM (#33281324)
I don't know how it is in all cases, but at least when using java back in the day, the source of a binary was trivial to look at?

And now many apps are written in js

Re:How Google is forcing us to make our open source VoIP app... by heavyset_go on Thursday October 20, 2022 @06:10PM (#33281473)
SafetyNet can obfuscate compiled code so that it's a pain to decompile and reverse engineer.
Re:How Google is forcing us to make our open source VoIP app... by throwaway27727 on Thursday October 20, 2022 @06:27PM (#33281620)
Proguard
Re:How Google is forcing us to make our open source VoIP app... by heavyset_go on Thursday October 20, 2022 @11:56PM (#33284342)
Thanks for the correction
Re:How Google is forcing us to make our open source VoIP app... by smeagull on Thursday October 20, 2022 @06:14PM (#33281507)
You're right, Google have long been incompetent at managing user generated anything. They should probably stop building things that depend on it, because they're so bad at it.
Re:How Google is forcing us to make our open source VoIP app... by kazinator on Thursday October 20, 2022 @07:37PM (#33282295)
If Google are going to be so paranoid about contacts, they should have an API which makes them completely opaque. The application, having access to the contacts, means that it can get a list of abstract tokens representing contacts, but not actually peek at their details. For everything imaginable you'd want to do with/to/by-means-of a contact, an API is provided which does it opaquely. Including UI stuff; like displaying a contact to the user.

Properties of a contact coud also be opaquely handled in a UI. Say you access contact.phoneNum. You get some abstract thing that doesn't give you the phone number string. But the object has a token which can be shoved into a UI form, and the UI form's textBox widget (being privileged, trusted code) can get the phone number in order to display it.

Re:How Google is forcing us to make our open source VoIP app... by amluto on Friday October 21, 2022 @02:40PM (#33291547)
> Even if they did, how to check final the uploaded binary?

By requiring and verifying a reproducible build. It would be awesome if open source apps on an app store has a badge indicating which commit of which git tree they came from and only allowed updates that similarly come from public trees.

Even failing that, favoring reproducible builds would add a considerable degree of traceability to the entire distribution process.

Re:How Google is forcing us to make our open source VoIP app... by lupire on Sunday October 23, 2022 @06:34PM (#33310942)
Even easier for the platform owner: if they have your code, then can compile it themselves.
Re:How Google is forcing us to make our open source VoIP app... by franga2000 on Sunday October 23, 2022 @07:14AM (#33306087)
Google's stance seems to be "even if you don't upload contacts, you need to say you upload contacts because we can't prove you don't". They are equating your technical ability to do something with you doing it. How is that in any way reasonable? I own a knife, does that mean I stab people? Should I have to say "I stab people" when I enter a kitchen so people know they might be in danger because there's nothing technically preventing me from going on a murder rampage?
Re:How Google is forcing us to make our open source VoIP app... by chiggsy on Sunday October 23, 2022 @09:47AM (#33306978)
They could change the code after 8 months to exfiltrate your address book, easily. Most businesses pivot for whatever reasons, a giant database of users contacts would be precisely what one would want in order to mitigate unforeseen problems with the business model.

As for your kitchen example, you don't need to say anything. Walk into any room with a weapon and people will know they might be in danger. If I'm in that kitchen, and you walk towards me, I'll move out of arm's reach.

Basically it's the same problem: Assurances are worthless. Rationalization provides seemingly excellent reasons for any course of action. So, the onus is on you to show that no harm will be done. It certainly is not the responsibility of some 3rd party to establish this, that is a coercive worldview.

Re:How Google is forcing us to make our open source VoIP app... by franga2000 on Sunday October 23, 2022 @11:03AM (#33307529)
The thing is, there's no way to prove you won't do something in the future if you have the ability to do it. All you can do is promise that you won't, preferably in a legally binding way (such as a privacy policy) and stake your reputation on it. That's the basis of society. Just because someone doesn't believe you doesn't give them the right to force you into a false confession.

The app developer says "all your contacts stay on your phone, we only use the internet for calls". Google says "this app is able to access both your contacts and the internet any time for any purpose". Both of those statements can coexist and be presented to the user for evaluation. The app being required to pretend like it's uploading your data is just lying to the user.