upvote
I hope people remember this when advocating for chromium. Just because it is open source doesn't mean they don't control it. We need to start the long process of hard forking now or turn to alternatives like Firefox as a new foundation.

  > Google simply regrets android being open source.
Android wouldn't be what it is if it wasn't open source. With all the work from outside Google. The same is true chrome.

But they won't learn that on their own. They are breaking the deals. So we move. We force their hand

reply
> But they won't learn that on their own

I think they're fully aware of this. They just don't care, because the goal of "get market share super high" has been reached, so now they have no need for it to continue being open.

I don't disagree about what that means we should do; I just don't think we should assume they're being naive here. It's like writing a program to play chess; you should select your move assuming the opponent is smart and will make the optimal counterplay rather than assuming weakness, and then if they end up being less smart than that, you're still in a good place.

reply
Tbh I don't think fighting open source is Google's best play. I think it is in their own best interest to keep it fully open. It is free labor by those who are most passionate. It gives strong signals at what people want, this direction you develop. It strengthens security as more people try to test it. It means people work on forks rather than alternatives. All this is true even with a monopolistic market share.

So yes, I do think they are being naïve. The stance is myopic. It is only a good move in the short term, and barely even that. It is under the false belief that we operate in a zero sum game.

reply
Most successful open source projects have devs being paid by big corporations, including Linux itself, which only really took off in the 2000's when companies like IBM started caring.

Also in the last century most software was commercial, and thanks to business friendly licenses we are back to demos, PD, Shareware and co, only with new names for a younger generation.

Google will do just fine.

reply
I don’t get the hate for business licenses.

I’ve seen many open source contributors deflated because they wanted to share their code/solutions with other individuals and the world to learn from only to have their work sold as a service by a big cloud vendor without seeing something back for it. Or maybe even getting more work back to support the cloud vendor for free.

So I’m not surprised at all that licenses that allow commercial use up to a point and above that require seperate license or contributions back. It is still open source in a lot of ways. Can still be part of other open source distributions that themselves make no profit etc. And only companies that are more than able to pay must pay something.

reply
It's a good idea if it actually works. Are enough commercial users paying up so that these projects get some serious funding?

If companies avoid using software governed by such licenses then the overall impact is negative in my opinion, because it will lead to competing and diverging clean room clones that just split the community and the ecosystem.

reply
which only really took off in the 2000's when companies like IBM started caring.

Correlation is not causation.

What I lived through, was Linux taking off like a juggernaut, and IBM embracing it as a result. Large corps came along for the ride, they didn't drive it and at best paid for some gas.

DEVs being paid is simply what it is. The entire scsi/sata stack was originally re-authored by 3ware for example.

Why?

To sell stuff, and the guy was an advocate too.

It's always been this way, under the great wonder of the GPL, blessed be it.

reply
Google learned that it's exactly not in in their best interest when they lost their court case against Epic a few years ago which is why they are shifting focus away from open source and moving towards Apple's walled garden approach. If they had locked down their platform similarly as Apple did, Epic would probably have lost it's case for similar reasons.

Granted, we know Android would not be where it is today without open source contributions.

reply
I think this is true, but I also believe the original people who built it are not the people in charge now.
reply
Like most projects, anyone that thinks Linux or Steam will stay as they are when the generation that started it all is gone, is in for a surprise.
reply
We haven't had antitrust enforcement for 25 years. It's high time we did.

Google needs to be broken up.

reply
MS was never broken up.
reply
So do M$ as well ?
reply
Hard forking doesn't solve the problem of closed source.

If the goal of a hard fork is "the community will invest equal resources that Google does today" then you wildly underestimate how many engineers work on Chrome.

reply
Not denying than many engineers work on Chrome just wondering how many of them work on Chrome features that are anti pattern, reducing privacy, improving information collection or tracking or against users interest in broad.
reply
You can just look at the commit stream and see for yourself. Despite community pearl-clutching, 99% of the work is just good old fashioned software engineering.
reply
Can anyone actually share 1 - 3 examples where a hard fork of a living os project has actually succeeded ?

If AMZN couldnt make their fire whatever it was called fork of Android really grow, what chance has the community got ?

reply
OwnCloud -> Nextcloud, OpenOffice -> LibreOffice, Elasicsearch -> OpenSearch, privacyIDEA -> eduMFA
reply
https://en.wikipedia.org/wiki/Apache_OpenOffice

Difficulties maintaining a sufficient number of contributors to keep the project viable have persisted for several years. In January 2015, the project reported a lack of active developers and code contributions.[49] There have been continual problems providing timely fixes to security vulnerabilities since 2015.[50][51][52][53] In September 2016, OpenOffice's project management committee chair Dennis Hamilton began a discussion of possibly discontinuing the project, after the Apache board had put them on monthly reporting due to the project's ongoing problems handling security issues.[54][55][56]

Sounds like AOO is effectively dead, so this example is a fail to my challenge.

OpenSearch & ElasticSearch both seem alive, as well as OC & NC.

Neither https://github.com/privacyidea/privacyidea or https://github.com/eduMFA/eduMFA say either is a fork of the other.

I think you failed to share 3, 2 seem to valid examples of my challenge but the other 2 are questionable.

reply
AOO became a thing after LibreOffice essentially won. Before that it was OpenOffice.org owned by oracle, forked into LibreOffice in 2010, with LibreOffice getting significant traction and Oracle throwing in the towel and donating OO to Apache Foundation in 2011.
reply
>wildly underestimate how many engineers work on Chrome.

It is completely insane how many people work on Chrome. It seems like it is time to deprecate web browsers and do something different. Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway). Get rid of 99.9% of the cruft that has accumulated over the decades in browsers. If you want to have some of that cruft, that is a library you have to send.

reply
Or go the other way and make web pages not programs at all, like they originally were. Unfortunately, just communicating information isn't cool, doesn't monetize, and certainly doesn't get clicks.
reply
The biggest mistake the web ever made was leaving it up to to the website to choose how content renders.

It should be the users choice how their browser renders, it's their damn browser. Instead, browsers are built to follow standards that mostly favor the developers preferences above those of the person who actually own the device rendering it.

The modern web is user hostile by design.

