ProTruckDriver
Contributor
Thank you. I'll give it a try later.It does the same thing that tab search menu in Chrome (except it does not have "Recently closed" section). Integrates well so I think it's worth it.
Thank you. I'll give it a try later.It does the same thing that tab search menu in Chrome (except it does not have "Recently closed" section). Integrates well so I think it's worth it.
If this is related to any of machines in your signature then yes it looks like at some point Safari starts to suffer from these issues. One of my older machines is MacbookPro 12,1 and on that I found that Ventura was last actually workable system. Safari 17 (on Sonoma) seemed still to be usable but pegged CPU often up to level that started to feel uncomfortable. One possible explanation may be that Safari 16 came out with Monterey and that was last officially supported OS for that machine (Safari 17 came out on Sonoma).I could update to version 18, but it bothers me that Safari 18 has WebGL issues (I don't know if this affects all Macs or just some Macs and OCLP). So, for example, if I want to return items on Amazon, the maps showing the courier pickup locations don't open, and so on.
I will never use Chrome the reason because of privacy, and can slow it down on any computer Chrome is under own by google etc, I use safari and FirefoxChrome
OK.I will never use Chrome the reason because of privacy, and can slow it down on any computer Chrome is under own by google etc, I use safari and Firefox
Years ago I have iMac 2011 and try to use Chrome for a little while and noticeable it slowing down, then my friend were telling me careful over chrome etc
I use to use Firefox all the time when they updated the browser once a month or so. Now it seems like it's every other day. It became a PITA. Sometimes it would break my Password Manager when they would update.As such, I moved over to Firefox.
For a number of years I was largely using TenFourFox, which is a PowerPC fork of Firefox. This was primarily back when I was on PowerPC. T4Fx came about through a dev intent on keeping PowerPC running on a modern browser roughly equivalent to whatever Firefox was offering at the time. Eventually the dev abandoned the project (it got too difficult) and for myself I'd moved on to Intel Macs.I ran ungoogled-chromium for a while because it supports the god awful webHID standard that lots of hardware manufactures adopted. My keyboard and mice requires it. But then discovered that once I set them up, I really don't need said software and can always download their even worse electron wrappers should the need arise (and remove them once done).
As such, I moved over to Firefox. It took an annoying amount of time to harden it and tailor it my liking, but through the use of userChrome.css, themes and a lot of secret config:about hacking, it now leaks a lot less than any other browser (even Safari), and I can manage a lot of aspects not open to control in Safari (like remove that ghastly fullscreen video notice to name one). It also supports handoff from my other devices even if they run Safari (mobile Firefox is just trash thanks to needing webkit on the backend), which was a pleasant surprise.
I am also loving the vertical tabs and find that I kind can't live without them anymore lol.
Safari is still the best browser, though.
No problem. Just thought I'd offer. For us at that time, the problem was that more modern Macs simply had the ability to power through bad website code. PowerPC never had that advantage because website code is all processed by the CPU and not the GPU. So our efforts were largely centered around loading and interpreting a page quickly so that the CPU was not being hammered. That, in large part is what made browsing slow on old Macs. But it was all trial and error with a lot of misses.@eyoungren
I used mostly this: https://brain****sec.github.io/firefox-hardening-guide and https://github.com/Renatoissance/firefox-hardening-guide and https://cyberinsider.com/firefox-privacy/
I know FF 67+ changed a lot of things under the hood so it's been a challenge searching online and going thru the litany of settings in about:config but I think I have enough to manage it all, thanks for the offer tho.
TBH, even just using a lot of the available settings in FF are likely good enough for most people.
I have also made use of the deadass simple policies feature to disable the auto updates, something Mozilla doesn't have a setting for anymore. And I don't like things updating on me nor pinging servers without my consent, even if it's just a benign update server. Times have changed and new version don't have the best track record.
There's a Github project called Betterfox that I often use as a baseline for my FF tweaks on Linux. I'm sure there are better and more complete guides out there, but if you want a quick .js copy-paste for quick tweaks, it's a good start.@eyoungren
I used mostly this: https://brain****sec.github.io/firefox-hardening-guide and https://github.com/Renatoissance/firefox-hardening-guide and https://cyberinsider.com/firefox-privacy/
I know FF 67+ changed a lot of things under the hood so it's been a challenge searching online and going thru the litany of settings in about:config but I think I have enough to manage it all, thanks for the offer tho.
TBH, even just using a lot of the available settings in FF are likely good enough for most people.
I have also made use of the deadass simple policies feature to disable the auto updates, something Mozilla doesn't have a setting for anymore. And I don't like things updating on me nor pinging servers without my consent, even if it's just a benign update server. Times have changed and new version don't have the best track record.