WhyJiffie
google play integrity works at a different level. it checks if you are running a google-approved, "sealed" operating system
which is not true, as fairphones also support relocking. Besides, graphene has dozens of other very useful features that don't rely on hardware security features or the ability to relock. and I guarantee you, if another android rom adopted their unique features, they would be loudly complaining that they are stealing code (from an open source project...)
and the tradeoff includes dozens more permissions related features that don't rely on hardware security features
not true, fairphones support that too. calyxos makes use of it, it's proven to be working
has much, much fewer settings for permissions and privacy leaking functions. how do you even disable network access for an app?
oh! I don't know how nix containers work, but I would be looking into creating a shared network between the containers, that is not the normal network.
you have completely lost your mind.
wtf is wrong with you. they claim its in the published epstein files package. the least they should do is link to it and show quotes
oh, I see what you mean!
they do that for the sake of providing an example that works instantly. but on the long term it's not a good idea. if you intend to keep using a service, you are better off connecting it to a postgres db that's shared across all services. once you get used to it, you'll do that even for those services that you are just quicly trying out.
how I do this is I have a separate docker compose that runs a postgres and a mariadb. and these are attached to such a docker network, which is created once with a command, rather than in a compose file. every compose file where the databases are needed, this network is specified as an "external" network. this way containers across separate compose files can communicate.
my advice is its best to also have this network as "internal" too, which is a weird name but gist is, this network in itself won't provide access to your LAN or the internet, while other networks may still do that if you want.
basically setup is a simple command like "docker network create something something", and then like 3 lines in each compose file. you would also need to transfer the data from the separate postgreses to a central one, but thats a one time process.
let me know if you are interested, and I'll help with commands and what you need. I don't mind it either if you only get around to this months later, it's fine! just reply or send a message
just to be clear, are you saying that most beginners just copy paste the example docker compose from the project documentation, and leave it that way?
I guess that's understandable. we should have more starter resources that explain things like this. how would they know, not everyone goes in with curiosity to look up how certain components are supposed to be ran
OP is actually a bot. so many posts within an hour regularly, and compared to that, very few comments. whoever controls the account is not here to have a discussion