reply
If a web browser allows images, then the website always has full control over how content renders. It's the default. HTML and related standards are trying to persuade developers to cede some of that control in the name of accessibility, user choice, searchability, device compatibility etc. that all-image websites lack. But this can only succeed if the developers still can do everything they want to. If they can't, then they'll fall back to images and everyone loses.
reply
> Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway).

The biggest thing standing in the way of this is actually Apple, since they don't allow competing browser engines or equivalent so you can't make something like this for iOS whatsoever.

reply
Apple can create a clone for their wall-garden when they want to catch up to the times.
reply
Those times will never happen.
reply
But the open source project wouldn’t need to invest as much as Google does. There are all kinds of features and things they are working on that the general public really does not care about.
reply
> But the open source project wouldn’t need to invest as much as Google does.

Not at first. Yet over time the work increases as one must differ more and more from Chrome. I believe that's why so many forks are giving up on Manifest V2.

reply
Forks are giving up on mv2 because it's not as important as the people online say it is. If mv2 was what would cause a browser to gain market share they would keep maintaining it, but if the market is not rewarding browsers with mv2 then it does not make sense to maintain.
reply
Seriously. The average person in real life has no idea what MV2 or MV3 is. And despite what people here would have you believe uBlock Origin Lite works nearly as good as uBO and is generally indistinguishable from its MV2 counterpart. A casual user wold not be able to tell the difference, nor do they care.
reply
Differentiating isn’t as important as not engaging in Google‘s heinous practices
reply
The bigger problem is wasting developer effort contributing to Google's platform. The real secret behind Android being "open" (sorta) is that while almost nobody runs AOSP, Google has tricked a bunch of fools into working on Android forks instead of building a real competitor.

Playing at their table is a losing game, the house always wins.

reply
Windows only isn't still 90% market share because of Wine, then Proton.
reply
More like thanks to Apple, in what concerns desktop computing.
reply
Neither Wine nor Proton run on Windows. Building Android emulators for Linux: Worth your time. Building Android knockoffs which claim to remove the Google from Google's operating system? Foolishness.
reply
Valve is working on supporting apks for their new VR operating system. If this goes anything like Proton then I'm hopeful for the future of Android without Google.
reply
Gamedevs would still target Android, just like they target Windows, letting Valve run after them.

Android is even more of tragedy, given how all relevant NDK game development APIs are also available on GNU/Linux.

reply
Reimplementing Windows was a huge task. If the windows source code was available, why wouldn't you begin with a copy-paste?
reply
ReactOS was also a good idea.
reply
The developer effort is not wasted because it's open source. Anyone can fork it at any time. None of it can be thrown away from humanity, wasting it.

The reason why no one runs AOSP is because the phone market rewards differentiation. Each phone manufacture wants to build their own experience and building on top of AOSP is how they do so.

Is it really a losing game? Building a new OS from scratch is not worth it. Why throw away an entire app catalog for your device? Consumers want access to existing app catalogs when buying a phone. If anything is a losing game it's building a new mobile operating system over forking Android as a base.

reply
> The reason why no one runs AOSP is because the phone market rewards differentiation.

This is what empire-building middle managers say to rationalize their boondoggles, but in actual fact most customers can't even tell the difference between two different vendors' Android skins, definitely can't tell the difference before they buy one, and the way they actually differentiate phones is on real hardware differences that show up in the specs like the camera or performance.

The hardware company's idiosyncratic fork of the software is irrelevant at best and annoyingly irregular in the common case.

reply
> The reason why no one runs AOSP is because the phone market rewards differentiation.

No, the reason is that AOSP doesn't even include a functional keyboard nor a functional call manager nowadays.

AOSP apps were abandonned around Android 11, you can't just keep them as is for real users, it looks amateur.

Even the open-source ROMs came to the same conclusion eventually and developed their own.

reply
>the reason is that AOSP doesn't even include a functional keyboard nor a functional call manager nowadays

No one was using those apps so it didn't make sense to spend time on them.

reply
So.. The market didn't actually support differentiation?
reply
If you are not working to destroy Android, you are supporting it. You might feel happy about your custom ROM nonsense and how it protects your privacy, but that just means you're selfish, because nearly everyone will still be trapped on Google's version.

Technologists need to aggressively reject solutions which don't spread freedom to ordinary users as well.

reply
It wasn't worth it, but it's 2026, not 1991, when Linus first released Linux. AI can shit out a new OS, given enough tokens, and a VM/compatibility layer would let you run Android apps until native ports became available. The question is why would you want to do that? Computers are vastly more capable than they were when the Linux kernel was originally designed, and the needs of programs and their permissions have changed as well. https://xkcd.com/1200/ While throwing away all the learnings and starting from scratch are usually not justified, sometimes it is the right choice, if enough things have changed. Should GPS location, fine grained or coarse, and related permissions, be a part of the OS kernel or a user space daemon that other processes can query or some other thing? That wasn't a question when Linux was created but should be a core consideration for a replacement system that was created today, along with a myriad of other modern day questions that didn't exist back then. I don't think it's a loosing game, and I don't have the resources to make one myself, but I do think that the world's materially changed enough to justify building a new one from scratch.

AI generating code changes the game significantly, though there are issues with that. A new OS would have taken several millions and multiple teams, but can now be done for far less. The problem is hardware to run it on. Who'd pay $2,000 for a shittier phone with less features when a $500 used one with GrapheneOS is right there? So the market, (in)efficiently, hasn't come up with a new phone OS. Not because it isn't warranted, but because the free market isn't a perfect system.

reply
You mean proprietary AI can do that, running on big corp servers.
reply
LLMs can't even get much simpler programs right without humans holding their hand, let alone an OS. The odds of an LLM just banging out an OS are nil.
reply
Why bother building a compatibility layer when you can just start with Android and start promoting your LLM from there?
reply
It wasn't worth it, but it's 2026, not 1991, when Linus first released Linux. AI can shit out a new OS, given enough tokens, and a VM/compatibility layer would let you run Android apps until native ports became available. The question is why would you want to do that? Computers are vastly more capable than they were when the Linux kernel was originally designed, and the needs of programs and their permissions have changed as well. https://xkcd.com/1200/ While throwing away all the learnings and starting from scratch are usually not justified, sometimes it is the right choice, if enough things have changed. Should GPS location, fine grained or coarse, and related permissions, be a part of the OS kernel or a user space daemon that other processes can query or some other thing? That wasn't a question when Linux was created but should be a core consideration for a replacement system that was created today, along with a myriad of other modern day questions that didn't exist back then. I don't think it's a loosing game, and I don't have the resources to make one myself, but I do think that the world's materially changed enough to justify it.
reply
but perhaps we dont need several gigabytes compressed code to have a browser. perhaps what google have been doing is an utter abomination?
reply
This is cool until Google doesn't load in your free browser.
reply
Then, you use this: https://duckduckgo.com/

