frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•2m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
3•sakanakana00•5m ago•0 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•7m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•8m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•9m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
3•Nive11•10m ago•4 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•13m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
2•chartscout•16m ago•0 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•19m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•20m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•25m ago•0 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•27m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•29m ago•0 comments

Bash parallel tasks and error handling

https://github.com/themattrix/bash-concurrent
2•pastage•29m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
2•billiob•30m ago•0 comments

Reverse Engineering Medium.com's Editor: How Copy, Paste, and Images Work

https://app.writtte.com/read/gP0H6W5
2•birdculture•36m ago•0 comments

Go 1.22, SQLite, and Next.js: The "Boring" Back End

https://mohammedeabdelaziz.github.io/articles/go-next-pt-2
1•mohammede•41m ago•0 comments

Laibach the Whistleblowers [video]

https://www.youtube.com/watch?v=c6Mx2mxpaCY
1•KnuthIsGod•43m ago•1 comments

Slop News - The Front Page right now but it's only Slop

https://slop-news.pages.dev/slop-news
1•keepamovin•47m ago•1 comments

Economists vs. Technologists on AI

https://ideasindevelopment.substack.com/p/economists-vs-technologists-on-ai
1•econlmics•49m ago•0 comments

Life at the Edge

https://asadk.com/p/edge
4•tosh•55m ago•0 comments

RISC-V Vector Primer

https://github.com/simplex-micro/riscv-vector-primer/blob/main/index.md
4•oxxoxoxooo•59m ago•1 comments

Show HN: Invoxo – Invoicing with automatic EU VAT for cross-border services

2•InvoxoEU•59m ago•0 comments

A Tale of Two Standards, POSIX and Win32 (2005)

https://www.samba.org/samba/news/articles/low_point/tale_two_stds_os2.html
4•goranmoomin•1h ago•0 comments

Ask HN: Is the Downfall of SaaS Started?

4•throwaw12•1h ago•0 comments

Flirt: The Native Backend

https://blog.buenzli.dev/flirt-native-backend/
3•senekor•1h ago•0 comments

OpenAI's Latest Platform Targets Enterprise Customers

https://aibusiness.com/agentic-ai/openai-s-latest-platform-targets-enterprise-customers
2•myk-e•1h ago•0 comments

Goldman Sachs taps Anthropic's Claude to automate accounting, compliance roles

https://www.cnbc.com/2026/02/06/anthropic-goldman-sachs-ai-model-accounting.html
4•myk-e•1h ago•5 comments

Ai.com bought by Crypto.com founder for $70M in biggest-ever website name deal

https://www.ft.com/content/83488628-8dfd-4060-a7b0-71b1bb012785
1•1vuio0pswjnm7•1h ago•1 comments

Big Tech's AI Push Is Costing More Than the Moon Landing

https://www.wsj.com/tech/ai/ai-spending-tech-companies-compared-02b90046
6•1vuio0pswjnm7•1h ago•0 comments
Open in hackernews

I'll only buy devices with GrapheneOS

https://www.jonashietala.se/blog/2025/08/28/ill_only_buy_devices_with_grapheneos/
103•lawn•5mo ago

Comments

pjmlp•5mo ago
The fallacy is that AOSP (which GrapheneOS forks from), and Chromium used to install it, are both dependendent on Google engineers, money, and the willigness to keep the platforms open, to some extent.
gradientsrneat•5mo ago
A fallacy which the author acknowledges.

> "I guess the best way to degoogle right now is to buy from Google"

Google has a monopoly on sort-of-open-but-not-really smartphones. And interoperability on ARM desktop isn't looking pretty either.

pjmlp•5mo ago
This looks the same kind of situation when I noticed FOSDEM corridors started to be full of Apple laptops, but apparently the irony is lost on new generations.
hungmung•5mo ago
I remember about 10 or 15 years ago somebody pointed out that a big chunk of the GNOME devs used Apple laptops, even at public appearances, and it answered a lot of my questions about the state of the project.

(and I say this as a user of GNOME)

estimator7292•5mo ago
I think that perfectly explains why GNOME is the way it is.

Funny enough, that's also why Windows is in the state it's in. Funny how that works.

jajuuka•5mo ago
They really don't. It's just that development of custom roms like GrapheneOS are centered around Pixels. Plenty of other devices have unlockable bootloaders. The custom rom scene though is so small that concentrating on a couple devices is the only way to keep development moving forward though. Same reason why Asahi Linux is the only option on Apple Silicon Macs.
wkat4242•5mo ago
Many have unlockable bootloaders (though the number is rapidly declining with Samsung closing up). But not many have relockable bootloaders. This is one of the things that grapheneos have set as a minimum standard, hence the reliance on pixels. There's a few other specific things that the titan chip provides which they rely on but the relocking is the main thing.
ycombinatrix•5mo ago
To be more specific - relockable with a custom AVB key. I think most devices can relock with the default Google AVB key.
wkat4242•5mo ago
Well they can but not with custom firmware installed. As grapheneos is custom firmware, the google key makes no sense in this context.
subscribed•5mo ago
"unlockable bootloader" is the requirement to flash anyone alternative on the phone, yes, but the GrapheneOS you mentioned will support _any_ device that is "flashable" and secure enough: https://grapheneos.org/faq#future-devices

