Mapbox CEO says the map calling New York City ‘Jewtropolis’ has been 100% fixed
techcrunch.com
techcrunch.com
EDIT: (Apparently my HN account is rate-limited so I can't reply directly.) How about this: anyone who wants access, email me and I'll send you a link. The site is up and running. People can send the link to their friends, and it'll be a private HN-only sub-community.
Or at least invite only?
source: was a moderator for reddit r/place
We've also effectively given everyone else access to information, communication and opportunities to expand their worldview that have been more profoundly transformational than even the printing press.
No, creating the internet was not a mistake, any more than any means of mass communication is a mistake because it can be misused as well as used wisely. Without the internet, global culture would be entirely controlled, centralized and limited by media conglomerates, digital rights management and distribution by physical media, and our means of mass communication limited to telephones. The same internet that grants freedom of expression to the "absolute worst elements of society" grants it to you and I as well.
The internet is just a network, but I believe the good it's done for humanity has far outweighed the ill.
Like the sexual abuse in Hollywood, for one example.
Do you really prefer the "absolute worst elements of society" to remain hidden rather than come out?
Porn might prevent the next generation from being born, worst case.
You know it's possible to watch porn and have sexual relationships with other people though, right?
For systems: queries of death, queries with highest serving latency, records with huge size compared to rest of the entries in DB, records with extremely high fan-in for your streaming pipeline, ...
For society, a tiny minority of: users who would vandalize online data sets, refugees who commit terrorism / crimes, citizens committing crimes, recipients cheating welfare programs, people avoiding taxes, ...
It is also the tail that imposes the maximum cost on your system / society.
This is not true for every case. Excessive focus on tail risks (and moral hazard,) in fact, can be absurdly costly.
OpenStreetMap wouldn't be possible without it either. :)
For OSM, humans are the strongest link, they are often the best way to fix these kinds of changes. A strong local community is the solution. OSM fixed this vandalism within 2 hours.
Mapbox don't keep their maps up to date, and probably used a snapshot of the data which happened to have gotten in the few hours before it was reverted.
[1] https://www.openstreetmap.org/relation/175905
[2] https://www.openstreetmap.org/api/0.6/relation/175905/histor...
The OSM history of an object shouldn't really be seen as the historical status of the thing.
FB (like Mapbox) don't keep their OSM based maps up to date, instead they make sure it's safe. They think that's a very important, and have developed a lot of tools to do that. I'm not sure if Mapbox promise to have their maps safe and curated, they just stopped updating them frequently.
Mapbox is a product aimed at less tech-savvy users, so it's more likely to be a victim of trolls.
Then I came in to read this story.
Yesterday we were trying to figure out what our update strategy would be, if we would pull daily deltas, do quarterly updates, etc... We discussed the idea of vandalism and didn't have a good answer for how to prevent it. We thought about lagging behind the latest changes and then doing a "catch up" if vandalism was detected. Really what we'd like to do is make changesets based on the age of the change, except including our most recent changes (because our reputation is great :-), but I don't even know how to start doing that.
I'm pretty sure you can get a stream of all the changes, so you would need to do something like have one copy of the database where you processed updates in near real time, and a second (production) copy where you had a delayed replication stream; in that stream, you'd want to look ahead at the real time database to calculate your stability heuristic.
Alternatively, you could have the realtime database also populate a changed object queue -- anytime an object is changed pull it out of the middle of the queue and place it at the end again. If it makes it to the front, pull the current object data and place it in your production database.
This should help with vandalism, but you do run the risk of accepting only parts of a coordinated edit of several objects. You could consider simply stopping replication into your production database in case anything ends up ultimately unstable, but I suspect it's hard to find a point in time where everything edited before was not edited again in the next 15 days (or whatever your threshold is).
This is definitely a complex problem to solve, especially since you would want to have some escape hatches so your changes happen quickly, or you could flag upstream changes to apply quickly, or worst case, you might want to revert to an earlier version of the database.
If you can figure out how to divide the data into different regions, you might have better luck, but sometimes object ids are moved around quite a bit. Geodata is already messy, and having a multitude of editors doesn't help with consistency etc.
Do city names change so frequently that they need to be dynamically updated? I can see some use for it when you get to the neighbourhood level to account for local nicknames, but not full cities.
Such a system of differentiation of map elements by likelihood of change could be good in the long term, but it would be a huge undertaking to classify them.
Maybe that's the bug. It didn't occur to me until I read your comment [0] that the system could simply accept user-submitted data only above a certain level of detail. It won't eliminate the damage, but it would keep it more contained.
[0] OTOH, GIS isn't my day-to-day like it would be if I worked at, say, MapBox.
(after all, someone has to be able to edit things like the label for New York)
For instance, there's tens of millions of objects in OSM. Step one to locking some of them is deciding which ones. That alone is a big project.
There are legitimate reasons to edit even the information for major world cities (most of them, for example, don't have translations into all major languages yet), but there's little reason to need those changes to be applied immediately.
You'll still need some way to deal with ongoing edit wars -- I'd imagine the mapping of Jerusalem to be prickly, for example. But at least you can tell that content is dangerous and direct your human review in that direction.
Even better, less than 2 hours.
The entire map is user submitted! It's a wiki map.
OSM isn't finished (and never will be), so we need to keep adding to it. Even the place node for New York (which was edited here) has dozens of different tags as well as just the "place=city name=New York"
Kind of interesting to see all the other active blocks in effect and the corresponding explanatory notes.