HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Glench
fuzzyset.js
JavaScript2018–2021
Glench / fuzzyset.js

fuzzyset.js

fuzzyset.js - A fuzzy string set for javascript

2Distinct people
4Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

fuzzyset.js - A fuzzy string set for javascript

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, 1:49:46 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 year4 dated mentions

Observed mentions: 2018-07-03 22:13:36 UTC to 2021-03-01 21:36:58 UTC.

0122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

4 sources
> 2. How much can one reasonably expect to earn per user per month or year in your experience? (My extension is by no means mission critical but it solves a (simple) problem rather elegantly IMHO). There's no way to tell for sure! It really depends on the value the extension provides, your market, exposure and reviews on the Chrome store, etc. I can say that one of the extensions that uses ExtensionPay is a really simple utility that allows switching between recently used tabs in Chrome (https://chrome.google.com/webstore/detail/alt-%20-q-switch-r...) but users love it and it makes a surprising amount of money! But all that is ultimately speculative for your extension. One reason I made ExtensionPay was to lower the barrier to making paid extensions enough so instead of speculating you could just try it out and see what happens! > 1. Is t
Read the rest
here a socially acceptable path to go from free to non-free? From what I've seen there will be a very loud but very small minority of users that will get angry and leave bad reviews. I think if you try to make these users happy (maybe by giving them free access?) and let the others know why you're asking them to pay then it will go alright. Here's what I wrote about charging for a previously-free JavaScript library: https://github.com/Glench/fuzzyset.js#license
In Doing the impossible, monetising Chrome Extensions

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.