Live data from Hacker News

Keep Android Open

f-droid.org

201–210 of 764 posts

Re: Keep Android Open

#201

It is a disgrace how Google has managed this situation. To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe. But this promised feature hasn't appeared in any Android 16 or 1…

Good thing restricting side-loading isn't legal in the European Union! Not a problem here. Apple had to enable side-loading on their EU-based phones and so will Google if they restrict it.

Yes it is, and no they didn't. Apple has to allow (heavily restricted) alternative app stores, and I'm not clear on whether any actually exist right now.

Re: Keep Android Open

#202
post #151
post #143

Earlier quoted context omitted.

> and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected. That's just objectively wrong, both Brave and Opera still support manifest v2 and are committed to continue doing so for the foreseeable future. Even Edge apparently still has it, funnily enough.

Nope, actually "both Brave and Opera still support manifest v2" is objectively wrong. Brave does NOT support manifest v2. They have instead hand picked exactly 4 manifest v2 extensions (AdGuard, NoScript, uBlock Origin, and uMatrix) and have hard-coded special support for them. They quite literally say in https://brave.com/blog/brave-shields-manifest-v3/ that all other v2 extensions will go away from Brave once Googl…

which begs the question, why ublock origin is not native on all browser yet?

addons for firefox were at first a way to test features. we only have devtookls because one person wrote an addon copying ie6 dev tool. next Firefox release it was part of the core browser.

Re: Keep Android Open

#203

It is a disgrace how Google has managed this situation. To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe. But this promised feature hasn't appeared in any Android 16 or 1…

Personally I'm excited about the death of Android, now resources can be put toward mainstreaming and maturing the Linux Phone ecosystem Hopefully 2026 or 2027 will be the year of the Linux Phone

I.. don't think it will happen. For several reasons too. It is not that I don't think Android will change substantially, but the following constraints suggest a different trajectory:

- AI boom or bust will affect hardware availability - there is a push on its way to revamp phones into 'what comes next' -- see various versions of the same product that listens to you ( earing, ring, necklace ) - small LLMs allow for minimal hardware requirements for some tasks - anti-institutional sentiment seems to be driving some of the adoption

Re: Keep Android Open

#204

It is a disgrace how Google has managed this situation. To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe. But this promised feature hasn't appeared in any Android 16 or 1…

Personally I'm excited about the death of Android, now resources can be put toward mainstreaming and maturing the Linux Phone ecosystem Hopefully 2026 or 2027 will be the year of the Linux Phone

Strong disagree. Linux, its permission system and its (barely existent) application isolation are lightyears away from the security guarantees that Android brings.

Re: Keep Android Open

#205
post #8

I contacted the EU DMA team about my concerns and got a real reply within 24 hours. Not just an automated message, it looked like a real human read my message and wrote a reply. I'd urge other EU citizens to do the same.

[flagged]

Party B has access to the market of Party A at Party A's mercy.

Re: Keep Android Open

#206

Earlier quoted context omitted.

The problem is that step by step ownership of your device is taken away. First most phones stopped supporting unlocking/relocking (thank Google for keeping the Pixel open), now the backtracked version of this, next the full version, etc.

Yes, that is a real problem. But it doesn't justify arguing uncritically or unrealistically in other areas. I think people should be free to do anything they want with their own devices. They should be able to install any software they want. That's very different than demanding someone make their software exactly how you desire. ie. You should be able to install your own operating system, you don't get to tell them h…

> They should be able to install any software they want. That's very different than demanding someone make their software exactly how you desire. ie. You should be able to install your own operating system, you don't get to tell them how theirs should operate.

I don't think the distinction exists the way you're trying to describe. If I should be allowed to install any software I want, surely that includes any .apk I want? Conversely, someone could make the exact claim one step down the chain and argue that you don't get to tell them how their firmware should work and if you want to install your own OS you should just go buy a fab, make your own chips, write your own firmware, and make your own phone. And that's absurd, because users should be allowed to run their own software without being forced to ditch the rest of the stack for no reason.

Re: Keep Android Open

#207

It is a disgrace how Google has managed this situation. To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe. But this promised feature hasn't appeared in any Android 16 or 1…

I like it, because more and more people see Google as what it is: a ruthless, selfish and extremely greedy mega-mega-corporation. The less we depend on it the better.

Re: Keep Android Open

#208

Earlier quoted context omitted.

> Aren't the politicians or their appointed bureaucrats who'd be making all the decisions if these needs were government owned? Well that would be true under a capitalist government. > Why would state control lead to less policing? Its not just "the state runs it", its "we actively become the state". Collective ownership through peoples councils, peoples courts with a world view that keeps it all open: socialism. The…

Thanks for responding.

Yeah, dude thanks for the good faith.

A lot of people are allergic to this rhetoric and will just assume I have a deep irrational bias, but I was actually a staunch free market supporter before.

Once I decided to be more intellectually honest with myself and read more about what both sides meant historically and currently, it really just made sense.

Re: Keep Android Open

#210

Earlier quoted context omitted.

Personally I'm excited about the death of Android, now resources can be put toward mainstreaming and maturing the Linux Phone ecosystem Hopefully 2026 or 2027 will be the year of the Linux Phone

Strong disagree. Linux, its permission system and its (barely existent) application isolation are lightyears away from the security guarantees that Android brings.

This assumes that the mentioned systems are the only security considerations on a Linux system. Clearly this is not the case so I am unsure why you omit other security-related aspects of Linux here.
Post reply on HN