Wasted an hour of my life tracking down this one - its just appeared on
my linux systems today. One system oddly isn't affected.

Symptoms are that firefox sometimes/always hangs forever on trying to
access (some?) sites.

https://bugzilla.mozilla.org/show_bug.cgi?id=1749908

There is a simple workaround

or more.

Anyway if you are experiencing this, just try some of the fixes.

My browser worked by disabling http3 dns support

--
When plunder becomes a way of life for a group of men in a society, over
the course of time they create for themselves a legal system that
authorizes it and a moral code that glorifies it.

Frédéric Bastiat

The Natural Philosopher wrote:
> Wasted an hour of my life tracking down this one - its just appeared on
> my linux systems today. One system oddly isn't affected.
>
> Symptoms are that firefox sometimes/always hangs forever on trying to
> access (some?) sites.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
>
>
>
> There is a simple workaround
>
> or more.
>
> Anyway if you are experiencing this, just try some of the fixes.
>
> My browser worked by disabling http3 dns support
>
>
1749910 - [2022-01-13] Hangs in socket thread

https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52

"Firefox has witnessed outages and we are sorry for that. We believe
it's fixed and a restart of Firefox should restore normal behaviour. We
will provide more information shortly"

Status: NEW → RESOLVED

On 13/01/2022 11:23, Andrei Z. wrote:
> The Natural Philosopher wrote:
>> Wasted an hour of my life tracking down this one - its just appeared
>> on my linux systems today. One system oddly isn't affected.
>>
>> Symptoms are that firefox sometimes/always hangs forever on trying to
>> access (some?) sites.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
>>
>>
>>
>> There is a simple workaround
>>
>> or more.
>>
>> Anyway if you are experiencing this, just try some of the fixes.
>>
>> My browser worked by disabling http3 dns support
>>
>>
> 1749910 - [2022-01-13] Hangs in socket thread
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52
>
> "Firefox has witnessed outages and we are sorry for that. We believe
> it's fixed and a restart of Firefox should restore normal behaviour. We
> will provide more information shortly"
>
> Status: NEW → RESOLVED
>
in v 96...will have to wait for the package managers to get it into the
distro tree ...meanwhile it has resolved itself on the one machine I
didn't hack...
I think it was not just firefox, but also some other external issue.

--
All political activity makes complete sense once the proposition that
all government is basically a self-legalising protection racket, is
fully understood.

On Thu, 13 Jan 2022 11:58:12 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

> On 13/01/2022 11:23, Andrei Z. wrote:
> > The Natural Philosopher wrote:
> >> Wasted an hour of my life tracking down this one - its just
> >> appeared on my linux systems today. One system oddly isn't
> >> affected.
> >>
> >> Symptoms are that firefox sometimes/always hangs forever on trying
> >> to access (some?) sites.
> >>
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
> >>
> >>
> >>
> >> There is a simple workaround
> >>
> >> or more.
> >>
> >> Anyway if you are experiencing this, just try some of the fixes.
> >>
> >> My browser worked by disabling http3 dns support
> >>
> >>
> > 1749910 - [2022-01-13] Hangs in socket thread
> >
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52
> >
> > "Firefox has witnessed outages and we are sorry for that. We
> > believe it's fixed and a restart of Firefox should restore normal
> > behaviour. We will provide more information shortly"
> >
> > Status: NEW → RESOLVED
> >
> in v 96...will have to wait for the package managers to get it into
> the distro tree ...meanwhile it has resolved itself on the one
> machine I didn't hack...
> I think it was not just firefox, but also some other external issue.
>
>

You can also disable http3 in about:config