Currently it's only Pixels from 8 up.

Other alternative firmware projects don't seem to be too concerned about security (eg they don't support relocking bootloader, don't support secure boot, don't release patches for months), so they're not really in the same ballpark ALTHOUGH I agree that they still might be better option than stock OS on the device abandoned by the vendor.

subscribed•5mo ago
There's simply no choice with hardware now if someone wants it to meet some secure baseline.

No other vendor makes secure android hardware.

neodymiumphish•5mo ago
Is your alternative that someone should build a complete from-scratch alternative OS that can still be booted on the same hardware?

For the time being, AOSP and Chromium are still open source, so why not piggy-back off of all that labor and development to provide what GrapheneOS users want at minimal cost and effort?

pjmlp•5mo ago
If the goal is to be fully free from backdoors and development being cutted out at any time, yes.
neodymiumphish•5mo ago
If the source is fully open (it is) than detecting and disabling backdoors is completely possible. Not to mention the fact that other OS projects face the same risks.

If Google cuts development of AOSP in favor of some closed-source alternative, the GrapheneOS team could simply continue development of AOSP on their own.

wolvesechoes•5mo ago
> If the source is fully open (it is) than detecting and disabling backdoors is completely possible

There exists a possible world where a group of underpaid FOSS devs forked Chromium and AOSP and effectively developed it further.

But it is not our world.

> the GrapheneOS team could simply continue development of AOSP on their own.

They won't be able to do so.

neodymiumphish•5mo ago
Which makes the idea that a group like them could build their own OS from scratch all the more unattainable... That's the point I'm trying to make. At least if Google ever drops AOSP, it would be when it's still an intact OS available to continue development on. Additionally, I suspect a group like Graphene could get a lot more support developing AOSP's replacement in that instance, considering how many other manufacturers and devices utilize AOSP-derived software.
phendrenad2•5mo ago
What makes AOSP so much more complex than open-source frameworks like Gtk and KDE? Or even partially-funded software like Gnome?
twelvedogs•5mo ago
Graphene relies on a lot of closed source driver code I would imagine
mindslight•5mo ago
If you define the goal that way, then you actually need to clear a much higher bar of making your own hardware. Personally I'd much rather maintain a long term fork of AOSP than have to design, market, sell, and support a new device.
BoredPositron•5mo ago
Sailfish is alright.
pdimitar•5mo ago
Do you have experience daily-driving it? Any prominent negatives?
BoredPositron•5mo ago
I use it on an XA2, which is a bit of an older phone, but even there it runs fine. Sometimes the Android apps slow down and you have to relaunch the application layer, but that's just one click and takes about 5 seconds. That said, most Android apps run fine. All the enterprise stuff works great (Okta, MS Authenticator, Exchange etc.). Native Apps are a bit hit and miss but development is rather easy.

I'd say the biggest pain point is that Google Maps doesn't work because of the lack of Google Play Services. The missing Maps/Play Services also breaks apps that rely on the maps API. Most of them just fall back to not showing a map at all while the rest of the app functions normally, but it's still an inconvenience. For turn by turn navigation I switched to HERE Maps which works without problems.

tpoacher•5mo ago
i used to have a jolla and loved my sailfish phone ... until the phone died and i could fix it ...

sailfish itself was great though. admittedly the android compatibility layer really helped though

msgodel•5mo ago
Desktop Linux works very nicely on smartphones actually provided all the drivers are there. I lived with a PinePhone running FVWM on Xorg for a couple years and if the hardware didn't crumble away I'd still be using it today.

No need to "build a complete from-scratch alternative OS" when that was already done 30 years ago.