Actually, use it now.

reply
This. Also, use OSM for maps and run your own SMTP server, if you can. Nobody should need Google.
reply
This works for nerds, but not for grandma who can't even describe what she's doing without using the word "google".
reply
Nerds with grandmas can manage grandma's DNS or better yet set up MDM (I'm serious).
reply
Actually it is still cool if they don't.

Because of their enshitification we do have alternatives that were developed.

At this point the their only services I'm using are Maps, Translate and Keep Notes and it is mostly due to lazyiness as all of those already have alternatives.

Edit: forgot about YouTube, which is ironic, because that one is a toughest one because the value comes from creators, but I'm doing my part and using GrayJay[1] so I can follow them if they switch their platform.

[1] https://grayjay.app/

reply
> Android wouldn't be what it is if it wasn't open source.

Yes, and now that they've achieved market saturation, it's time to pull up the ladder.

Thanks for all the free work, suckers!

reply
Don't worry, we will fork and just repeat the pattern with new names! See you next time!
reply
GNU generation is over 50 nowadays, and newer don't really get open source as we used to.

I mean, FOSDEM full of Apple laptops on the corridors, the message was really lost.

reply
I would say its even more proactive than support other projects. It is becoming clearer that every single technically competent member of the friends or family is now required to educate and proactively change devices.

Remember this upcoming Christmas that the ye oldie tradition of fixing PCs clearing awful exploiting phone apps (and cancelling subscriptions) should also include the "fix my browser" again, instead of Internet Explorer being replaced by Chrome, our collective duties is to replace Chrome with Firefox, plus its useful extensions to block ads and improve the web experience removing trackers etc.

Your call to arms today is to ensure all your tech colleagues join the movement, and then we can see Google's management views on "market growth"; they forget they made Chrome, we sold it - its our fault we forgot the "infinite growth of shareholder value"...

reply
> or turn to alternatives like Firefox

Implying I ever left Firefox in the first place.

reply
> or turn to alternatives like Firefox as a new foundation.

With the way Firefox is heading, that might not be the best idea. Nowadays Mozilla seem more focused on riding the AI-hype wave than actually making an excellent browser people want to actually use.

reply
Is Firefox or Mozilla perfect? Heck no. But we're not comparing Mozilla against pre-IBM Red Hat or Ben & Jerry's or whatever your concept of the ideal corporate citizen is. We're comparing Mozilla against Google. That's a very low bar that Mozilla clears with ease, especially if you're criteria includes shoving AI down your throat.
reply
I'm not sure Mozilla clears it. Zen or Librewolf or PaleMoon clears it.
reply
Firefox is no longer part of most browser compatibility matrices, what ease?
reply
> Firefox is no longer part of most browser compatibility matrices, what ease?

What would be the point of a browser compatibility matrix then?

reply
Compatibility between market relevant browsers.

Which for the large majority of companies means Chrome and Safari nowadays.

Thanks to Apple's stance on iOS, otherwise it would be only Chrome, as younger generations apparently never got the IE history lesson.

reply
Either way we're still stuck with it.
reply
Mozilla definitely wastes a bunch of money building features I don’t want. But underneath it all, Firefox is still an excellent web browser. You just occasionally have to disable “pocket” or “gadgets” or something.
reply
It is sad to see Firefox riding various hype trains over the years, but I can't really blame them. Miss the wrong train, and you fall behind and may not be able to catch up. Miss the train to nowhere, and you are only wasting resources.

As for the excellent browser that people want, that raises the question of what people want. There are likely as many answers as people.

reply
I don't understand this - what is wrong with Firefox these days? It does everything I need, and very few things I don't want.

Very puzzled why there isn't more love for Firefox, even on HN.

reply
Yeah. It’s a tough balance to achieve but that’s the situation we’re in right now so Mozilla really ought to step up (and I totally wish they would).

My biggest pain point at the moment (entirely subjective mind you) is not even the AI nonsense, but how disjointed and alien the Firefox UX and general feel is to Apple platforms (what I use, at the moment). I don’t want Firefox to mirror Safari 1:1 but I do want the Firefox UI and UX to feel polished, well thought out and thoroughly in line with system HIG specs—given that I spend a lot of time in a browser, it shouldn’t feel like a stranger in a strange land amidst my other desktop applications.

Aggressive UI improvements would go a long way to restore some faith in the incandescent fox‘ mission—at least for me.

reply
Behaving like a native application also has tradeoffs. If you're only working on one platform, then sure you will want it to behave like a native application. If you're working on multiple platforms, chances are that you're going to value consistency. And while macOS users prefer their UI, the same can be said of Linux and Windows users. Guess which one is going to win out there.
reply
Maybe I'm not enough of an Apple fanboy but using work provided mac with firefox for 15 years I never noticed UI being disjointed from the system any more than Chrome.
reply
> Maybe I'm not enough of an Apple fanboy

Maybe you’re too preoccupied trying to discredit valid criticism as “fanboyism” to realise how important UI and UX are for products such as browsers.

Besides, Chrome itself is already an absolute mess of conflicting and downright distasteful UX choices and patterns. Firefox seems to be stuck in the past but Chrome seems to actively DESPISE being available on Mac.

reply
What aspects feel foreign on macOS? The Firefox preferences for sure. Anything else?
reply
Tab close buttons are on the right (windows style) instead of on the left (macOS style), for one.
reply
Not only that, but general colours are system-like but offputtingly different (dark theme is different from Mac dark theme just enough to be unsettling). Spacing (padding, margins, etc) is uneven on a lot of options, toggles and fields. Swipe back/forth being a simple arrow on the corner of the screen instead of full page swipe (like Safari) in the year of our lord 2026 is a complete disgrace (yes, chrome does this too, yes chrome also sucks). Press CMD+F and just watch as a search bar that hasn’t been updated to modern visuals in about 20 years pops up at the bottom. Pretty much everything around Firefox feels like a random collection of Windows and Linux behavioural patterns mashed together like a digital Frankenstein monster.