On 13/01/2022 19:37, noscript wrote:
> On Thu, 13 Jan 2022 11:58:12 +0000
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>
>> On 13/01/2022 11:23, Andrei Z. wrote:
>>> The Natural Philosopher wrote:
>>>> Wasted an hour of my life tracking down this one - its just
>>>> appeared on my linux systems today. One system oddly isn't
>>>> affected.
>>>>
>>>> Symptoms are that firefox sometimes/always hangs forever on trying
>>>> to access (some?) sites.
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
>>>>
>>>>
>>>>
>>>> There is a simple workaround
>>>>
>>>> or more.
>>>>
>>>> Anyway if you are experiencing this, just try some of the fixes.
>>>>
>>>> My browser worked by disabling http3 dns support
>>>>
>>>>
>>> 1749910 - [2022-01-13] Hangs in socket thread
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52
>>>
>>> "Firefox has witnessed outages and we are sorry for that. We
>>> believe it's fixed and a restart of Firefox should restore normal
>>> behaviour. We will provide more information shortly"
>>>
>>> Status: NEW → RESOLVED
>>>
>> in v 96...will have to wait for the package managers to get it into
>> the distro tree ...meanwhile it has resolved itself on the one
>> machine I didn't hack...
>> I think it was not just firefox, but also some other external issue.
>>
>>
>
> You can also disable http3 in about:config
>

That is what I did on this machine. Another machine seemed not to be
suffering, and the laptop 'fixed itself'

It seems tio be an interaction between firefox and certain external
things and the internal 'ET phone home' firefox software. Anyway, its
all working now and you know where to look if it catches you out

--
Renewable energy: Expensive solutions that don't work to a problem that
doesn't exist instituted by self legalising protection rackets that
don't protect, masquerading as public servants who don't serve the public.

On Thu, 13 Jan 2022 19:43:41 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

> It seems tio be an interaction between firefox and certain external
> things and the internal 'ET phone home' firefox software. Anyway, its
> all working now and you know where to look if it catches you out
>
>
>

I usually disable telemetry like this:

* about:config **browser.cache.disk.enable** = false
* about:config **browser.cache.memory.enable** = false
* about:config **browser.cache.offline.enable** = false
* about:config **browser.cache.offline.storage.enable** = false
* about:config **browser.cache.disk_cache_ssl** = false
* about:config telemetry set to false, and telemetry.rejected set to
true
* about:config **keyword.enabled = false** (do not send keys typed in
address bar to search engine)
* about:config **browser.urlbar.suggest.searches** = false
* about:config **network.trr.mode** = 5 (disable trusted recursive
resolver dns over https by choice)
* about:config **extensions.webextensions.retrictedDomains** = ""
(enable ad blockers on all domains, inculding mozilla domains)

noscript <september@noulin.net> wrote:
> On Thu, 13 Jan 2022 19:43:41 +0000
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>
>> It seems tio be an interaction between firefox and certain external
>> things and the internal 'ET phone home' firefox software. Anyway, its
>> all working now and you know where to look if it catches you out
>
> I usually disable telemetry like this:
>
> * about:config **browser.cache.disk.enable** = false
> * about:config **browser.cache.memory.enable** = false
> * about:config **browser.cache.offline.enable** = false
> * about:config **browser.cache.offline.storage.enable** = false
> * about:config **browser.cache.disk_cache_ssl** = false

They disable the cache. What's the cache have to do with telemetry?

> * about:config telemetry set to false, and telemetry.rejected set to
> true

Those settings are not found (not even as defaults), but the
about:telemetry and about:studies pages show that telemetry is
disabled in my Firefox configuration.

> * about:config **network.trr.mode** = 5 (disable trusted recursive
> resolver dns over https by choice)

That's a handy one, though apparantly the browser is supposed to
prompt you to opt-in when they decide the time is right anyway.

I notice at the end of the bug report discussion they're talking
about changing the network.http.http3.enabled setting in the future
because people might have toggled it as a temporary fix and
forgotten about it. So continues the endless cat and mouse game of
the Firefox developers swapping around about:config settings and
users who genuinely want those setting to work having to hunt
around obscure forum threads in order to find the name of the new
secret config. concoctions.

--
__ __
#_ < |\| |< _#

On 13/01/2022 21:52, Computer Nerd Kev wrote:
> So continues the endless cat and mouse game of
> the Firefox developers swapping aroundabout:config settings and
> users who genuinely want those setting to work having to hunt
> around obscure forum threads in order to find the name of the new
> secret config. concoctions.

Oh yaaas!
Thunderbird is EVEN WORSE.

Upgrade happened, wouldn't talk to my smtp server, all the icons
changed, all the colors changed the fonts were rubbish...took me two
days of userchrome hacks to sort te appearance out and an hour to track
down the magic spell to stop it using advanced, advanced, advanced TLS,
and just use what had been working fine for the last 10 years...

