Firefox Community Forum

hi

the element i really like / liked about Pocket were the curated stories that firefox publishes on its new tab page.

yes i used the "save to pocket" option but one can easily enough just visit the article and bookmark in the normal way.

NOTE: i think i wasn't appreciating the offline easy-to-read aspect to pocket (because i'd just read the article online and/or save to pocket) but it's too late now!

I've seen articles on multiple websites and reddit about pocket alternatives but people seem to only talk about pocket in terms of the capacity to save-to-read-later, tagging, book marking management, etc.

Btw, i've read the mozilla pocket FAQ support page (https://support.mozilla.org/en-US/kb/pocket-recommendations-firefox-new-tab). It was updated mid march 2025 (when mozilla surely knew they were shutting down pocket) and ironically it recommends for more articles to visit pocket.

1) this FAQ really needs to be updated to reflect pocket ceasing

2) it could reflect what is happening with the "thought-provoking stories" feature within firefox browser

My questions:

1) will the "thought provoking stories" feature aka curated articles of interest continue in firefox in any capacity after pocket ceases?

i don't know given i believe they're sourced from pocket.

EDIT: i've just discovered about "pocket hits" (or "ten tabs" as reportedly it's being renamed to) email newsletter. I knew nothing about this. Might the content / curated articles replace those from pocket on the new tab page?

2) if not, can people suggest alternatives to pocket's curated articles (i'm less fussed about saving the articles because i've seen many recommendations on that)?

thanks,

Gary

I'm on Linux.

I've been using this method to setup a custom new tab page for Firefox for almost 4 years, and it has worked great: https://jamesnorth.net/knowledge-base/article/firefox-new-tab-page

---

Navigate to /usr/lib/firefox.

Create autoconfig.cfg:

// var {classes:Cc,interfaces:Ci,utils:Cu} = Components;

/* set new tab page */ try {

 Cu.import("resource:///modules/AboutNewTab.jsm");  
 var newTabURL = "file:///home/james/ff/index.html";  
 AboutNewTab.newTabURL = newTabURL;  

} catch(e){Cu.reportError(e);} // report errors in the Browser Console

Create defaults/pref/autoconfig.js:

// pref("general.config.filename", "autoconfig.cfg"); pref("general.config.obscure_value", 0); pref("general.config.sandbox_enabled", false);

---

However, upon updating to Firefox 136, I only get a blank page. All of my autoconfig files still exist in /usr/lib/firefox.

When I create a new tab with Ctrl+T, it's a blank page. When I create a new window, it loads the local page I want it to load with the file path in the URL (which it never had before; the URL bar was blank in Firefox 135). So it seems to be partially working.

Any tips?

This has been asked before here, but it seems currently there is no solution:

Firefox's default behavior when using the mouse middle-click on an empty area of the tab bar area will create a new tab; I don't want this behavior. How can I disable it?

On the posts I found here, they mention using UserChrome.css, I enabled it and tried, doesn't work. custom styles are enabled but not disabling this feature.

I use DisplayFusion on my multi-monitor setup since years, and middle-clicking a window title bar or Chrome tab bar or Firefox tab bar will move the current window to a second monitor.

Currently with Firefox, middle-clicking the tab bar will move the window to the second monitor AND open a new tab. I use it a lot with YouTube, so when I move a playing video to the second monitor, I get an empty tab with audio in the background.

I recently moved from Chrome to Firefox, but this is driving me crazy.