redbird: closeup of me drinking tea, in a friend's kitchen (Default)
[personal profile] redbird
I realized over the weekend that I hadn't checked on those insurance/medical specialist referrals, and when I did check, they were all sitting in MyChart, but hadn't been sent to the insurance company. The insurance chat agent was able to tell me that yes, they need to be in their system, and gave me a fax number to give my GP's office. So I called this morning (yesterday having been a holiday) and asked my doctor's office to do that, urgently, because I'm seeing Dr. Awad tomorrow.

When nothing had happened by midday, Adrian suggested I call the insurance company and ask whether it would be OK if they received the referral after the appointment, on the theory that this probably happens a lot. So I called, and they said yes it would, so I'm going to cross my fingers, and didn't call to reschedule that appointment.

I also finally managed to talk to my Fidelity advisor, and set up a three-way call with him and BNY (where the inherited IRA is). That involved a lot of waiting on hold, and the agent saying he needed to check one more thing.... He then told me that it would take more time for them to figure out where that unexpected balance came from, and they had to figure that out before they could transfer the money. No, I don't know why: the balance information is from their system. So someone is supposed to call me back, hopefully soon, and then I hope they will either transfer the money to Fidelity, or be willing to send me a check for the balance and close the account.

It took me a little while to figure out why I was feeling worn out, but at least part of it is that I made multiple phone calls, and everything is still in process, if not in limbo. A bowl of Lizzy's "chocolate orgy" ice cream helped some.

On top of everything else, my gum is bothering me again ("again" because it's a problem for a day or two, then it's fine for a while, and then recurs).

My office is an office again!

Feb. 18th, 2026 01:02 am
[syndicated profile] seanan_mcguire_feed

Posted by Seanan McGuire

…and I am finding things.

Specifically, I found the remaining hardcover stock of Velveteen vs. The Seasons, the original ISFiC printing of volume three, soon to be rendered obsolete by the release of the second omnibus (which includes volume four). But I have a lot of copies of this book. Like, a lot. So…

If you had wanted one of these limited release books, as a keepsake or a curiosity, or just to save something a little easier to hold than a massive omnibus edition, I am going to try and sell these, for $20 + shipping costs from Seattle. To ask for one, please send an email through the contact form, and we’ll get things sorted out.

Please buy copies of this book. I want them to give me back my office. There are so many. So many…

They’re taking over.

ETA: This offer applies ONLY to Velveteen vs. The Seasons, original ISFiC printing, volume three in the series. I do not have copies of any other volume of the series available for sale, including the omnibus editions. If I did, I would have stated so explicitly.

duskpeterson: The lowercased letters D and P, joined together (Default)
[personal profile] duskpeterson

The Emorian Palace

Entrance to the palace

Do not be offended if you are denied entrance to the Emorian palace. The fact that you have come far enough to be denied that entrance shows that the Emorians' trust in you is high indeed.

The strong manner in which Emor protects its ruler, the Chara, is not evidence that the Chara is weak and frightened. Rather, it is a simple fact that being Chara is the most dangerous job in the Three Lands. Fully four-fifths of the Charas have died before their time, many from assassination. Few Charas live beyond the age of thirty.