nolist_policy•5mo ago
Did you actually use it as a phone?
msgodel•5mo ago
Yes although mostly over VOIP. Voice calls aren't actually very complex though of you prefer using those directly.
phendrenad2•5mo ago
Nah I consider that a fallacy. I'll call it the fallacy of the oranges. Let's say I control all of the orange trees in town. People resell my oranges. I begin using really strong insecticide that resellers try their best to wash off. I keep upping the strength and they keep trying to remove it. At the same time, there is one banana tree in town, and conveniently for my analogy, no pesticides are needed for bananas. As oranges continue to become worse, people will keep eating them, and saying that "there's no way people can switch to bananas. If they could, they would have already. And besides, there's only one tree..." Yes but these things can change. And eventually, people will switch to bananas en masse. People will truck in bananas. And we'll all act like we predicted the great banana switch the whole time. Like MySpace to Facebook, or Digg to Reddit. Or GSuite to Outlook. Or Skype to Zoom.
hollow-moe•5mo ago
Imo, Graphene wants to be a "Google certified" ROM OEM, they don't make devices but software. A good and secure ROM for sure but they're still begging them for Play Integrity[1] and "sandboxing" GMS isn't fighting Google. [1] https://grapheneos.social/@GrapheneOS/112878070618462132
jasonvorhe•5mo ago
"Taking legal steps" isn't "begging" though.
gausswho•5mo ago
This is not what they've claimed. Their pursuit of their own hardware phone next year could rattle the phone duopoly. If, and a big if, the intelligence agencies of the world will allow it to be sold.
jajuuka•5mo ago
If Pine64 can't pull it off with millions in funding then I'm not sure how Graphene is going to accomplish that.
gausswho•5mo ago
Those operations, much as i respect them, did not reach the attention that GrpaheneOS has. Have they reached a takeoff velocity that more principled players didn't? Wouldn't be the first time we sang that chorus.
pjmlp•5mo ago
As someone seeing this going on since OpenMoko, was at Nokia when Nokia 770 Internet Tablet was shown to employees for feedback before going public, it has always been the same story regarding getting these devices actually flying off the shelves from consumer shops.

Some enjoy more attention than others, savy people buying them online, and eventually fade away for the next attempt, while general public continues unaware of their existence.

gausswho•5mo ago
This too is part of a pattern. Punk followed rock and roll. Is GrapheneOS the band that brings the culture? I wanna say yes on its own merits, but it's the political buffoonery that makes me think it's caught some lightning in a bottle.
subscribed•5mo ago
No, they aren't begging?

They wrapped Google services into sandbox for users relying on done software (with great success, even Android Auto works), and raise Play Integrity lie/false security with developers and regulators (Google claims a handset without security updates for years is safe).

There's better (standard aosp) attestation mechanism GoS fully supports and which is supported by slowly growing number of developers (including banks).

subscribed•5mo ago
s/done software/some software/, sorry
playforclaude•5mo ago
There is no winning. Get an iPhone, or a dumbphone.
wkat4242•5mo ago
An iPhone is even less open
playforclaude•5mo ago
None of these options are "open". You just have to decide what you really want from a communications device.
jasonvorhe•5mo ago
A Pixel with GrapheneOS is pretty much as open as it gets. Any iPhone or Samsung is a downgrade from that.
playforclaude•5mo ago
How do you see that playing out in the medium to long term? Google have made it very clear that they're done with the "open" side to Pixel, and they have comparatively unlimited resource to throw at the issue.
tiagod•5mo ago
GrapheneOS team have published that they're working with a smartphone manufacturer that is working on releasing a phone that matches their security requirements.
wkat4242•5mo ago
But even then, Google will keep hampering AOSP efforts too in the long run.

They're also introducing a new requirement that sideloaded apps must be validated by them.

akimbostrawman•5mo ago
Which is irrelevant because GOS does not by default implement Google playstore and play services that have that limitation.

If Google implements the same play services sideloading limitation in AOSP which is unlikely, it can be removed like anything else because it's open source.

playforclaude•5mo ago
You missed the primary issue OP mentioned, which is that ASOP is becoming a smaller and smaller part of the entire OS, and there's an ever-increasing amount of work needed to make it work on a real phone.
wkat4242•5mo ago
Yes and also more and more apps are blocking custom ROMs.

Even the McDonald's app is doing it now (I know, you're not missing much there but still...). It refuses to launch if it was installed by any method other than the official play store.

subscribed•5mo ago
Still, GOS team have confirmed they are able to unlock bootloader, flash custom keys and relock it on the new Pixel 10, so?medium term seems to be safe.

They previously ported Android 16 within 2 weeks on all the supported devices despite obstacles.

It's not so bad.

