News Feed Eradicator for Chrome and Firefox

Why News Feed Eradicator Targets Infinite Social Feeds

News Feed Eradicator addresses a specific browsing problem: social media feeds expose a continuous stream of posts that can encourage repeated checking. The project replaces that feed with a quote rather than adding another control panel, moderation list, or statistics display. Its package description states the goal as erasing distractions and taking back control of browsing, while the README defines the behavior more directly as replacing a social media feed with a quote.

The intended audience is narrow but understandable. People who recognize that an algorithmic feed distracts them may prefer removing the feed from the page entirely instead of relying on self-control alone. The approach is direct for Chrome and Firefox users because the project is distributed through both extension stores and is built as a WebExtension, the shared browser-extension standard used by those browsers.

This is not a general-purpose distraction blocker. The README does not promise that it blocks advertisements, tracks time, manages multiple social networks through configurable rules, or works on every site. It also does not document a catalog of supported sites. That distinction matters because a feed replacement extension can be a poor fit for someone who wants a configurable browser policy rather than one predetermined interruption page.

A WebExtension That Swaps Feed Pages for Quotes

Based on the repository layout, the implementation is a browser extension written primarily in TypeScript. The development script lives under `src/dev/`, while application dependencies include `solid-js`, `vite`, and `vite-plugin-solid`. The presence of `vite-plugin-solid` and `solid-js` indicates that the extension UI is compiled through the Solid toolchain, although the README and package metadata do not expose the individual site rules, quote selection logic, content scripts, or manifest behavior.

The documented data flow is simple from the user's perspective. A reader opens a supported feed, and the extension replaces what would normally be the feed with a quote. The README does not say whether the quote is selected locally or obtained from a remote service, whether original feed content is still downloaded before replacement, or whether the extension applies to the home page, individual post pages, or both. It also does not document configuration controls for quote sources or per-site behavior.

That thin documentation is itself an adoption consideration. The visible outcome is easy to understand, but the implementation surface cannot be fully audited from the README alone. An engineer considering a fork would need to inspect the manifest, source files, and site-specific logic before deciding how the replacement is triggered.

Installing the Extension in Chrome or Firefox

For an end user, the README provides official store links rather than a command-line installation path. A Chrome user can select the Chrome Web Store installation link, while a Firefox user can select the Firefox Add-ons link. The README does not document signing, enterprise deployment, or manual installation from the repository for ordinary users, so those installation methods should not be assumed.

The developer build is documented separately. Clone the repository, install `bun` and `make`, then run the following command from the repository root. It installs JavaScript dependencies and starts the extension build in watch mode.

make dev

If the command succeeds, the README says to inspect the `build` directory. That directory can be loaded into Chrome or Firefox as an unpacked or temporary extension. After every source change, the developer must reload the temporary extension in the browser because the build command recompiles changes but does not reload the browser automatically.

For a production archive, use the default Make target. The current Git tag becomes the package version, the extension is built, and the files are compressed into the `dist` directory.

make

The expected artifact is a ZIP under `dist` whose filename begins with `NewsFeedEradicator_` and includes the Git-derived tag. Firefox source packaging has a separate target because its add-on store requires submitted source rather than only the distributable extension package.

make package-source

Minimal Scope and Deliberate Limits on Contributions

News Feed Eradicator presents minimalism as a maintenance decision rather than a roadmap for broad configurability. The README says pull requests are generally accepted only for bug fixes or documentation improvements. Feature requests and ideas belong in the Ideas discussion board, and readers are invited to fork the project if they want a more complex version. The maintainer's stated reason is to reduce the maintenance burden after considering the project done.

That policy has two consequences. Prospective contributors cannot assume that a useful configuration panel, new customization model, or feature-heavy interface will be accepted upstream. A fork may be the more predictable route when the desired behavior requires substantial changes. At the same time, keeping feature work out of the main repository can help preserve a small and understandable project, although the repository does not quantify its size or support burden.

Bug reports have a dedicated GitHub issue tracker. Feature requests and site suggestions should go through the Ideas discussion board, where the README asks readers to check for an existing proposal and upvote it if so. This separation gives a clear contribution route, but it is not a promise that popular ideas will be implemented. The maintenance policy favors keeping the extension minimal.

The repository is not archived, and its last push was on 2026-08-23. Recent releases include `v3.0.4` on 2026-02-13, `v3.0.3` on 2026-02-12, and `v3.0.2` on 2026-02-06. The package metadata currently reports version `3.0.5`. These facts show recent repository activity, but they do not establish a release cadence or guarantee continued development.

AGPL-3.0-only Implications for Browser Distribution

The package metadata identifies the license as `AGPL-3.0-only`, matching the repository's stated AGPL-3.0 license. For users who install the published extension, the license identifier communicates the project's licensing basis. For developers who distribute a modified build or provide the modified software to other users, the obligations of the GNU Affero General Public License must be examined against the specific distribution model.

This review does not provide legal advice. The important project-specific point is that News Feed Eradicator is licensed under a copyleft license rather than a permissive license. An engineer planning to rebrand the extension, operate a hosted modification, or incorporate its code into another project should review `LICENSE` and the AGPL-3.0-only terms before publishing the result.

The build process does not obscure the basic distribution choices. `make` creates a distributable extension ZIP, while `make package-source` creates a source archive with `git archive` for Firefox submission. Anyone using those commands to distribute a modified extension remains responsible for following the applicable license terms. The README does not document a commercial licensing option or an alternative permissive license.

Comparing a Fixed Feed Replacement with a Configurable Blocker

The clearest alternative is a configurable content blocker or distraction-blocking extension. The two approaches differ in where behavior is decided. News Feed Eradicator applies a fixed product decision to supported feed pages: replace the social feed with a quote. A configurable blocker instead relies on user-defined rules that determine which URLs, request patterns, page elements, or categories are blocked or hidden.

That difference makes News Feed Eradicator simpler when the goal is to remove a feed completely and stop exposing its stream. It also removes controls that some users may need. The README does not describe settings for selecting individual sites, reviewing blocked pages, allowing temporary access, or inspecting why a page changed. A reader who only wants to stop one page element, or who needs an audit trail and exceptions, may find a rule-based blocker more suitable.

Neither approach should be assumed to cover every social network. News Feed Eradicator does not publish a supported-site list in the README, while the alternative is discussed here only by mechanism rather than by naming a product. The first verification should therefore be simple: find the extension's supported-site documentation or inspect its source before relying on it for the site that causes the most distraction.

Editorial conclusion

Adopt this extension if your browsing habits depend on the social feeds it supports and you prefer a fixed quote page to configuring filters yourself. Do not adopt it if you need site-specific controls, feed blocking rules, analytics, or a broader content filter. Before installing, verify that it covers the site you use most and review the AGPL-3.0-only terms for your intended distribution or modification.

Frequently asked questions

Official sources

1. Issues
2. jordwest/news-feed-eradicator on GitHub
3. License: AGPL-3.0
4. README
5. Releases