tsujamin

Imagine missing such a great bug-chain because an off-hand AI comment at the start put you off

Surely that added flexibility negatively impacts the density/parameter count of the model you could etch?

I ended up migrating to ebooks.com and importing them into Calibre (after some work to get Adobe Digital Editions to import nicely) and using that to manage my Kindle. Did the same with my old Amazon library too when they were talking about stopping you exporting the azw3's

> not who made it

I’m not going to get the wow of “how did they perform that phrase/melody/rhythm” the same way from music that wasn’t actually performed (ack this doesn’t apply to all genres obviously)

That warning also doesn’t render right on my iPhone (the buttons are overlapping slightly), and I don’t recall seeing it on other repos. Is it new/bespoke?

And this is a comment, about a comment, about a book review, about a book, about a book reviewer who reviewed books.

For what it’s worth, Trusted Signing verification has been a moving target over the last 12 months. It was open for individuals, then it was closed to anyone except (iirc) US businesses with DUNS numbers, then it opened again to US based individuals (and a few other countries perhaps).

My completely uninformed guess was that someone had done something naughty with Trusted Signing-issued code signing certificates.

Anyway, when I first saw the VeraCrypt thing this morning my initial reaction was “I wonder if this is them pushing developers onto trusted signing the hard way?”

They did, just further into the article:

> According to a post on Hacker News, the popular VPN client WireGuard is facing the same issue.

It could be a flag in the per-network CarrierConfig bundle. I imagine that would help with jurisdictions that might require this protocol for legislative reasons

That the original post to HN linked in the blog was done on a throwaway kind of implies a level of awareness (on the part of the dev) that the code/claims were rubbish :)

https://news.ycombinator.com/item?id=46780837

To name a few (presumably): drivers, proprietary protocols, vendor warranties/support, licensing/relicensing, paying you to do the work, waiting for the work to be done/tested, paying for workforce re-training, justifying this to management etc.

All these reasons suck, but they’re all reality in one industry or another sadly.

There’s also API Sets: where DLLs like api-win-blah-1.dll acts as a proxy for another DLL both literally, with forwarder exports, and figuratively, with a system-wide in-memory hashmap between api set and actual DLL.

Iirc this is both for versioning, but also so some software can target windows and Xbox OS’s whilst “importing” the same api-set DLL? Caused me a lot of grief writing a PE dynamic linker once.

https://bookkity.com/article/api-sets

Strong recommendation for Alistair Reynold’s Century Rain if you want another of his. It’s part 20th century alternate history, part hard boiled crime noir, and part hard space opera.

Cutting a long list short, the _best_ thing I read this year was W. Somerset Maugham’s Of Human Bondage.

It’s not a book where the world changes greatly or great things are done, but honestly that’s kind of nice: It’s a compelling story of a life, the characters were engrossing (one in particular stands out for how strongly _dislikeable_ they are) and the I loved the prose.

Also shoutout to Standard EBook’s excellent, public domain edition (and all their volunteers other work!): https://standardebooks.org/ebooks/w-somerset-maugham/of-huma...

I thought I was going crazy, but it started feeling materially worse sometime in last few weeks.

> Great Dead Bars of New York:

> 1. SIBERIA in any of its iterations. The one on the subway being the best.

Timely, as the latest reincarnation of SIBERIA just re-opened in 59th Street/Columbus Circle station

So long as you’re writing your smart contracts with a chisel, into a stone tablet, with no compilers or assemblers in sight!

A Pwnie for "unilaterally shutting down a counterterrorism operation”

You say beautiful, I say existentially terrifying, let’s split the difference

Obviously not speaking for others experience, but it all makes me feel pretty fatigued, and as if this growing expectation of "AI-enhanced productivity" is coming at the expense of a craft and process (writing software) that I enjoy.

> wireless file transfers between Android and iOS being completely impossible at the moment

P2P proximal wireless transfer, sure, but there's half a dozen apps on your phone that'll let you punt a document, a photo, an invite to someone on the other phone OS platform.

Maybe I'm an edge case, but probably 90% of my Airdrop usage is between my own devices, so the platform taking care of the authentication story is of more utility than cross-platform transfers. If someone isn't on iOS I'll just send them the file on Signal since, if the source is my phone in the first place, it's probably not a huge transfer anyway.

They already have a compostable automation api with 3rd party integrations: Shortcuts!

It’s not perfect, but surely you could natural language -> llm -> temporary shortcut script and that gets you a decent part of the way to a smarter Siri

How does SBOM and such account for this? If you’re a package maintainer, do you need to include CI pipeline plugins, their dependencies, going down as far as the pipeline host, in your security-relevant dependencies? Hard problems :/

I can’t remember the example (it was a conference talk a few years ago), but I’m pretty sure there’s LE and DFIR companies who also reverse this stuff and assist in recovery, they just don’t publish the actual flaws exploited to recover the data.