More likely it's slow-loading javascript and ads.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Ventura 13.4 RC Fixes Bug With Content Filter Apps
- Thread starter MacRumors
- Start date
- Sort by reaction score
It could be, but the issue didn't exist before Ventura and before the last update the problem went away.
Something is wrong somewhere
If you've got content filtering programs installed, just disable them or uninstall them, problem solved.
This is you right now:
You might want to go into Safari Develop menu and make sure experimental features is reset to default (choice on very bottom of scrollable list). Develop menu is enabled in the advanced settings of Safari settings if you never enable to show on menu bar. Safari has an awful lot of things to play with. Firefox should just work OK for you (113) but if it does the same I doubt it has to do with browsers more to what you were thinking.
Not sure what's up with 13.2.1 but it's buggier than any Mac OS I've used in the past 5 years, at least. Logic Pro often disappears from its assigned desktop and I cannot access it unless I force quit and reopen (It won't quit via the Quit command … still shows as open but all its menu items are greyed out) Happens to some Adobe apps occasionally as well. Occasionally an app won't open when clicking on a project file … have to open the app first, then the project. Very strange. Hoping for some improvements soon.
It's not the first time Apple undermined user privacy involving content filtering https://www.macworld.com/article/67...ams-bypass-firewalls-and-vpns-in-big-sur.html
I think the problem is that Apple doesn’t seem to test their builds against small third party utilities.
Still trouble using a custom DNS and a secondary DNS coming out via DHCP. At work we use one that has a domain name pointing to an internal server and in Safari it works to load that page every other time, as if it's ”seeing” the custom DNS only every other load. If I manually add just the custom DNS to the network interface it works consistently.
No problems at all havinng more than one DNS come out via DHCP in Monterey, so something is definitely different in Ventura when it comes to this. If it's by design I'd like to read more about it but seems like faulty behaviour to me.
No problems at all havinng more than one DNS come out via DHCP in Monterey, so something is definitely different in Ventura when it comes to this. If it's by design I'd like to read more about it but seems like faulty behaviour to me.
Last edited:
I always thought that in transparency, Little Snitch should be bought out by Apple and fully incorporated into MacOS.
Such functionality is indispensable, but could be made optional for less sophisiticated users.
The only drawback would be Apple not wanting users to know just how much the OS is "phoning home".
Such functionality is indispensable, but could be made optional for less sophisiticated users.
The only drawback would be Apple not wanting users to know just how much the OS is "phoning home".
Low expectations will just keep allowing Apple software to get worse and worse. If it could be fixed so quickly, then why did the bug exist. Obviously, it was not tested for. So obviously it was NOT adequate.
Perhaps its as I previous commented that Apple just biding their time with implementing additional firewall options for outgoing content filtering that might be present MacOS14.
Because bugs happen all the time when programming - especially when you're dealing with something as massive as an OS (and an OS that has now existed for over 20 years). Your complaints show you have zero understanding of how software development works, or even what the point of the beta is.
I cannot stress this enough, because so many people seem to simply not understand this (or refuse to understand it?), betas will have bugs, full stop. Ideally those bugs will get fixed before the beta process is over, which is why betas exist in the first place! This bug has been fixed, it does not exist in the RC build, the beta process did its job. The vast, vast majority of Mac users will have no idea this bug ever existed.
Bemoaning about bugs in beta software is like bemoaning about getting wet while standing in the rain. If you're using beta software, you better damn well understand that there will be bugs - just like if your standing in the rain, you better damn well understand you're going to get wet.
I agree with you (and all your posts on this). It's mind boggling how some people just want to turn this beta bug into their "Apple software quality sucks" narrative without considering what the point of betas is.
I've had this argument many times over the years with my development teams. The good teams understand it and get better. The mediocre or worse teams always use this excuse and really never get any better.
Anyone who have been beta testing for years knows that beta testing is just an expanded hardware/software variance of testing against what is released to see what issues show up, not that it is a example of purging of all bugs like developing a app.
This documented toggling something to override specific third party software with the firewall was probably just testing something that they were working on before it goes to a stable release. I've seen similar toggle instances previously with a long history of MacOS evolution, they have a purpose in mind. It does make me curious to see how expanded/changed MacOS 14 will be as far as system settings after Ventura particularly the firewall. Given the various security patches we had this year don't be too surprised if that occurs.
Please note there is a RC2 now available as a full install for Devs and PB testers OTA. Was 12.88 GB install on AS based Macs.