Event JSON
{
"id": "007d20527c83a6d21d9fce90bb0b5cd96429f6ae3eb973ad62620c2c0322cf27",
"pubkey": "b3ba3c5045fbaf99be9cb4daa9f1d7baeedaba0fc5b91596511e2fb7a70dd7f9",
"created_at": 1744905952,
"kind": 1,
"tags": [
[
"p",
"b3ba3c5045fbaf99be9cb4daa9f1d7baeedaba0fc5b91596511e2fb7a70dd7f9"
],
[
"p",
"cad0067c2e639a39baa229625aae3fe70186a0d68a0b92afdb7d16912a0fed2c"
],
[
"proxy",
"https://grapheneos.social/@GrapheneOS/114354156535000835",
"web"
],
[
"e",
"d5ff748a07833c2ec6dec0cfdb12a8897e0fa98a7044f129d7c6b3cd87469925",
"",
"root",
"cad0067c2e639a39baa229625aae3fe70186a0d68a0b92afdb7d16912a0fed2c"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/114354156535000835",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://grapheneos.social/users/GrapheneOS/statuses/114354156535000835",
"pink.momostr"
],
[
"-"
]
],
"content": "You can work around the Terminal app not being compatible with a VPN by running it in a separate profile (work profile, Private Space or secondary user) since each profile has their own VPN configuration. It's an upstream bug in the VPN lockdown mode causing it to block the internal virtual machine interface being used to communicate between the Terminal app and the VM it's managing even though it's not a VPN leak for it to be doing that. We need to implement a workaround for it.",
"sig": "5ed6281fe423476aa1682ce96b277720bbd2893da8966a1070455ecbbb59bc7f3425c66be11a005adb1b3e668395eaf30c2632baba1eb51b6a3b6557e73d2e98"
}