Recent submissions

Comment · 11 months ago
is this real?
Comment · 1 year ago
More context, Comet browser (which is Chromium-based) clearly states its use of Chromium in its Help > About Comet section (comet://settings/help). Similarly, other Chromium-based browsers like Dia (via Dia > About Dia) and Arc (Arc > About Arc) explicitly attribute their open source foundation in their About sections, making the credits easily discoverable for users. It seems Atlas could improve transparency by following this standard and including similar attribution in its About/help dialog.
Comment · 1 year ago
That does help a bit—at least there is some public acknowledgment buried in the help docs. But isn’t BSD license attribution usually expected within the product itself (like a credits screen or in-app NOTICE)? It feels like this isn’t meeting the standard for open source transparency—especially for a major project like Atlas.
Comment · 1 year ago
Thanks for mentioning atlas://credits! If it's not linked anywhere or visible to regular users, I'm not sure it really counts for proper attribution. License compliance usually means info is discoverable without digging—otherwise, transparency is lost. It seems like Atlas should make their open-source credits more accessible.
Comment · 1 year ago
Comment · 1 year ago
Honestly, it feels like they're intentionally trying to scrub any traces of Chromium or Google. No mention anywhere, blocked chrome:// pages, UI stripped of references—it's as if they don't want users to realize it's built on open-source tech. It's a weird move for transparency and doesn't sit right with me, especially with all the attribution requirements.
Comment · 1 year ago
Something's bugging me about Atlas - it's clearly Chromium-based (you can tell from the user agent and UI), but I can't find any credit to Chromium anywhere. No license info, no acknowledgments, and when I try to access chrome:// pages they're blocked.

Maybe I'm overthinking this, but shouldn't there be some transparency about what you're building on top of? Especially with open source projects that have attribution requirements? I get that it's still early days, but this feels like a pretty basic thing to get right.

Anyone else notice this or know if this is standard practice? Just seems odd to me that they're not being upfront about the foundation they're building on.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton