moonshot5
Joined 8 years ago
Karma
57
Submissions
9
Member since
Aug 9
Recent submissions
Comment · 1 day ago
There is more than one valid path :)
Comment · 1 day ago
> I kinda wish I had a chance with some of the other reductions
New puzzle every day!
I thought about making previous puzzles available, but I've decided we've got enough things on the internet trying to hold our attention as long as possible, and that isn't my goal here.
It's not very interesting technically. Standard nextjs / react webstack. Most of the fun to be had here was in writing the puzzle generation algorithm.
Comment · 1 month ago
AOSP eng here;
I don't interact with Graphene or any of their folks at all; I'm just a distant observer like most folks here.
Still, I can't help but think that Graphene seems to want to complain about everything and anything that doesn't fit their niche use case. (As much as it seems beloved here, people that flash custom Android OSs are the very definition of niche users.)
My personal attitude to Graphene seems to get a bit more negative with each one of these "rants" and I doubt I'd go far out of my way to help them, even if I had exposure to them.
Comment · 1 year ago
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!
Comment · 1 year ago
Only one way to find out. :)
Comment · 1 year ago
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.
Comment · 1 year ago
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.
Comment · 2 years ago
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.