Since then all that talk went away and there’s been 2 years of this social media ban.
Surely a coincidence.
[edit: not a senator, a member of the House of Reps]
3,522 karma · joined May 9, 2013
Adelaide, Australia
Since then all that talk went away and there’s been 2 years of this social media ban.
Surely a coincidence.
[edit: not a senator, a member of the House of Reps]
The figure was four times more polluting than a train if driving a plug-in hybrid electric car, or almost two-and-a-half times more if using a battery electric car."
Right down the bottom of Settings > Accessibility.
Edit: you can also enable screen curtain in iOS (and watchOS!), which means your phone can operate with the screen completely off when in VoiceOver.
Good for privacy / battery!
It’s the iOS automation tool, and the context was controlling the car via the app in lieu of directly in their app, which isn’t something you do while driving.
5) I don't trust the cruise control at all. It will frequently disengage for no good reason (e.g. a car parked on the side of the road). If you don't have your foot on the accelerator (which you typically won't when in CC), the cark decelerates HARD suddenly with little time to respond.
Obvious fix: Option to disable "adaptive" part of cruise control, so it doesn't automatically disengage.
6) The app is kinda quirky. For example, if you open the "Charging" screen, the start/stop charging buttons jump up the screen slightly after it's done loading the list of superchargers. This frequently causes me to tap "Stop Charging" instead of "Start Charging".
Obvious fix: Offer Siri Shortcuts to all the car control functions in the app. That would be a killer use of shortcuts.
* Better long tail of older device support
(meaningless if the app doesn't work, and completely debunked now that ENF supports iOS 12)
* They want to control contact tracing, rather than have the app directly notify the user
(this isn't a requirement of ENF, but the Govt falsely claims it is. In fact, ENF can still notify authorities so a contact tracing phone interview can take place. The only difference is that with ENF, you can't force a user to enter their phone number to start using the app)
* They want a better picture of the entire social graph, since ENF gives more vague / anonymous data.
This is the only partially valid claim they make, however, this is predicated on the current app actually working and providing that information, which is does not.
Separately, when I read this paragraph, it prompted me to check my “DND while driving” settings, which for some reason were no longer enabled.
Authors can write about controversial / bad things.
Also, the Apple implementation requires user to manually approve access to user private tokens each and every time for apps trying to access them.
Fastmail's iOS app does support this functionality.
In the March 2019 Apple TV+ announcement event, Apple renamed the non-4K Apple TV hardware from "Apple TV" to "Apple TV HD".
So the hardware options are now "Apple TV HD" and "Apple TV 4K".
How do you like them ads?
Update: https://www.flatpanelshd.com/news.php?id=1416894724&subactio...
Important to note that it’s not NPR per-se, but a group including NPR.
As an indie dev* making a living from Apple Watch, I concur with the difficulty of having to debug these things.
For example, some arbitrary resource limit may have transparently been applied, leading to some unexpected behaviour in your app.
Now, make a minor change to code to diagnose this issue and deploy to device - could take 2-3 minutes to copy to device, and another 30 seconds to run the binary.
Series 3 still has its issues but it is 1000x better than the original.
* https://outcastapp.com, plus various others
When paying somebody, when you enter a recipient’s PayID, the bank confirms by showing the recipient account holder name.
So in effect, they’ve just implemented a nationwide number-to-name lookup system.
Separate to this, these two banks are pushing it hard. It feels like a land grab, since a single phone number can only be assigned to a single bank.
1. Stopped using clamshell mode (laptop lid closed) and that has helped.
2. Downloaded the LG firmware update for the monitors. Updated both monitors, also seems much more reliable.
(10 day uptime, up from about the usual 12 hours)
1. Charge more than 99c. Double the price and your sales will likely drop by less than half, making it profitable to do so.
2. If you’re going to half-ass the port to Android, why even bother? It will do more damage than it’s worth.
Edit: It seems the $800k includes Apple's cut. As an app developer myself, even considering that amount is torturing yourself. Apple _only_ report the remaining 70%, especially when you consider promo codes, refunds, etc... - doing a crude sales*price is somewhat inaccurate.
(Fun fact: I'm an Australian developer. Of the amount I get paid, I also need to deduct sales tax for any sales I make to Australian consumers. For a 99c app, I would make 63c for Australian sales and 70c for other countries).
iOS at least gives you the option to deny apps access to the photo library, to prevent this from being available.
Perhaps an additional privacy control specifically related to allowing apps to read EXIF data?
Opt-in, but you get a special badge on your App Store listing.
My "project that doesn't make me money" is https://transitfeeds.com
Currently it archives a ton of static schedule data, and some basic GTFS-realtime archiving stuff.
My longer-term goal is to archive all the GTFS-rt feeds every 30 seconds to provide similar analysis to what you've done here.
Obviously this requires even more storage than I'm already using and a ton of data processing, which is probably above my pay grade.
Any app that reads/writes HealthKit data is required to provide a privacy policy before it passes App Store approval.
Additionally, apps can only access that data after a full-screen permissions screen is displayed, and the user manually toggles on the categories of Health data that the app can access.
In my experience, the bar for getting apps that use HealthKit is at least slightly higher than for non-HealthKit apps.
I'd be more than happy for it to be 0%, but you do get a few things for that cut:
* Credit card processing
* Handling refunds (you need to do this manually on refund, just another thing to deal with)
* Some level of app discovery
* Distribution of app and files
My biggest problem with the 30% is that it is now the de-facto amount that other similar services charge developers for everything now (Google Play - there are others too that escape me now).