> but also allowing an attacker to run an offline decryption attack with unlimited attempts. This invariably leads to your main password getting compromised.
Do the OpenSSH authors not know about PKBDF2 or similar?
How does PBKDF2 prevent an offline decryption attack with unlimited attempts?
All it does is slow down the attempts, but for the average person's easy-to-remember password, it's probably increasing the effort from milliseconds to a few days.
> Recommendations are hugely influenced by what you watched very recently.
Ah, well, I don't know that I fully agree.
I watch channels that are people building things, repairing tools, or goofing around in an easy-going way without a lot of product placement or sponsored content.
And yet, all of the recommendations I get are either sponsored unboxing videos with AI voiceovers or click-baity channels with ugly reaction faces in the video thumbnails. I guess those probably make more money for Google.
I suspect ad revenue isn't good for maker/hacker type videos. I watch a lot of woodworking and cnc projects, and I mostly get the kind of recommendations you're talking about
Well, if you look at the prompts, they are basically told to sound like that.
And if you ask me, I think these models were trained on tween fiction podcasts. (My kids listen to a lot of these and dramatic over-acting seems to be the industry standard.)
Also, their middle-aged adult with an "American English" accent sounds like any American I've ever met. More like a bad Sean Connery impersonator.
I've used a bunch of the SOTA models (via my work's Windsurf subscription) for HTML/CSS/JS stuff over the past few months. Mind you, I am not a web developer, these are just internal and personal projects.
My experience is that all of the models seem to do a decent job of writing a whole application from scratch, up to a certain point of complexity. But as soon as you ask them for non-trivial modifications and bugfixes, they _usually_ go deep into rationalized rabbit holes into nowhere.
I burned through a lot of credits to try them all and Gemini tended to work the best for the things I was doing. But as always, YMMV.
Yeap, along with `+++`, `**` and mixing if I remember correctly.
I don't understand the logic of using an non-standard syntax because some non-standard implementations may not render correctly.
Actually, yes, now you know for a fact that none of the Markdown implementation will render it correctly.
So, I guess, they used `~~~` instead and it was an error in OP post.
The problem here is that if you use ``` as a token in a non-markdown language, then it's going to be very hard to embed that code in a markdown code block. That problem doesn't happen with other syntax as it's already escaped by the code block. `---` inside a markdown code block will render as a literal `---`.
For new implementations, sure. But it's harder to change existing implementations (anything not already CommonMark-compatible will introduce unexpected changes to existing content if you switch to CommonMark), and especially for anything that's not being actively developed it's unlikely to ever change.
Do you... usually read content in a full-screen window on that thing?
I only have a 27" monitor and sit about 2.5 feet away from it and I move my head _slightly_ to focus on different windows. But that's the reason I have a larger monitor, so I can have a bunch of normal-sized windows open at once.
If the edges of the screen are further from your eyes than the center, the content and text doesn't appear at the same size. If you wear glasses, the edges might even fall out of focus unless you physically move closer.
I like having three columns of code open in my editor, but the left edge of the leftmost column (since code is left-justified) gets pretty far away from my face. Or I need stronger glasses, one of the two.
reply