(I should explain to any mainlanders who are puzzled at this point that noble peninsulareans have been known to live as long as one hundred years. Even commoner peninsularans often live till they are fifty. If you meet a thirty-year-old, he is not an elder; by peninsularean standards, thirty years old is barely out of one's youth)

Under these circumstances, it is only natural that the Emorians should seek to protect their Chara, giving him the opportunity to live at least long enough to father an heir. By Emorian law, the Chara may not leave his palace, except in wartime. The number of visitors who are allowed past the outer wall of the palace grounds is small. The number of visitors who are allowed past the inner wall of the palace grounds is even smaller. The number of visitors who are allowed inside the palace is very small indeed. And the number of visitors who are allowed inside the East Wing of the palace, where the Chara lives, can be counted without losing your breath.

In practice, this means that the only people who see the Chara are his council, officials from the palace and army, boys who are training to be palace officials, royal messengers, the palace guards, and honored guests, such as ambassadors.

And the servants. Everyone forgets the servants. If you want to see the Chara, I suggest entering into training for high service.


[Translator's note: The perils of living as a Chara can be seen in Empty Dagger Hand.]

The water's depths can't kill me yet

Feb. 17th, 2026 04:44 pm
sovay: (Otachi: Pacific Rim)
[personal profile] sovay
I did not end up accompanying [personal profile] rushthatspeaks and his child to the zoo this morning because I crashed so hard last night that I slept ten to eleven hours and am having difficulty remembering the day of the week, but he just dropped by with a [personal profile] nineweaving in the car and brought me my Christmas present of a sweater in the pattern of the Minoan octopus flask from Palaikastro and the cup with the scale motif from Archanes: it's spectacular. I was able to give him the collected cartoons and comics and poems of Le Guin's Book of Cats (2025). I got to see photographs of Artic and fennec foxes, flamingos and peccaries, sloth and snow leopard, porcupine and poison dart frog. Having spent the prior portion of my afternoon in the excitement of calling doctors and paying bills, my evening's plans involve couch and books.

The Big Idea: Darby McDevitt

Feb. 17th, 2026 04:48 pm
[syndicated profile] scalziwhatever_feed

Posted by Athena Scalzi

The intentions behind one’s actions speaks louder than words ever could. Author Darby McDevitt leads us on a journey through the exploration of intention, desires, and consequences in the Big Idea for his newest novel, The Halter. Take the path he has laid out for you, if you so desire.

DARBY MCDEVITT:

Many years ago I worked for a video game company in Seattle that shoveled out products at a rate of four to six games per year. Most of these were middling titles, commissioned by publishers to fill a narrow market gap and slapped together in six to nine months by teams of a dozen or two crunch-weary developers. We worked hard and fast, with passion and determination, but the end results never quite equaled the ambitions we had.

A common joke around the office, told at the end of every draining development cycle, went like this: “Sure, the game isn’t fun, but the design documents are amazing.” The idea of offering consumers our unrealized blueprints in lieu of a polished game was ridiculous, of course, but it came from a place of real desperation. We wanted our players to know that, despite the poor quality of the final product, we really tried.

The novelist Iris Murdoch has a saying that I repeat often as a mantra, always to guard against future disappointment: “Every book is the wreck of a perfect idea.” Here again is the notion of a Platonic ideal at war with its hazy shadow. How familiar all this is. Experience tells us that people falling short of their ideals is the natural course of life. We never live up to the best of our intentions.

In my new novel, The Halter, I compare this process of “intension erosion” to the more upbeat phenomenon of Desire Lines – footpaths worn over grassy lawns out of an unconscious need for efficiency. Desire lines appear wherever the original constraints of an intentionally designed geographic space don’t conform with the immediate needs of the men and women walking through it. In video games we use a related term – Min-Maxing – the act of looking for ways to put in a minimum amount of effort for maximum benefit. In both cases, the original, ideal use of a space or system is superseded by a desire for efficiency.

In The Halter, these same principles take hold on a grand scale inside an idealized “surrogate reality” metaverse called The Forum, where artists, scientists, and thinkers from all disciplines are invited to probe the deepest and most difficult aspects of human behavior and society. One Forum designer creates a so-called theater to explore the tricky business of language acquisition by sequestering one-hundred virtual babies together with no adult interaction. Another theater offers visitors a perfect digital copy of themselves as a companion, as a therapeutic approach to self-discovery. A third lets visitors don the guise of any other individual on earth so they may literally fulfill the empathetic idiom of “walking a mile in another man’s shoes.”

Noble intentions, arguably – yet in every case, after repeated exposure to actual human users, each theater devolves into something less than the sum of its parts. A prurient playground, or an amusing distraction, or a mindless entertainment. Shortcuts are taken, efficiencies are found, novel-uses imposed. The empathy theater is transformed into a celebrity-fueled bacchanalia; the digital doppelganger becomes a personal punching bag. The baby creche, a zoo. Each and every time, execution falls short of intention. Each theater crumbles, becoming a wreck of its original, perfect idea … and audiences are riveted.

The phenomena described here are common enough that several terms encompass them, each one differentiated for the situation at hand. Desire paths were my first exposure to the concept. The CIA calls it Blowback, when the side effects of a covert operation lead to disastrous results. Unintended Consequences and Knock-On Effects are cozier names, both of which can yield positive or negative results. And a Perverse Incentive is the related idea that the design of a system may be such that it encourages behavior contrary to its intended purpose. Taken together we begin to see the shape of the iceberg that wrecks so many perfect ideas.

I wrote The Halter to explore the highs and lows of these effects, and to shed light from a safe distance on the invisible forces that push and pull constantly at our behavior, often without our knowledge or consent. At one point in the middle of the novel, a collection of idealistic designers, most of whom have given years of their lives to the Forum designing and testing theaters of varying utility, commiserate on what they feel has been a collective failure. Their beloved theaters, they fret, have been co-opted and corrupted by The Forum visitors who have no incentive to behave or play along – they simply show up and engage in the simplest and most efficient way possible. How sad. How crushing. If only these morose designers could share their original design documents….

Their folly, in my view, was to treat their original intentions as merely a point of inspiration and not a goal to be achieved. Their error was to abandon their work in the face of a careless, sleepwalking opposition. The heroic path forward requires vigilance, not surrender, and if an outcome is unexpected, unwarranted, or undesirable, it may be more productive to tweak the inputs than blame the user.

We mustn’t fret that our perfect idea is laying at the bottom of the sea, five fathoms deep. We mustn’t fetishize our design documents – be it a holy book, an artwork, a game, a manifesto, or the U.S. Constitution – because design documents are merely static pleas for unrealized future intentions. They can always be corrupted, upended, misinterpreted. Have faith and patience. The hopeful paths are yet unmade, lying in wait for a thousand shuffling feet to score the way forward.


The Halter: Amazon|Barnes & Noble|Bookshop|Powell’s

Author socials: Website|Bluesky|Facebook

james_davis_nicoll: (Default)
[personal profile] james_davis_nicoll


What hope has 10th century Icelandic culture against an armed and moderately educated 20th century American?

The Man Who Came Early by Poul Anderson

Side-Channel Attacks Against LLMs

Feb. 17th, 2026 12:01 pm
[syndicated profile] bruce_schneier_feed

Posted by Bruce Schneier

Here are three papers describing different side-channel attacks against LLMs.

Remote Timing Attacks on Efficient Language Model Inference“:

Abstract: Scaling up language models has significantly increased their capabilities. But larger models are slower models, and so there is now an extensive body of work (e.g., speculative sampling or parallel decoding) that improves the (average case) efficiency of language model generation. But these techniques introduce data-dependent timing characteristics. We show it is possible to exploit these timing differences to mount a timing attack. By monitoring the (encrypted) network traffic between a victim user and a remote language model, we can learn information about the content of messages by noting when responses are faster or slower. With complete black-box access, on open source systems we show how it is possible to learn the topic of a user’s conversation (e.g., medical advice vs. coding assistance) with 90%+ precision, and on production systems like OpenAI’s ChatGPT and Anthropic’s Claude we can distinguish between specific messages or infer the user’s language. We further show that an active adversary can leverage a boosting attack to recover PII placed in messages (e.g., phone numbers or credit card numbers) for open source systems. We conclude with potential defenses and directions for future work.

When Speculation Spills Secrets: Side Channels via Speculative Decoding in LLMs“:

Abstract: Deployed large language models (LLMs) often rely on speculative decoding, a technique that generates and verifies multiple candidate tokens in parallel, to improve throughput and latency. In this work, we reveal a new side-channel whereby input-dependent patterns of correct and incorrect speculations can be inferred by monitoring per-iteration token counts or packet sizes. In evaluations using research prototypes and production-grade vLLM serving frameworks, we show that an adversary monitoring these patterns can fingerprint user queries (from a set of 50 prompts) with over 75% accuracy across four speculative-decoding schemes at temperature 0.3: REST (100%), LADE (91.6%), BiLD (95.2%), and EAGLE (77.6%). Even at temperature 1.0, accuracy remains far above the 2% random baseline—REST (99.6%), LADE (61.2%), BiLD (63.6%), and EAGLE (24%). We also show the capability of the attacker to leak confidential datastore contents used for prediction at rates exceeding 25 tokens/sec. To defend against these, we propose and evaluate a suite of mitigations, including packet padding and iteration-wise token aggregation.

Whisper Leak: a side-channel attack on Large Language Models“:

Abstract: Large Language Models (LLMs) are increasingly deployed in sensitive domains including healthcare, legal services, and confidential communications, where privacy is paramount. This paper introduces Whisper Leak, a side-channel attack that infers user prompt topics from encrypted LLM traffic by analyzing packet size and timing patterns in streaming responses. Despite TLS encryption protecting content, these metadata patterns leak sufficient information to enable topic classification. We demonstrate the attack across 28 popular LLMs from major providers, achieving near-perfect classification (often >98% AUPRC) and high precision even at extreme class imbalance (10,000:1 noise-to-target ratio). For many models, we achieve 100% precision in identifying sensitive topics like “money laundering” while recovering 5-20% of target conversations. This industry-wide vulnerability poses significant risks for users under network surveillance by ISPs, governments, or local adversaries. We evaluate three mitigation strategies – random padding, token batching, and packet injection – finding that while each reduces attack effectiveness, none provides complete protection. Through responsible disclosure, we have collaborated with providers to implement initial countermeasures. Our findings underscore the need for LLM providers to address metadata leakage as AI systems handle increasingly sensitive information.

New Cover: “But Not Tonight”

Feb. 17th, 2026 02:14 am
[syndicated profile] scalziwhatever_feed

Posted by John Scalzi

I was not expecting to make another cover so soon, so, uh, surprise: A cover of Depeche Mode’s most cheerful song, done as if Erasure decided to crack at it. Why did I do this? Because I was trying to clean up a previous version of this song that I did (it was sonically a little smeary and I hadn’t learned how to edit out when I loudly took in breaths), which necessitated laying down a new vocal track, and once I did that, one thing led to another, and here we are.

I am actually really happy with this one. I did harmonies! Intentionally! Also, I do think it really does sound kinda like Erasure covering Depeche Mode (if such a thing is a possible considering the bands share a Vince Clarke in common). I mean, I don’t sing like Andy Bell, but then, who does, so, fine. Good enough for an afternoon! Enjoy.

— JS

PURL

Feb. 16th, 2026 03:57 pm
oracne: turtle (Default)
[personal profile] oracne
I have learned to purl! I got several rows into "stockinette," alternating garter stitch and purling, until my loops were too tight and I had to start over.

I shall be practicing more!

Go me!
[syndicated profile] scalziwhatever_feed

Posted by Athena Scalzi

If you caught my last two posts over Dozo, Dayton’s premier underground sushi dining experience, then you already know how much I love it. What better way to celebrate the day of love than with Dozo’s special Valentine’s Day 7-course omakase style chef’s menu that offers off-menu selections and limited, intimate seating at the bar so you can watch the chefs work their magic? And trust me, it is indeed magic.

Not only was I extremely excited about the curated sushi menu and brand new sake pairing to go alongside it, but Tender Mercy (the bar that houses Dozo) posted their Valentine’s Day cocktail line-up a few days ago, and it looked incredible, as well.

Long story short, I knew my tastebuds were in for a real treat.

I booked the 8:30pm slot on their first day of offering this menu, which was Tuesday. Getting a later start to dinner than usual only made me that much hungrier for what was to come.

I got to Tender Mercy about twenty minutes early, so I just had a seat at their bar and perused the special cocktail menu:

A small paper menu listing Tender Mercy's Valentine's Day cocktails. There's a detailed border in the corners and two Cupid-esque angels in the top corners. There's four cocktails and one NA cocktail listed.

I love this dessert cocktail menu because whatever your poison is, they’ve got it. A gin drink, a vodka cocktail, even tequila and bourbon. And, of course, a mocktail. They all sounded so delicious but also very rich, and I didn’t want to spoil my appetite with something on the heavier side (like that cheesecake foam, YUM) so I actually opted for the Pillow Princess and asked the bartender to put his spirit of choice in it. He said he recommended Hennessey Cognac (I’m pretty sure it was Hennessy Very Special but I’m just guessing from the brief look I got at the bottle).

I can’t say I’ve had Cognac all that much, but the sweet, almost vanilla-like flavor of the Hennessy worked super well in it.

A small rocks glass with an orange-ish yellow liquid in it with a little bit of a foamy layer on top. There's a metal cocktail pick with raspberries and blueberries on it on top. The drink sits on a black, leather-looking bar and the beautifully lit wood and glass shelves of the bar can be seen in the background.

I’m glad I went with the bartender’s recommendation, he’s truly a pro and has never steered me wrong before so I trust his judgement a hundred percent.

After a few minutes, it was time to get seated in Dozo. There were only six of us total at the bar, a group of three on my right and a couple on my left. Our menu was tucked into our envelope shaped napkin and I briefly surveyed what was going to be served.

A small paper menu labeled

Truly the most eye-catching dish was the wasabi ice cream. Listen, I trust Dozo, but man, did that sound absolutely bonkers. I held strong in my faith, though.

Per usual, I went with the sake pairing, because when else do I get to try so many different expertly curated sakes? Plus, the chef said he tried each of the sake pairings and highly recommended it.

Up first was a spicy salmon onigiri:

A big ol' triangle of onigiri. The rice is more of like a brownish color instead of pure white, with visible flecks of seasoning throughout. It's served on a small square matte black plate.

I wasn’t sure how spicy the salmon would actually end up being, so I had my water on standby. After getting through the warm, soft, perfectly seasoned rice, I was met with a generously portioned salmon filling that wasn’t at all too spicy! This onigiri was hands down the best one I’ve ever had, though I will admit my experience is rather limited in that department. Of course, it’s not everyday I have an onigiri, but this one definitely takes the cake.

For the sake pairing I was served Amabuki’s “I Love Sushi” Junmai. Obviously, this is a fantastic name for a sake. It says all you need to know about it right in the name, plain and simple. Jokes aside, this was a perfectly fine sake. With a dry, crisp flavor, it didn’t really stand out to me much but paired well with the umami flavor of the onigiri.

Off to a great start (I expected no less), the second course was looking mighty fine:

Three pieces of nigiri in a row on a rectangular matte black plate.

From left to right, we have hamachi (yellowtail), hirame (flounder), and skipjack tuna. The hamachi’s wasabi sauce packed a ton of great wasabi flavor without painfully clearing my sinuses. It had just the right amount of strength, a very balanced piece. The flounder was exceptionally tender with a melt-in-your-mouth texture. The skipjack has always been a tried and true classic in my previous Dozo experiences, and today’s serving of it was no different. All around a total winner of a course, with tender, umami packed pieces.

To accompany this course, I was served Takatenjin “Soul of the Sensei,” which is a Junmai Daiginjo. This sake is made with Yamadanishiki, which is considered to be the king of sake rice. “Soul of the Sensei” was created as a tribute to revered sake brewer Hase Toji. Much like the first sake we were served, it was crisp with a slight dryness, pairing well with the fresh fish and savory flavors. It had just a touch of melon.

Up next was this smaller course with a piece of chu toro and a piece of smoked hotate:

Two pieces of nigiri on a small round black plate, one piece a dark pink fatty tuna and the other an orangeish beige colored piece of smoked scallop.

Both pieces looked stunning and fresh. The chef explained that chu toro is the fatty belly meat of the tuna, which is a more prized and delicious cut, a real treat. Indeed, it was very buttery and had a rich mouthfeel. I didn’t know what hotate was, but it turns out it’s a scallop, and I think they mentioned something about hotate scallops come from a specific region in Japan, but I might be misremembering. Anyways, I love scallops, but I’ve definitely never had one that’s been smoked before. It was fun to watch the chef smoke all of the pieces before dishing them out.

Oh my goodness this piece was incredible. It had a luscious texture and complex, beautifully smokiness that didn’t detract from the flavor of the scallop. It was a masterfully smoked piece of high quality, fresh scallop. Remarkable piece! Great course all around.

Instead of sake for this course, we were served a shot of Suntory Whiskey. but I have no idea which type specifically. Maybe the Toki? But also very well could’ve been the Hibiki Harmony because the shot was definitely a dark, ambery color. I wish I had a palate for whiskey, especially premium Japanese whiskey that the kitchen so generously gifted upon each guest, but truthfully it was a tough couple of sips for me. Like fire in my throat, that shit put some damn hair on my chest. Super grateful for the lovely whiskey, but sheesh it definitely burned. The chefs actually took the shot with us, how fun!

Fear not, there was some lovely mushroom and yuzu ramen on the way to ease the pain:

A beautiful stoneware bowl filled with ramen noodles and a lovely broth, garnished with small green onion pieces.

This ramen is actually vegetarian, made with umami-packed mushrooms and bright yuzu citrus. The green onions and drops of chili oil drizzled on top added a fantastic balance of flavors for a well-rounded, hearty, warm bowl of delicious ramen that was good to the last drop. I wish they had ramen more often, it was so great to sip on some warm broth while it was below freezing outside. I absolutely loved the stoneware bowl it was served in, I would love to have something like that in my own kitchen.

For the sake, this one was truly special. Hana Makgeolli “MAQ8 Silkysonic.” Look how CUTE these cans are! These adorable single-serve cans contain a fun, slightly bubbly, just-a-touch-sweet sake that was a great addition to the night’s line-up. It’s a bit lower alcohol content than some other sakes at 8%, making it so you can enjoy more than one can of this bubbly goodness if you so desired.

I was definitely pretty full by this point, but I powered on for this next course consisting of some torched sake, unagi, and suzuki.

Three pieces of nigiri lined up on a black rectangular matte plate.

It was a little confusing with the first piece of fish in this lineup being called sake, since I assumed sake was just the drink we all know and love, but sake is actually also salmon. It was fun to watch the chefs use a blowtorch to torch the salmon, as any course involving fire is a great course. The salmon had a sauce on top that I hate to say I can’t remember what exactly it was. I know, I had one job! I should’ve taken better notes, but there was so much going on between being served the sake and explained the specifics of that plus the chefs explaining the whole course, plus the couple next to me conversing with me (we had lovely conversations). It was a lot, okay! Sauce aside, the salmon was excellent and beautifully torched.

For the unagi, I actually love eel, so I knew this piece was about to be bomb. With the sweet, thick glaze on top and fresh slice of jalapeno, this piece was loaded with deliciousness. I was worried the jalapeno slice would bring too much heat to the dish for me, but it was perfect and not hot at all, just had great flavor.

The final piece, suzuki, is Japanese sea bass. There is a small pickled red onion sliver on top, it is not a worm, to be clear. Apparently the Japanese sea bass is known by different names depending on how mature the fish is, suzuki being the most grown stage of the fish. This piece was very simply dressed and the tender fish spoke for itself.

The sake for this course was Tentaka’s “Hawk in the Heavens” Tokubetsu Junmai. Much like with the food of this course, I should have taken better notes, because I don’t remember this sake at all. I don’t remember what it tasted like, my thoughts on it, nothing. I didn’t even remember the name until I looked at the menu again. I am so sorry, it is truly only because it was the sixth course and I had just taken a shot and was busy talking! Forgive me and we shall move on.

For our last savory course, it was two pieces of the chef’s choice:

Two pieces of nigiri, one being fish and one being wagyu.

The chefs said in honor of it being Valentine’s Day, they wanted to give us a bit more of a lux piece, and opted for wagyu and torched toro. Sending off the savory courses with wagyu was truly a delight, it really provided the turf in “surf and turf.” Every time I’ve had wagyu from Dozo it’s been so tender and rich, the fat just melting in my mouth. It’s also a fun novelty since I don’t really have wagyu anywhere else.

Finally, it was time for dessert. I couldn’t wait to try the wasabi ice cream:

A small glass coupe shaped bowl holding the wasabi ice cream. There's crushed wasabi peas on top.

I would’ve never imagined that wasabi ice cream could be even remotely edible, let alone enjoyable, but oh my gosh. Oh my gosh. How was this so good?! The creaminess contrasting with the crunchy wasabi peas, the perfect amount of sweetness mixing with the distinct flavor of the wasabi, LORD! It was incredibly, bizarrely delicious. The wasabi didn’t have that sinus-clearing bite to it, yet retained its unmistakable palate. What a treat.

For the final sake, I was served Kiuchi Brewery’s “Awashizuki” Sparkling Sake. I was particularly excited for this one because I love sparkling sakes, they are undoubtedly my favorite category of sake. Anything with bubbles is just better! I will say that the Awashizuki seemed to be much more lowkey on the bubbles than some other sparkling sakes I’ve had before. The bubbles were a bit more sparse and toned down, but it was still lightly carbonated enough that you could tell it wasn’t still. It was sweeter and more refreshing than the others in the evening’s lineup, which makes sense since it was the dessert course pairing. I really liked this one!

All in all, I had yet another fantastic experience at Dozo, and I absolutely loved their Valentine’s Day lineup. The limited seating at the bar made it feel all the more exclusive and special, and every course was totally delish. I got to try lots of new sakes and have really nice chats with the people next to me, and really just had a great evening all around.

The ticket for this event was $95, after an added 18% gratuity and taxes, it was more like $125. The sake pairing was $50 and I also tipped the waitress that was pouring the pairings and telling me about them. It was definitely a bit of a splurge event but hey, it was for V-Day! Gotta treat yourself. And I’m so glad I did!

Which piece of fish looks the most enticing to you? Or perhaps the ramen is more your speed? Have you tried any of the sakes from the lineup? Let me know in the comments, and have a great day!

-AMS

The Promptware Kill Chain

Feb. 16th, 2026 12:04 pm
[syndicated profile] bruce_schneier_feed

Posted by Bruce Schneier

The promptware kill chain: initial access, privilege escalation, reconnaissance, persistence, command & control, lateral movement, action on objective

Attacks against modern generative artificial intelligence (AI) large language models (LLMs) pose a real threat. Yet discussions around these attacks and their potential defenses are dangerously myopic. The dominant narrative focuses on “prompt injection,” a set of techniques to embed instructions into inputs to LLM intended to perform malicious activity. This term suggests a simple, singular vulnerability. This framing obscures a more complex and dangerous reality. Attacks on LLM-based systems have evolved into a distinct class of malware execution mechanisms, which we term “promptware.” In a new paper, we, the authors, propose a structured seven-step “promptware kill chain” to provide policymakers and security practitioners with the necessary vocabulary and framework to address the escalating AI threat landscape.

In our model, the promptware kill chain begins with Initial Access. This is where the malicious payload enters the AI system. This can happen directly, where an attacker types a malicious prompt into the LLM application, or, far more insidiously, through “indirect prompt injection.” In the indirect attack, the adversary embeds malicious instructions in content that the LLM retrieves (obtains in inference time), such as a web page, an email, or a shared document. As LLMs become multimodal (capable of processing various input types beyond text), this vector expands even further; malicious instructions can now be hidden inside an image or audio file, waiting to be processed by a vision-language model.

The fundamental issue lies in the architecture of LLMs themselves. Unlike traditional computing systems that strictly separate executable code from user data, LLMs process all input—whether it is a system command, a user’s email, or a retrieved document—as a single, undifferentiated sequence of tokens. There is no architectural boundary to enforce a distinction between trusted instructions and untrusted data. Consequently, a malicious instruction embedded in a seemingly harmless document is processed with the same authority as a system command.

But prompt injection is only the Initial Access step in a sophisticated, multistage operation that mirrors traditional malware campaigns such as Stuxnet or NotPetya.

Once the malicious instructions are inside material incorporated into the AI’s learning, the attack transitions to Privilege Escalation, often referred to as “jailbreaking.” In this phase, the attacker circumvents the safety training and policy guardrails that vendors such as OpenAI or Google have built into their models. Through techniques analogous to social engineering—convincing the model to adopt a persona that ignores rules—to sophisticated adversarial suffixes in the prompt or data, the promptware tricks the model into performing actions it would normally refuse. This is akin to an attacker escalating from a standard user account to administrator privileges in a traditional cyberattack; it unlocks the full capability of the underlying model for malicious use.

Following privilege escalation comes Reconnaissance. Here, the attack manipulates the LLM to reveal information about its assets, connected services, and capabilities. This allows the attack to advance autonomously down the kill chain without alerting the victim. Unlike reconnaissance in classical malware, which is performed typically before the initial access, promptware reconnaissance occurs after the initial access and jailbreaking components have already succeeded. Its effectiveness relies entirely on the victim model’s ability to reason over its context, and inadvertently turns that reasoning to the attacker’s advantage.

Fourth: the Persistence phase. A transient attack that disappears after one interaction with the LLM application is a nuisance; a persistent one compromises the LLM application for good. Through a variety of mechanisms, promptware embeds itself into the long-term memory of an AI agent or poisons the databases the agent relies on. For instance, a worm could infect a user’s email archive so that every time the AI summarizes past emails, the malicious code is re-executed.

The Command-and-Control (C2) stage relies on the established persistence and dynamic fetching of commands by the LLM application in inference time from the internet. While not strictly required to advance the kill chain, this stage enables the promptware to evolve from a static threat with fixed goals and scheme determined at injection time into a controllable trojan whose behavior can be modified by an attacker.

The sixth stage, Lateral Movement, is where the attack spreads from the initial victim to other users, devices, or systems. In the rush to give AI agents access to our emails, calendars, and enterprise platforms, we create highways for malware propagation. In a “self-replicating” attack, an infected email assistant is tricked into forwarding the malicious payload to all contacts, spreading the infection like a computer virus. In other cases, an attack might pivot from a calendar invite to controlling smart home devices or exfiltrating data from a connected web browser. The interconnectedness that makes these agents useful is precisely what makes them vulnerable to a cascading failure.

Finally, the kill chain concludes with Actions on Objective. The goal of promptware is not just to make a chatbot say something offensive; it is often to achieve tangible malicious outcomes through data exfiltration, financial fraud, or even physical world impact. There are examples of AI agents being manipulated into selling cars for a single dollar or transferring cryptocurrency to an attacker’s wallet. Most alarmingly, agents with coding capabilities can be tricked into executing arbitrary code, granting the attacker total control over the AI’s underlying system. The outcome of this stage determines the type of malware executed by promptware, including infostealer, spyware, and cryptostealer, among others.

The kill chain was already demonstrated. For example, in the research “Invitation Is All You Need,” attackers achieved initial access by embedding a malicious prompt in the title of a Google Calendar invitation. The prompt then leveraged an advanced technique known as delayed tool invocation to coerce the LLM into executing the injected instructions. Because the prompt was embedded in a Google Calendar artifact, it persisted in the long-term memory of the user’s workspace. Lateral movement occurred when the prompt instructed the Google Assistant to launch the Zoom application, and the final objective involved covertly livestreaming video of the unsuspecting user who had merely asked about their upcoming meetings. C2 and reconnaissance weren’t demonstrated in this attack.

Similarly, the “Here Comes the AI Worm” research demonstrated another end-to-end realization of the kill chain. In this case, initial access was achieved via a prompt injected into an email sent to the victim. The prompt employed a role-playing technique to compel the LLM to follow the attacker’s instructions. Since the prompt was embedded in an email, it likewise persisted in the long-term memory of the user’s workspace. The injected prompt instructed the LLM to replicate itself and exfiltrate sensitive user data, leading to off-device lateral movement when the email assistant was later asked to draft new emails. These emails, containing sensitive information, were subsequently sent by the user to additional recipients, resulting in the infection of new clients and a sublinear propagation of the attack. C2 and reconnaissance weren’t demonstrated in this attack.

The promptware kill chain gives us a framework for understanding these and similar attacks; the paper characterizes dozens of them. Prompt injection isn’t something we can fix in current LLM technology. Instead, we need an in-depth defensive strategy that assumes initial access will occur and focuses on breaking the chain at subsequent steps, including by limiting privilege escalation, constraining reconnaissance, preventing persistence, disrupting C2, and restricting the actions an agent is permitted to take. By understanding promptware as a complex, multistage malware campaign, we can shift from reactive patching to systematic risk management, securing the critical systems we are so eager to build.

This essay was written with Oleg Brodt, Elad Feldman and Ben Nassi, and originally appeared in Lawfare.

Bundle of Holding: Downcrawl-Skycrawl

Feb. 16th, 2026 02:07 pm
james_davis_nicoll: (Default)
[personal profile] james_davis_nicoll


Downcrawl and Skycrawl, twin toolkits from designer Aaron A. Reed that help you create spontaneous tabletop roleplaying adventures in the Deep, Deep Down and the Azure Etern.

Bundle of Holding: Downcrawl-Skycrawl
[syndicated profile] strangehorizons_feed

Posted by Dawn Macdonald

Into The Sun coverCharles Ferdinand Ramuz is the most important twentieth-century Franco-Swiss writer you’ve never heard of. Ramuz (pronounced “raw mew”) was born in 1878 in Lausanne, making him a contemporary of writers like Thomas Mann and James Joyce. His apocalyptic novel Présence de la mort, originally published in French in 1922, appeared in English translation in 1948 under the title The End of All Men and has been newly retranslated by Olivia Baes and Emma Ramadan as Into the Sun. The stylistic simplicity of this short, 140-page book belies its subtlety and its strangeness. The publisher of this re-translation has billed it as a “frighteningly prescient climate-disaster novel,” but the themes are not specific to cli-fi; it’s about individual and societal breakdown in the face of any existential threat.

The set-up given in the first two-page chapter is this: “Because of an accident within the gravitational system, the Earth is rapidly plunging into the sun, pelting toward it, to melt there.” How did this accident occur? No idea. Is there anything we can do to stop it? No. Can we escape to, say, some other planet? The question doesn’t even come up. This is not about climate change mitigation, adaptation, or technological solutionism. It is about the mind faced with certain death. Of course, we are all already faced with certain death. “Because one does not come without the other,” the narrator reminds us. “Life had an intimate sister. You didn’t marry one or the other, you married both.” Death and life, inseparable twins.

At first, people in the book barely react to the news of their impending doom. A few words printed in the newspaper: What can they have to do with real life? One woman in the small village where the story opens, seeing the headlines, says, “What do I care?” We were all going to die anyway; the only difference is that now we will die together instead of separately. The lackadaisical attitude of the villagers is not sustained indefinitely. Soon the signs of unrest appear—there are guards stationed outside the bank in town; strange noises are heard at night; mobs begin to form. Money cannot continue to mean anything, and then no one owns anything, and then violence is the medium of exchange. But it’s gradual, and even this is not the point of the story. To be honest, there isn’t really a story. There is more of a slow unwinding which, as it unspools in the maddening sun, reveals what was inside of everything all along.

If Into the Sun does not really have a plot, neither does it really have characters. The narrative voice flexes between first-person, third-person, and even occasional second-person invocations. Ramuz is fond of the French third-person impersonal pronoun “on,” which the translators have rendered as the English first-person plural “we.” Similarly, the authorial “I” does not necessarily designate a specific individual, but rather an Everyman who serves as an observer at a range of shifting scenes. According to his biographical entry in the Dictionnaire Historique de la Suisse, Ramuz had by this point in his career abandoned expository narrative (“roman explicatif”), which follows the exploits of an individual, in favor of a more “epic” style exploring the response of an entire community to a serious challenge or threat. He was writing about war, disease, and the existence of evil, but also about religious miracles and healing (see La guérison des maladies, 1917). At the same time, he was dedicated to delineating the rhythms and voices of people of the countryside. The translators’ note at the end of the present edition of Into the Sun quotes him imploring the reader to think of the “shuffling step of the person who returns from harvesting or pruning his vineyard: consider this gait and the fact that our sentences don’t have it.”

Ramuz’s efforts to remake the novel as a new form true to the inner life of ordinary people places him within a strand of Modernism. The 1920s was, in the West, a period of disillusionment following what was then still called in English the “Great War,” which was in turn accompanied by a devastating pandemic in 1918. The 1920s might be remembered now as a non-stop party filled with carefree flappers and hot jazz, but much literature of the era depicts a troubled milieu of dissipation, cynicism, and apathy. Quite a few classics of apocalyptic and dystopian fiction appeared around this time, including Yevgeny Zamyatin’s We (1924), Karel Čapek’s stage play R.U.R.: Rossum’s Universal Robots (1920) and his novel The Absolute at Large (1922), and W.E.B. Du Bois’s short story “The Comet” (1920). The end-times had, perhaps, been narrowly averted, and could still be just around the corner. If any of this sounds like right now, well, yes, it does and it should.

In this translation, Ramuz’s sentences have the beauty of a beam of sunlight through swirling dust—simple, elegant, illuminating the structure of the invisible. Repeatedly he invokes a mirrored world, in which constructions partner natural objects, and the mind reconstitutes reality in its own image. A streetlight resembles the moon, it “looks like the real moon when bad weather is coming. And so we search for the real moon, and after a moment we’ve found it, over there, behind the rooftops, behind the chestnut trees, still so low in the sky and not any smaller than the other moon, but pale, so pale and immobile, as if painted as decoration in the sky with a brush.”

The sky is a backdrop; the landscape is a canvas; the moon is a bit of trompe-l’oeil; stars are paper lanterns. The world is a human world. “Our own world is so small,” explains Ramuz. “Our own world goes as far as our eyes can reach; it’s our eyes that create it for us.” To grasp the enormity of the coming disaster, “We would have to imagine the sky, the stars, the continents, the oceans, the equator, the two poles. Yet we can only imagine the self and what we have.”

As the destruction gets underway, the first-person narrator laments that he “loved the world too much. When I sought to imagine something beyond it, it was still the world that I imagined. When I sought to go past it, there I found it again. I tried closing my eyes to see the heavens; it was the Earth; and the heavens were the heavens only when they became Earth once again.”

Towards the end, when few people remain alive to experience themselves in isolation, a solitary pilot ascends with his plane in search of some respite from the heat. Failing, he begins his descent, and hearing the roar of the plane’s engine he finds that the “noise that he alone makes irritates and astonishes him. He seeks a response in this noise; he seeks an answer to himself from himself. He doubts that he exists, not perceiving any existence but his own anywhere. He considers himself angrily; he is a disruption. And he keeps descending, in pursuit of a resemblence and something like symmetry.”

One of the many symmetries in the text is provided by a lake, which appears in the first pages as a site of relaxation and pleasure, later as a refuge from increasing heat, and ultimately as a locus of death. A lake implies the symmetry of reflection, but by the time the unnamed pilot approaches it in his aircraft these qualities have eroded. “This expanse presented to him the absolute wasteland of its waters, motionless as metal, perfectly silent and fixed, bare, with no reflection, no image, no response.” The world has ceased to function as a mirror for humanity. Once the mirror is broken, could there be another, more real and primal perception that arises only in the face of death? To fall into the Sun is to come too close to the source, where our matchstick houses and stick-built hypotheses will burn away. The collapsing roofs of a town begin to look, from above, like a mud pie that a child has left to fissure in the heat. Our works were those of children and playtime is over. Now is time for a new world, an impossible world, a place we cannot live.


New Cover Song: “These Days”

Feb. 16th, 2026 12:10 am
[syndicated profile] scalziwhatever_feed

Posted by John Scalzi

I moved my home music studio up from the basement to Athena’s old bedroom in the last couple of weeks, so now it’s time to put it to use, and for my first bit of music in the new space, I decided to record an old tune: “These Days” by Jackson Browne, first released in 1973.

Having said that, this arrangement is rather more like the 1990 cover version by 10,000 Maniacs, which was the first version of the song I ever heard. I originally tried singing it in the key that Natalie Merchant sang it in, and — surprise! — I was having a rough time of it. Then I dropped it from G to C and suddenly it was in my range.

I’m not pretending my singing voice is a patch on either Ms. Merchant or Mr. Browne, but then, that’s not why I make these covers. Enjoy.

— JS

(no subject)

Feb. 15th, 2026 06:17 pm
skygiants: the aunts from Pushing Daisies reading and sipping wine on a couch (wine and books)
[personal profile] skygiants
I never got around to writing up Anne McCaffrey's The Mark of Merlin when I read it last year, but I've been thinking about McCaffrey a lot recently due to blitzing through the Dragons Made Me Did It Pern podcast (highly recommended btw) and [personal profile] osprey_archer asked for a post on my last-year-end round-up so now seems as good a time as any.

The important thing to know about The Mark of Merlin is that -- unlike many of the things I've read recently! -- it is not, in any way, the least little bit, Arthuriana. They are not in Great Britain. There are no thematic Arthurian connections. There is absolutely zero hint of anything magical. So why Merlin? Well, Merlin is the name of the heroine's dog, and he's a very good boy, so that's all that really needs to be said about that.

Anyway, this is McCaffrey writing in classic romantic suspense mode a la Mary Stewart or Barbara Michaels, and honestly it's a pretty fun time! Our Heroine Carla's father Tragically Died in the War, so he asked his second-in-command to be her guardian and now she's en route to stay with Major Laird in his isolated house in Cape Cod. Tragically scarred and war-traumatized Major Laird has no Gothic-trope concerns about this because Carla's full name is Carlysle and her dad accidentally forgot to tell him that the child in question was a daughter and not a son; Carla is fully aware of the mixup and but has not chosen to enlighten him because she thinks it's extremely funny to pop out at Major Laird like "ha ha! You THOUGHT I was a hapless youth and wrote me a patronizing letter about it, but INSTEAD I am a beautiful and plucky young co-ed so joke's on you!"

There is an actual suspense plot; the suspense plot is that Someone is hunting Carla for reasons of secret information her dad passed on in his luggage before he died, and also his death was under Mysterious Circumstances, and so we have to figure out what's going on with all of that and eventually have a big confrontation in the remote Cape Cod house. But mostly the book is just Carla and the Major being snowed in, romantically bickering, huddling for warmth, cooking delicious meals over the old Cape Cod stove, etc. etc. Cozy in the classic sense, very little substance but excellent for reading in a vacation cottage while drinking tea and eating a cheese toastie.

As a sidenote, I did not know until I started listening to Dragons Made Me Do It that McCaffrey's Dragonflight preceded The Flame and the Flower, the book that's credited as being the first bodice-ripper romance novel and launching the genre of historical romance as we know it today, by a good four years. It's interesting to place this very classic romantic suspense novel -- which was published almost a decade after Dragonflight, but, at least according to this Harvard student newspaper article I turned up, at least partially written in 1950 -- against the full tropetastic dubcon-at-best dragonsex Pern situations, which clearly belong to a later moment. And speaking of later moments, it's also a bit of a mindfuck for me to think very hard about McCaffrey's place in genre history and realize how very early she is. I was reading McCaffrey in the nineties, against Lackey and Bujold. Reading her in conversation with Russ and LeGuin is a whole different experience.

But this is all a tangent and not very much to do with The Mark of Merlin, a perfectly fun perfectly fine book, very short on the wtf moments that have characterized most of my experiences with McCaffrey, and if anything comes late to its moment rather than early.
sovay: (Haruspex: Autumn War)
[personal profile] sovay
I have not slept in two nights as opposed to brief random hours elsewhere on the clock, but the sunlight this afternoon was gorgeous.

I'm a little hungover and I may have to steal your soul. )

Like just about the rest of this weekend, any plans I had to attend even part of this year's sci-fi marathon at the Somerville did not survive contact with my stamina. Hestia has now broken four slats out of my blinds for a better view on Bird Theater and having tired herself out chattering at their delicious players sleeps innocently against my mermaid lamp, softly and a little snufflily breathing out a purr.

The Demolished Man by Alfred Bester

Feb. 15th, 2026 07:12 am
james_davis_nicoll: (Default)
[personal profile] james_davis_nicoll


Ben Reich plans a perfect murder in a world where getting away with murder is impossible.

The Demolished Man by Alfred Bester
sovay: (Viktor & Mordecai)
[personal profile] sovay
I spent the first half of Valentine's Day unromantically fulfilling some medical errands and then trying to sleep off a migraine, but in the evening I made keyn-ahora plans with [personal profile] rushthatspeaks and [personal profile] spatch and I ordered an accidentally four-person quantity of dinner from Chivo and watched Tales of the Tinkerdee (1962), an early fractured fairy tale of a Muppet curio whose relentlessly older-than-vaudeville gags we frequently missed from still laughing at a line about three jokes earlier. "A solid ruby gold-panning inlaid electric-fried antique!" After that I fell asleep on the couch.
[syndicated profile] scalziwhatever_feed

Posted by John Scalzi

Because it feels like a good time to do it, some current thoughts on “AI” and where it, we and I are about the thing, midway through February 2026. These are thoughts in no particular order. Some of them I’ve noted before, but will note again here mostly for convenience. Here we go:

1. I don’t and won’t use “AI” in the text of any of my published work. There are several reasons for this, including the fact that “AI”-generated text is not copyrightable and I don’t want any issues of ownership clouding my work, and the simple fact that my book contracts oblige me to write everything in those books by myself, without farming it out to either ghostwriters or “AI.” But mostly, it’s because I write better than “AI” can or ever will, and I can do it with far less energy draw. I don’t need to destroy a watershed to write a novel. I can write a novel with Coke Zero and snacks. Using “AI” in my writing would create more work for me, not less, and I really have lived my life with the idea of doing the least amount of work possible.

If you’re reading a John Scalzi book, it all came out of my brain, plain and simple. Better for you! Easier for me!

2. I’m not worried about “AI” replacing me as a novelist. Sure, someone can now prompt a novel-length work out of “AI” faster than I or any other human can write a book, and yes, people are doing just that, pumping into Kindle Unlimited and other such places a vast substrate of “AI” text slop generated faster than anyone could read it. Nearly all of it will sit there, unread, until the heat death of the universe.

Now, you might say that’s because why would anyone read something that no one actually took any effort to write, and that will be maybe about 5% of the reason. The other 95% of the reason, however, will be discoverability. Are the people pumping out the wide sea of “AI” text slop planning to make the spend for anyone to find that work? What are their marketing plans other than “toss it out, see who locates it by chance”? And if there is a marketing budget, if you can generate dozens or hundreds of “AI” text slop tomes in a year, how do you choose which to highlight? And will the purveyors of such text slop acknowledge that the work they’re promoting was written by no one?

(Answer: No. No they won’t).

I am not worried about being replaced as a novelist because I already exist as a successful author, and my publishers are contractually obliged to market my novels every time they come out. This will be the case for a while, since I have a long damn contract. Readers will know when my new books are out, and they will be able to find them in bookstores, be they physical or virtual. This is a huge advantage over any “AI” text slop that might be churned out. And while I don’t want to overstate the amount of publicity/marketing traditional publishers will do for their debut or remaining mid-list authors, they will do at least some, and that visibility is an advantage that “AI” text slop won’t have. Even indie authors, who must rely on themselves instead of a publicity department to get the word out about their work, have something “AI” text slop will never have: They actually fucking care about their own work, and want other people to see it.

I do understand it’s more than mildly depressing to think that a major market difference between “AI” text slop and stuff actual people wrote is marketing, but: Welcome to capitalism! It’s not the only difference, obviously. But it is a big one. And one that is likely to persist, because:

3. People in general are burning out on “AI.” Not just in creative stuff: Microsoft recently finally admitted that no one likes its attempt to shove its “AI” Copilot into absolutely everything, whether it needs to be there or not, and is making adjustments to its businesses to reflect that. “AI” as a consumer-facing entity rarely does what it does, better than the programs and apps it is replacing (see: Google’s Gemini replacing Google Assistant), and sucks up far more energy and resources. Is your electric bill higher recently? Has the cost of a computer gone up because suddenly memory prices have doubled (or more)? You have “AI” to thank for that. It’s the solution to a problem that not only did no one actually have, but wasn’t a problem in the first place. There are other issues with “AI” larger than this — mostly that it’s a tool to capture capital at the expense of labor — but I’m going to leave those aside for now to focus on the public exhaustion and dissatisfaction with “AI” as a product category.

In this sort of environment, human-generated work has a competitive advantage, because people see it as more authentic and real (which it is, to the extent that “authentic” and “real” mean “a product of an actual human brain”), and more likely to have the ability to surprise and engage the people who encounter it. I don’t want to oversell this — humans are still as capable of creating lazy, uninspired junk as they ever were, and some people really do think of their entertainment as bulk purchases. Those vaguely sad people will be happy that “AI” gives them more, even if it’s of lesser quality. But I do think in general when people are given a choice, that they will generally prefer to give their time and money to the output of an actual human making an effort, than to the product of a belching drain on the planet’s resources whose use primarily benefits people who are already billionaires dozens of times over. Call me optimistic.

Certainly that’s the case with me:

4. I’m supporting human artists, including as they relate to my own work. I’ve noted before that I have it as a contractual point that my book covers, translations and copyediting have to be done by humans. This is again both a practical issue (re: copyrights, quality of work, etc) and a moral one, but also, look, I like that my work pays other humans, and I want that to continue. Also, in my personal life, I’m going to pay artists for stuff. When I buy art, I’m going to buy from people who created it, not generated it out of a prompt. I’m not going to knowingly post or promote anything that is not human-created. Just as I wish to be supported by others, I am going to support other artists. There is no downside to not promoting/paying for “AI” generated work, since there was no one who created it. There is an upside to promoting and paying humans. They need to eat and pay rent.

“But what if they use AI?” In the case of the people working on my own stuff, it’s understood that the final product, the stuff that goes into my book, is the result of their own efforts. As for everything else, well, I assume most artists are pretty much like me: using “AI” for their primary line of creativity is just introducing more work, not less. Also I’m going to trust other creators; if they tell me they’re not using “AI” in their finished work then I’m going to believe them in the absence of a compelling reason not to. I don’t particularly have the time or interest in being the “AI” police. Anyway, if they’re misrepresenting their work product, that eventually gets found out. Ask a plagiarist about that.

With all that said:

5. “AI” is Probably Sticking Around In Some Form. This is not an “‘AI’ Is Inevitable and Will Take Over the World” statement, since as noted above people are getting sick of it being aggressively shoved at them, and also there are indications that a) “this is the worst it will ever be” is not true of AI, as people actively note that recent versions of ChatGPT were worse to use than earlier versions, b) investors are getting to the point of wanting to see an actual return on their investments, which is the cue for the economic bubble around AI to pop. This going to be just great for the economy. “AI,” as the current economic and cultural phenomenon, is likely to be heading for a fall.

