testetsjjsjsshs
Unless you have a time machine, you can't get features like an isolated loopback device and App Communication Scopes today. They are not developed yet. Planned GrapheneOS features take significant time to research and then implement. It can't go any faster without more developers and more funding.
I'm a big fan of the Pixel Camera and GBoard designs, would love to use them on GrapheneOS. Just by disabling the Internet right they will still be able to communicate via IPC, is there any way for me to avoid this?
There's nothing about this specific to the Network toggle. An app you grant the Contacts permission could share it with another app in the same profile. An app you give data could share it with another app in the same profile. It's not specifically relevant to the Network permission added by GrapheneOS. This is a common misconception. These apps are not malware and are not exfiltrating sensitive data via network access in the first place unless you opt-in to sending usage data, so it's not really clear what you're aiming to accomplish by coming up with extreme ways they could do it as if they're malware colluding with other malware to bypass the permission model. It should be noted that the purpose of the Network permission is not what you're trying to use it to accomplish. It is not a data exfiltration toggle, which would require apps having quite a few things taken away for basic enforcement including ability to play audio.
Perhaps by running the programme under a different user? Is anything going to change?
Apps in separate users can't communicate via standard IPC mechanisms and profile data is separate. That means they can only communicate via the network, which is essentially blocked via external networks by using a VPN not allowing local network traffic but they can still use the loopback network device. We have a planned feature of a per-profile loopback network device with a toggle, and a per-app variant too to go along with App Communication Scopes.
And actually internet right and IPC are the only things through which programm x can send information somewhere?
Interprocess communication can be done via any access you've granted to shared resources or any access they have to shared resources by default. You seem to be misunderstanding what it means and think it's a much more narrow concept than it is. If you grant two apps access to the same file, or Contacts, or anything else, then you provided another way to do IPC yourself.