I when to check and I think I get it now, the link-local is routeable (switchable?) but only at the local level, but then you might ask why bother with SLAAC at all then. It's due to router being unable to route anything with a link local origin or destination as they are not globally unique so if you need to talk to anything past layer 2 you need unique-local address (or global).
If any org had any use for telemetry they'd have no incentive into to adhere to something that would make it easier for users to opt-out. In fact that thee whole reason you have to opt-out instead of opt-in in the first place.
Its an ok solution, but will never be implement and doing it actively goes against the interest of those who would have to do implement it.
Simple, you can serve a reasonable amount of unobtrusive ads and I and others might turn off adblock to support the publication or you can do what you're doing, I'll keep it on and see no ads at all.
I've personally used and still use FF for year and have now no intentions of switching.
I don't care about the Ai stuff as long is mostly opt-in or easily disabled at least.
Having said that I've been looking forward the Ladybug project as a another browser not part of the chromium swarm. I'm sure I'll give it a try when it's more mature.
It'd just devolve into security whack a mole about what permissions need those special account or not, ending with basically all of them making it the same as just needing dev verification anyway for anything remotely useful.
And despite that, you assuming that dev verification means no malware. The Play Store requires developers to register with the same verification measures we're talkingand malware is hardly unheard of there.