tjoff
Joined 15 years ago
Joined 15 years ago
Up until 5 hours ago this fix was not present:
> The displayed target is sanitized so invisible and line-breaking characters cannot conceal the effective destination.
https://github.com/ghostty-org/ghostty/security/advisories/G...
The sensible default is to have it turned off. And by the looks of it Ghostty versions before this you couldn't even turn it off.
AI isn't brute-forcing, or it would have been completely unusable for code.
Go straight to jpeg xl and/or avif when the they are mature.
But would be cool with a separate buzzer of sorts where you get the normal buzzer notification and then hold a finger somewhere specific and get details that way.
Clear and to the point. Not even a cookie popup (which ni user respectable site needs, so super low bar to clear).
If you meant the text then I agree.
It will die so just leave it alone.
I haven't used Konsole, but I do like this "recent" focus on terminals and have used many of the newer ones. Dailydrived st,alacritty,wezterm,ghostty,kitty,foot (probably forgot some) and I live for the regex pattern matching copy shortcuts etc.
I learned about OSC8 because my terminal (whichever it was) used one of its features and I didn't know it was possible to do that. My immediate thought was, how is the security?
And it is very disappointing to see how little effort people have spent on that. That is really one part that I expect more from modern incarnations of the old terminals where I can sort of forgive them for the lack of security posture.
I like ghostty, I really do. But this is not a good look, and to be clear it isn't just ghostty. Without looking for it I've stumbled upon several OSC8 and OSC52 bugs (in other software) recently.