I think it says something that we live in a world where NOAA data could be seen as an underground or less than legal means of getting the weather.
Perhaps AccuWeather has been successful in their campaign to keep free weather data as obscure as possible.
I'm imagining designing a software product around this and presenting it to a C-Level, explaining that we use "PirateWeather" and I think I'm going to get grilled with lots of questions and concerns based on the name alone.
This is a good service and should be "branded" with a better name. Maybe a play on the whole DarkSky name like LightSky or "Sunset" which works exceptionally well since DarkSky was sunset by Apple. Maybe StarrySky, LateSky, NewSky.
I am usually someone who says that names don't matter as much as people think they do, but PirateWeather just seems like a huge hit in the wrong direction. But the product is solid so maybe it can survive despite the name.
And variants thereof perhaps
I’m a massive fan of - and indeed contribute data to - the weather underground project, but the naming has always made me a little uncomfortable.
More likely
1. they will not ask
2. If they ask they will care
3. If they care they will not with a short explanation
this seem like a non-issue, and if the biggest thing you have to worry about is some C Level with a stick up their ..... well I think you have nothing to worry about then
the name is fine...
That depends on who you ask... People who are fans of, e.g., ThePirateBay probably would disagree with you.
Also, there's a shipping service called PirateShip that's totally legal (it's basically a frontend to USPS shipping labels). The website is pretty amusing with the "Arr, matey!" stuff.
Maybe we're on different webs, but in my mind "pirate" has good connotations. As in, a rebel, a free spirit, a fighter of oppression.
Alternatively, imagine what the world would be like if we spent less time thinking about what C-suite executives think.
Firefox:
brightearth.app:6:4322
XML Parsing Error: mismatched tag. Expected: </input>.
Location: https://brightearth.app/
Line Number 6, Column 4322: 2
fetchWeather.ts:31:31
Uncaught (in promise) TypeError: l.querySelector(...) is null
g fetchWeather.ts:31
Safari: App.tsx:46
[Error] Unhandled Promise Rejection: TypeError: null is not an object
(evaluating 'l.querySelector("creation-date").textContent')
(anonymous function) (index.2994085b.js:139:2367)
asyncFunctionResume
(anonymous function)
promiseReactionJobWithoutPromise
promiseReactionJobOP is talking about the copyrightability of API's (which they are clearly exposed to as they built a drop-in replacement). The relevant case: https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_....
Why do you draw that conclusion? It seemed to be making a joke about the fact that APIs are NOT copyrightable and considered fair use. The site is pretty clearly fully legal.
This answers the first question I had upon seeing the name, which was, is it free, open, documented and legal? Based on the above the answer seems to be "probably".
Very commendable effort, and I hope the project can last. It seems to be very difficult to maintain a free and reliable weather API so hopefully the dev is not biting off more than he can chew.