DeletedUser496 @brightjob4495 your setup is very well crafted and interesting. How much metadata do you reckon you are able to avoid sending out to Meta by doing so and how much metadata are you still sending ?
I'm sharing my phone number, the IP of my server, which groups I'm in and who I'm talking to and when, which is unavoidable.
I'm avoiding sharing anything the app itself could have access to: app interactions, when I'm connected and my phone's IP of course. Probably what apps I have installed on my phone, local network devices, what WiFi networks I have saved on my phone and advertising ID if I had Play Services. And if I had given the relevant permissions, nearby devices, phone media files, contacts, location, microphone and sensor data. And probably more things I can't recall right now.
Then there's all the weird shenanigans Meta might pull off. From my point of view, any software developed by Meta might as well be malware, because they behave like malware: their apps are full of dark patterns tricking the user to give permissions they don't need. Sometimes they get caught having their apps and libraries in other apps or websites behave as if they were malware. The last one I remember the one where they were deanonimising mobile web browser traffic through localhost port communication between their libraries embeded in webs and their apps. Vanadium's defaut settings weren't vulnerable to this, but most mainstream browsers were unless extra protections were enabled. What other things might they be doing that they haven't been caught yet? For example it's theoretically possible to use gyroscope data as a low fidelity microphone, so I assume that if any of their apps has the sensors permission granted (which can only be denied in GrapheneOS), they'll do that.
In summary, Meta is by far the big tech company I trust the least.