I can say from being on the Pale Moon forum, which suffers from this problem even worse than Firefox, that the usual outcome is to be told "Use Chrome."

And it's not only the sites that are the problem, but also Gooble which has the power to change internet/browsing/web standards, and who also happens to have the most used browser. It's a case of the fox guarding the hen house.

Thanks for the link. Didn't see this thread. So I guess it's now 1 👍 and 1 👎.

How long has it been since you updated? I had a "big" amount of updates this morning. That is, big to me since I check for updates just about every day. Here's what I had:

CCommit Log for Sun Jun 30 07:40:01 2024

Upgraded the following packages:
bash (5.2.15-2+b2) to 5.2.15-2+b7
curl (7.88.1-10+deb12u5) to 7.88.1-10+deb12u6
gir1.2-gdkpixbuf-2.0 (2.42.10+dfsg-1+b1) to 2.42.10+dfsg-1+deb12u1
intel-microcode (3.20231114.1~deb12u1) to 3.20240514.1~deb12u1
libbluetooth3 (5.66-1+deb12u1) to 5.66-1+deb12u2
libcjson1 (1.7.15-1) to 1.7.15-1+deb12u1
libcpupower1 (6.1.90-1) to 6.1.94-1
libcurl3-gnutls (7.88.1-10+deb12u5) to 7.88.1-10+deb12u6
libcurl4 (7.88.1-10+deb12u5) to 7.88.1-10+deb12u6
libfreetype6 (2.12.1+dfsg-5) to 2.12.1+dfsg-5+deb12u3
libgdk-pixbuf-2.0-0 (2.42.10+dfsg-1+b1) to 2.42.10+dfsg-1+deb12u1
libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) to 2.42.10+dfsg-1+deb12u1
libgdk-pixbuf2.0-common (2.42.10+dfsg-1) to 2.42.10+dfsg-1+deb12u1
libglib2.0-0 (2.74.6-2+deb12u2) to 2.74.6-2+deb12u3
libglib2.0-bin (2.74.6-2+deb12u2) to 2.74.6-2+deb12u3
libglib2.0-data (2.74.6-2+deb12u2) to 2.74.6-2+deb12u3
libgnutls30 (3.7.9-2+deb12u2) to 3.7.9-2+deb12u3
libltdl7 (2.4.7-5) to 2.4.7-7~deb12u1
libpython3.11 (3.11.2-6) to 3.11.2-6+deb12u2
libpython3.11-minimal (3.11.2-6) to 3.11.2-6+deb12u2
libpython3.11-stdlib (3.11.2-6) to 3.11.2-6+deb12u2
libqt5concurrent5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5core5a (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5dbus5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5gui5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5network5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5printsupport5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5sql5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5sql5-sqlite (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5widgets5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5xml5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libseccomp2 (2.5.4-1+b3) to 2.5.4-1+deb12u1
libssl3 (3.0.11-1~deb12u2) to 3.0.13-1~deb12u1
libtool (2.4.7-5) to 2.4.7-7~deb12u1
linux-compiler-gcc-12-x86 (6.1.90-1) to 6.1.94-1
linux-headers-amd64 (6.1.90-1) to 6.1.94-1
linux-image-amd64 (6.1.90-1) to 6.1.94-1
linux-kbuild-6.1 (6.1.90-1) to 6.1.94-1
linux-libc-dev (6.1.90-1) to 6.1.94-1
nano (7.2-1) to 7.2-1+deb12u1
openssl (3.0.11-1~deb12u2) to 3.0.13-1~deb12u1
python3-idna (3.3-1) to 3.3-1+deb12u1
python3.11 (3.11.2-6) to 3.11.2-6+deb12u2
python3.11-minimal (3.11.2-6) to 3.11.2-6+deb12u2
wpasupplicant (2:2.10-12) to 2:2.10-12+deb12u1

Installed the following packages:
linux-headers-6.1.0-22-amd64 (6.1.94-1)
linux-headers-6.1.0-22-common (6.1.94-1)
linux-image-6.1.0-22-amd64 (6.1.94-1)

Not to get philosophical here, but animals only do what they've been programed to do (to use a computer analogy). That's one thing that makes them animals. Human beings have free choice, and as you alluded to, most are using that free choice in a wrong way. Yes, I'm paying attention.

Dan made a post just 2 days ago on his sourceforge page, and made no mention at all of this other version.

https://sourceforge.net/p/miyolinux/dis … 0494056cf/

EDIT
Got the answer on Dan's sourceforge page (the link above), yes he does endorse Jim's version.

Did Dan ever mention why he stopped developing Miyo?

Is version 125.0.6422.76-1 the one you're on now? That's the version I was updated to yesterday.

Check out this link, see if there's something there that can help before you go the nuclear option.

https://docs.xfce.org/xfce/xfce4-panel/start

Found the answer. fonts-noto-core did the trick.

The problem is solved. It was a bad ethernet port on the back of the router. Switching to a different one fixed it (it's been ~24 hours and no issues).