Good question!

The real answer seems to be "right" and "left".

Source: https://english.stackexchange.com/a/174112

Both Oxford English Dictionary and Merriam-Webster agree that "nitch" was the correct pronunciation in both British and American English until very recently. You already linked Merriam-Webster, so here's O.E.D:

N.E.D. (1907) gives only the pronunciation (nitʃ) /nɪtʃ/ and the pronunciation /niːʃ/ is apparently not recorded before this date. H. Michaelis & D. Jones Phonetic Dict. Eng. Lang. (1913), and all editions of D. Jones Eng. Pronouncing Dict. up to and including the fourteenth edition (1977) give /nɪtʃ/ as the typical pronunciation and /niːʃ/ as an alternative pronunciation. The fifteenth edition (1991) gives /niːʃ/ in British English and /nɪtʃ/ in U.S. English.

(N.E.D is the original name of the O.E.D. "/nɪtʃ/" is pronounced "nitch" and /niːʃ/ is pronounced "neesh".)

It looks like organic products mostly avoid this.

• 11/12 (92%) of conventional oat-based products had it
• 1/8 (12.5%) of organic oat-based products had it

(from https://www.nature.com/articles/s41370-024-00643-4/tables/2 )

For meetings, https://meet.jit.si/ is like Zoom or MS Teams but open source and free. You don't even need to create an account.

ALGOL-60 had its own keyboard (sort of): https://retrocomputing.stackexchange.com/questions/16082/was-there-an-input-device-capable-of-entering-all-algol-60-symbols-with-correct

Another that's been around forever and still has an active community: GemStone IV

FormLabs, but they start at $2500.

https://formlabs.com/3d-printers/catalog/

Are you saying that organic oat-based products use more pesticides than conventional oat-based products? Or are you talking about organic products in general? In either case, I'd be interested in learning more if you have any good sources.

I upvoted. Thanks for providing sources. I read both. My takeaway is that the amount of pesticide residue on conventional products is considered safe, but organic products contain less pesticide residue.

I think that Scientific American article is low quality in general (which is a shame--I used to subscribe to them). I think the relevant part is this quote:

According to the National Center for Food and Agricultural Policy, the top two organic fungicides, copper and sulfur, were used at a rate of 4 and 34 pounds per acre in 1971 [1]. In contrast, the synthetic fungicides only required a rate of 1.6 lbs per acre, less than half the amount of the organic alternatives.

• Their reference is https://ncfap.org/, which leads to a broken website for me.
• It's talking about usage of two specific fungicides from over 50 years ago.

(The article has other red flags as well that suggest lack of rigor.)

The paper seems more rigorous to me, but it actually refutes your point:

While conventional produce was between 2.9 and 4.8 times more likely to contain detectable pesticide residues than organic produce, samples of organic produce frequently contained residues.

That said, I think the important point is that both organic and conventional food are considered safe. Both papers agree with that, as does Harvard Health, which I consider reputable, although it also says that organic produce has less pesticide residue:

According to USDA data, organic foods have fewer pesticide residues than conventionally grown produce. But the amounts for both types of produce are within the level for safe consumption. And it's unclear if the pesticides used in organic farming are safer than nonsynthetic pesticides used in conventional farming.

(from https://www.health.harvard.edu/staying-healthy/should-you-go-organic )

Perhaps you would consider editing your original post to get rid of the "more of"?

Factory pattern can return a mock type for testing or a production type, as needed, which makes it possible to unit test the code that uses the produced object.

This quick guide explains it well. Then it improves on it by explaining dependency injection.

https://github.com/google/guice/wiki/Motivation

I have had the same issue a few times. Their troubleshooting page suggests a (not very helpful) workaround: add a shortcut to their webpage to your home screen.

https://proton.me/support/troubleshooting-sending-messages-android

I hope this is solved soon as well. It has led to some unfortunate miscommunication.

Just a guess... Try different settings in https://support.mozilla.org/en-US/kb/dns-over-https (I.e. try Max Protection and Off; either might help.) I've had problems with it interfering with VPN.

Another random idea... See if it happens with older versions of Firefox. Maybe they pushed an update in the past few weeks that changed something.

You might find more info in the Firefox developer console (as opposed to the network tab) if you haven't checked there already.

If I were debugging this, my next steps would be Wireshark, Postman proxy, or Burp proxy, to see what's actually happening to the packets that are failing.

For what it's worth, my gut feeling when I read the symptoms was that packets were getting misrouted. I had a similar issue when my NAT was misconfigured, so packets were going out the clear net but with the VPN's source IP. If so, it would appear as if packets were getting dropped. Those half-open connnections could conceivably cause ns_binding_abort, since the browser is making lots of requests but many of them never get responses. Maybe.

Some other random tidbits, in case they're helpful:

• When I ran OpenVPN on Android and tethered my PC, the tethered traffic didn't go over VPN, only traffic originating from the phone did. From what I recall, that was normal on Android. Maybe Mullvad and/or EasyTether changes that. But maybe they don't change it reliably? I have no idea why that would be Firefox specific, though. You could try ipleak.net to see if it gives you any clues about traffic leaking from your VPN.

• I also recall that some mobile carriers use the TTL on packets to detect tethering. I believe there's an Android setting that affects that behavior, which you can set with ADB. If the carrier detects that your packets' TTLs are lower than they should be, they might drop the packets. Again, I have no idea why that would be Firefox specific or sporadic.

Good luck!