HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
toolbox-team
reddit-moderator-toolbox
JavaScript2023–2024
toolbox-team / reddit-moderator-toolbox · Archived

reddit-moderator-toolbox

Moderator toolbox for reddit extension development.

Web Development
Explore on GitHubRead Hacker News discussions
2Distinct people
4Mentions
0Explicit recommenders
124GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Moderator toolbox for reddit extension development.

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

Observed mentions: 2023-06-14 03:57:33 UTC to 2024-08-21 11:17:29 UTC.

01232023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 20232023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 20242024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsAug 2024

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 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC101
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC000
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC000
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC000
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC000
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC303

What Hacker News says

4 sources
creesch·Aug 21, 2024
The only really difference sometimes is in the manifest. If you target the webextension api and use the Mozilla poly fill library, your code base does not need to be duplicated at all. It adds the benefit of being able to use all API calls in a promise based manner instead of needing to use callbacks. Edit: To give it a bit more context (although you can find that in other comments I left under this post). The polyfill library itself: https://github.com/mozilla/webextension-polyfill Which if included allows you to swap out `chrome` callback based calls for promise based `browser` calls. So instead of using `chrome.extension.api.call(() => { // callback})` you do something like `await browser.extension.api.call()` with the same results working in both browsers. Then the only thing where you still need some separation is for the manifest a
Read the rest
s some keys are Firefox specific and vice versa. An example you can find here: https://github.com/toolbox-team/reddit-moderator-toolbox Where all code lives in one directory and there is just two manifest files, one for chrome and firefox: https://github.com/toolbox-team/reddit-moderator-toolbox/tre... Building is nothing more than rollup packaging the code and grabbing the right manifest to put in the build directory for each browser: https://github.com/toolbox-team/reddit-moderator-toolbox/blo...
In Plasmo – A framework for building modern Chrome extensions
creesch·Aug 21, 2024
I wrote a more extensive comment elsewhere, but for basic compiling a browser extension you can also simply use common tooling like rollup [0] where your manifest just points to the rollup generated files [1]. And if you forgo modern frameworks entirely, you can just have everything in one directory and run everything more or less directly from there [2]. As far as I am concerned, the structure and packaging of web extensions isn't what makes them complicated, although it does seem to be what a lot of people get hung up on. The web extension APIs and their interaction is often a bigger challenge. Publishing is also somewhat of a pain to deal with, although that is more the process around it and the lack of communication from both Mozilla and Google about it at times. [0] https://github.com/toolbox-team/reddit-moderator-toolbox/blo... [1]
Read the rest
https://github.com/toolbox-team/reddit-moderator-toolbox/blo... [2] https://github.com/creesch/readReddit
In Plasmo – A framework for building modern Chrome extensions
creesch·Aug 21, 2024
The project might do a better job of explaining what it actually intends to solve. At least as far as the readme.md goes. I have been active in the area of browser extension development for over a decade now. And to me, it wasn't very clear at first glance. It isn't crossbrowser extension development (which these days is actually fairly easy if you ignore Safari.... [0]). The README showcases adding a lot of other frameworks and scaffolding, which to me isn't what makes extension development all that challenging. In fact, using a modern modular approach can be achieved using something like rollup [1]. Of course, I do believe that Plasmo makes setting it all up a lot easier. But just looking at the terminal animation I also can't help but feel that it adds a lot of abstraction I might regret later. To be clear, I also do realize that some
Read the rest
people don't mind this and think it is easier to not have to think about the details. Only when digging a bit deeper into the actually documentation [2] it starts to make more sense to me. From what I gather: - Manifest creation is done entirely by plasma. You can just declare the thing you want to use or create in the right place like an options page [3]. Which is actually quite neat and something I can see makes things a bit easier for someone freshly starting with extensions. Although I'd argue that the manifest of an extension is not the most complex thing [4], even more when I see that for that with Plasmo you still need to declare similar things just at a different spot [5] - It provides some scaffolding and abstractions around things like storage and messing between content_scripts and background workers. - There are some neat utilities available for publishing extensions. Overall, it looks like it like it does take away the creation of an extension and a lot of the utility functions you would need to write anyway. However it comes at the cost, in my opinion, of extreme abstraction to the degree that a beginner basically will have learned Plasmo and still have next to no understanding of browser extensions themselves. It's one of those things where I wish this sort of tooling was available around a decade ago but I am also glad that it was not given the knowledge it gained me. [0] https://news.ycombinator.com/item?id=41043974 [1] https://github.com/toolbox-team/reddit-moderator-toolbox/blo... [2] https://docs.plasmo.com [3] https://docs.plasmo.com/framework/ext-pages#adding-the-optio... [4] https://github.com/toolbox-team/reddit-moderator-toolbox/blo... [5] https://docs.plasmo.com/framework/content-scripts#adding-a-s...
In Plasmo – A framework for building modern Chrome extensions
bshipp·Jun 14, 2023
For sure, and I haven't moderated in a few years so perhaps the internal reddit tools have improved since I last used them. They used to be pretty basic and cruddy. The moderation team I was a part of relied pretty heavily on the moderator toolbox: https://github.com/toolbox-team/reddit-moderator-toolbox I don't know if the proposed API changes will affect this specific tool, but I doubt moderators would be nearly as up in arms if their tools were going to keep working the way they had in the past.
In Reddit Doubles Down

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.