Live data from Hacker News

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

voys.co.za

81–90 of 296 posts

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

#81
post #45
post #29

Earlier quoted context omitted.

Oh man, you should have seen the mobile sphere before Android...

Before iOS, to be fair. Touchscreens got the attention but the use of the iPod’s popularity to negotiate a non-terrible cellular market was equally transformative. The carriers used to charge something on the order of $50k each to be listed in their app stores and their percentage of revenue was high and negotiated based on your perceived ability to pay: we had several clients bail on J2ME projects because they were…

> Before iOS, to be fair.

iOS didn't move the needle on open source, open bootloaders or anything gp mentioned. All iOS did was shift the balance of power from telecom companies to Apple.

Android was far more open than all that came before it: the source code was available,it used open source & contributed back, and brought a very "PC" mindset[1] to an industry that had always considered handsets to be appliances (save a few Nokia models in the Communicator line).

1. "Intents" that could be handled by any app of the users choosing was very much like "Open with..." on PCs. Even disregarding the open source stuff, Android was very much an open system just for that reason.

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

#82
post #42

Earlier quoted context omitted.

no joke. what a hellhole that was.

I kinda liked J2ME...

You're the first person I've ever heard saying this. People used to complain a lot about Android fragmentation, but J2ME was easily 50x worse. Maybe 100x.

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

#83

Earlier quoted context omitted.

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.

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…

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

#84
post #45

Earlier quoted context omitted.

Before iOS, to be fair. Touchscreens got the attention but the use of the iPod’s popularity to negotiate a non-terrible cellular market was equally transformative. The carriers used to charge something on the order of $50k each to be listed in their app stores and their percentage of revenue was high and negotiated based on your perceived ability to pay: we had several clients bail on J2ME projects because they were…

> Before iOS, to be fair. iOS didn't move the needle on open source, open bootloaders or anything gp mentioned. All iOS did was shift the balance of power from telecom companies to Apple. Android was far more open than all that came before it: the source code was available,it used open source & contributed back, and brought a very "PC" mindset[1] to an industry that had always considered handsets to be appliances (sa…

Going back to the original comment, iOS improved the situation from the carrier having veto power over the entire experience to just the phone vendor and the App Store is more open than some of the earlier ones were (standard terms). It also doesn’t have the ad / activity data issues.

Android can be more open but let’s not pretend that a lot of devices have locked bootloaders, too, and has never lived up to that “PC” model due to things like proprietary drivers and apps refusing to run on unlocked devices. The future is very much unsettled here and we need something like legislation to reverse that trend.

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

#85
post #84

Earlier quoted context omitted.

> Before iOS, to be fair. iOS didn't move the needle on open source, open bootloaders or anything gp mentioned. All iOS did was shift the balance of power from telecom companies to Apple. Android was far more open than all that came before it: the source code was available,it used open source & contributed back, and brought a very "PC" mindset[1] to an industry that had always considered handsets to be appliances (sa…

Going back to the original comment, iOS improved the situation from the carrier having veto power over the entire experience to just the phone vendor and the App Store is more open than some of the earlier ones were (standard terms). It also doesn’t have the ad / activity data issues. Android can be more open but let’s not pretend that a lot of devices have locked bootloaders, too, and has never lived up to that “PC”…

> Android can be more open but let’s not pretend that a lot of devices have locked bootloaders

Not all Android handsets have unlockable bootloaders - but all handsets with unlockable bootloaders run Android.

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

#86

Ahh a privacy oriented company, that won't allow you to opt out of their analytic cookies this breaking the law in the EU. Or in other words, not privacy oriented at all.

europe's cookie fiasco is so idiotic - why don't you just disable them in your browser if you care?

Because the EU knows that you don't need cookies or client cooperation to track people as there is enough information the client sends (and has to send for functional purposes - think IP address, user-agent, browser fingerprint) to reidentify it down the line even without a persistent identifier.

If you think clearing cookies will defuse industrial-scale spyware from the likes of Facebook, Google or the various data brokers:

1) Don't waste your time clearing them; modern browsers already heavily restrict third-party cookie access and clear them on their own

2) I have a bridge to sell you

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

#87
post #29

The mobile ecosystem has been built with the sole intent of milking users through targeted advertising, media consumption and unnecessary services subscription, so I find normal that corporations behind the OSes fight hard to maintain the platform as closed as possible (proprietary or seemingly open OSes, closed drivers, locked bootloaders etc). Their deepest fear is seeing their ecosystem conquered by Open Source, o…

Oh man, you should have seen the mobile sphere before Android...

It was a nascent market, and the first versions of Android and iOS were not significantly better than what was already being offered. Is the suggestion that we wouldn't have put any effort into developing the ecosystem if Google and Apple didn't decide to involve themselves in it?

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

#88

Ahh a privacy oriented company, that won't allow you to opt out of their analytic cookies this breaking the law in the EU. Or in other words, not privacy oriented at all.

europe's cookie fiasco is so idiotic - why don't you just disable them in your browser if you care?

the irony of that, is that all to many times, one must enable cookies to be able to dismiss the, often full screen takeover, cookie notice to "disable" cookies

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

#89
post #31

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…

Absolutely the same here. WhatsApp is a nightmare to use without contacts, but I don't care, they are not having my contacts.

Facebook wouldn't have paid billions for just a messaging app. What they really paid for is people's social graphs.

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

#90
post #88

Earlier quoted context omitted.

europe's cookie fiasco is so idiotic - why don't you just disable them in your browser if you care?

the irony of that, is that all to many times, one must enable cookies to be able to dismiss the, often full screen takeover, cookie notice to "disable" cookies

Non-compliant & dumb implementations doesn't mean the law itself is bad. The problem is a major lack of enforcement.
Post reply on HN