Once all that drama is done and we’ve sorted through the damage, the backend of “AI” and its various capabilities will still be around, either relabeled or as is, just demoted from being the center of the tech universe and people making such a big deal about it, scaled down and hopefully more efficient. I understand that the “AI will probably persist” position is not a popular one in the creative circles in which I exist, and that people hope it vaporizes entirely, like NFTs and blockchains. I do have to admit I wouldn’t mind being wrong about this. But as a matter of capital investment and corporate integration, NFTs, etc are a blip compared to what’s been invested in “AI” overall, and how deep its use has sunk into modern capitalism (more on that in a bit).

Another reason I think “AI” is likely to stick around in some form:

6. “AI” is a marketing term, not a technical one, and encompasses different technologies. The version that the creative class gets (rightly) worked up about is generative “AI,” the most well-known versions of which were trained on vast databases of work, much of which was and is copyrighted and not compensated for. This is, however, only one subset of a larger group of computational systems which are also called “AI,” because it’s a sexy term that even non-nerds have heard of before, and far less confusing than, say, “neural networks” or such. Not all “AI” is as ethically compromised as large-scale generative “AI,” and a lot of it existed and was being used non-controversially before generative “AI” blew up as the wide-scale rights disaster it turned out to be.

It’s possible that “AI” as a term is going to be forever tainted as a moral hazard, disliked by the public and seen as a promotions drag by marketing departments. If and when that happens, a lot of things currently hustled under the “AI” umbrella will be quietly removed from it, either returning to previous, non-controversial labels or given new labels entirely. Lots of “AI” will still be around, just no one will call it that, and outside of obvious generative “AI” that presents rights issues, fewer people will care.

