Hacker News: moonshot5

New comment by moonshot5 in "Atuin – Magical Shell History"

moonshot5 — Tue, 24 Jun 2025 10:11:18 +0000

For zsh users who like this idea and don't want to have to worry about anything leaving the device (not to insinuate that Atuin is doing anything below board, I don't think they are) I built my own version of this for myself called raven:

https://github.com/tylersaunders/raven

Raven has no sync component, stores your history in a sqlite, and never tries to move data off the device. It has a similar / large overlap in features with Atuin.

Sharing here in case anyone else could benefit from it, it only supports zsh for the moment since that's what I use.

Atuin is great though!

New comment by moonshot5 in "Google Pixels are no longer the AOSP reference device"

moonshot5 — Thu, 12 Jun 2025 18:08:20 +0000

Only one way to find out. :)

New comment by moonshot5 in "Google Pixels are no longer the AOSP reference device"

moonshot5 — Thu, 12 Jun 2025 17:36:01 +0000

Android can run natively on x86_64. The ART folks spent quite a bit of time getting this to work.

A lot of our CI targets run android in this configuration.

New comment by moonshot5 in "The recently lost file upload feature in the Nextcloud app for Android"

moonshot5 — Wed, 14 May 2025 16:07:22 +0000

AOSP platform dev here. (Filesystem) Opinions my own, I don't speak for Google.

Disclaimer: I don't use nextcloud, and have not looked at their app specifically, this is just a surface level observation from my relatively informed perspective.

My take: SAF would work for this use case, as others have already mentioned.

Google Drive does not have the permissions that next cloud claims Google is giving preferential treatment to, and is delivered via the Play store in the same way nextcloud's app is.

As others have also observed, permissions such as MANAGE_EXTERNAL_STORAGE have been rampantly abused in the past, often in horrific ways.

New comment by moonshot5 in "GrapheneOS finds Bluetooth memory corruption via ARM MTE"

moonshot5 — Mon, 11 Mar 2024 16:41:49 +0000

AOSP engineer here; I don't have a deep knowledge of the issue at hand as I don't work on the bluetooth part of the OS, but I did just want to call out that GrapheneOS (while a really cool project!) supports ~11 total device types, and changes in AOSP have to keep a much larger context in mind.

I'm always looking for ways to implement cool stuff and make things in android better, but it's a little myopic to ignore the larger OEM ecosystem when complaining about specific feature roll outs.

I highly doubt the reason this isn't enabled is the 3% memory/cache usage, and there's some other consideration that's informing the decision.