Hacker News Reader

Comment by tommica | Hacker News Reader

Its the monetizing part that makes me think its not Omarchy - they have no monetizing things.

They're referring to Omarchy, it's very clear on their IRC

I saw that's there is an Omarchy for Mac "team" consisting mostly of one guy who is active on Twitter (and quickly amassed many followers) and seems to have no prior experience of working on Linux kernel. They do not mention Asahi anywhere which isn't surprising to me given the reputation of DHH and Omarchy. This hijacking of open source by bad faith actors is very concerning.

Yeah, on their GitHub for example, in their m1n1 fork they tend to refer to "upstream" as... the main branch of their fork.

Very interesting choice of words, but again, all their work including all issues and docs are LLM-generated.

Nonsense.

> Omarchy on... > Apple M1/M2 chips# > Asahi Alarm is a version of Arch for Apple M1/M2 computers built on top of Asahi Linux. You can get Omarchy running on top of that with some effort. See the user-driven guide.

Source: https://omarchy.org/manual/omarchy-on/

> [...] You finished what Asahi started, and you’re already pushing on to M4, M5, and M6. Thank you!

Source: https://omarchy.org/news/2026/11/marcelo-alcantara-and-birk-...

Omarchy has gotten somewhat of a reputation for getting a lot of sponsorship money from commercial actors. If by monetize you mean "Get people to pay us" omarchy are definitely monetizing. Not much different to Asahi themselves of course, but is it right/moral to fork another active projects code and use it in order to gain your own patrons? I don't hold the answers. But no they aren't selling anything.

edit: worth noting this example, where DigitalOcean started cutting OSS support only to pledge millions of dollars to Omarchy. No wonder people consider the project a leech to the OSS community, but also consider correlation != causation: https://itsfoss.com/news/digitalocean-open-source-credits-en...

DigitalOcean obviously cut their OSS support because they gave it as credits for a year and it required constant human review and interaction.

At the same time it was mostly to small OSS projects that dont have formal non-profits so no tax exemption benefits to DigitalOcean.

It is worth noting the same article's discussion of nodejs reads as "DO shut down a program, possibly planning a v2 of said program, but failed to communicate it to its dependents and didn't realize until they started planning to leave". Or they were just fighting the fires caused by a github issue named "Transition off of Digital Ocean" caused \o/

They do have large entities donating to them

Reply on news.ycombinator.com