This isn’t about the user being treated as untrustworthy or as less than an adult, it’s about the security model GrapheneOS is based on. The team explains it well in this thread: https://discuss.grapheneos.org/d/18953-why-the-stigma-against-rooting

If you want to trade away the benefits of that security model to be able to tinker with things and feel more in control of your phone, you can use something else that lets you do that by default, or patch and build a rootful Graphene yourself. Ironically, the risk there is of giving full control of your phone and privacy to a potential malicious third party anyways, but different threat models may deem that acceptable or low-risk enough.

but desktop OSes function fine giving users root abilities.

Again, threat models. They may function fine for most people, and for most people the risk is low, but the linux desktop world is a security nightmare.

The primary focus and benefit of GrapheneOS is security, and user>root privilege escalation completely undermines that securiy model. The project doesn’t and likely never will support root access for that reason.

It’s the central meta-community for our instance, which has been having a lot of downtime the last few days. We tend to check in here when it comes back online.

PostmarketOS recently added support for the Pixel 3, and I’d recommend that instead of what you’ve proposed. That gives you a great way to tinker with it alongside an active development community, without being completely on your own.

That’s what I just did with my old 3a that was collecting dust after it went EOL, and it’s been a really fun project.

Excellent, now we can be eaten by a GNU grue

deleted by creator

“Jo March becomes god, Massachusetts is consumed by horrors beyond human comprehension, and everyone dies”

Bakker’s Second Apocalypse to Little Women was a pretty jarring transition already…

What do you do to winterize the garden? We don’t get snow or much frost where I live, so I’m curious how it’s done elsewhere.

I designed and built a very simple electric friction drive for my old bicycle, and I’m taking it out for its inaugural test ride this weekend. It’s small and simple, fits the elegant utilitatian aesthetic of the bike without altering it, and should make my commute a lot easier. I’m really proud of it.

I just set up Readeck a few weeks ago, and I’ve been liking it. Very minimalist, utilitarian. One feature I’d like that isn’t included is the ability to add specific labels or collections to the sidebar, but that’s my only quibble so far.

It has an official browser extension for adding urls to it, but if you can’t or don’t want to use that, it has a nice api. I use the api to add bookmarks from my phone using a termux-url-opener script, which is as easy as the extension - just hit the “share” button and select termux, and it does the rest.

Navigating around supporting bad actors in the foss community is probably far easier than in the closed, commercial software space, given that all the code, discussion, and money are out in the open.

Also I think the proportion of fascists and bad actors in the foss community is probably lower than elsewhere in the first place, given that the community is based on the free and open sharing of work and knowledge.

First time I’ve ever seen this, and I love it.

I think my favorite thing in tech is blinkenlights, and my homelab is designed with that in mind. It’s pretty, and it’s like you can see the bits and bytes flowing around ♥️✨

I compile the kernel on all of my raspberry pis with LEDS_TRIGGER_ACTIVITY enabled, just so I can turn the power light into a cpu blinkenlight, and set the led triggers to some kind of activity on all my laptop and openwrt leds to turn them into blinkenlights too. Blinkenmaxxing.

I wouldn’t say it’s a big mistake, you’ve likely still got a few years left on your current drives as-is. And you can replace them with same- or larger-capacity drives one at a time to spread the cost out.

Keep an eye out for retired enterprise ssds on ebay or the like - I got lucky and found mine there for $20 each, with 5 years of uptime but basically nothing written to them so no wearout at all - probably just sat in a server with static data for a full refresh cycle. They’ve been great.

The actual write cache there - writeback accumulates writes before flushing them in a larger chunk. It doesn’t make a huge difference, nor did tweaking zfs cache settings when I tried it a few years ago, but it can help if the guest is doing a constant stream of very small writes.

The datasheet for the Samsung PM893 3.84TB drives say they’re warrantied for 7PBW and 2 million hours MTBF (can write 7PB or run for 2 million hours before average drive failure). Quite pricey, but looks like it’ll run forever in a home environment.

Good luck!

I delved into exactly this when I was running proxmox on consumer ssds, since they were wearing out so fast.

Proxmox does a ton of logging, and a ton of small updates to places like /etc/pve and /var/lib/pve-cluster as part of cluster communications, and also to /var/lib/rrdcached for the web ui metrics dashboard, etc. All of these small writes go through huge amounts of write amplification via zfs, so a small write to the filesystem ends up being quite a large write to the backing disk itself.

I found that vms running on the same zfs pool didn’t have quite the degree of write amplification when their writes were cached - they would accumulate their small writes into one large one at intervals, and amplification on the larger dump would be smaller.

For a while I worked on identifying everywhere these small writes were happening, and backing those directories with hdds instead of ssds, moving /var/log from each vm onto its own disk and moving it onto the same hdd-backed zpool, and my disk wearout issues mostly stopped.

Eventually, though, I found some super cheap retired enterprise ssds on ebay, and moved everything back to the much simpler stock configuration. Back to high sustained ssd writes, but I’m 3 years in and still at only around 2% wearout. They should last until the heat death of the universe.

What a cool concept!

I think one of the issues inherent to the node ecosystem is that the coast is never clear. When the ethos is to never reinvent the wheel, and instead pull in a dependency chain of thousands of tiny things made by thousands of people (not necessarily a bad thing, it saves time and lets developers focus on what they really want to do), you’re going to have supply chain attacks that go undetected, because nobody has time to vet every single change to all those thousands of things.