Based on the user's results, it sounds like it didn't matter much.  I'm guessing the kali-rolling repo probably broke a metric shit-ton of critical packages during the installation process.

Glad you got it working.  Can you mark the thread as "solved" so future readers will know that your method "just works"?

A lot of people were very unhappy about that, to say the least...

...but Ubuntu isn't going to be much better, in that regard...

...so, your best bet is trying them out in a nonpersistent, throwaway, live environment, and reporting back to us, so as to provide the community some well-researched and tested insights...

...because in a persistent environment, you'll want to be careful when you repomix, especially in light of the systemd-ubuntu disclaimer above.

I appreciated the irony in this couplet.  The trickle-down effect of RHEL on other distros gives me pause for concern.  I imagine groups like this and Gentoo and Slackware will maintain workarounds.  I wonder if other projects, including Debian (which is based on systemd and GNOME3), will "just work" in the same way as Windows.

What app are you using for the topbar, and can you post/link to a config?  It looks great.

https://www.respondus.com/products/lockdown-browser/

That's not creepy or anything.  Hopefully you're not using this for a class on Orwellian literature lol.

Looks like it rejects VM usage of any sort, too.  I would hope your campus has some sort of virtual lab.

Also, if you do want to migrate sooner than later, it may be worthwhile to dump your spare configs in a separate partition or backup; bleach your system and install a preferred Devuan-based alternative; and then copy your backups wherever you desire (or keep that backup partition permanently mounted through /etc/fstab or whatever).

It's stock iridium on openbsd, but you get the idea.

https://ibb.co/kc1AU9

If anyone wants to run something a little more sophisticated than tcptrack, I'm all eyes.  All of this further disincentivizes me from using chrome-like browsers for any reason.

My point is that the ESR branch is no less an "old" version of Firefox than any of the listed derivatives: they all use "old" code and are actively maintained, their UIs being clear, visual examples.  The biggest difference is their project's goals.  ESR sacrifices "newness" for overall stability and security updates.  Its forks are separate projects, with their own separate goals, and there are already threads here which profess their pros and cons.

I am curious where you read that iceweasel is something other than a transitional package to firefox-esr.

The very "material" difference is the upstream Firefox ecosystem -- which is creating some of the problems that OP inadvertently discovered.  Without Mozilla's objectives changing over the years, PM would never have had its past; because it is still changing, and significantly, PM may lose an advantage in the future.  On the other hand, the ESR branch will, at least, be "stable enough."  Many people are okay with that.

Not what I expected to read from someone so committed to projects like grsec.  Am I in a coma...?
Anyways,

I wouldn't necessarily say unsolved so much as "probably unexplored."  The troublesome code, according to the user "skymt", is located in chrome/browser/history/web_history_service.cc.  I don't see that file in the source code anymore.  I skimmed through similarly-named files and didn't see any explicit URLs.
https://github.com/iridium-browser/irid … er/history
That's not to say that a similar function isn't embedded elsewhere in the source, though.

One thing I have not yet tried (which I assume someone has, by now) is opening up a tcpdump session with iridium.  I do have all telemetry disabled, to the best of my knowledge, so I'll be interested to see what can be found, and what happens when I use a blank config folder.

Yeah I'm not sure if Ungoogled Chrome is the gold-tier for privacy, but if that's what works for you...

@dx: you're absolutely right.  It's a shame that javascript is becoming a new "norm."

@Altoid: if you might humor me for a minute, what about Quantum did you dislike?  Was it only the UI?  I'm just curious.

Same behavior.  Here's my current config:

# iptables -L --line-numbers
Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain
2    ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain

Chain FORWARD (policy ACCEPT)
num  target     prot opt source               destination         
1    ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
2    ACCEPT     all  --  anywhere             anywhere            
3    ACCEPT     all  --  anywhere             anywhere            
4    ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
5    ACCEPT     all  --  anywhere             anywhere            
6    ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    ACCEPT     udp  --  anywhere             anywhere             udp spt:domain
2    ACCEPT     udp  --  anywhere             anywhere             udp spt:domain