HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kkamperschroer
musicality
HISTORICAL RECORD2014–2014
kkamperschroer / musicality · Not publicly available

musicality

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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, 5:04:57 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 week2 dated mentions

Observed mentions: 2014-06-26 21:55:17 UTC to 2014-09-12 19:41:34 UTC. Weeks start Monday, UTC.

012014-06-23 00:00:00 UTC to 2014-06-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 232014-06-30 00:00:00 UTC to 2014-07-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-07 00:00:00 UTC to 2014-07-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-14 00:00:00 UTC to 2014-07-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-21 00:00:00 UTC to 2014-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-28 00:00:00 UTC to 2014-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 282014-08-04 00:00:00 UTC to 2014-08-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-11 00:00:00 UTC to 2014-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-18 00:00:00 UTC to 2014-08-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-25 00:00:00 UTC to 2014-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-01 00:00:00 UTC to 2014-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-08 00:00:00 UTC to 2014-09-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 8

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
Jun 232014-06-23 00:00:00 UTC2014-06-30 00:00:00 UTC101
Jun 302014-06-30 00:00:00 UTC2014-07-07 00:00:00 UTC000
Jul 72014-07-07 00:00:00 UTC2014-07-14 00:00:00 UTC000
Jul 142014-07-14 00:00:00 UTC2014-07-21 00:00:00 UTC000
Jul 212014-07-21 00:00:00 UTC2014-07-28 00:00:00 UTC000
Jul 282014-07-28 00:00:00 UTC2014-08-04 00:00:00 UTC000
Aug 42014-08-04 00:00:00 UTC2014-08-11 00:00:00 UTC000
Aug 112014-08-11 00:00:00 UTC2014-08-18 00:00:00 UTC000
Aug 182014-08-18 00:00:00 UTC2014-08-25 00:00:00 UTC000
Aug 252014-08-25 00:00:00 UTC2014-09-01 00:00:00 UTC000
Sep 12014-09-01 00:00:00 UTC2014-09-08 00:00:00 UTC000
Sep 82014-09-08 00:00:00 UTC2014-09-15 00:00:00 UTC101

What Hacker News says

2 sources
I know the permissions are overbearing. The reason it requests permissions for all sites instead of just the supported players is because of the way Chrome updates extensions. If I were to go that route and at some point add another player (which happens often), Chrome would disable the extension for everyone until they re-approve the changed permissions. I believe there is a way to do it dynamically and allow the user to choose which players they want to allow access to, and then accept the changed permissions. However a majority of my user base will not care, and would actually prefer the one click install ease of use. At least that's my reasoning. For those of you really concerned, you can download the source and modify manifest.json to change where the contentscript is injected for peace of mind. https://github.com/kkamperschroer/Musi
Read the rest
In My first Chrome Extension. Looking for constructive criticism and advice

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.