Comment by pona-a

Open in a window
Comment

Comment by pona-a

GrapheneOS is not a cryptography project, like a secure messenger would be. It's goal is practical security, which does depend on practical considerations: without MTE, similar memory security would cost an unreasonable performance penalty, without TPM conventional authentication methods like PIN-code and fingerprint would be vulnerable to bruteforce, without secure boot users would not be able to verify if their phone was physically tampered with in a brief window they were away from it... And if you have closed-source radio chips running their own untrusted software loaded over the air, integrated in such a way they can independently wiretap you, like most phones have, you'd already failed at protecting the user before you start.

Furthermore, Android's ecosystem is structured in a way even the most basic software security concerns, like not running a comically out of date kernel, depend on the vendor's blessing, and sadly most manufacturers, including very desirable ones like Fairphone, hadn't been keeping up with such duties. Porting new kernels to old hardware is an extremely inefficient time-consuming endeavor that will take up most of volunteer time to non-satisfactory results; I can testify to that as a former member of the Ubuntu Touch project, and our standards of security were comically lax.

Again, you CAN lower your standards of security and go for the lesser evil: many people run Lineage or Ubuntu Touch despite known gaps in their security models. But to make that choice, you have to be honest about what you're compromising. If you shut your eyes and plug your ears pretending everything is fine, you'll end up with someone killed because they listened to your uncritical advise.

Also, I struggle to see how it's GrapheneOS's fault choosing the most secure hardware on the consumer market because it might be deemed suspicious to own it. GOS could have chosen the most popular budget Samsung (ignoring the aforementioned security issues) and it would have the same effect. Besides Pixels aren't an obscure unusual hackerphone made in small quantities, shipped from out of the country; it's among the most popular phone brands, advertised from huge billboards I pass on my bus route to university. If they chose something like the PinePhone like Genode, this point would be somewhat defensible.

Finally, what's up with the repeated conspiratorial insinuations about financing? I admit I hadn't looked deeply into this question, even as a one-time small donor, but what are you expecting to find? Is it serious concern about the financial health of a project, or an attempt to manufacture a hysteria around some controversial donor, similar to the Tor Project?

Replies pona-a · 7d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. The list is kept in this browser only.

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
]
Read the next story in the same article-reader applet. Back returns to the previous story.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked and minimized readers keep their articles when you select another story from the sidebar. A window's Next story link reads on down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.