And despite what many people here like to think: these things matter. UX improvements compound exponentially, and so do UX problems. Firefox has an opportunity here to be a first-class citizen on every OS it runs on. It has the opportunity to be the browser that respects your OS choices no matter what, but alas, Firefox seems rather content carrying its “ah yeah I remember using it back in ‘06” reputation.

Firefox is not a bad browser by any means, but it feels like Firefox is the browser equivalent of the “how do you do fellow kids” meme. An out-of-time experience pretending to blend in under the guise of “AI”.

reply
I mean, it’s the same on every browser except Safari
reply
Orion also does it right.

Every other browser aren’t using macOS native UI therefore are wrong in this environment. But right on their own in being the same everywhere.

reply
Unfortunately “being the same everywhere” only works if your application is distinctive enough in functionality that it can’t be anything else but itself. Firefox is just a browser. Safari is also a browser. Chrome is also a browser. And none of these apps are more important or relevant than the operating system they are working under.

If my OS says windows and tabs close on the left, then I expect every single app to be a good platform citizen and not make me relearn default controls just to operate simple functions. Windows and tabs close on the left. End of story.

reply
Just because everybody does it wrong doesn’t make it right.
reply
Mozilla gets 100M a year from Google ??? No fucking way they are biting the hand that feeds.
reply
Closer to 500M, actually.
reply
~$585 million in 2024 (86% of total revenue) https://stateof.mozilla.org/pdf/Mozilla%20Fdn%202024%20-%20A...

Mentioned as "one customer" in the PDF.

reply
Lol yeah off by a factor of 6 but yeah no fucking way still stands

Edit: spelling

reply
It's not really a "both sides" thing given the scale difference between what Google is up to and that.
reply
No one is forcing Mozilla’s hand (afaik) and no one is actually thinking “if Firefox had a chatbot that might convince me to move over”. Youre right that it is not a “both sides” thing, its a “Mozilla thing”. Through and through.
reply
Some people are thinking "Firefox doesn't have a chatbot so I'll use chrome" though
reply
Are any of those people not investors?
reply
Really? How many people can that possibly be, and how many of those would a reasonably sane developer actually want?

If your competition is attracting the worst kind of users, do you really want to get in their way?

reply
Yes you want more users not less. This is business 101. Even business 000. Customers good.
reply
Business 101 is to make sales! Users sometimes represent sales, but not always. That may be business 201 though.
reply
Where is the form, forum or spot in general where one can tell Mozilla?
reply
The next board meeting, after buying at least 51% of the shares.
reply

  So we move. We force their hand
How?
reply
Google is starting to turn into early 2000s / late 90s Oracle.
reply
The “we” in your post is interesting to me. Who do you mean? Individuals?
reply
> advocating for chromium.

Advocating for chromium to do what?

reply
> So we move. We force their hand

What do you have in mind?

reply
> We need to start the long process of hard forking now or turn to alternatives like Firefox as a new foundation.
reply
deleted
reply
oh yes sure. just like we can shift the population into installing Debian into their machines so we also deter M$ and Apple abuse /s
reply
We did it before. Thanks to Firefox we broke the IE6 monopoly even on Windows.
reply
How did that happen, anyway? Tabs? What's the next killer feature after tabs? Maybe sync?
reply
Adblock, I would have thought. And Google can't compete in this space, by their very nature.

This is the message that Firefox needs to push: Hate ads? Use Firefox.

reply
Considering that Firefox by itself doesn't block anything without extensions, that seemingly less than 10% of users use extensions and that tgere5are already quite a few snappier browsers that block ads by default...
reply
Haven't all the major browsers had sync for ages? I've been using Firefox's built-in sync for so long I don't even remember what it was like without it.
reply
You act like it hasn't been done before.

Also, switching browsers is trivial. I do it on my parents' machines and they don't notice

reply
It's so much easier to switch browsers than platform/OS. Unless you have an iPhone or iPad.
reply
I'm reading your comment on Firefox. You can probably read mine and write a reply on it too!
reply
That's crazy! I'm commenting from Firefox! What a crazy world! How is this even possible?!
reply
Donate to Ladybird https://ladybird.org/
reply
reply
I don't think he said anything factually incorrect though?
reply
And yet again comes someone pretending as if unhinged far right rants embracing racism and white victimhood is some sort of objective truth seeking. It's unfortunate that this has become so normalized here.
reply
They have their own problems. They may be "open source", but they don't accept contributions. I'm skeptical it will ever become more than a hobby project.
reply
Is not accepting contributions the only/biggest issue you have with the project? I'm honestly becoming more and more okay with the "cathedral" style of open source. Depending on the project, catering to "the community" can lead a loss of focus, lack of a cohesive "vision" or scope, and just generally trying to be everything to everyone without the resources to maintain a giant beast.

With something like a browser (engine), I'm totally okay with someone saying "I'm an expert and I'm trying something with my own vision/priorities. I don't want input from random people that I have to spend time evaluating."

reply
Yes I can relate to this. Picking good, valuable feedback out of the noise has become a chore.
reply
Commit activity actually increased after they blocked external contributions in June: https://github.com/LadybirdBrowser/ladybird/graphs/commit-ac...
reply
It's on BSD license, Google or someone else can again Embrace, Extend, Extinguish.
reply
That is not possible. Google, or anyone else, can make a fork of the project. But they can't take away the original from the commons.
reply
Well, it is time to realise that GPL and similar variants, are better in the long term. I like MIT too, but GPL worked so much better for the linux kernel. Google and others abuse the ecosystem of open source contributors here.
reply
You mean the Linux kernel that the GrapheneOS project has to request every update for and then has to wait up to weeks to get a Google Drive link?

The GPL is worth nothing if nobody is enforcing it aggressively.

reply
The GPL is the only reason they even get that. More enforcement would certainly be good, but it's not like the GPL is worthless without a legal team backing you up.
reply
Could you quote the part of the GPL that they're not adhering to (which you seem to be implying), in this situation?
reply
There has been a long discussion about this a while ago on HN when these delays came up. The relevant blurb:

Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

Many people argued that 'customarily used for software interchange' is worded-as is to always be relevant to the times when the license is applied and that providing access to a Git repository is customary nowadays. In fact:

- The upstream Linux tree is distributed through Git.

