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!

[1]: iNat's geoprivacy explainer https://help.inaturalist.org/en/support/solutions/articles/1... [2]: platform-specific guidance on configuring geoprivacy for an Observation https://help.inaturalist.org/en/support/solutions/articles/1...

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.

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.

$25 for 12 minutes from one place in the loop to O'Hare

CTA is $2.50 for 37 minutes (the $5 is if you start from O'Hare)

This is only benefitting people for whom 25 minutes is worth $20/$22.50.

$1bn or whatever absurd cost it comes out to be is much better spent on improving transit for the actual public.

Or you know, to stop shutting down schools.

EDIT: typo

Comments URL: https://news.ycombinator.com/item?id=17066850

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=16943482

Points: 3

# Comments: 0

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.

https://www.rallyhealth.com/about/careers/1048473

Comments URL: https://news.ycombinator.com/item?id=16376460

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=16318956

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=16219115

Points: 3

# Comments: 0

We have the most expensive medicine in the world, but it's all treatment, not prevention and both only for those who can afford it.

AFAIK, arrow functions do (and should) have names if they're assigned to a variable.

  const foo = () => {};
  // undefined
  foo.name
  // "foo"

  export const foo = () => {};

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.

FWIW, this isn't an issue in Babel 7.

Some good ones: "thinking in React", "lifting state up", "controlled components", and similar docs in redux: "you might not need redux"