if anyone wants to know how, i wrote about it here https://tuananh.net/2024/01/21/reproducibility/

how do you deal with "access to the proxy"? because one can access maliciously without accessing to the token/secret.

Agent Vault should remain in close proximity to the sandboxed agent and not be exposed to the public internet; your standard network security controls apply.

The proxy itself currently implements a token-based auth scheme. Depending on your setup, you can have an orchestrator mint an ephemeral token to be passed to a sandboxed agent to authenticate with the proxy.

this feels like vpn all over again. the location shouldn't grant any inherent trust.

it show whataspp key transparency is currently disabled since `Verified: Mar 13, 2026, 15:37:48 UTC`. any idea about this?

https://radar.cloudflare.com/key-transparency

what about the other way around?

i'm aware about waydroid but it has too many problems with nvidia. also require wayland.

I can't help you with nvidia, but the Wayland thing can be worked around quite easily by running it under a nested compositor like cage. (This is how I run waydroid under Xorg)

thanks. good to hear that. i just have to wait for nvidia support now.

Have you tried https://wiki.archlinux.org/title/Waydroid#Software_rendering ? Obviously not ideal, but possibly functional.

There's for example redroid (https://github.com/remote-android/redroid-doc) which seems to be exactly that. Android inside a container.

X86 builds of Android are stuck at many generations back of the OS. Running Android in a VM on X86 is basically dead AFAIK. :(

I'm actually optimistic that this will improve. Google has apparently been working on replacing Chrome OS with android, which I have pretty strong opinions on but the upside is that if they want to go that route they're going to have to make Android officially work well on x86, at which point there's no reason that eg. LineageOS wouldn't be expected to follow suit.

You could run a windows VM and run windows subsystem for android.

Windows subsystem for Android is deprecated. There's a community maintained alternative but it seems to have a few problems wrt. Windows updates.

The community maintained version seems to work okay most of the time, but you're correct a better solution is needed.

that's right. graphic stack is one thing you dont want to use older release.

> Notice: Only variables should be passed by reference in /Users/maciej/Code/iw/site/month.php on line 8

if author is reading this, you should fix this maybe.

I'm sorry it bugs you!

oh it's nothing. it just that there maybe some security issues.

It's all flat files on the server

iximuiz also give you 1 hour per day free i think.

very easy to use. almost instant.

what if a distro uses systemd and systemd implements age verification?

That is already in the works, atleast the base for it.

https://news.ycombinator.com/item?id=47436240

Systemd seems to have only implemented a place to store a birthdate. I doubt they will do anything else.

it's an enablement layer. as long as the information is there, its only matter of time before some other apps decide to use it.

Ya, I don't see any point in systemd adding this, but they did it already. Near as I can tell most of the laws just want to know a rough age category that can be provided by the OS. Seems to me an `echo "adult" > ~$USER/.config/law_compliance/age_category` would do the trick.

Anyone that cares can go check that file if they want an age category for some reason. Why does this need to be any more complicated?

If a parent really wanted, they could change the perms so only they could change that file.

I have no doubt that systemd will implement a place to store political party membership, religion, LGBT status, veteran or draft status, or ethnic group membership if a handful of governments start to require that information.

I mean, why wouldn't they?

there's also capsudo by kaniini

https://github.com/kaniini/capsudo