- The relevant Pixel kernel sources used to be distributed through Git.

IANAL, so I am not sure how this part of the license will hold up in court, but the spirit is clear. Providing a Google Drive link is not customarily used for software interchange.

Also, I think it is fairly clear that the procedure is put in place to make everyone's life difficult, given that the relevant source used to be distributed through Git.

reply
Yes, as opposed to the Fuchsia kernel where they wouldn't even get that. We're lucky Google is institutionally incapable of creating things.
reply
LOL "start" using Firefox. I've been using Firefox for half a decade. There's zero I miss about Chrome.
reply
Rather than being smug, I’ll say awesome! The best time to start using Firefox is yesterday. The second best time is now.

IOW:

Don’t threaten to stop using Google Chrome if they do one more evil thing. Start now.

reply
Some of us have been using it for two decades more or less.
reply
LOL half a decade.

I've been using it for more than 20 years.

I don't know why either of use loled though

reply
LOL, I've been using it since Netscape Navigator 3.0 Gold, via Mozilla M3 (SeaMonkey tech preview), Phoenix, Firebird, and then finally Firefox :D
reply
Me too. Too bad I had to abandon it because Mozilla seem more focused on making AI-nonsense than a browser nowadays. No, Firefox, you don’t need AI features. You do need a better UI. You do need smoother scrolling. You do need privacy focus (which automatically means you do not need AI features). You do need to feel like you belong on the platform you’re installed on and not wish everything were Linux. You do need better designers that understand UX is not just “add controls everywhere”.
reply
I'm assuming you use Lynx now then? Because I don't think you would be using Chrome or its clone if that's where you draw the line?
reply
Huh? What ai features? Firefox seems largely the same as it did a few years ago.

I’m not doubting they added some ai junk somewhere. But whatever they did seems very easy to ignore.

reply
Its just an excuse people use to keep using thier beloved shiny brand.
reply
Oh, those great days when the competition was NCSA Mosaic.

