Re: [gentoo-user] Pocket sneaks back

[Dale]

Michael wrote:
> On Monday, 16 March 2020 21:08:10 GMT Dale wrote:
>> Ian Zimmerman wrote:
>>> After the latest stable firefox upgrade to version 68.6 I again started
>>> seeing DNS queries for Pocket related domains.  I found this in
>>> prefs.js:
>>>
>>> user_pref("browser.newtabpage.activity-stream.section.highlights.includePo
>>> cket", true);
>>>
>>> I am not sure if this setting was new with this version or if firefox
>>> just started acting on it now, but in any case I am adding it to my
>>> user.js with a value of false, right now.
>> I admit I don't know what these are for but I went to look at mine.  I
>> also found this which is a little different than the one you posted but
>> still pocket related.
>>
>> services.sync.prefs.sync.browser.newtabpage.activity-stream.section.highligh
>> ts.includePocket
>>
>> I run unstable here but mine is set to true for that one as well.
>>
>> Dale
>>
>> :-)  :-)
> I didn't even know what pocket is, let alone that it is enabled as a default.
>
> I'm on FF 68.6.0esr, but I do not have a pocket button showing in the address
> bar.  I may have disable it sometime in the past, thinking that got rid of it
> - little I knew.
>
> Going to about:config and searching for pocket reveals a number of related
> settings, with 'extensions.pocket.enabled' being one you should pay attention
> to.
>
> https://help.getpocket.com/article/1025-disabling-save-to-pocket-features-in-firefox
>
> It is worth mentioning, Palemoon does not have pocket in it.  ;-)


I don't want to set them to false because I still don't know what they
do, google didn't help any either.  I don't want to break websites or
something and then be trying to figure out why a site works for everyone
but me, and maybe you if you happen to visit the same site.  ;-)

Can someone share a link that tells what a pocket is exactly?  If I
don't need it, I'd like to disable it.  It may help with the extension
thingy that takes up tons of memory and sends one core of my CPU to
100%.  So far, restarting Firefox is the only solution.  It sometimes
hit several GBs in no time flat.  It runs fine for days and then BAM. 
Overload.  :/

Thanks.

Dale

:-)  :-)