fugueish@wandering.shop
Posts
-
aah, the reason why the in-app kindle purchase flow in german has a button labeled "Bitte lesen" (which translates to "Please read") for opening the purchased ebook is that someone mistranslated "Read now" as if it was meant in imperative form? -
aah, the reason why the in-app kindle purchase flow in german has a button labeled "Bitte lesen" (which translates to "Please read") for opening the purchased ebook is that someone mistranslated "Read now" as if it was meant in imperative form? -
aah, the reason why the in-app kindle purchase flow in german has a button labeled "Bitte lesen" (which translates to "Please read") for opening the purchased ebook is that someone mistranslated "Read now" as if it was meant in imperative form?@freddy @jann A bunch of years ago, I went on a giant quest to improve translation in Chrome (including getting colleagues to set Chrome to their native languages, which resulted in some 'great' bug reports). Lots of native speakers disagreeing with each other about what words mean.

One thing I discovered: Apparently, nobody on the team had ever set their locale to an RTL language. Text flying in every direction all over the place. I fixed as many of them as I could.
-
Yes, yes, Mastodon hates LLMs and all that — sure.Yes, yes, Mastodon hates LLMs and all that — sure. I probably hate them at least as much as you.
But LLMs really are finding vulnerabilities and really are developing exploits for them.
There are ways, both by using and not by using LLMs, to make more resilient software, and we absolutely must do so. Ignoring empirical reality is not going to result in success for engineers or the people who depend on software and information services.
-
Korn’s 1st album came out in 1994, making it officially öld metalKorn’s 1st album came out in 1994, making it officially öld metal
-
is it just me, or does the a. i. companies’ recent focus on automating exploit finding read as an “engage with us Or Else” ploy against the projects that wouldn’t take generated code contributions but can’t ignore security issues@tef @joe Which is: not fully true! Defenders get to define the territory, including audit and observability. Finding a vuln, developing an exploit — way too easy. Making it operational and maintaining the capability over time: somewhat to substantially more fraught. (Still way, way too easy, of course)
-
is it just me, or does the a. i. companies’ recent focus on automating exploit finding read as an “engage with us Or Else” ploy against the projects that wouldn’t take generated code contributions but can’t ignore security issues -
is it just me, or does the a. i. companies’ recent focus on automating exploit finding read as an “engage with us Or Else” ploy against the projects that wouldn’t take generated code contributions but can’t ignore security issues@tef @joe They seem to avoid talking about solid defensive remedies (some of which LLMs likely will also be able to do well, such as translation and theorem proving — there are already results), for some reason. Until that strong medicine is applied, I think they'll continue producing new bugs and new kinds of bugs. Underestimating them is unwise for defenders. Keep in mind also they are military contractors.
-
I always forgive Git a lot of its bullshit on account of how it's one of those programs originally created in the 70s that are just half a century of cruft layered on top of outdated UI conventions that they were still making up as they went.@andrewt The mansplaining replies you’re getting also date back to the 1970s 🫠