A simpler, better time. I miss it :(

reply
Mosaic :P
reply
I've been using it since the time it was called Netscape Navigator. Just sayin'
reply
Loved netscape navigator! That entire suite with mail, website builder (composer?)
reply
Shit, remember Mosaic? Gopher?
reply
Any fellow CompuServe users around???
reply
There are already several different forks of Chromium and they are able to make their own decisions on points where they want to differentiate from upstream or other browsers in the market.
reply
> Just because it is open source doesn't mean they don't control it

Just point out how that hurts security or privacy and we’re with you!

reply
Ahem. Ladybird.
reply
It's sad we lost ChromeOS. They got Linux, they got open source, they didn't make so so so many unforced errors.

Now that the chromebooks are also Android, it feels like the slide is only going to grow ever more fearsome.

reply
Google is also seriously dropping the ball in terms of security. The CVE-2026-43499 root LPE (aka ghostlock) is still unpatched across all Pixel devices, on the latest """security""" update, despite weaponized exploits being public for months.
reply
Pixels used to have far better updates than any other Android devices but they stopped improving it years ago. It should have kept improving because it's not at all adequate. They need to be able to release OS updates more than once per month and it shouldn't take months for patches to make it into the OS. It currently takes them at least around 2 months to get even the most urgent patches into the OS. They could fix emergency calls being broken if the patch was made around 3 weeks before an OS release, but that's about as quick as they can go. It's not at all adequate for security and is a complete joke compared to Chromium's release cycle. They can get an emergency Chrome update released within a couple days. They should at least be able to do it for the Pixel OS in a week.

GrapheneOS is often around 4 to 6 months ahead on merging Linux kernel LTS releases. We used to handle this ourselves but switched to the Android GKI LTS branch maintained by Greg KH. Unfortunately, it was often struggling to keep up even before the absolutely massive increase in Linux kernel security patches this year. AI models have rapidly accelerated vulnerability discovery and it's an ongoing crisis for the Linux kernel. We want to be on the latest LTS revision within days and want to be using the latest LTS branch within months of it being released. We're not at all happy with how Android is handling things and plan to fix that ourselves. We'll get things back to how they should be.

We also ship all the AOSP userspace patches months before Pixels due to shipping all of the security preview patches as soon as possible. There are sometimes minor regressions but we find and fix them ourselves downstream. The security preview system has a terrible design especially considering that frontier AI models can reverse engineer the patches. There should at least only be a source embargo for around 24 to 72 hours rather than pretending as if it can work with the patches available 2 to 6 months in advance.

reply
I'd love to use GrapheneOS on less secure devices, just for the sake of Google autonomy rather than privacy.
reply
GrapheneOS will be available on Motorola devices meeting all of our requirements for updates and security features in 2027. It will be starting out on a high end flagship and expanding down from there as devices improve to meet our requirements. We aren't going to support devices unable to provide a reasonable level of security.
reply
GrapheneOS's goal is privacy for the world and that's achieved through secure devices. You can get a phone specifically for GrapheneOS just as you choose a new device when you're buying a new one. Soon there will be two different phone brands which you can install it on. There's already an estimated 500,000 users with Pixel exclusivity.

https://grapheneos.social/@GrapheneOS/117249893761790371

reply
> GrapheneOS's goal is privacy for the world and that's achieved through secure devices.

Perfect is the enemy of good. What's better for privacy, an old but inexpensive smartphone running Android 11, or the same smartphone running an up-to-date third-party rebuild of Android 16 or newer with as many privacy-improving bells and whistles as the hardware can support?

> Soon there will be two different phone brands which you can install it on.

...will they be available in my country (Brazil)? I don't think I've ever seen a Google Pixel phone in person.

reply
What's better for privacy, an old but inexpensive smartphone running Android 11, or the same smartphone running an up-to-date third-party rebuild of Android 16 or newer

I see your point, but it would be very misleading, since the phone would still have a lot of known holes. Only the OS would get updated, typically not the drivers, driver firmware, possibly not the kernel. The phone would still be easily compromised through all the known RCEs. So you tie up non-profit projects in a lot of extra work to get an improvement that does not really matter.

This is a mess created by the OEMs and they will continue to create this mess until people will stop buying from OEMs that only give lip service to security updates (roll out Android Security Bulletins to show a high patch level, while in reality the phone the phone has many known CVEs).

reply
Are all of these unsuitable [0]?

Not sure if you have any experience with eBay. I looked it up and people had problems selling to Brazil [1] but there are various listings that offer to ship. So maybe not a great option.

KaBuM!, Intec Store, Performance Solutions all charge significantly more with a 10a being more than double than from Google.

Motorola officially sells the Signature in Brazil [2] at the same price or cheaper than in the UK. It will be supported by GrapheneOS in 2027 on the 2027 version. From then on, hopefully Qualcomm brings MTE to the non-flagship chips and Motorola and GrapheneOS support budget or midrange devices.

>perfect is the enemy of good

I don't consider that relevant when users deserve ≥ security than an iPhone. GrapheneOS is not purpose-built to avoid big-tech's services although it does that more completely than any other alternative mobile operating system, the focus is privacy.

GrapheneOS on the state of privacy and security for their ethos: https://x.com/GrapheneOS/status/2044440381803069778

[0] https://www.ebay.com/sch/i.html?_nkw=google+pixel+9

[1] https://reddit.com/r/Ebay/comments/1d92pyn/

https://community.ebay.com/forum/shipping-57923/topic/diffic...

[2] https://www.motorola.com.br/smartphone-motorola-signature/p?...

reply
> Are all of these unsuitable [0]? [...] I looked it up and people had problems selling to Brazil [1] but there are various listings that offer to ship.

Do these phones have ANATEL certification? Because if they don't, they will be rejected by customs. It's not simply a case of the item being held until you pay a 60% import tax.

reply
Same thing here, I use Graphene for the sake of user control. All the security features and hardening of the Pixel phones and of the OS are good to have, but they not the main reason.
reply
You can dot his but it won't be Graphene but something else, like LineageOS. As long as Graphene's selling point is extreme privacy and not just more privacy, it will be this way.
reply
There is no such thing as extreme privacy; it isn't something any phone can provide, especially if you are going to rely on third party software and services like email and instant messengers where the likes of Google and Facebook are dominant players. Even behind a VPN, Vanadium is fingerprintable by commercial trackers like fingerprint.com. Short of disabling Javascript, browsers leak enough information to basically follow anyone around the internet.
reply
deleted
reply
I just ran https://github.com/CakesTwix/Android-CVE-2026-43499 on my Pixel 9 Pro and it seems to have been patched. I did get a system update not long ago, though.
reply
Try https://github.com/alex193a/Root-My-Pixel, worked on my 9a as of a few days ago (the version table in the readme is stale). I haven't checked the September update yet though (installing it now, to check).

Edit: September update for 8a has a kernel build from July. I believe it's still vulnerable but the exploit will need its offsets adjusting etc.

reply
deleted
reply
There's "dropping the ball" and then there's "not reaching out your glove to catch it to begin with".

It'd be interesting to see which one is happening here.

reply
It's not a regret. Android would never have been popular in the first place if it had not been open source. If phone makers had been able to anticipate how much the demons at Google would be able to lock down the Android then they would never had used the OS back in ~2009.
reply
I don't think this is actually true. Phone makers seem happy to have the platform locked down even further. They're putting even more roadblocks, as evidenced by most of them making bootloaders unlockable.
reply
They're happy that it is locked down. They're not happy that they're not the ones doing the locking down.
reply
They can easily go back 30 years ago, when each one had their own proprietary in-house OS, using current Android as baseline, or something BSD like PlayStation.
reply
Any discussion about this is shut down. I just read an article https://www.bbc.com/news/articles/ckqxvy98x578o In the UK according to the BBC, politicians are pressing Samsung and apple to make stolen phones bricks. Samsung in response said that they have implemented several security features for this purpose. I think Samsung considers removing OEM unlocking a security feature according to the bootloader unlock hall of shame.

Intel used to do the same with their anti theft technology aka Intel theft deterrent on their classmate PCs, so students had to enter unlock codes from an IT admin every 3 months or every say 200 boots to prevent the computer from being locked at the bios level preventing it from booting an OS, and there was an update which disabled that functionality permanently. And you would be warned when you had around 50 boots left to get the unlock code.

reply
Normally the codes would be downloaded automatically from a server but sometimes the server would go down due to negligence because it would be owned by the school and well, student's laptops would start getting locked and they would have to go to a specific office somewhere in the city to get an unlock code from the it admin
reply
It could be disabled from the bios somehow if you knew the bios password or the bios could be reflashed with a programming Clip directly on the bios flash chip itself.
reply
Normally you have to unlock the phone before unlocking the bootloader, and that is the protection.
reply
I would think they are guessing most people's passwords are weak or something. Like a screen pattern is weak, can be broken in just 300k attempts or maybe less because people use the same patterns and people can't be bothered to use passphrases.
reply
A screen pattern is a different way to enter a PIN with no duplicate digits. Both PINs and patterns rely upon the security processor to resist bruteforces.
reply
Making the bootloaders unlockable is a good thing.
reply
I think OP misspoke. He probably meant that they're not able to be unlocked by the consumers, usually.
reply
This is what lots of people forget.

Android is not a Linux desktop or server distro. It is not about you getting to put what you want on the hardware you bought for free.

Operating systems are hellaciously expensive to maintain and that only gets worse in markets with rapid hardware improvements, as the smartphone market was up until maybe the late 2010s. Google is not a charity. SV did not come into national prominence for making investors $0. There is no money in giving maybe one in one-hundred smartphone users (and that's being generous) a bunch of code, for free, so that they can put it on their gizmo and talk to their nerd friends at their hacker meetup.

When they pitched Android as "open", they meant that carriers and device makers could load it up with all of the revenue-enhancing bloat that they wanted. In return, Google got a device that would let them hoover up all of the data they could ever want in order to build better ad service profiles for those using the devices. That is, after all, their business.

For a while, this could coexist with us screwing around with a real-life tricorder. At some point, though, the free stuff turned into a revenue opportunity that had to be exploited. And so, it will be.

reply
> For a while, this could coexist with us screwing around with a real-life tricorder.

Wish I could upvote you twice for that line alone. It perfectly sums up what I always wanted Android to be. Alas, the closer we are to this in hardware, the further away we are getting in software.

reply
Especially Android, which is an ever-growing pile of spaghetti almost as bad as Windows.
reply
I'd say Android is already worse. It uses more ram and resources to run smoothly than Windows does. Especially now that Microsoft is actively trying to speed up Windows 11 and make it use less resources.
reply
Haha and not true. You would need to provide objectively more than your experience. And for an example clicking on Android Contacts would be instant vs load time in Windows 11 (the one i have).
reply
Did you try to scroll the list tho?

(Did they fix that whole "store contacts in a linked list" problem in Android already?)

reply
That's a different axis from spaghettiness.
reply
That’s possible (never underestimate the bad decision-making of phone makers), but what would they have done instead? Windows Mobile 6 was the only licensable alternative, but it was a known quantity and obviously a generation behind Android and iOS.
reply
Symbian and LiMo were both available at the time. It is hard to say they were good alternatives though. Windows 7 - even with the weight of Microsoft behind it - wasn't able to attract enough hardware manufacturers.
reply
Windows Phone was pretty nice, too bad Microsoft didn't follow their DOS and Windows strategy of getting it preinstalled on every consumer PC sold. There was really only the Nokia Lumia line that I recall, but everyone I knew who had one loved it.
reply
Windows Phone 7 didn’t ship until 2 years after Android. 2 more years later Windows Phone 8 was released and it was a legitimate option but just too late.

Pre-7 was just not an operating system that anyone except the geekiest of geeks wanted to use.

reply
Not doing any OS upgrades from 7 to 8 and only very few from 8.x to 10 certainly didn't help either.
reply
Yeah I guess Apple set too high a bar and MS was caught flatfooted (again) and was too far behind.
reply
I don’t have visibility into what happened with the Windows Phone team, but Android from what I understand saw immediately that they needed to follow Apple’s lead and pivoted (originally they were building something closer to a BlackBerry). The Windows Phone team either didn’t believe they need to pivot initially or they just took too long to do so.

Windows Phone is a case study of missed opportunity.

reply
deleted
reply
Maemo.
reply
I remember using a Maemo device circa 2009. I recall overall really liking the OS.
reply
WebOS was pretty cool (Palm). But I’m not sure if Palm would have licensed it. Lg ended up with it.
reply
There were several credible competitors: WebOS, Symbian, Maemo/MeeGo, Palm OS 6, and of course Windows Mobile. But they required cooperating with a single vendor and/or a lot of work to adapt.

Android won because it was available "right now" and easy to hack. Vendors could get a BSP (Board Support Package) from a chip manufacturer, slap Android userspace on top of it, and ship a phone within half a year. It was a glorious mess for a while.

Google then slowly tightened the reins and made the ecosystem more ordered.

reply
Not even wearing rose tinted glasses right now, for having daily driven them back in the days, maemo and then WebOS had touch ergonomics and multitasking abilities which took Android/iOS decades to incompletely mimic. Maemo/Nokia N900's design principle seems to have been "let's provide the user with desktop-level productivity tools, and shrink the desktop into their pocket", the package was massive for the era's standards, but is tiny for today's, and those dumb-down/low density ergonomics we have now give us less capabilities for more screen estate and weight (even something like an iPod pro is a "dumb" content consumption device in comparison). WebOS on the other hand was not about "producing/delivering on the go" so much as it was about getting your digital must haves (booking an appointment, updating a contact details, moving a meeting, ...) done and out of the way with just a couple key presses and finger flips as so distract as little as possible from the present. Only some advanced Android launchers get close, but it's never the focused, well polished and distraction-free experience it was back then (and for the same reason, Android/iOS are addictive content delivery vehicules meant to sink your eyeballs and time as to sell you stuff or collect and merchandise your data).

I'm interested and wishing to see a future mobile OS that does not pander to the "attention economy" like Android/iOS are, but with billions now addicted and trapped by it, I'm realistic that it won't be an overnight success.

reply
Sailfish OS exists as a continuation of the Maemo project, even shipped their own phone recently.
reply
Yup, I would love to try it in-hands (I looked it up on emulator many years ago, and that was frankly underwhelming). I'm also not sure about their open source situation, which was the premise of this thread.
reply
No, everyone knew what they were getting into with Android. It wasn't taken lightly by the power users of the time either. I still have a phone somewhere with Ubuntu Touch on it. I really was hoping that would be my phone OS by now. Not that Canonical isn't capable of similar, but that it would bring about acceptance of Linux phones.

I think we're all more surprised by how long it took for Google to make these bad moves. For a period of time in the 2010s we actually started thinking maybe Google was alright.

reply
It wasn't Canonical's limitation. Mozilla can confirm: the barriers to enter the phone manufacturing market are immense. Samsung, Ericsson, Sony, LG, etc, all had solid control of the deals with the network operators worldwide. It's a highly regulated market, you can't get in without Verizon, att, Vodafone etc to let you in. Canonical, Open Moko, Mozilla... Didn't have the strength to push through. Google and Apple did.
reply
It's operators that have grips on manufacturers. Phone OEMs don't make any without the sales networks and financing structures of cellular carriers.

This is to extent that some carriers still insist that they design phones and phone manufacturers are just factories. People need to understand that power dynamic before blaming those "mere factories" for not making Linux phones.

There has to be like an SVP of SoandSo Wireless pushing like three pillar approach of iOS, Android and Linux. Otherwise the pitch decks for any alternative phones just go straight to trash(or into a motorized shredder if it is still physical).

reply
>It's operators that have grips on manufacturers

Only in the USA.

reply
In quite many more countries than just USA. A lot of people would still buy phones through carriers even where they come unlocked.
reply
Worst case we can buy phones and physically replace their Application Processors with liberated ones.
reply
Phone manufacturers had Symbian which became open source
reply
It didn't become a major regret really until the antitrust treated android as a competitive space and iphone separate. That decision led to a lot of wtf and tactics changing. Because the platform had been made open it was then an issue of tying vs if it had just been closed like apple there wouldn't have been an issue was a pretty stupid take if you ever want to see an open platform again.
reply
I'm convinced Android being open source is just an accident of history. It's been somewhat useful for Google to be able to ride on that goodwill, but they're not actually invested in open source beyond the ways it directly benefits them (or at least they haven't been in the last 10 years). Thus they're happy to throw the baby out with the bathwater if they believe they need the bathtub for anything that will earn them 0.1 cent more than that baby would.
reply
It's like PC parts being modular. IBMs greatest mistake and the industry wants to make sure it never happens again.
reply
When IBM tried that with PS/2 it didn’t go so well.
reply
Its more a reflection of the vastly different internal culture of the time (and different executive leadership).

When Patrick Pichette left and Sundar became CEO both led to massive culture shifts.

reply

  > Google simply regrets android being open source.
No, they are benefitting from it! They gained some trust and removed competition from the horizon. Now they are locking the platform down to do what their business is about: displaying ads.
reply
They want to be like Apple here and lock things down. Remember SMS? The ubiquitous text messaging protocol that had an API that developers could access? Now, the latest standard, RCS, is locked down with no API and behaves just like iMessage. Ring any bells?
reply
There was a split world for a long time even before the more recent changes because of the need to hide secret new features or products from the general public. It was always a tricky arrangement. They just decided one day that there wasn't a lot of folks contributing that lacked access to the private repos, so they might as well just switch all development to occur in that place. Honestly, it's somewhat rationale. If there was a significant number of folks contributing to Android without such access I'm sure that wouldn't have happened. We didn't lose as much as folks think we did given the code drops from the private repos still happened even previously.
reply
There's a non-zero chance that three-letter agencies are lobbying for at least some of this.
reply
Yeah. Which doesn't mean Google isn't happy to comply for its own profit motivations.
reply
It makes perfect sense when you apply the Friedman doctrine to their actions. [0]

Google is a lawn mower, stop anthropologizing them. This goes the same with Apple, Microsoft, Meta, Amazon, ...

[0] https://en.wikipedia.org/wiki/Friedman_doctrine

reply
Agree. The only time a company does something in the public interest is when it believes doing so would ultimately benefit the shareholders. Everything is a business decision.
reply
As an outsider in a hyper competitive commercial space like mobile os (apple, android) which part makes you think it's active obstruction and not just moving fast and trying to keep up, get ahead, etc and they want the open source side but it's a lower priority?
reply
> None of their decisions make any sense ..

What? Google is advertisement business. Not a software house. They sell ads. It all makes sense to build a walled garden. They are effectively a monopoly for half of the personal devices _in the world_. And they _will_ return their investments into the opensource. By locking Android and Chrome and showing ads to everyone.

Like the old days shitty TV, full of ads.

reply
The thread states that Google is putting out patches that affect other Android vendors too.

They're not treating GrapheneOS very differently from other vendors, except that Graphene isn't relevant enough to sign a contract with because they don't make phones (or money, really).

Google should be putting out the code and patches like they used to, but the constant badgering of Google on this issue feels off. I don't see anyone complaining that Samsung isn't supporting their security-focused fork enough, or complain that Apple is delaying the bootloader unlock process by a day.

Despite their very worst, selfish intentions, Google is the very best vendor of commercial open source software. While Google's open source project collapses, there's plenty of space for other vendors to step in.

We should bemoan Google's fall from grace, but only because they're on the way to becoming just as bad as every vendor but Librem if they keep this up another decade.

reply
Librem seems as bad as a typical Android OEM. Maybe I'm looking at the wrong repository, but the barely seem to update driver firmware?

https://source.puri.sm/Librem5/fw/firmware-librem5-nonfree

https://source.puri.sm/Librem5/arm-trusted-firmware

I hope I'm looking in the wrong place.

reply
> Google simply regrets android being open source.

Could Google backtrack on this if they wanted? If they suddenly decided to stop releasing public code updates, what would they be violating? I can guess: Anti-trust maybe. probable at least contractual commitments Or is there some stronger forcing function?

reply
Yeah I have trouble accepting it's pure coincidence this occurs just as GrapheneOS is starting to gain some noticeable traction.
reply
When you realize that keeping people on proprietary mobile OSes is a matter of national security it makes more sense. The USA spares no expense for national security.
reply
It's a net loss. Less data and in their view makes development harder.
reply
And don't forget about Manifest V2/uBlock Origin removal!
reply
deleted
reply
It's not that it doesn't make sense, you just said it, they regret - well maybe not regret since they'd never made it without, but they now want to reverse a decision they feel needs to be overhauled. I always thought they'll replace Linux with Fuchsia but that hasn't happened and it's not like they couldn't have done it.
reply
> None of their decisions make any sense

It only doesn’t make sense if you’re assuming conspiracy.

It makes a lot more sense if you assume they just don’t give a shit.

reply
> None of their decisions make any sense,

Of course, it does. Google is no longer afraid to spit on open source. People happy to use Chromium features better remember this. You are renting everything and your landlord will soon come demanding it back.

reply
If someone’s (or some company’s) decisions don’t make sense to you, you don’t understand their motivations.
reply
[dead]
reply
> Google

Can we just stop saying "Google" as if it's same faceless org? No, it's not Google, one or two asshole execs are behind this policy.

reply
The org takes responsibility. If you want to additionally name & blame an exec feel free.
reply
GrapheneOS does not even register on Google scale! It does not even manufacture its own devices!

Bigger problem is HarmonyOS and similar devices, compatible with Android. Opensource threat from china!

And no NSA backdoors or honeypots!

reply
If the hardware security is on par with iPhone / pixel 8+, then sure.

Otherwise there's no need for NSA backdoors (as Cellebrite matrix shows) :)

reply
GrapheneOS does, however, register on the FBI's radar because a lot of criminals know to use it, and the FBI can't crack it.
reply
Sure, let's just trade the NSA for the CCP, no issues there.
reply
One poses an active, unchecked threat to the constitutional rights of US citizens, has a chartered mission to subvert and undermine the very field of cryptography itself - going so far as to bribe standards bodies to adopt backdoored algorithms (using taxpayer funds to do so), has plotted to mass-violate the constitutional rights of their own citizens and lie about it to the national legislature (which they carried out successfully, committing perjury in the process and facing zero consequences for it), secretly cooperates with the criminal justice system via parallel construction to target nonviolent, law-abiding political activists with fabricated criminal charges as retaliation for politically disfavored speech, while the other is about 6500 miles away, has negligible presence in / reach into the US, and is generally unconcerned with the domestic political activities of US citizens.
reply
I agree–it's absurd to be more concerned about spying of China on American citizens than the spying of our own government. While allies of the US are problematic because of however many eyes.

Not particularly relevant but the lawful spying implemented in the telecommunications system by our own government has been abused by Chinese hackers as well.

reply
+ 3 social credits, comrade
reply
> has negligible presence in / reach into the US, and is generally unconcerned with the domestic political activities of US citizens.

lmao

reply