chirospasm

Worked for a newspaper for many years. This is a great question.

Good headlines are both intended to give reasonable summaries and drive readers toward articles they'd like to read, because newspapers -- and news media congregation systems in general -- don't have a true table of contents, only a series of categories under which article types live. Headlines, at a glance, function as a table of contents in newsprint formats because of this: you can scan for what you find interesting, but don't have to intake the whole newspaper page to understand what's being reported.

App scrolling through headlines, then, is functionally the same thing. Just a different UX, is all.

+1 !!

Currently, I prefer the Kagi model as my daily driver -- pay a small fee each month and not worry about having your search data, in all its forms, sold instead. They have some neat features, as well, like AI summaries.

There is also SearXNG, which is an open source, privacy-respecting, hackable metasearch engine. It can be self-hosted and also has a number of instances you can access.

GrapheneOS user here -- for many years and several devices. Also had many devices, prior to that, running LineageOS.

GrapheneOS

First thing to weigh, between your two options, is that GrapheneOS is considered its own mobile operating system at this point, and the development of this mobile operating system is driven chiefly by privacy and security. While founded on AOSP, GrapheneOS gets such benefits as -- but not limited to -- more frequently updated kernel patches, code removal or alteration to abate zero-day vulnerabilities normally addressed more slowly (or not at all) in vanilla Android, the security of a re-locked bootloader (only available on Pixel devices), an isolated and sandboxed Google Play to access normal apps (microG and other replacements are considered, in GrapheneOS circles, less secure), isolated user profiles for different sets of apps that have the ability to push notifications to each other, hardened memory allocation, and so much more.

Pixel hardware is a great fit for GrapheneOS due to the kind of security chipsets they employ, too. By selecting a device that allows users to re-lock the bootloader (other devices do not afford this), as well as leverage Pixel-specific hardware-level security features, there's a measure of consistency for overall security provided to GrapheneOS users and developers, alike. The devs don't have to provide workarounds, for example, in the same way other ROM makers do, such as for LineageOS. There can be focus. And that benefits everyone who is primarily interested in privacy and security in a phone OS.

LineageOS

Second thing to weigh, between your two options, is the intent behind LineageOS: it's an open source variation of AOSP, and is considered both an excellent extension mechanism for aging Android devices and an open source alternative to vendor-created -- and often vendor-locked -- ROMs that come, by default, on a variety of devices. LineageOS has been focused on being one of the most consistent, open source ROMs around. This means the consistency in UX, features, and flexibility of LineageOS can translate between many targeted devices. Over 20 vendors of devices benefit from the hard work of LineageOS.

Like GrapheneOS is focused on privacy and security for their users, LineageOS is focused on being a solid, consistent ROM for their users.

Further Consideration

I can go into the weeds of both, but at some point I made a decision to buy into the Pixel ecosystem -- and subsequently learned about GrapheneOS as an option. I value what they offer, and I understand their stricter alignment with their approach to developing an OS.

While I choose to lock myself into the Pixel lineup of phones, I would also consider LineageOS -- modified to my own specs -- if I had to shift to another device. Each have their strengths. Each have their focuses.

Features like this exist for putting the phone back at rest when there hasn't been a successful unlocking for X hours -- GrapheneOS, an Android OS, has a similar feature. The objective is to limit the window of time an attacker has to try to exploit anything the phone may have in operation during a not-at-rest state (when the user is still 'logged in' to the phone, certain background services / features may be available to exploit).

Rebooting automatically, especially if the phone not has not been successfully unlocked recently, may place the phone in a less exploitable state, as those services / features might not be available without logging in first.

OP bringin' out good memes, this run

That's super neat! It sounds akin to Cloudflare's camera-tracked lava lamp shelves. I'll have to try it out!

Jack Gilbert is one of my favorite poets. If anyone asked when I was reading it, I would give a copy of The Great Fires to them, no questions asked. My local bookstore had an agreement, after Gilbert passed, to always carry on the shelf. I would refill whatever I gave away the next day.

I love the saveitforparts YouTube channel. Dude is so fun to watch.

Let me supersonic for you, Kermie

If you have access to any kind of UX and UI folks, you automagicallly get a leg up on this, y'all. It is goddamn amazing.

Single dev on a personal project? Go find someone in the community who has an eye for design or hit up a design forum. Work has you on a project with only two other devs and limited resources? Ask for a favor from the UX team down the hall.

We are all tryna make good experiences out here. Let us avoid getting 'teabagged.'