• 5 Posts
  • 301 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle
  • And if you’re one of the people who can crack a beer open with the owners of Google, then you found your right community.

    However, in the general case, I don’t think these count as any individuals communities. You can’t rub elbows with the people maintaining Google and Facebook. You can’t talk to them about issues you’re having, they’re not going to dynamically modify the system for special cases that are important to your community. A community is a group of people who know each other.














  • I don’t believe it requires a Google account.

    I just used it on grapheneos, it does recommend you use a separate Google account for the private space, but I don’t have Google account on the phone, I was able to create a private space without any issue.

    This feels very much like a second profile, like a workspace. So now you can have three profiles on your main phone login. Normal, private, work.

    That’s nice. I would have liked it if the lock button wasn’t there, better to not reveal it at all… Upon checking the settings, there is a hide option. So yeah this is great

    I hid my private space, and now I can’t unhide it. I have to go through settings to show it again. Supposedly you should be able to open it by searching for “private space”. Might be a GOS bug.

    This is perfect for banking apps, password managers, anything that you don’t need to get notifications from






  • Oh God. The spaghetti belt puzzles. That’s a dark art, so tantalizing, but sets traps for the future.

    Like having one speed belt, and then a different speed belt going below it. Works for the moment, great throughput, as soon as an upgrade planner is applied boom everything stops working. A little time bomb for your future self


  • I wish it were that easy, there’s a lot of shared architecture in CPU design. So maybe there’s cache lines that are shared, those have to be disabled.

    Architecturally, maybe memory tagging for cash lines that in addition to looking at the TLB and physical addresses also looks at memory spaces. So if you’re addressing something that’s in the cache Even for another complete processor, you have to take the full hit going out to main memory.

    But even then it’s not perfect, because if you’re invalidating the cache of another core there is going to be some memory penalty, probably infotesimal compared to going to main memory, but it might be measurable. I’m almost certain it would be measurable. So still a side channel attack

    One mitigation that does come to mind, is running each program in a virtual machine, that way it’s guaranteed to have completely different physical address space. This is really heavy-handed, and I have seen some papers about the side channel attacks getting leaked information from co guest VMs in AWS. But it certainly reduces the risk surface