HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tessalt
echo-chamber-js
JavaScript2015–2026
tessalt / echo-chamber-js

echo-chamber-js

Commenting without the comments

12Distinct people
15Mentions
0Explicit recommenders
4.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Commenting without the comments

GitHub

Where it is used

No documented product use was verified in the last source check.

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 year15 dated mentions

Observed mentions: 2015-07-14 22:36:15 UTC to 2026-02-20 12:54:08 UTC.

01232015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC110
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC211
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
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 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

15 sources
Personal Blog Should Have Comments A spammer would agree. Trolls most certainly agree. If I was to add the function to comment it would use local storage. [1] not my repo If I wanted interaction from visitors I would make one of my forums public. They would at least have to register and they would be subject to normal moderation. As a new member only I would see their comments until their rank moves up from Guest, thus weeding out most low effort trolls and grifters. If I really wanted to hear from random visitors of a blog I would give them a throw-away email address or a form to contact me. [1] - https://github.com/tessalt/echo-chamber-js
In Personal Blog Should Have Comments
Seems odd that the strap-line (on the repo and main site, not just here) doesn't mention what might be its distinguishing feature. I've seen several general comment plugins like this, my favourite being https://github.com/tessalt/echo-chamber-js, though not that sign the comments (as mentioned lower down https://licom.fly.dev/). Though it doesn't say what use these signatures are put to (and I've not looked into the code). If there is no identity associated with the keys they don't prove the message comes from someone specific, just that the message hasn't been tampered with and came from the same person as other messages thusly signed.
In Show HN: Licom – browser plugin for comments on every webpage
Could it be that your site topics draw in negative folks? Some topics can evoke emotional feedback. In that case you might consider EchoChamber [1] javascript that stores comments in the browser. This is not my project. When a user submits a comment, echochamber.js will save the comment to the user's LocalStorage, so when they return to the page, they can be confident that their voice is being heard, and feel engaged with your very engaging content. It does not make any HTTP requests. Since LocalStorage is only local, you and your database need not be burdened with other people's opinions. [1] - https://github.com/tessalt/echo-chamber-js
In Various ways to include comments on a static site (2018)
Actual trolls should be able to spot this fairly quick as they often have multiple accounts and interact with their alternate personas. I would expect this to mostly silence wrong-think. e.g. anything not aligned with the group/tribe narrative. Another variation of this is echo-chamber [1]. The difference is creating a self contained echo chamber and the person leaving a comment will never see comments from real people. [1] - https://github.com/tessalt/echo-chamber-js
In Heaven Banning
Echochamber.js is missing from the list. > All of the commenting, none of the comments. > When a user submits a comment, echochamber.js will save the comment to the user's LocalStorage, so when they return to the page, they can be confident that their voice is being heard, and feel engaged with your very engaging content. It does not make any HTTP requests. Since LocalStorage is only local, you and your database need not be burdened with other people's opinions. https://github.com/tessalt/echo-chamber-js
In Open-source self-hosted comments systems for static websites
Other fun software made at least partly in jest (though still quite useful): eatmydata (https://packages.debian.org/sid/eatmydata) is an LD_PRELOAD library to disable filesystem syncs, to speed up test runs and other cases where you don't care about data integrity (such as if losing power would just mean you run the tests again from scratch anyway). echochamber.js (https://github.com/tessalt/echo-chamber-js) makes it look like your page accepts comments, displays them to the person who submitted them, but doesn't show them to anyone else.
In Volkswagen – detects when your tests are run in a CI server, and makes them pass

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.