610 karma · joined November 24, 2013
© 2021 Microsoft CorporationEarthstar Geographics SIO© 2021 TomTomTerms of Use
Jurij Stare, www.lightpollutionmap.info (v2.7.7) VIIRS Earth Observation Group, NOAA National Geophysical Data Center
I use the NWS API's in my personal weather app and they work fairly well.
It's not all doom and gloom, but they could be better. The NDBC went down for about 7 days last month due to a "catastrophic outage," and that was very unfortunate. But, the deliberately and with warning took the BOX radar offline for maintenance for the first time in decades. A mixed bag.
Too bad it isn't allowed for logged-in anonymous users to chat (though that would be confusing!)
Complexity shouldn't be the default but it can be the right answer
Sounds lightweight! I wonder if that will help with adoption
It also looks like they might first do all the work to retrieve all the results for a query. The first request is to an endpoint `search_v3/{term}?cache_key={key}` then subsequent requests are to `asyncresultset_{n}?cache_key={key}` so seems like they might have the result set cached from the first query.
The response to the autocomplete endpoint, which is fast, contains an `elastic_id` so perhaps they do partially use a document store.
[0] - https://stackshare.io/posts/the-tech-behind-instacarts-groce... [1] - https://tech.instacart.com/the-story-behind-an-instacart-ord...
Government reports, or those prepared by consultants, are often the worst offenders.
>Chrome plans to more aggressively restrict fingerprinting across the web. One way in which we’ll be doing this is reducing the ways in which browsers can be passively fingerprinted, so that we can detect and intervene against active fingerprinting efforts as they happen. [0]
This will include things like restricting the volume of Browser API checks allowed, etc, to reduce the number of bits that can be used in a fingerprint.
[0] https://blog.chromium.org/2019/05/improving-privacy-and-secu...