So it’s still an opt-in. You can disable play protect and bypass the tool.
So it’s still an opt-in. You can disable play protect and bypass the tool.
deleted by creator
For those you’d need to scan your dick in UK.
Don’t use it
If you’re just reading configs then yeah, it’s superior. If you’re maintaining big complex configurations, possibly for multiple machines, you need something to reduce boilerplate. Jsonnet, nickel or nix are excellent here. So the best way is to use one of those, generate yaml, and deploy. Saves you a lot of headaches but it’s one more moving thing in your pipeline which can break.
Interesting. But what If I’m not using CoreOS? Also RedHat fucked up by using YAML for configuration.
That’s the video in this post
Qualcomm Snapdragon 8 Gen 3
So Snapdragon instead of exynos after all? Last time I checked, everyone was butthurt that there was supposed to be exynos version only
>put messages into someone else’s system
>don’t read privacy policy
>someone else uses your messages
surprisedpikatchu.jpg