The Norwegian Meteorological Institute has an excellent free HTTP/JSON weather API that covers the globe. No signup required. https://developer.yr.no
I think weather underground did i.e. until Apple gulped it.
191–200 of 203 posts
The Norwegian Meteorological Institute has an excellent free HTTP/JSON weather API that covers the globe. No signup required. https://developer.yr.no
I think weather underground did i.e. until Apple gulped it.
Earlier quoted context omitted.
Are you in iOS 16 or iOS 15 - in iOS 15 the Weather Channel logo shows in all countries.
iOS 15 - interesting, assumed they’d only be attributing data they were actually using! Apple’s forecast does vary slightly from the ones the BBC (using MeteoGroup) and the Met Office give, so I’m not sure what their source is if it’s not the weather channel.
I always wondered how DarkSky got that "hyperlocal" weather data. After getting into amateur radio and learning about APRS, I'm thinking they used APRS weather beacons to obtain that data. If not, it sure would be good source for very localized weather in an app.
Earlier quoted context omitted.
> Apples’ “privacy” is that they retain monopoly control over my data. That's a strange way to describe the situation where Apple is not allowing third parties to share your private data without your permission. Apple is doing exactly what you wanted in your first paragraph, which is to let you decide who gets access to your private data. If you only give it to Apple, that's YOU deciding to voluntarily grant Apple th…
> You think it'd be better if Apple were giving your data to other companies so more companies could spy on you? No, I think it would be better if Apple stopped spying on me at all, full stop.
And regardless, if you don’t like it, the solution is entirely within your grasp. After all, there’s no law forcing you to reveal your private self to Apple.
Earlier quoted context omitted.
> Apples’ “privacy” is that they retain monopoly control over my data. That's a strange way to describe the situation where Apple is not allowing third parties to share your private data without your permission. Apple is doing exactly what you wanted in your first paragraph, which is to let you decide who gets access to your private data. If you only give it to Apple, that's YOU deciding to voluntarily grant Apple th…
The point is that there's no option where nobody gets to spy on me. I should have the option to host the server-side software myself, and/or delegate that to a third party of my choosing which provides a standardized API. Calling what Apple does "privacy" is a sleight of hand. True privacy means my data is mine, I am not forced to share it with whatever random employees of a multinational corporation happen to be abl…
Earlier quoted context omitted.
Seems like a win/win when the customers and businesses interests align. No one is pretending Apple is a charity. Of course they do all this for obscene amounts of profit. But if we get stronger privacy as a side effect, I think that’s a generally okay situation.
We're selling our freedoms for a sense of security. Apple is almost too big to defeat. With the flip of a switch, they could turn course. (I would argue in many senses that they have.) They're already obeying local governments as a central point of censorship and control. Even the FBI/NSA has them monitoring the files on your device. Apple is too many functions wrapped up as a single legal entity. They have too much…
Source?
Earlier quoted context omitted.
There are all kinds of potential performance benefits to a native SDK. Cross app caching for such common data could be a huge boon for watchOS complications & Home/Lock Screen widgets, for instance. No idea if they are implementing those kinds of enhancements but it’s no surprise that a native SDK would be provided. Also, how would they implement the privacy preserving black box location implementation with a REST AP…
> Cross app caching for such common data could be a huge boon for watchOS complications.. What is your differentiation criteria between anticipating a "huge" boon versus a "regular" or "modest" boon"?
Earlier quoted context omitted.
> Cross app caching for such common data could be a huge boon for watchOS complications.. What is your differentiation criteria between anticipating a "huge" boon versus a "regular" or "modest" boon"?
What's your differentiation criteria for whether a comment is worth posting or not?
Would you like to know more? If so just shoot me an email.