it's :)

At Zenimax: "Hey guys. This whole VR is becoming a real thing and we dismissed it along with this Carmack dude. Lets fill a suit against Zuckerberg for ludicrous amount of money, maybe we can get couple millions for free via settlement."

Context is the key.

They say HTTPS is complex to enable and imply they've been working on it for up to two years. And they finally get it done nine days before Trump.

Some people and organizations are panicking, either about his behavior or that net neutrality is out the window or about some boogeyman. That's why this story is relevant, now, because it's an indication that NYT may feel the internet will soon be a much more hostile environment.

This coupled with the Automatic Statistician (https://www.automaticstatistician.com/index/) will help fix a lot of biases and human errors that creep into scientific research.

Do you have any stats on youtube usage? Personally I don't use the offline feature very much.

A lot of people still have shitty, unreliable, expensive, and/or very limited internet connection. This is great for all of them.

I'm wondering if that's because of where you live? In the US at least, if your not in a top 10 city, chances are your data connection is terrible.

Of course it depends on where you live. Even in europe you'll find lots of underserved areas once you'll leave the cities. No provider is interested in building the network in these regions.

I've fixed this by converting the geodetic coordinates to ECEF. See v1.2 release notes here: https://github.com/thampiman/reverse-geocoder

Thanks!

Good point. I would need to use this distance function instead: http://www.movable-type.co.uk/scripts/latlong.html

On it!

Here's a python function we use to calculate haversine distances:

  import math
  from collections import namedtuple

  def haversine_distance(origin, destination):
      """ Haversine formula to calculate the distance between two lat/long points on a sphere """

      radius = 6371 # FAA approved globe radius in km

      dlat = math.radians(destination.lat-origin.lat)
      dlon = math.radians(destination.lng-origin.lng)
      a = math.sin(dlat/2) * math.sin(dlat/2) + math.cos(math.radians(origin.lat)) \
          * math.cos(math.radians(destination.lat)) * math.sin(dlon/2) * math.sin(dlon/2)
      c = 2 * math.atan2(math.sqrt(a), math.sqrt(1-a))
      d = radius * c

      # Return distance in km
      return int(math.floor(d))

  LatLng = namedtuple('LatLng', 'lat, lng')
  
  origin = LatLng(51.507222, -0.1275) # London
  destination = LatLng(37.966667, 23.716667) # Athens

  print "Distance (km): %d" % haversine_distance(origin, destination)

Thanks for that comment!

Good question regarding the license. I'm not too sure about that. I'd appreciate it if someone could shed some light on it.

Regarding the version, I've only tested it on python2. I should add that in the README. Thanks!

If its based on LGPL code, then any original code need to retain it's license.

Beyond that, everything regarding licenses look good if you ask me. MIT is both compatible if you modify the LGPL code or if you link with it, so one can use either of the two licenses.

hi, I am the author of the original library, which uses the LGPL license. My reason for using LGPL was so people would be obligated to share their modifications, so I would expect this is not compatible with MIT.

As of now, for Python 3 it does not work, but it seams that fixes are not hard: https://github.com/thampiman/reverse-geocoder/issues/2

UPDATE: I've just released v1.2 which supports Python 3. For details: https://github.com/thampiman/reverse-geocoder

Sweet!