On the matter of generative “AI,” here’s a thought:

7. There were and are ethical ways to have trained generative “AI” but because they weren’t done, the entire field is suspect. Generative “AI” could easily have been trained solely on material in the public domain and/or on appropriately-licensed Creative Commons material, and an opt-in licensing gateway to acquire and pay for copyrighted work used in training, built and used jointly by the companies needing training data, could have happened. This was all a solvable problem! But OpenAI, Anthropic, et al decided to train first, ask forgiveness later, on the idea that would be cheaper simply to do it first and to litigate later. I’m not entirely sure this will turn out to be true, but it is possible that at this late stage, some of the companies will go under before any settlements can be achieved, which will have the same effect.

There are companies who have chosen to train their generative models with compensation; I know of music software companies that make a point of showing how artists they worked were both paid for creating samples and other material, and get paid royalties when work generated from those samples, etc is made by people using the software. I think that’s fine! As long as everyone involved is happy with the arrangement, no harm, and no foul. But absent of that sort of clear and unambiguous declaration of provenance and compensation regarding training data, one has to assume that any generative “AI” has used stolen work. It’s so widely pervasive at this point that this has to be a foundational assumption.

And here is a complication:

8. The various processes lumped into “AI” are likely to be integrated into programs and applications that are in business and creative workflows. One, because they already were prior to “AI” being the widely-used rubric, and two, because these companies need to justify their investments somehow. Some of these systems and processes aren’t tainted by the issues of “generative AI” but many of them are, including some that weren’t previously. When I erase a blotch in an image with Photoshop, the process may or may not use Generative AI and when it does, it may or may not use Adobe’s Firefly model (which Adobe maintains, questionably, is trained only on material it has licensed).

