HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kiteco
kite-installer
JavaScript2017–2017
kiteco / kite-installer

kite-installer

Javascript library to install Kite app

7Distinct people
7Mentions
0Explicit recommenders
26GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Javascript library to install Kite app

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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 6-hour interval7 dated mentions

Observed mentions: 2017-07-26 18:13:30 UTC to 2017-08-01 19:54:06 UTC.

012342017-07-26 18:00:00 UTC to 2017-07-27 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 commentsJul 26, 18:002017-07-27 00:00:00 UTC to 2017-07-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 06:00:00 UTC to 2017-07-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 12:00:00 UTC to 2017-07-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 18:00:00 UTC to 2017-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 00:00:00 UTC to 2017-07-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 06:00:00 UTC to 2017-07-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 12:00:00 UTC to 2017-07-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 18:00:00 UTC to 2017-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 00:00:00 UTC to 2017-07-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 06:00:00 UTC to 2017-07-29 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 12:00:00 UTC to 2017-07-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 18:00:00 UTC to 2017-07-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 29, 18:002017-07-30 00:00:00 UTC to 2017-07-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 06:00:00 UTC to 2017-07-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 12:00:00 UTC to 2017-07-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 18:00:00 UTC to 2017-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 00:00:00 UTC to 2017-07-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 06:00:00 UTC to 2017-07-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 12:00:00 UTC to 2017-07-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 18:00:00 UTC to 2017-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 00:00:00 UTC to 2017-08-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 06:00:00 UTC to 2017-08-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 12:00:00 UTC to 2017-08-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 18:00:00 UTC to 2017-08-02 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsAug 1, 18:00

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
Jul 26, 18:002017-07-26 18:00:00 UTC2017-07-27 00:00:00 UTC404
Jul 27, 00:002017-07-27 00:00:00 UTC2017-07-27 06:00:00 UTC000
Jul 27, 06:002017-07-27 06:00:00 UTC2017-07-27 12:00:00 UTC000
Jul 27, 12:002017-07-27 12:00:00 UTC2017-07-27 18:00:00 UTC000
Jul 27, 18:002017-07-27 18:00:00 UTC2017-07-28 00:00:00 UTC000
Jul 28, 00:002017-07-28 00:00:00 UTC2017-07-28 06:00:00 UTC000
Jul 28, 06:002017-07-28 06:00:00 UTC2017-07-28 12:00:00 UTC000
Jul 28, 12:002017-07-28 12:00:00 UTC2017-07-28 18:00:00 UTC000
Jul 28, 18:002017-07-28 18:00:00 UTC2017-07-29 00:00:00 UTC000
Jul 29, 00:002017-07-29 00:00:00 UTC2017-07-29 06:00:00 UTC000
Jul 29, 06:002017-07-29 06:00:00 UTC2017-07-29 12:00:00 UTC000
Jul 29, 12:002017-07-29 12:00:00 UTC2017-07-29 18:00:00 UTC000
Jul 29, 18:002017-07-29 18:00:00 UTC2017-07-30 00:00:00 UTC000
Jul 30, 00:002017-07-30 00:00:00 UTC2017-07-30 06:00:00 UTC000
Jul 30, 06:002017-07-30 06:00:00 UTC2017-07-30 12:00:00 UTC000
Jul 30, 12:002017-07-30 12:00:00 UTC2017-07-30 18:00:00 UTC000
Jul 30, 18:002017-07-30 18:00:00 UTC2017-07-31 00:00:00 UTC000
Jul 31, 00:002017-07-31 00:00:00 UTC2017-07-31 06:00:00 UTC000
Jul 31, 06:002017-07-31 06:00:00 UTC2017-07-31 12:00:00 UTC000
Jul 31, 12:002017-07-31 12:00:00 UTC2017-07-31 18:00:00 UTC000
Jul 31, 18:002017-07-31 18:00:00 UTC2017-08-01 00:00:00 UTC000
Aug 1, 00:002017-08-01 00:00:00 UTC2017-08-01 06:00:00 UTC000
Aug 1, 06:002017-08-01 06:00:00 UTC2017-08-01 12:00:00 UTC000
Aug 1, 12:002017-08-01 12:00:00 UTC2017-08-01 18:00:00 UTC000
Aug 1, 18:002017-08-01 18:00:00 UTC2017-08-02 00:00:00 UTC303

What Hacker News says

7 sources
What precisely is Kite collecting in this case? Ideally backed by a link to a github repo proving that they're collecting whatever people are saying they're collecting. I've been reading for about 10 minutes and can't find any references. The closest I found was https://twitter.com/gerardroche/status/891802572373319680 which links to https://github.com/kiteco/kite-installer/blob/master/ext/tel... but that doesn't actually say what they're collecting. That class seems to be collecting time spent, identified by the variable `name`. But it's not immediately obvious what `name` is being set to. If it's set to a full file system path, then I agree it's a breach of trust. But if it's something generic like 'options screen' then clearly they're just trying to improve their product. People here seem to be losing their minds over this, so I'm tryi
Read the rest
ng to figure out whether it's justified or if it's another game of telephone. EDIT: Found the code: https://github.com/SideBarEnhancements-org/SideBarEnhancemen... Am I misreading this, or is everyone losing their minds over collecting how much time was spent editing certain file extensions? The only thing that seems to be remotely dubious is "activeNonBundledPackageNames", and that doesn't seem sensitive.
In Kite telemetry code in Sublime package SideBarEnhancements
they're also obscuring who this log data is being sent to by just posting JSON to an ec2 IP address (52.52.168.91). The server tries hard to not let you know it belongs to Kite. You know someone is ashamed of what they're doing when they take efforts to mask who's doing it. But you can see kite's own installer uses the same ip address for its telemetry: https://github.com/kiteco/kite-installer/blob/master/ext/tel...
In Kite telemetry code in Sublime package SideBarEnhancements

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.