If you're using it diligently enough to where some functions can be statically proven "pure", then yes. You can't call an impure function from a pure one.
It could just be the particular type of my colour-blindness or my monitor settings, but the red and amber colours look so similar that I couldn't tell that I had even clicked the button.
Opacity is fixed at 1. and obviously you can just break your own site until you get permission, but then people will probably leave before they give your website which has no business accessing the camera permission.
Take it up with your city council, if they're the ones require a smartphone to pay for parking.
But also, you're going to have to be more specific about what tracking you're worried about. Cell towers need to track you to give you service. But the parking app only gets the data you enable with permissions, and the data the city requires you to give the app (e.g. a payment method). So I'm not super clear what tracking you're concerned about?
If you don't use your smartphone for anything but paying for parking, I genuinely don't know what tracking you're concerned about.
2 caps: 1 for things that are charged for existing (e.g. S3 storage, RDS, EBS, EC2 instances) and 1 for things that are charged when you use them (e.g. bandwidth, lambda, S3 requests). Fail to create new things (e.g. S3 uploads) when the first cap is met.
Does that mean fail to create rds backups? And that AWS needs to keep your EC2 instance and RDS instance running while you decide if you really want to pay the bill?
reply