hey, iNat eng here, just want to chime in that this is all great feedback!
here's [1] some extra info on iNat's current geoprivacy treatment and [2] guidance on how to configure this for our different platforms for individual `Observations` (our core domain entity to which geo is attached).
I'll at least share that this is on our radar to look at, but I wouldn't expect changes in the next few months. For now, we still want your observations, but if this is a concern you have, please take a look at the geoprivacy settings!
handling this concern is on our radar but I can't speak to delivery timeline. It my involve timed "obscured" windows (obscure things for this hiking weekend) and/or user-configurable geofences (obscure observations around my home but not anywhere else).
we _also_ want to respect the geoprivacy of wildlife: sometimes observations generate _problematic_ attention. For sensitive species, we want people to report them, but we don't want to be complicit in or responsible for interested people flocking to the observation and potentially spooking the observed species.
that's funny because we _just_ introduced cloudflare.
it's not my wheelhouse, but it would be comedic so let me know if you get the legit cloudflare host connection warning _and then_ land on the how it works that you mentioned looks like cloudflare.
The component renders any time the setWhatever function is called, similar to this.setState() in class components. The presumption is anything that you're storing in state is depended on by the component. If it's not, it doesn't make sense to have it in state anyway.
Rally Health | Chicago, SF, DC, Minneapolis | ONSITE
React Native Engineer
We're hiring a React Native dev to help us build out a high profile consumer-facing app for a Fortune 10 company. You'll join a mixed team of React specialists and native mobile specialists. We're a well-disciplined group, with a strong focus on developer responsibility for quality (with the help of Enzyme and Detox). Our team also has dedicated time blocked off for OSS work to contribute back to the libraries we use.
Rally Health makes consumer-focused healthcare products that help people shop for care with doctor and pricing information, get into healthy habits, and learn about their benefits. Obligatory tech list: Scala, JavaScript, AWS, Postgres, Terraform, Docker, ElasticSearch, etc.
The name works fine in the browser, but since jest/enzyme use node to run tests, I had issues with functional components (defined as arrow functions and immediately exported) were missing their names.
Ditto for React. Pretty much every "how do I do this" is covered in the official tutorial and every "how should I do this" is covered by supplemental guides (still official docs).
Some good ones: "thinking in React", "lifting state up", "controlled components", and similar docs in redux: "you might not need redux"
It's pretty rough on newcomers as well as devs trying to find docs and blog posts, but in contrast to naming it something else, it was pretty effective at establishing a user base.
It would have been a lot easier on the world if 1.x was the last version of anything called Angular and Google named the new thing FooBarJS.
But Google knows how software teams work. Names and versions are easier to evaluate than trying things out or running comparative analysis.
Teams hire "Angular" developers which usually means "1 or 2" even though it very much shouldn't.
Teams will set aside time to "upgrade to Angular 2" more freely than they would set aside time to "switch to a different framework, FooBar.js", even though with Angular 2, those are the same.
Even if teams would set aside time to "Upgrade to new framework", they're much more likely to do a alternatives analysis if it's not just a version number changing.
That said, I think this hurts developers and teams, and I think it's loosely nefarious, but it was probably necessary for Angular 2 to get the adoption it has today.