moonshot5

5 ms·

1. 1.▲
   by moonshot5 15d 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
2. 2.▲
   by moonshot5 1y 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 calle
3. 3.▲
   by moonshot5 1y ago

   Only one way to find out. :)
4. 4.▲
   by moonshot5 1y 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.
5. 5.▲
   by moonshot5 1y 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 informe
6. 6.▲
   by moonshot5 3y 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