Live data from Hacker News

Google is forcing us to make our open source VoIP app worse

voys.co.za

141–150 of 296 posts

Re: Google is forcing us to make our open source VoIP app worse

#141
post #78

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…

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 mal…

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: Google is forcing us to make our open source VoIP app worse

#142

Earlier quoted context omitted.

Yeah, good luck with that. Nearly nobody installs apps from outside Google Play.

Huh? One example: everyone did sideload Pokemon Go in 2016 because its availability on Google Play was very limited for a very long time.

So why didn't Pokemon Go pull out of Google Play? Your only example is from 6 year and keep the 30% which Google takes? You only have one example from 6 years ago and people only sideloaded there only because it wasn't available on Google Play.

The one example you provided proves the opposite of what you wanted lol

Re: Google is forcing us to make our open source VoIP app worse

#143

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…

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

SafetyNet can obfuscate compiled code so that it's a pain to decompile and reverse engineer.

Re: Google is forcing us to make our open source VoIP app worse

#144
post #140

Earlier quoted context omitted.

It's not, it's a Dutch company

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”;

https://www.voys.nl/ exists

Re: Google is forcing us to make our open source VoIP app worse

#145

With the exception of Signal, I never give apps access to my contacts. If you think that's paranoid, remember how apps like LinkedIn used this kind of information in the past[1]. Thankfully on iOS apps almost always work without contact access (is this mandated by App Store rules?). It's not clear from the article if the app just asks for access to contacts or requires it, but if you can't make your Voip app work wit…

there are multiple apps i have encountered that would not let you type in a phone number to start a chat. you HAVE to give contact access and have whatever number you wanted to chat with saved as a contact

> you HAVE to give contact access...

Some apps require this, but the Android API allows apps to access very specific Contact information without having full access to all Contact data.

Re: Google is forcing us to make our open source VoIP app worse

#146

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…

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: Google is forcing us to make our open source VoIP app worse

#147
post #7

I'm not familiar with mobile app review process, would any change in code require a re-review/re-submit? If Google approved it as-is, could the developers add a few lines as an "update" and skip over the full review process? Seems like the ruling is being made on what can be done with the current permissions, rather than what is being done. If that's the case, I sympathize with the devs but I think I support the posi…

The code review is done 'black box' - ie. the reviewer doesn't have access to the code. All the reviewer can see is what permissions the app has. They see internet permission and contacts permission, and have to assume that evil code might be uploading the contacts to the internet. There isn't really any other way to do it - even a thorough code audit (a process that would take months for just a single app) would be…

It seems most likely that there is some static analysis being done to the binary here, or maybe some instrumented JVM that "poisons" bytes that come from the contact list and traces them to see if they ever land on disk or sent on the network. Clearly Google doesn't ban every app with that combination of permissions.

Re: Google is forcing us to make our open source VoIP app worse

#148
Is Google seriously just run by AI at this point? I imagine at some point up the middle management chain it’s just a layer of AI making decisions that no one has the authority to override.

Similar to how Amazon warehouse workers say that they’re working for an algorithm at this point making hiring/firing decisions.

Re: Google is forcing us to make our open source VoIP app worse

#149
post #148

Is Google seriously just run by AI at this point? I imagine at some point up the middle management chain it’s just a layer of AI making decisions that no one has the authority to override. Similar to how Amazon warehouse workers say that they’re working for an algorithm at this point making hiring/firing decisions.

Amazon runs on hire quickly and fire quickly policy (many other businesses have already copied this style of recruitment), which is why they are finding themselves running out of massive pools of workers.

Re: Google is forcing us to make our open source VoIP app worse

#150
post #144
post #140

Earlier quoted context omitted.

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”;

https://www.voys.nl/ exists

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.

Post reply on HN