Yes. 100%. Do it, don't look back. Disable it on a per-website basis if needed, but... largely, I simply accept that I don't need to do those things I can't

Yes. 100%. Do it, don't look back. Disable it on a per-website basis if needed, but... largely, I simply accept that I don't need to do those things I can't do with it on. I've been running Lockdown on my iOS devices since before iOS 16 came out (I installed the betas to play with it). The only actual annoyances I've found in practical, regular, daily use: - Lots of websites use webfonts for icons. Those don't render, and you get empty "No font glyph" boxes instead for various arrows and icons. It's not a big deal in regular use. - If someone sends you an animated gif as a MMS message (maybe iMessage too), it won't actually animate. Nothing of value is lost. - The latest from "that guy" won't work, because there's no WebGL support for Javascript animations of watches, bicycles, cameras, etc. Given that the JS is non-obfuscated, I don't mind disabling Lockdown for his site. - Some websites still use image formats that don't render, but this is far better than it was even six months ago when Lockdown was fresh and new. Otherwise... I've eliminated an awful lot of actively exploited interfaces for almost no loss in functionality.