--
“Those who can make you believe absurdities, can make you commit
atrocities.”

― Voltaire, Questions sur les Miracles à M. Claparede, Professeur de
Théologie à Genève, par un Proposant: Ou Extrait de Diverses Lettres de
M. de Voltaire

On 1/13/22 2:37 PM, noscript wrote:
> On Thu, 13 Jan 2022 11:58:12 +0000
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>
>> On 13/01/2022 11:23, Andrei Z. wrote:
>>> The Natural Philosopher wrote:
>>>> Wasted an hour of my life tracking down this one - its just
>>>> appeared on my linux systems today. One system oddly isn't
>>>> affected.
>>>>
>>>> Symptoms are that firefox sometimes/always hangs forever on trying
>>>> to access (some?) sites.
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
>>>>
>>>>
>>>>
>>>> There is a simple workaround
>>>>
>>>> or more.
>>>>
>>>> Anyway if you are experiencing this, just try some of the fixes.
>>>>
>>>> My browser worked by disabling http3 dns support
>>>>
>>>>
>>> 1749910 - [2022-01-13] Hangs in socket thread
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52
>>>
>>> "Firefox has witnessed outages and we are sorry for that. We
>>> believe it's fixed and a restart of Firefox should restore normal
>>> behaviour. We will provide more information shortly"
>>>
>>> Status: NEW → RESOLVED
>>>
>> in v 96...will have to wait for the package managers to get it into
>> the distro tree ...meanwhile it has resolved itself on the one
>> machine I didn't hack...
>> I think it was not just firefox, but also some other external issue.
>>
>>
>
> You can also disable http3 in about:config
>

Seems, like Winders, the more they "improve" it
the more problems.

And Win-11 ... I'm surprised a massive number of class action
lawsuits haven't been filed already ...... time for MS to
go *down* forever and always. What hateful crap.

1.AAC0832 <z24ba7.net> wrote:
....
> Seems, like Winders, the more they "improve" it
> the more problems.

