I know they are both ‘not production ready,’ but I’m really enjoying the PG database with this AppVerifier fork. I see the first release of the database is immutable, as @ignoramous suggested. Great job getting the ball rolling, @jonah

@ignoramous What do you think about PG integrating a simple signed timestamp authority (RFC 3161)? While this would only prove _when_ data existed, not _whether it was correct_ , it seems more attainable in the near term while still working toward the same goal.

I’m sorry, but that is precisely what was being discussed by @jonah and @ignoramous. If no VPN actually meets that criterion, then we need to:

1. Remove Proton since it is not on the same level as the other providers (on MacOS/Linux).
2. Remove all VPNs because none of them meet one of the criteria (kill switch).
3. Keep all 3 providers (Mullvad, iVPN, and Proton) and add notes on which…

Update: I have found a workable solution!

Though each android profile supports an independent, singular VPN, they share common access to the local loopback interface, aka localhost/127.0.0.1. We can use this to share network data between profiles over localhost - the same mechanism used by the Inter Profile Sharing App we’ve discussed here before

Requirements

• A secondary user profile…