very cautious sneef 😊🥰
grow a plant, hug your dog, lift heavy, eat healthy, be a nerd, play a game and help each other out
very cautious sneef 😊🥰
The picture with your pup is especially sweet. Glad mum came back for the bebi.
And the Linux / Unix-specific ecosystem & technology arguments therein.
oh look at that lil snoot 😊🥰
I feel this. I strongly associate that design language they had with my studies.
Very sunny and relatively care free 😅
Do you have examples of the first one? Is this like, the designs we saw on the original Google now cards?
my best guess would be “cat related things”
Someone suggested to me the other day that safetynet was now (or will soon be) deprecated. I’m not sure what the situation is with regards to attestation, though I sort of dread to think about what will replace it.
Appreciate the additional context! Have thankfully not needed to use the safetynet module with microg either.
I appreciate that you’re trying to inform me but if you make such a claim, you should be able to prove it.
A friend was able to provide some context, regardless:
The one binary I’m aware of microG downloading (assuming it still does) is the SafetyNet “DroidGuard” thing, which it only does if you explicitly enable SafetyNet, which is not on by default. There is no other way to provide it.
microG only has privileged access if you install it as a privileged app, which is up to you / your distribution, as microG works fine as a user app (provided signature spoofing is available to it). Also, being privileged itself really doesn’t mean giving privileges to “Google”.
Apps needing Google services may indeed contain all sorts of binaries, generally including Google ones, which doesn’t mean they contain Google services themselves. Anyway, they are proprietary apps and as such will certainly contain proprietary things, and it’s all to you to install them or not. It’s not like microG includes them.
Its also just a reimplementation of a small handful of useful Google services, such as push notifications, or the maps (not the spyware stuff like advertising) and each can be toggled on/off.
Also all apps on android are sandboxed
I appreciate the info. For my own learning, could you provide a link to some context around the types of official binaries leveraged by microG? The only firm info I have of its behaviour is that it will pseudonomise as much user information as possible.
I’m familiar with sandboxed google play on grapheneOS and have used it in the past.
Can you elaborate on being misled there?
As for google devices - yes, there’s irony in the notion that the most de-googleable phones are theirs, sure. They’re often sold at a loss around the holiday season, though.
I also use calyx but I’ll agree that graphene is technologically superior of the two. I’m more comfortable with the idea of using MicroG as opposed to sandboxes google play but that’s not to slant the implementation in any way.
Good to know, though same could be said for ROCm + HIP for AMD. Gets a bit weird as you generally want that for OCL support too.
Best of luck with this, let us know how it goes
This may take time but Intel have extremely deep pockets, they understand the value of presence in this market, I’m sure they can and will stick to it.
It’s kind of crazy to me how well it works! It’s hard for me to wrap my head around it sometimes.
My end goal is to not have to eventually not need to use windows at all but I’m still very impressed with how this behaves.
Very welcome! Yes, exactly as you described. The nice thing is that you have greater control over Windows in this virtualized environment, particularly with regards to limiting device and network access.
I gather that display dummy plugs are pretty common in the looking glass community.
From.the FAQ