> And Win-11 ... I'm surprised a massive number of class action
> lawsuits haven't been filed already ...... time for MS to
> go *down* forever and always. What hateful crap.

Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(
--
Slammy new week as expected. Lots of spams again! 2022 isn't any better and different so far. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

On 2022-01-13, Computer Nerd Kev <not@telling.you.invalid> wrote:
>> I usually disable telemetry like this:
>>
>> * about:config **browser.cache.disk.enable** = false
>> * about:config **browser.cache.memory.enable** = false
>> * about:config **browser.cache.offline.enable** = false
>> * about:config **browser.cache.offline.storage.enable** = false
>> * about:config **browser.cache.disk_cache_ssl** = false
>
> They disable the cache. What's the cache have to do with telemetry?

It is directly connected to telemetry, but it increases privacy and I
usually disable telemetry for privacy.

>
>> * about:config telemetry set to false, and telemetry.rejected set to
>> true
>
> Those settings are not found (not even as defaults), but the
> about:telemetry and about:studies pages show that telemetry is
> disabled in my Firefox configuration.

The exact settings are:
toolkit.telemetry.rejected=true
toolkit.telemetry.server is empty
*.telemetry.*enabled=false

The Natural Philosopher wrote:
> On 13/01/2022 19:37, noscript wrote:
>> On Thu, 13 Jan 2022 11:58:12 +0000
>> The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>>> On 13/01/2022 11:23, Andrei Z. wrote:
>>>> The Natural Philosopher wrote:
>>>>> Wasted an hour of my life tracking down this one - its just
>>>>> appeared on my linux systems today. One system oddly isn't
>>>>> affected.
>>>>>
>>>>> Symptoms are that firefox sometimes/always hangs forever on trying
>>>>> to access (some?) sites.
>>>>>
>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
>>>>>
>>>>>
>>>>>
>>>>> There is a simple workaround
>>>>>
>>>>> or more.
>>>>>
>>>>> Anyway if you are experiencing this, just try some of the fixes.
>>>>>
>>>>> My browser worked by disabling http3 dns support
>>>>>
>>>> 1749910 - [2022-01-13] Hangs in socket thread
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52
>>>>
>>>> "Firefox has witnessed outages and we are sorry for that. We
>>>> believe it's fixed and a restart of Firefox should restore normal
>>>> behaviour. We will provide more information shortly"
>>>>
>>>> Status: NEW → RESOLVED
>>> in v 96...will have to wait for the package managers to get it into
>>> the distro tree ...meanwhile it has resolved itself on the one
>>> machine I didn't hack...
>>> I think it was not just firefox, but also some other external issue.
>>>
>>>
>>
>> You can also disable http3 in about:config
>>
>
> That is what I did on this machine. Another machine seemed not to be
> suffering, and the laptop 'fixed itself'
>
> It seems tio be an interaction between firefox and certain external
> things and the internal 'ET phone home' firefox software. Anyway, its
> all working now and you know where to look if it catches you out
>
>
>
1749957 - `content-length` is not properly parsed when using viaduct
over HTTP3
https://bugzilla.mozilla.org/show_bug.cgi?id=1749957

Status: RESOLVED FIXED
Milestone: 98 Branch

On 14.01.22 08:39, Ant wrote:
> 1.AAC0832 <z24ba7.net> wrote:
> ...
>> Seems, like Winders, the more they "improve" it
>> the more problems.
>
>> And Win-11 ... I'm surprised a massive number of class action
>> lawsuits haven't been filed already ...... time for MS to
>> go *down* forever and always. What hateful crap.
>
> Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(

Sad but true: the good old days are gone.

On 14/01/2022 09:24, Andrei Z. wrote:
> The Natural Philosopher wrote:
>> On 13/01/2022 19:37, noscript wrote:
>>> On Thu, 13 Jan 2022 11:58:12 +0000
>>> The Natural Philosopher <tnp@invalid.invalid> wrote:
>>>
>>>> On 13/01/2022 11:23, Andrei Z. wrote:
>>>>> The Natural Philosopher wrote:
>>>>>> Wasted an hour of my life tracking down this one - its just
>>>>>> appeared on my linux systems today. One system oddly isn't
>>>>>> affected.
>>>>>>
>>>>>> Symptoms are that firefox sometimes/always hangs forever on trying
>>>>>> to access (some?) sites.
>>>>>>
>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
>>>>>>
>>>>>>
>>>>>>
>>>>>> There is a simple workaround
>>>>>>
>>>>>> or more.
>>>>>>
>>>>>> Anyway if you are experiencing this, just try some of the fixes.
>>>>>>
>>>>>> My browser worked by disabling http3 dns support
>>>>>>
>>>>> 1749910 - [2022-01-13] Hangs in socket thread
>>>>>
>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1749910#c52
>>>>>
>>>>> "Firefox has witnessed outages and we are sorry for that. We
>>>>> believe it's fixed and a restart of Firefox should restore normal
>>>>> behaviour. We will provide more information shortly"
>>>>>
>>>>> Status: NEW → RESOLVED
>>>> in v 96...will have to wait for the package managers to get it into
>>>> the distro tree ...meanwhile it has resolved itself on the one
>>>> machine I didn't hack...
>>>> I think it was not just firefox, but also some other external issue.
>>>>
>>>>
>>>
>>> You can also disable http3 in about:config
>>>
>>
>> That is what I did on this machine. Another machine seemed not to be
>> suffering, and the laptop 'fixed itself'
>>
>> It seems tio be an interaction between firefox and certain external
>> things and the internal 'ET phone home' firefox software. Anyway, its
>> all working now and you know where to look if it catches you out
>>
>>
>>
> 1749957 - `content-length` is not properly parsed when using viaduct
> over HTTP3
> https://bugzilla.mozilla.org/show_bug.cgi?id=1749957
>
> Status: RESOLVED FIXED
> Milestone: 98 Branch
>
Mmm. it seems - not having time to really understand that, that a rogue
response could essentially stop firefox from working at all, or even
closing..so a combination of a rogue site on the net and a bug in firefox.

Nasty.

Explains why my laptop is now working tho - they fixed the rogue site
perhaps and the fix to firefox will come soon enough with V96...

Which contains another bug fix to an old bug I reported I think. anyway
they decided to finally look into that and a fix is on the way.

--
"And if the blind lead the blind, both shall fall into the ditch".

Gospel of St. Mathew 15:14

On Thu, 13 Jan 2022 22:56:08 +0200
noscript <september@noulin.net> wrote:

> On Thu, 13 Jan 2022 19:43:41 +0000
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>
> > It seems tio be an interaction between firefox and certain external
> > things and the internal 'ET phone home' firefox software. Anyway,
> > its all working now and you know where to look if it catches you out
> >
> >
> >
>
> I usually disable telemetry like this:
>
> * about:config **browser.cache.disk.enable** = false
> * about:config **browser.cache.memory.enable** = false
> * about:config **browser.cache.offline.enable** = false
> * about:config **browser.cache.offline.storage.enable** = false
> * about:config **browser.cache.disk_cache_ssl** = false
> * about:config telemetry set to false, and telemetry.rejected set to
> true
> * about:config **keyword.enabled = false** (do not send keys typed in
> address bar to search engine)
> * about:config **browser.urlbar.suggest.searches** = false
> * about:config **network.trr.mode** = 5 (disable trusted recursive
> resolver dns over https by choice)
> * about:config **extensions.webextensions.retrictedDomains** = ""
> (enable ad blockers on all domains, inculding mozilla domains)
>

Why go to all that trouble when you could just use Waterfox?

https://www.waterfox.net/

If you use MX Linux, it's in the repository.

On 1/13/22 23:39, Ant wrote:
> 1.AAC0832 <z24ba7.net> wrote:
> ...
>> Seems, like Winders, the more they "improve" it
>> the more problems.

You must have a vision of better that is not the same
as the Vision at Microsoft. So do I but mine was inspired by
the very imperfect but very usable AmigaOS. Amiga was like a
custom built sports care and was not nearly as expensive.
Still I could never afford a new Amiga Computer when it
was selling well.

>
>> And Win-11 ... I'm surprised a massive number of class action
>> lawsuits haven't been filed already ...... time for MS to
>> go *down* forever and always. What hateful crap.
>
> Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(

Apple was another computer out of my price range. It may get better or
worse I still cannot afford a good Apple computer.
I buy second hand Dell Latitudes to run Linux.

That is just age speaking, Ant, and how is Grasshopper?

PCLinuxOS gets better in any event, resisting entropy.

But it seems there is always a debate over what exactly
"better" may mean.
Even Leonard Poettering believes that his awful creation
is somehow better. What has happened is that his captive audience
forced to use a grab-bag tool has gotten better at dealing with
its complications.

bliss - brought to you by the power and ease of PCLinuxOS
and a minor case of hypergraphia

--
bliss dash SF 4 ever at dslextreme dot com

ant@zimage.comANT (Ant) writes:

> 1.AAC0832 <z24ba7.net> wrote:
> ...
>> Seems, like Winders, the more they "improve" it
>> the more problems.
>
>> And Win-11 ... I'm surprised a massive number of class action
>> lawsuits haven't been filed already ...... time for MS to
>> go *down* forever and always. What hateful crap.
>
> Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(

Don't know about Apple, but as for Linux, NO FREAKING WAY.
It continues to improve. No, I do not use a desktop, fvwm3 here.
I don't see a lot of change, but when I do, it's a change for the better.

--
Dan Espen

On 2022-01-14, Bobbie Sellers <bliss@mouse-potato.com> wrote:

> On 1/13/22 23:39, Ant wrote:
>
>> 1.AAC0832 <z24ba7.net> wrote:
>> ...
>>> Seems, like Winders, the more they "improve" it
>>> the more problems.
>
> You must have a vision of better that is not the same
> as the Vision at Microsoft. So do I but mine was inspired by
> the very imperfect but very usable AmigaOS. Amiga was like a
> custom built sports care and was not nearly as expensive.
> Still I could never afford a new Amiga Computer when it
> was selling well.
>
>>
>>> And Win-11 ... I'm surprised a massive number of class action
>>> lawsuits haven't been filed already ...... time for MS to
>>> go *down* forever and always. What hateful crap.
>>
>> Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(
>
> Apple was another computer out of my price range. It may get better or
> worse I still cannot afford a good Apple computer.
> I buy second hand Dell Latitudes to run Linux.
>
> That is just age speaking, Ant, and how is Grasshopper?
>
> PCLinuxOS gets better in any event, resisting entropy.
>
> But it seems there is always a debate over what exactly
> "better" may mean.

True. What makes it complicated is that "better" means different
things to different people. Microsoft's products might be a
technical disaster, but if you define "better" as "making lots
of money", then their products are among the best that have
ever been created. See my .sig.

--
/~\ Charlie Gibbs | Microsoft is a dictatorship.
\ / <cgibbs@kltpzyxm.invalid> | Apple is a cult.
X I'm really at ac.dekanfrus | Linux is anarchy.
/ \ if you read it the right way. | Pick your poison.

On 2022-01-14, Johnny <johnny@invalid.net> wrote:

> Why go to all that trouble when you could just use Waterfox?
>
> https://www.waterfox.net/
>
> If you use MX Linux, it's in the repository.

Interesting. I left Firefox for Seamonkey as of release 29,
when they changed the user interface in ways I didn't like.
To this day, Seamonkey preserves the classic interface:
a standard menu instead of that dreadful hamburger menu,
and a tab bar configurable to disappear when you only have
one tab open (as I usually do).

The web page says, "you can use it with the interface of
Firefox 27+, 56, and 68" - maybe I could bring it back to
the classic interface. Looks like it's worth checking out.

Any other Seamonkey users out there?

https://www.seamonkey-project.org

--
/~\ Charlie Gibbs | Microsoft is a dictatorship.
\ / <cgibbs@kltpzyxm.invalid> | Apple is a cult.
X I'm really at ac.dekanfrus | Linux is anarchy.
/ \ if you read it the right way. | Pick your poison.

noscript <september@noulin.net> wrote:
> On 2022-01-13, Computer Nerd Kev <not@telling.you.invalid> wrote:
>>> I usually disable telemetry like this:
>>>
>>> * about:config **browser.cache.disk.enable** = false
>>> * about:config **browser.cache.memory.enable** = false
>>> * about:config **browser.cache.offline.enable** = false
>>> * about:config **browser.cache.offline.storage.enable** = false
>>> * about:config **browser.cache.disk_cache_ssl** = false
>>
>> They disable the cache. What's the cache have to do with telemetry?
>
> It is directly connected to telemetry, but it increases privacy and I
> usually disable telemetry for privacy.

It's for performance actually:
https://en.wikipedia.org/wiki/Web_cache

>>> * about:config telemetry set to false, and telemetry.rejected set to
>>> true
>>
>> Those settings are not found (not even as defaults), but the
>> about:telemetry and about:studies pages show that telemetry is
>> disabled in my Firefox configuration.
>
> The exact settings are:
> toolkit.telemetry.rejected=true

I haven't got that, but instead there's toolkit.telemetry.enabled,
which is not only set to False but greyed out so that I can't
toggle it True. Maybe that's because I also added ".invalid" to
the end of the toolkit.telemetry.server domain, or maybe they just
don't want to know what goes on in my world?

--
__ __
#_ < |\| |< _#

Dan Espen <dan1espen@gmail.com> wrote:
> ant@zimage.comANT (Ant) writes:
>> 1.AAC0832 <z24ba7.net> wrote:
>>> Seems, like Winders, the more they "improve" it
>>> the more problems.
>>
>> Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(
>
> Don't know about Apple, but as for Linux, NO FREAKING WAY.
> It continues to improve. No, I do not use a desktop, fvwm3 here.
> I don't see a lot of change, but when I do, it's a change for the better.

But that depends, eg. my router running OpenWRT keeps getting
slower to boot and has less free space in the 8MB of flash after
each major upgrade, yet doesn't do anything I want it to any
better. If it weren't for security fixes, I'd be much better off
sticking with a very old release. Granted some redesigning of
kernel functionality is done partly in the name of security, but
as a rule increasing the amount of code isn't the way to reduce
security vulnerabilities.

"As the current stable 21.02 release uses kernel 5.4 that is roughly
0.5 MB larger than the kernel 4.14 used in the old 19.07.x releases"
https://openwrt.org/supported_devices/432_warning

That said, in these discussions people do far too often confuse
the Linux kernel with popular Linux distros where bloated software
like default "desktops"/WMs get much worse over time than any picky
issue I have with the growth of the Linux kernel itself. I use JWM
here, also no Systemd, nor PulseAudio, and find that on a PC there
indeed isn't that much obvious change going on, with maybe a rare
useful feature appearing unobtrusively in the kernel from time to
time. So compared to M$ and Apple, who aren't even trying to make
something that would be practical to run on an old consumer-level
router, Linux is remaining extremely good.

--
__ __
#_ < |\| |< _#

On 2022-01-14 16:20, Computer Nerd Kev wrote:
> noscript <september@noulin.net> wrote:
>>
>> The exact settings are:
>> toolkit.telemetry.rejected=true
>
> I haven't got that, but instead there's toolkit.telemetry.enabled,
> which is not only set to False but greyed out so that I can't
> toggle it True. Maybe that's because I also added ".invalid" to
> the end of the toolkit.telemetry.server domain, or maybe they just
> don't want to know what goes on in my world?

Many/most Linux distributions completely disable telemetry in their
builds. The distros and their package maintainers still care about
privacy. (At least somewhat.) That's why it's cannot be enabled in the
version of Firefox you're running.

Firefox v96.0.1 is out now. Upgrade and retry?

The Natural Philosopher <tnp@invalid.invalid> wrote:
> Wasted an hour of my life tracking down this one - its just appeared on
> my linux systems today. One system oddly isn't affected.

> Symptoms are that firefox sometimes/always hangs forever on trying to
> access (some?) sites.

> https://bugzilla.mozilla.org/show_bug.cgi?id=1749908

> There is a simple workaround

> or more.

> Anyway if you are experiencing this, just try some of the fixes.

> My browser worked by disabling http3 dns support

--
Slammy new week as expected. Lots of spams again! 2022 isn't any better and different so far. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

John-Paul Stewart <jpstewart@personalprojects.net> wrote:
> On 2022-01-14 16:20, Computer Nerd Kev wrote:
>> noscript <september@noulin.net> wrote:
>>>
>>> The exact settings are:
>>> toolkit.telemetry.rejected=true
>>
>> I haven't got that, but instead there's toolkit.telemetry.enabled,
>> which is not only set to False but greyed out so that I can't
>> toggle it True. Maybe that's because I also added ".invalid" to
>> the end of the toolkit.telemetry.server domain, or maybe they just
>> don't want to know what goes on in my world?
>
> Many/most Linux distributions completely disable telemetry in their
> builds. The distros and their package maintainers still care about
> privacy. (At least somewhat.) That's why it's cannot be enabled in the
> version of Firefox you're running.

No actually I'm using the official Mozilla binary of v. 96, so it's
definitely the Firefox developers who prevented that setting from
being toggled in my about:config for some reason (possibly because
I've fiddled with so many other about:config settings).

Actually, I just tried starting Firefox in a new profile and
toolkit.telemetry.enabled is still locked at False, yet the
telemetry settings in preferences (which it prompted me to look at
on start-up) are set to enabled, and about:telemetry says that
telemetry is enabled. So I'm confused.

--
__ __
#_ < |\| |< _#

On Fri, 14 Jan 2022 11:45:15 -0500, Dan Espen wrote:

>>
>> Don't forget Apple's stuff too. Even Linux. Everything is getting worse. :(
>
> Don't know about Apple, but as for Linux, NO FREAKING WAY.
> It continues to improve. No, I do not use a desktop, fvwm3 here.
> I don't see a lot of change, but when I do, it's a change for the better.
>

Good choice (fvwm3)!

As far as browsers, Palemoon is the only choice, and coupled
with graphical links (links -g) there is no better way (IMO) to
access the degenerate web.

http://links.twibright.com/

There is also ungoogled chromium:

https://github.com/Eloston/ungoogled-chromium

Any web sites that cannot be viewed in the above browsers are
not worth the INTELLIGENT man's time.

--
Scratch your technical itch:
https://www.linuxfromscratch.org/