HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
osmlab
name-suggestion-index
JSON2016–2019
osmlab / name-suggestion-index

name-suggestion-index

Canonical common brand names, operators, transit, and flags for OpenStreetMap.

2Distinct people
2Mentions
0Explicit recommenders
893GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Canonical common brand names, operators, transit, and flags for OpenStreetMap.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year2 dated mentions

Observed mentions: 2016-05-25 16:57:52 UTC to 2019-11-11 16:27:37 UTC.

012016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

1 sources
> I'm assuming it isn't just a matter of grabbing a logo (jpg) from Facebook. I assume iD is sending (meta) data about the person who is simply browsing the map to Facebook (i.e. without disclosing that info is being sent or what data is sent)? Given the scale of the drama, you'd assume that it was something nefarious, but it isn't. iD loads images for brands from Facebook, and nothing more: here's the relevant code https://github.com/osmlab/name-suggestion-index/blob/66412f0... Fun story from back in the day: we added 'social share' buttons to iD. Knowing the fundamentals of web security, they were implemented as simple links, with no JavaScript component on the iD side, no 'trackers', nothing of the sort. But some buzz came out about how other Facebook trackers were up to no good, and the OSM community got in a tizzy about how we had in
Read the rest
stalled nefarious tracking devices in the codebase, and after a few days someone recommended that we should implement the buttons as simple links, which is precisely what they were in the first place. That combination of bad faith and nobody reading the code was constant.
In ID editor: It is time for us to end this abusive relationship

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.