playforclaude•5mo ago
That just means that the Pixel 10 meets their security requirements. Porting this time around will require a significant amount more work (if it's even possible), due to various changes in the way Google publishes updates to ASOP.
wkat4242•5mo ago
It's not so bad but depending on the 'hand that feeds' in the long term is unsustainable, especially if that hand can't be trusted.
wkat4242•5mo ago
Yes this is why the current duopoly is so toxic.
estimator7292•5mo ago
They said less open.

You can rank how smelly two turds are compared to each other, but if you must live with one, which are you going to choose?

playforclaude•5mo ago
Honestly, I rate "open" less and less as time goes on. It's a fine principle, but there are other valuable principles (like minimal advertising and tracking, and quality of finish and performance).

I think that the ethics and ill-effects of Meta, Google and the like are significantly worse than locked software ecosystems. Once you've decided that, then you don't want a smartphone at all.

If I had to get a smartphone, I would get an Apple.

Given how many people go to all this hassle for "openness" in their mobile software ecosystem and then install Whatsapp/Gmail/Instagram etc - what is the point?

jamesnorden•5mo ago
I've noticed in this type of thread that the typical HNer can't fathom that people like using Android as an OS and they're not using it solely because you can sideload apps or install custom ROMs. Maybe there's a name for that.
playforclaude•5mo ago
The article in question almost entirely focuses on those topics, so such comments are entirely relevant.

There's nothing special about liking Android as an OS. I'm sure it applies to practically everyone who has an Android phone :-).

jdboyd•5mo ago
The problem with GrapheneOS as a way to protest what Google is doing with Android is that you have to buy a Google Android device to be able to use it. Buying a Google device to be able to protest what Google is doing with their Google devices seems counter productive.

I don't know how good /e/OS is, but at least there is a place to get it factory loaded on cell phones and install it on phone brands other than Google.

And then there is Lineage OS, which I've had good luck using the extend the life of phones in the past. I haven't tried it since Play Integrity started being such an important feature, but I suppose that just pushes one to be even more open source on their Lineage device. I've been wanting to try Lineage again, but I misplaced the phone I want to try it on.

ementally•5mo ago
there's already a comparison mentioned in the article

https://eylenburg.github.io/android_comparison.htm

lawn•5mo ago
GrapheneOS is luckily working with another OEM but that's still 1-2 years away.

Buying a phone from Google is hardly ideal, but the effect is limited by the earnings being nothing but a blip in the grand scheme of things. Having an alternative OS is important enough to offset it IMO.

gitaarik•5mo ago
Yeah this was also my reasoning, that's why I got a second hand OnePlus 9 Pro and installed LineageOS on it. Well actually iodé, which is a privacy oriented fork of LineageOS with MicroG and a firewall installed. It works flawlessly, I'm very satisfied with it.
jdboyd•5mo ago
The OnePlus One was my favorite phone to hold ever, but it was sadly let down in software reliability due to the the melt down in the relationship with Cyanogen.
backscratches•5mo ago
Never buy new
Cpoll•5mo ago
Better, but supporting the resale market still improves the appeal for new buyers who plan to eventually sell.
estimator7292•5mo ago
It's really unfortunate that until now, the only decent phone you can buy was a google phone. Everyone else locks and encrypts the bootloader and probably self destructs if you even try.

We all knew this was inevitable, but nobody made any better options.

hoppp•5mo ago
The more I read about google removing sideloading the more I feel like the internet has become an animal farm from George Orvell, and we are on one side of the fence. Are we on the farm or outside looking in?
phendrenad2•5mo ago
This is going to be like a dam breaking. A small trickle of privacy-conscious developers will put cracks in the wall, and once there's a tiny opening, people who are privacy-conscious-if-convenient will follow through, expanding the hole, and then, the flood of people who want true freedom on their devices (for a multitude of different reasons) will find that hole purely by random and pour through, destroying market share and revolutionizing the mobile market. And little secret sneak peek: Corporations will notice this and align themselves with it, seeking profit. It's going to be glorious.

We're already at a point where smartphones have reached hardware stagnation, and white-labeled devices are coming. There will be no 6G. Smartphones and laptops are converging. The idea that a computer that happens to be smaller than most gives a random company the right or ability to build a wall around it and collect a tax is going to look, in retrospect, really silly.

mercenario•5mo ago
I think a better idea would be to bet in running/adapting linux on smartphones. I have actually looked into this in the past. It could be very awkward in the beginning with most of the things hard to use because they were made for desktops but as popularity rises every linux app would move more and more towards being easier to use on both desktop and smartphones.
mkidd•4mo ago
I looked at several alternatives before settling on GrapheneOS. Many made claims that sounded good but only GrapheneOS had deep technical documentation. I'm not an Android developer so some of it goes over my head but I've written detailed software documentation. I know you don't write what is in their FAQ or revision history if you don't know what you are doing.

I've been using GrapheneOS for about a year and it has worked well. Only have two minor issues:

1) I'd like the ability to have timestamp data added to the EXIF image info. There is an option to have the GPS data added, so timestamp really ought to be an option too, though I certainly understand why some users would choose neither. I'll probably end up writing a Perl driver for exiftool to add the timestamp based on the image filename which is YYYYMMDD_HH_MMSS_MSEC.

2) There aren't many fonts and Roboto supplies 1037 glyphs. The card suit symbols are missing which matters to a bridge player. E-books that display correctly almost everywhere don't on GrapheneOS unless the e-book explicitly includes a font with glyphs for the suits.