Well, don’t use Photoshop, I hear you say. Which, okay, but I have some bad news for you: Nearly every photoediting suite at this point incorporates “AI” at some point in its workflow, so it’s six of one and half dozen of the other. And while I am a mere amateur when it comes to photos, lots of professional photographers use Adobe products in their workflow, either because they’ve been using it for years and don’t want to train on new software (which, again, probably has “AI” in its workflow), or they’re required to use it by their clients because it’s the “industry standard.” A program being the “industry standard” is one reason I use Microsoft Word, and now that program is riddled with “AI.” At a certain point, if you are using 21st century computer-based tools, you are using “AI” of some sort, whether you want to or not. Some of it you can turn off or opt out of. Some of it you can’t.

(Let’s not even talk about my Google Pixel Phone, which is now so entirely festooned with “AI” that it’s probably best to think of it as an “AI” computer with a phone app, than the other way around.)

This is why earlier in this piece, I talk about the “final product” being “AI”-free — because it’s almost impossible at this point to avoid “AI” in computer-based tools, even if one wants to. Also, given the fact that “AI” is a marketing rather than a technical term, what the definition of “AI” is, and what is an acceptable level of use, will change from one person to another. Is Word’s spellcheck “AI”? Is Photoshop’s Spot Healing brush tool? Is Logic Pro’s session drummer? At what point does a creative tool become inimical to creation?

