I feel any fuzzy tab grouping feature [0] is a significant security risk by default. Especially with black-box LLMs.
Consider a phishing site which opens up in a new tab, tricking the browser into color-coding and sliding it over into the middle of the user's existing tabs for the real site: "Huh, my bank says I got logged out and need to re-enter my credentials, well, no problem, I mean this is obviously the same interface I was working with earlier, right?"
Protecting against that attack would require some deterministic security rules, such as refusing to add to any group if the domain isn't already represented there... But at that point, isn't the AI-fuzziness really only useful for deciding when not to group things by domain?
It's always the departments that are closest to the customer that pay the price in my experience. At one company, after killing QA, the support team created their own internal QA process. They were going to deal with the issues anyways, so they wanted to catch as many as they could first.
SKIP LOCKED was added in 10.6 (~2021), years after MySQL had it (~2017). My company was using MariaDB around the time and was trailing a version or two and it made implementing a queue very painful.
reply