(On a much larger industrial scale, this will be an extremely interesting question when it comes to animation, CGI and VFX. “AI” is already here in video games with DLSS, which upscales and adds frames to games; if similar tech isn’t already being used for inbetweening in animation, it’s probably not going to be long until it is.)

Again, I’m not interested in being, nor have the time to be, the “AI” police. I choose to focus on the final product and the human element in that, because that is honestly the only part of the process that I, and most people, can see. I’m certainly not going to penalize a creative person because Adobe or Microsoft or whomever incorporated “AI” into a tool they need to use in order to do their work. I would be living in a glass house if I threw that particular stone.

9. It’s all right to be informed about the state of the art when it comes to “AI.” Do I use “AI” in my text? No. Do I think it makes sense to have an understanding of where “AI” is at, to know how the companies who make it create a business case for it, and to keep tabs on how it’s actually being used in the real word? Yes. So I check out latest iterations of ChatGPT/Claude/Gemini/Copilot, etc (I typically steer clear of Grok if only because I’m not on the former Twitter anymore) and the various services and capabilities they offer.

The landscape of “AI” is still changing rapidly, and if you’re still at the “lol ‘AI’ can’t draw hands” level of thinking about the tech, you’re putting yourself at a disadvantage, particularly if you’re a creative person. Know your enemy, or at least, know the tools your enemies are making. Again, I’m not worried about “AI” replacing me as a novelist. But it doesn’t have to be at that level of ability to wreak profound and even damaging changes to creative fields. We see that already.

One final, possibly heretical thought:

10. Some people are being made to use “AI” as a condition of their jobs. Maybe don’t give them too much shit for it. I know at least a couple of people who were recently hired for work, who were told they needed to be fluent in computer systems that had “AI” as part of their workflow. Did they want or need to use those systems to do the actual job they were hired for? Almost certainly not! Did that matter? Nope! Was it okay that their need to eat and pay rent outweighed their ethical annoyance/revulsion with “AI” and the fact it was adding more work, not less, onto their plate? I mean (waves at the world), you tell me. Personally speaking, I’m not the one to tell a friend that they and their kid and cat should live in a Toyota parked at a Wal-Mart rather than accept a corporate directive made by a mid-level manager with more jargon in their brain than good sense. I may be a softie.

Be that as it may, to the extent you can avoid “AI,” do so, especially if you have a creative job, where it’s almost always just going to get in your way. Your fans, the ones that exist and the ones you have yet to make, will appreciate that what they get from you is from you. That’s what people mostly want from art: Entertainment and connection. You will always be able to do that better than “AI.” There is no statistical model that can create what is uniquely you.

— JS

Profile

ashnistrike: (Default)
ashnistrike

January 2019

S M T W T F S
  12345
6789101112
131415161718 19
20212223242526
2728293031  

Style Credit

Expand Cut Tags

No cut tags
Page generated Feb. 18th, 2026 10:41 am
Powered by Dreamwidth Studios