#open source definition

[mostlysignssomeportents]

"Open" "AI" isn’t

Tomorrow (19 Aug), I'm appearing at the San Diego Union-Tribune Festival of Books. I'm on a 2:30PM panel called "Return From Retirement," followed by a signing:

https://www.sandiegouniontribune.com/festivalofbooks

The crybabies who freak out about The Communist Manifesto appearing on university curriculum clearly never read it – chapter one is basically a long hymn to capitalism's flexibility and inventiveness, its ability to change form and adapt itself to everything the world throws at it and come out on top:

https://www.marxists.org/archive/marx/works/1848/communist-manifesto/ch01.htm#007

Today, leftists signal this protean capacity of capital with the -washing suffix: greenwashing, genderwashing, queerwashing, wokewashing – all the ways capital cloaks itself in liberatory, progressive values, while still serving as a force for extraction, exploitation, and political corruption.

A smart capitalist is someone who, sensing the outrage at a world run by 150 old white guys in boardrooms, proposes replacing half of them with women, queers, and people of color. This is a superficial maneuver, sure, but it's an incredibly effective one.

In "Open (For Business): Big Tech, Concentrated Power, and the Political Economy of Open AI," a new working paper, Meredith Whittaker, David Gray Widder and Sarah B Myers document a new kind of -washing: openwashing:

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4543807

Openwashing is the trick that large "AI" companies use to evade regulation and neutralizing critics, by casting themselves as forces of ethical capitalism, committed to the virtue of openness. No one should be surprised to learn that the products of the "open" wing of an industry whose products are neither "artificial," nor "intelligent," are also not "open." Every word AI huxters say is a lie; including "and," and "the."

So what work does the "open" in "open AI" do? "Open" here is supposed to invoke the "open" in "open source," a movement that emphasizes a software development methodology that promotes code transparency, reusability and extensibility, which are three important virtues.

But "open source" itself is an offshoot of a more foundational movement, the Free Software movement, whose goal is to promote freedom, and whose method is openness. The point of software freedom was technological self-determination, the right of technology users to decide not just what their technology does, but who it does it to and who it does it for:

https://locusmag.com/2022/01/cory-doctorow-science-fiction-is-a-luddite-literature/

The open source split from free software was ostensibly driven by the need to reassure investors and businesspeople so they would join the movement. The "free" in free software is (deliberately) ambiguous, a bit of wordplay that sometimes misleads people into thinking it means "Free as in Beer" when really it means "Free as in Speech" (in Romance languages, these distinctions are captured by translating "free" as "libre" rather than "gratis").

The idea behind open source was to rebrand free software in a less ambiguous – and more instrumental – package that stressed cost-savings and software quality, as well as "ecosystem benefits" from a co-operative form of development that recruited tinkerers, independents, and rivals to contribute to a robust infrastructural commons.

But "open" doesn't merely resolve the linguistic ambiguity of libre vs gratis – it does so by removing the "liberty" from "libre," the "freedom" from "free." "Open" changes the pole-star that movement participants follow as they set their course. Rather than asking "Which course of action makes us more free?" they ask, "Which course of action makes our software better?"

Thus, by dribs and drabs, the freedom leeches out of openness. Today's tech giants have mobilized "open" to create a two-tier system: the largest tech firms enjoy broad freedom themselves – they alone get to decide how their software stack is configured. But for all of us who rely on that (increasingly unavoidable) software stack, all we have is "open": the ability to peer inside that software and see how it works, and perhaps suggest improvements to it:

https://www.youtube.com/watch?v=vBknF2yUZZ8

In the Big Tech internet, it's freedom for them, openness for us. "Openness" – transparency, reusability and extensibility – is valuable, but it shouldn't be mistaken for technological self-determination. As the tech sector becomes ever-more concentrated, the limits of openness become more apparent.

But even by those standards, the openness of "open AI" is thin gruel indeed (that goes triple for the company that calls itself "OpenAI," which is a particularly egregious openwasher).

The paper's authors start by suggesting that the "open" in "open AI" is meant to imply that an "open AI" can be scratch-built by competitors (or even hobbyists), but that this isn't true. Not only is the material that "open AI" companies publish insufficient for reproducing their products, even if those gaps were plugged, the resource burden required to do so is so intense that only the largest companies could do so.

Beyond this, the "open" parts of "open AI" are insufficient for achieving the other claimed benefits of "open AI": they don't promote auditing, or safety, or competition. Indeed, they often cut against these goals.

"Open AI" is a wordgame that exploits the malleability of "open," but also the ambiguity of the term "AI": "a grab bag of approaches, not… a technical term of art, but more … marketing and a signifier of aspirations." Hitching this vague term to "open" creates all kinds of bait-and-switch opportunities.

That's how you get Meta claiming that LLaMa2 is "open source," despite being licensed in a way that is absolutely incompatible with any widely accepted definition of the term:

https://blog.opensource.org/metas-llama-2-license-is-not-open-source/

LLaMa-2 is a particularly egregious openwashing example, but there are plenty of other ways that "open" is misleadingly applied to AI: sometimes it means you can see the source code, sometimes that you can see the training data, and sometimes that you can tune a model, all to different degrees, alone and in combination.

But even the most "open" systems can't be independently replicated, due to raw computing requirements. This isn't the fault of the AI industry – the computational intensity is a fact, not a choice – but when the AI industry claims that "open" will "democratize" AI, they are hiding the ball. People who hear these "democratization" claims (especially policymakers) are thinking about entrepreneurial kids in garages, but unless these kids have access to multi-billion-dollar data centers, they can't be "disruptors" who topple tech giants with cool new ideas. At best, they can hope to pay rent to those giants for access to their compute grids, in order to create products and services at the margin that rely on existing products, rather than displacing them.

The "open" story, with its claims of democratization, is an especially important one in the context of regulation. In Europe, where a variety of AI regulations have been proposed, the AI industry has co-opted the open source movement's hard-won narrative battles about the harms of ill-considered regulation.

For open source (and free software) advocates, many tech regulations aimed at taming large, abusive companies – such as requirements to surveil and control users to extinguish toxic behavior – wreak collateral damage on the free, open, user-centric systems that we see as superior alternatives to Big Tech. This leads to the paradoxical effect of passing regulation to "punish" Big Tech that end up simply shaving an infinitesimal percentage off the giants' profits, while destroying the small co-ops, nonprofits and startups before they can grow to be a viable alternative.

The years-long fight to get regulators to understand this risk has been waged by principled actors working for subsistence nonprofit wages or for free, and now the AI industry is capitalizing on lawmakers' hard-won consideration for collateral damage by claiming to be "open AI" and thus vulnerable to overbroad regulation.

But the "open" projects that lawmakers have been coached to value are precious because they deliver a level playing field, competition, innovation and democratization – all things that "open AI" fails to deliver. The regulations the AI industry is fighting also don't necessarily implicate the speech implications that are core to protecting free software:

https://www.eff.org/deeplinks/2015/04/remembering-case-established-code-speech

Just think about LLaMa-2. You can download it for free, along with the model weights it relies on – but not detailed specs for the data that was used in its training. And the source-code is licensed under a homebrewed license cooked up by Meta's lawyers, a license that only glancingly resembles anything from the Open Source Definition:

https://opensource.org/osd/

Core to Big Tech companies' "open AI" offerings are tools, like Meta's PyTorch and Google's TensorFlow. These tools are indeed "open source," licensed under real OSS terms. But they are designed and maintained by the companies that sponsor them, and optimize for the proprietary back-ends each company offers in its own cloud. When programmers train themselves to develop in these environments, they are gaining expertise in adding value to a monopolist's ecosystem, locking themselves in with their own expertise. This a classic example of software freedom for tech giants and open source for the rest of us.

One way to understand how "open" can produce a lock-in that "free" might prevent is to think of Android: Android is an open platform in the sense that its sourcecode is freely licensed, but the existence of Android doesn't make it any easier to challenge the mobile OS duopoly with a new mobile OS; nor does it make it easier to switch from Android to iOS and vice versa.

Another example: MongoDB, a free/open database tool that was adopted by Amazon, which subsequently forked the codebase and tuning it to work on their proprietary cloud infrastructure.

The value of open tooling as a stickytrap for creating a pool of developers who end up as sharecroppers who are glued to a specific company's closed infrastructure is well-understood and openly acknowledged by "open AI" companies. Zuckerberg boasts about how PyTorch ropes developers into Meta's stack, "when there are opportunities to make integrations with products, [so] it’s much easier to make sure that developers and other folks are compatible with the things that we need in the way that our systems work."

Tooling is a relatively obscure issue, primarily debated by developers. A much broader debate has raged over training data – how it is acquired, labeled, sorted and used. Many of the biggest "open AI" companies are totally opaque when it comes to training data. Google and OpenAI won't even say how many pieces of data went into their models' training – let alone which data they used.

Other "open AI" companies use publicly available datasets like the Pile and CommonCrawl. But you can't replicate their models by shoveling these datasets into an algorithm. Each one has to be groomed – labeled, sorted, de-duplicated, and otherwise filtered. Many "open" models merge these datasets with other, proprietary sets, in varying (and secret) proportions.

Quality filtering and labeling for training data is incredibly expensive and labor-intensive, and involves some of the most exploitative and traumatizing clickwork in the world, as poorly paid workers in the Global South make pennies for reviewing data that includes graphic violence, rape, and gore.

Not only is the product of this "data pipeline" kept a secret by "open" companies, the very nature of the pipeline is likewise cloaked in mystery, in order to obscure the exploitative labor relations it embodies (the joke that "AI" stands for "absent Indians" comes out of the South Asian clickwork industry).

The most common "open" in "open AI" is a model that arrives built and trained, which is "open" in the sense that end-users can "fine-tune" it – usually while running it on the manufacturer's own proprietary cloud hardware, under that company's supervision and surveillance. These tunable models are undocumented blobs, not the rigorously peer-reviewed transparent tools celebrated by the open source movement.

If "open" was a way to transform "free software" from an ethical proposition to an efficient methodology for developing high-quality software; then "open AI" is a way to transform "open source" into a rent-extracting black box.

Some "open AI" has slipped out of the corporate silo. Meta's LLaMa was leaked by early testers, republished on 4chan, and is now in the wild. Some exciting stuff has emerged from this, but despite this work happening outside of Meta's control, it is not without benefits to Meta. As an infamous leaked Google memo explains:

Paradoxically, the one clear winner in all of this is Meta. Because the leaked model was theirs, they have effectively garnered an entire planet's worth of free labor. Since most open source innovation is happening on top of their architecture, there is nothing stopping them from directly incorporating it into their products.

https://www.searchenginejournal.com/leaked-google-memo-admits-defeat-by-open-source-ai/486290/

Thus, "open AI" is best understood as "as free product development" for large, well-capitalized AI companies, conducted by tinkerers who will not be able to escape these giants' proprietary compute silos and opaque training corpuses, and whose work product is guaranteed to be compatible with the giants' own systems.

The instrumental story about the virtues of "open" often invoke auditability: the fact that anyone can look at the source code makes it easier for bugs to be identified. But as open source projects have learned the hard way, the fact that anyone can audit your widely used, high-stakes code doesn't mean that anyone will.

The Heartbleed vulnerability in OpenSSL was a wake-up call for the open source movement – a bug that endangered every secure webserver connection in the world, which had hidden in plain sight for years. The result was an admirable and successful effort to build institutions whose job it is to actually make use of open source transparency to conduct regular, deep, systemic audits.

In other words, "open" is a necessary, but insufficient, precondition for auditing. But when the "open AI" movement touts its "safety" thanks to its "auditability," it fails to describe any steps it is taking to replicate these auditing institutions – how they'll be constituted, funded and directed. The story starts and ends with "transparency" and then makes the unjustifiable leap to "safety," without any intermediate steps about how the one will turn into the other.

It's a Magic Underpants Gnome story, in other words:

Step One: Transparency

Step Two: ??

Step Three: Safety

https://www.youtube.com/watch?v=a5ih_TQWqCA

Meanwhile, OpenAI itself has gone on record as objecting to "burdensome mechanisms like licenses or audits" as an impediment to "innovation" – all the while arguing that these "burdensome mechanisms" should be mandatory for rival offerings that are more advanced than its own. To call this a "transparent ruse" is to do violence to good, hardworking transparent ruses all the world over:

https://openai.com/blog/governance-of-superintelligence

Some "open AI" is much more open than the industry dominating offerings. There's EleutherAI, a donor-supported nonprofit whose model comes with documentation and code, licensed Apache 2.0. There are also some smaller academic offerings: Vicuna (UCSD/CMU/Berkeley); Koala (Berkeley) and Alpaca (Stanford).

These are indeed more open (though Alpaca – which ran on a laptop – had to be withdrawn because it "hallucinated" so profusely). But to the extent that the "open AI" movement invokes (or cares about) these projects, it is in order to brandish them before hostile policymakers and say, "Won't someone please think of the academics?" These are the poster children for proposals like exempting AI from antitrust enforcement, but they're not significant players in the "open AI" industry, nor are they likely to be for so long as the largest companies are running the show:

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4493900

I'm kickstarting the audiobook for "The Internet Con: How To Seize the Means of Computation," a Big Tech disassembly manual to disenshittify the web and make a new, good internet to succeed the old, good internet. It's a DRM-free book, which means Audible won't carry it, so this crowdfunder is essential. Back now to get the audio, Verso hardcover and ebook:

http://seizethemeansofcomputation.org

If you'd like an essay-formatted version of this post to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:

https://pluralistic.net/2023/08/18/openwashing/#you-keep-using-that-word-i-do-not-think-it-means-what-you-think-it-means

Image: Cryteria (modified) https://commons.wikimedia.org/wiki/File:HAL9000.svg

CC BY 3.0 https://creativecommons.org/licenses/by/3.0/deed.en

[taradactyls]

Found something interesting for Pride and Prejudice fans relating to Elizabeth's takedown of Mr Darcy's perception of himself a gentleman.

I'm reading Thomas Fuller's 'The Holy State, and the Profane State' (published 1642 but this version republished in 1841 so the views were clearly still applicable) for a research essay, and in the chapter labelled 'The True Gentleman' he states:

He is courteous and affable to his neighbours … the truly generous are most pliant and courteous in their behaviour to their inferiors.

And of course, during the Hunsford proposal, Darcy has just objected to Elizabeth's family, she's called him out, and we get the iconic lines:

"Nor am I ashamed of the feelings I related. They were natural and just. Could you expect me to rejoice in the inferiority of your connections?—to congratulate myself on the hope of relations, whose condition in life is so decidedly beneath my own?" "You are mistaken, Mr. Darcy, if you suppose that the mode of your declaration affected me in any other way, than as it spared the concern which I might have felt in refusing you, had you behaved in a more gentlemanlike manner."

So Elizabeth drops that bomb just after he's been ungenerous and discourteous about her inferior relations... in direct contradiction of one of the rules of true gentlemanly behaviour. No wonder he can't rebut her words at all in the moment, even though Darcy later says "it was some time, I confess, before I was reasonable enough to allow their justice." He might not believe he's got a real problem yet, but there's been examples Elizabeth could call on from even during the course of their conversation too blatant for him to disagree with entirely!

And then later, obviously, he reflects and finds it's true he also hasn't been gentlemanlike in this and other ways in too many aspects of his life.

[theweirdowithcoffee]

Armored Core, Video Games, Mecha: A Cultural Study of A Genre.

In 1997, From Software (フロム・ソフトウェア) released "Armored Core" (アーマード・コア) for the Sony PlayStation. While definitely not the first "Mecha Game" as we'll be referring to ad nauseam in this bizarre, overly long, essay thing of sorts- it more than the rest is arguable the most important. Through its mechanics, story, gameplay, and even setting- everything about Armored Core reinforces that it is the first Mecha IP made for the brand new at the time "video game medium" that fully embodied everything that defines the cultural and historical influences of the modern Mecha Genre, while redefining that genre for the newer medium. To this day, with the most recent release of "Armored Core VI: The Fires of Rubicon" in August of 2023, the series continues to uphold and redefine this legacy. Yet, what does any of that even mean?

To make a long story shortened, somewhat long once again; as we know it outside of Japan "Mecha", is a niche of a niche in some cases. Not necessarily that it's unpopular, or doesn't make an insane amount of money (which it is and does in both cases quite often), but in that it is a genre almost entirely defined by its roots in Japan, primarily through various Manga Comics and especially Animated Series. Go Nagai's (永井 豪) "Mazinger Z" (1972) is credited most often as the birth of the genre's identity, most notably as the first real breakout attempt at conceptualizing the idea of a large robot that was controlled through the use of a cockpit within the robot itself. In Go Nagai's words within the book "A Brief History of Japanese Robophilia"; "I wanted to create something different, and I thought it would be interesting to have a robot that you could drive, like a car."

From this idea and the incredible popularity of Mazinger Z, "Robot Anime" (ロボットアニメ) was born, and Go Nagai went on to create more influential works that helped further expand the genre as well as develop this particular flavor as "Super Robot". Now, Super Robot being the first and oldest sub-category to the genre makes what came after works like the aforementioned Mazinger Z and later "Getter Robo" (also from Go Nagai, 1974) fascinating from an outsider to the culture and times of the late 20th Century Japan. Without going too much into a side tangent, shows like Mazinger Z and Getter Robo were the foundation of which everything that would come to pass was built on. Discussing Mazinger Z and Getter Robo with friends and people who love it, however, the one thing that was constantly said was that "They still were and are, monster of the week animated shows", the Super Robots being genuinely not too dissimilar to how super heroes or super powered characters in other cartoons or comics were depicted other than they were both vehicle and the powers themselves. They are still shows about cool/surprising fights with evil monsters or wicked folk- and that's what they really want to be.

Not to say there's little under the surface (I would never dare to even humor a claim like that in regards to near any media), but for example- Getter Robo, which introduced the concept of "gattai" (合体), better known as "combination", where these super robots or aspects of them could "combine together" to create a bigger, stronger, or better robot- combined with the introduction of the show's "Getter Rays", the primary antagonists being what are genuinely, dinosaur aliens, Getter Robo has a very clear and distinct theme of "Evolution" that permeates through its entire core- but its also secondary to the actual point of the series from what I've been informed. To quote directly from a friend who's a massive fan and shill for the series: "This is the invention of the wheel, no one has thought to put trims on it," which is not a criticism at all- but I think it's important to especially point that out here and now that this is what the Super Robot era of early Mecha was, really cool and fun ideas for media that wanted to be surprising, fun, and fresh for the early 1970s.

The other thing that was most interesting about the era of Super Robot, was that despite robots- the powers and abilities explored in these series were supernatural or magical in nature; Getter Rays for example is quite literally, human will made manifest- allowing their machines to fire beams of energy, transform their parts, amongst several other things. Some would say it's "on the nose", but frankly it's inspired and has persisted as an idea all the way to present in even modern Mecha that isn't Super Robot.

But then, what did come after the Super Robot era of early Mecha? When a genre has only escalated and expanded, going further into the fantastical and erratic energy of its fore-bearers and contemporaries; bigger, brighter, louder- where do we look once we've waged battle with every single light in the sky? When there's no battles left to be fought with aliens, kaiju, or other such monsters that threaten to snuff out our spark, try to tango with the human spirit and its indomitable will- eventually our sights go from the stars above, back to where all battles and conflict are directed at.

Each other.

(this post is continued in a series of reblogs, be sure to check them out!)

[jils-things]

Wait a While Longer

this fic is written by my friend, sarah! (@throughpatchesofviolet) it was for a trade we exchanged months back. i asked for a lovely stevaide fic and she delivered! she has given me her permission to repost this story and i'm more than happy to share it. also using this opportunity to read it easily hehehe 💚💜 thank you again!

"Here we are …” Jaide mused, smiling as she crouched beside the oven, patting a small, reptilian Pokémon on the head as she pointed at the pie visible through the window. “See? It’s almost ready, Aron—just a few more minutes.”

The steel-type titled his head, studying the pastry before turning to his companion, blinking up at her with his large, blue eyes.

“In the meantime, how about we clean up?” Jaide suggested, standing up and lightly sidestepping Aron so she could reach the sink, where a mound of dirty dishes awaited her. “Can’t leave the house in disarray, after all.”

Aron huffed, but he trotted after her, sitting obediently at her feet as she turned on the faucet, humming softly to herself as she rinsed the first of many bowls.

As she squirted dish soap onto a cloth, beginning to scrub a large mixing bowl, her thoughts turned towards her husband, Steven. Early that morning, the jangling tone of a phone had roused them both—an urgent call from Steven’s father, who requested Steven make an appearance at an upcoming meeting.

Naturally, Steven had agreed, and had promptly dressed, pressed a soft kiss to his wife’s forehead, and departed, all in the span of a few minutes.

I hope he’s doing alright, Jaide thought, frowning at a stain on the dish she was washing. He left so early … and after working so hard, the night before, too. He must be exhausted …

The buzzing of a timer snapped Jaide from her thoughts, and she dropped the rag and bowl into the sink, spinning around to find Aron had moved to stand in front of the oven. The Pokémon sniffed the air as she approached, drawing another smile from his companion.

“It smells pretty good, doesn’t it?” she asked, grabbing a pair of oven mitts before squatting down beside Aron and opening the oven door, a blast of hot, cinnamon-scented air rushing over them.

Leaning forward, Jaide carefully removed the pie, as Aron grunted in irritation, his eyes narrowing as he crouched behind her, trying to avoid the heat.

Jaide laughed as she rose to her feet, setting the pie on a cooling rack. “I tried to warn you, when we started—the oven gets hot!”

Aron snorted, glaring at her before turning away, visibly irritated.

“Aw, Aron … I’m sorry! I wasn’t laughing at you …” Jaide glanced at the pie, the golden crust shimmering beneath a cloud of steam, then back at Aron. “How about I give you the biggest piece to make up for it? Would you like that?”

The steel-type refused to look at her for a moment longer, then slowly sighed, and Jaide smiled as his large eyes drifted back towards her face.

“Alright—Aron gets the largest piece of pie, tonight. Promise.”

The Pokémon beamed up at her, then snapped to alertness, his gaze darting towards the living room: the soft jangling of keys had grabbed his attention—and Jaide’s, as well.

Aron bolted as the front door creaked open, eager to welcome Steven home, and Jaide sighed, smoothing her dress before stepping into the other room, where her husband was trying not to trip over the tiny Pokémon weaving between his legs.

“… I don’t have anything for you, this time, Aron, I’m sorry!” Steven held out his empty hands to the steel-type, who squinted up at him. “I was in a meeting all day, so I didn’t have time to grab any ore … next time, I promise!”

Aron huffed, then spun around and marched back into the kitchen.

“I don’t think he liked your excuse,” Jaide teased, smiling as she approached Steven, already reaching to help him take off his coat. “How was your meeting, dear? You’re not too tired, are you?”

“No, no … I’m perfectly fine. Not tired—” Steven broke off mid-sentence, yawning, but he quickly stifled it, gently waving Jaide aside. “Not tired at all …”

His wife raised an eyebrow, but she decided to play along. “Alright … how about we sit down? We both could use some rest, after today.”

“Oh?” he frowned as she took his arm, quietly guiding him towards the soda. “What did you get up to …?”

“Well,” Jaide began, patting her husband’s arm as they sank onto the couch cushions. “After you left, I managed to fall back asleep for a few more hours … then I was up to make breakfast for me and Ruby … we had pancakes—the ones where we use fruit to make them look like Pokémon. Ruby managed to make his look just like Fofo …”

“Mm … which form?” Steven mumbled, leaning his head against Jaide’s shoulder.

“It was her Sunny Form,” Jaide replied, smiling as she recalled how carefully Ruby had arranged slices of banana around his pancake that morning. “He took a photo, of course—it was quite cute.

“After that, Ruby told me he was going to hang out with some friends at a Secret Base—though, he wouldn’t tell me where it was … I suppose that’s to keep it a “secret” base, isn’t it?

“Then I was on my own, so I did some housework, ran to the store for groceries, and then Aron and I baked a pie … oh, you should have seen his face when I opened the oven—his eyes scrunched up and he huddled behind me … it was adorable! Although, he was upset about it, so now I owe him a huge slice of pie as an apology.

"And now you’re home, so I can start making …” Jaide trailed off as soft snoring tickled her ears, and she glanced over to see Steven dozing against her shoulder.

Smiling, Jaide gently lowered Steven’s head so it was resting in her lap, chuckling quietly as she brushed his hair from his face, admiring his features.

“You’re a terrible liar,” she whispered, pressing a soft kiss to Steven’s forehead.

I suppose dinner can wait a bit longer, Jaide thought, closing her eyes. Steven needs to rest, and Ruby’s not home, yet, either … besides, I can’t possibly move, now—it’d wake him!

She snuggled into the couch cushions, humming a quiet lullaby as she stroked Steven’s hair.

Yes … dinner can wait just a little longer …

—

“What a day …” Ruby muttered, sighing as he stepped into the living room.

“Ar?”

The boy blinked, looking down to find his mother’s Aron gazing up at him. The Pokémon studied him for a moment, then turned his head, nodding towards the sofa.

Following Aron’s gaze, Ruby found his parents lounging on the couch—his father’s head rested in his mother’s lap. Thought she was sitting upright, he could tell Jaide was fast asleep, her fingers still tangled in Steven’s hair.

He glanced at Aron as he slid his backpack off, kneeling on the floor beside the Pokémon as he rummaged through its contents. “Shall we?” he asked, pulling out a camera.

“Aron!” the Pokémon chirped, beaming at him.

“I’ll take that as a yes!”

Powering the camera on, Ruby focused it on his parents, still snoozing on the sofa, and snapped a quick photo before settling down beside Aron, showing him the picture.

“What do you think? The lighting look okay?”

The steel-type stared at the photograph, then nodded

.

“Great! Then let’s leave them alone—we’ll have plenty of time to tease them with this, later.”

Ruby stood up, slinging his backpack over his shoulder as he marched into the kitchen, Aron trotting behind him. He paused when he saw the pie resting on the counter, and the Pokémon grunted, gently headbutting his leg.

“Aroooooon!” he hissed, glaring up at Ruby.

“Ar!”

“Right, right—sorry. Let’s go.”

Aron snorted as he watched the boy run into the other room. Nobody was going to touch that pie—not until Jaide served him his portion, anyway. She’d promised him a huge piece, after all!

The Pokémon cast one more glance up at the counter, then nodded to himself, scampering after Ruby. After all … dinner could wait a while longer.

[xylophone888]

if you can't infodump about rocks to your wonderful beautiful amazing precious husband during a romantic candlelit dinner in an egregiously expensive restaurant what are you even married for /j

[cipher-speaks]

Mandatory introductory post!

Since the MOMENT the original GF show aired, I was kinning YOUR problematic fave; thats well over a decade! And boy oh boy am I SO fucking back. (I never left.)

Keep in mind; at the initial time, I was a child and didn't know what kinning was (small brain, big big plans!) which puts me over the legal drinking age now. No kiddos interact, come back once you hit legality.

I'll be honest, its been years since I've made a sideblog (or a main blog) for kinning; I don't really care either way if people wanna talk to me, but I'm not against having some fun! I'm here for a good time, and for the love of GOD no drama. Does that still happen in kin communities or has everyone finally grown up?

Anyway, I'm shoving every little thing I relate to into this one little sideblog on this shithole of a site. Thats it.

This is my ONE POST I'll make to scream into the void just to establish this new sideblog and why its here; at current time, I don't even have it up and running yet. Not even a profile pic. It doesn't look pretty, but it will eventually! Maybe! We'll see.

[lgbtlunaverse]

It's actually pretty fun and not a crime to read fanfiction of media you haven't read/watched yourself. Maybe an author you like from a fandom you're in started writing for this new thing now, and even if you don't know the characters their writing is great. It's like dropping in on the 5th season of a good tv show. Do you know who these people are? Not a clue. Does this fuck? Supremely.

And then maybe you check out their bookmarks and find a bunch more fics from that fandom and hey you sort of know these characters' names by now and the writing is still good, and you're just enjoying yourself! You're not participating in the discourse, you have no idea what's ooc or not and you don't have serious opinions on it. You're just vibing. Taking in the craft. For all you know these are all just conspicuously similarly named OCs. It's harmless as long as you refrain from tricking yourself you actually know what's going on in canon and start posting, that's the devil talking and you mustn't give in.

[quatregats]

I will say that while I like LibreOffice very much and am quite pleased with it I do wish it would let me keep documents, presentations, and sheets in separate apps

[angeloftrumpets]

this man website updated and

[lorillee]

[wifegideonnav]

Hey, I saw your post about how people talk about personality disorders and I wanted to ask, is there any agreed upon term for "people who don't have a personality disorder"? I can't seem to find anything conclusive online.

hi! personally, i have never heard one, either an official term or a colloquial one. i don't really frequent online pd spaces so i def could just be missing it, tho i've spent enough time in treatment/known enough other pwpds and therapists irl that i feel like i probably would have picked up on any common term for that. honestly it's clunky, but i think the best bet is to just go with "people without personality disorders," that's what i say. if anyone knows any terms tho pls sound off!!

[raskies456]

I keep seeing that post that’s like “everything should be open source, cars don’t weld the hoods shut so you can’t look at the engines” and while I get what the post is trying to say the metaphor always throws me bc cars def straight up have a bunch of embedded computer units in them w a lot of inaccessible source code

[stories-of-iclin]

ᒥ🤡ᒧ—        When it comes to Drow information, I am only like 3 books in. Please permit me if I get anything wrong 😭 I am a noobie to the books lmaoo

[sreegs]

hey it's me black mold. thanks for running your window air conditioner all summer. whatever you do, do not regularly clean the removable filter. that's not necessary

you should also never ever unplug the air conditioner and stick a flashlight in the vent that blows air to see if we're in there. it's very bad, that place should not be checked

and whatever you do, if you've already made the mistake of unplugging it, don't remove it from the window for cleaning if possible. and whether it's possible to remove the unit or not, don't carefully disassemble the front panel, document where the screws go and plastic bits go, and open up the vent more to be able to get into it easily

as black mold, i'm an expert on this. you should heed my warnings: now, if you've somehow made the mistake of doing all of the above, you should not use warm water and dish soap to CLEAN the inside of the vent thoroughly. DON'T ever use a bottle brush to get into the hard to reach places. and certainly don't rinse and dry the cleaned area before carefully putting it back together

there's nothing wrong with us, black mold. we don't cause or exacerbate breathing conditions like asthma or other illnesses. it's cool, we're cool

furthermore, if you're capable of removing the window unit, DONT take a hose with the same soapy water and wash the portion of the window unit that sits outside the window and is therefore weatherproofed.

whatever you do, don't allow the air conditioner to dry before plugging it back in and turning it on again

and if you have a central air conditioner, you will definitely never ever consult a manual or sources online to perform a similar cleaning procedure on the cooling unit outside.

lastly, if you're physically unable to do the things we (the black mold) warned you not to do above, you should never ever ask someone to help you or hire a service to do it.

[kaijutegu]

Alligator Bites Might Never Heal, But Doechii Is Good At Holding Alligators

Doechii won the Grammy for Best Rap Album for Alligator Bites Never Heal, but she also should have won the coveted and definitely not fictitious "Best Alligator Handling" award for the way she held Coconut on the cover!

(Yes, it's this Coconut.)

And the best part? She released a BTS video showing how they shot the cover, meaning that we can see more than just the still image! If a picture's worth a thousand words, video's worth... a lot more. (Sorry if it autoplays I don't think I have any control over that either way)

So, using the photoshoot images and video as evidence, let's take a look at how Doechii handled this alligator very well! I'm going to go into excruciating detail here because I think it's important to know why something is good just as much as it is important to know why something is bad. It's hard to understand alligator body language a lot of the time, so in this writeup, I will address how Doechii's holding the gator and what she's doing right, as well as point out how you can tell from Coconut's reactions that she is not distressed.

Body Support

In the album cover image, Doechii is seated, which is good, because even though she's a small alligator, Coconut is a very strong and powerful creature. That tail is pure muscle! But even in the standing images, you can see that Doechii is giving Coconut great body support and holding her correctly- close to the body, but without grabbing too tightly or being restrained uncomfortably. I think for a gator of this size I would have recommended pinning the back foreleg against her body for a little additional support and movement restriction- but I don't think she had to restrict movement because Coconut seems quite relaxed!

In the seated image, Doechii has one hand under Coconut's chest, supporting her sternum and head. The other hand is on top of her tail, and her knee is under the pelvic girdle. This type of hold lets the alligator feel safe; remember that these are aquatic and terrestrial creatures. An insecure hold that risks dropping them is going to stress them out and make them uncomfortable. By holding the alligator gently against her body and not squeezing, she's avoiding any uncomfortable pressure.

Head and Throat Support

In all of the images, Doechii is bringing her hand under Coconut's neck, creating a cradle with her hand so that the alligator can rest her head. But what she's not doing is she is not squeezing or grabbing the throat. The throat is one of the soft bits of an alligator, and squeezing it too tightly is very uncomfortable for them. But the way Doechii is supporting her gives her several degrees of freedom to move her head if she so chooses.

Body Language

Another indication of good handling is that it's clear that Coconut is not uncomfortably stressed. Alligators express displeasure with being held in a lot of ways, including struggling to get away, hissing, and holding their mouths open. (If you want to know more and see my sources, you can read my post on alligator body language. LOTS of info there, including peer-reviewed ethology sources that explain what alligators do and why they do it! Go get your data-driven answers!)

But Coconut isn't doing that; she's calm and alert. You can see in the BTS video that she's active on set. She's not shut down, and when she wants to walk around, she's not restrained. Obviously the video is an edited timelapse, and it's not the whole story- but when people show alligators in media, they usually don't know enough about them to edit out any uncomfortable body language. So I think that if she had been upset, we would have seen that.

We can also see in the video that Coconut is unbanded, meaning her mouth was not held shut. I thought they might have banded her and then edited the band out for the cover, but no, there was nothing restricting any distress cues. Banding is usually done for public safety, but the facility Coconut's from... doesn't do that, so I'm not surprised she's unbanded. At least it gives more evidence that she's not trying to gape!

One more good indicator that Coconut was comfortable is that she's got her eyes open, which you can even kinda see in the video if you zoom in. Reptiles will often squinch their eyes shut to avoid distressing stimuli or signal distress, and albino alligators have even more reasons to do this. They're much more sensitive to light than their pigmented counterparts. But it looks like her on-set work was completed quickly, meaning that she didn't have to be around bright lights for long.

In conclusion:

Doechii's album cover is an example of good alligator handling. Yay!

That said, please note that this is only about handling and is divorced from any other issues surrounding this particular alligator. (Read the body language post if you want more on that.) These are not issues I'm touching in this post, because that's not the point! I simply want to point out an instance of good handling and how you can identify relaxed body language in an animal that is notoriously hard to read when posted on social media.

[lolab4t]

off duty - fluff

18 + part two

pairing: avenger!bucky barnes x fem!avenger!younger!reader summary: after a rare night off, you stumble back into avengers tower at 2 am.. tipsy, feet hurting, and definitely not expecting to run into bucky barnes on the couch. word count: 5.8k warning(s): light cursing, alcohol consumption/intoxication, fluff, use of nicknames, humor, age gap, mild suggestive language, reader is a young adult avenger, reader is described as wanting to party a/n: here's my first fic! it's a throwback to the avengers before the infinity war. i really hope you enjoy :) and if you do, please like, comment, or reblog! <3

cherry - lana del rey

being a young adult and an avenger at the same time wasn't easy. you wanted to be like others your age... party, stay out late, maybe dance with a random guy you found mildly attractive under the dim nightclub lighting, then bolt when you actually saw his face in the light. hell, you would settle for just shopping or grabbing lunch with your friends, however mundane that sounded.

but, as a full-time avenger, you weren't privy to this lifestyle. the main issue was your schedule. being an avenger isn't exactly a 9–5 job... it's more 24/7. you're meant to always be ready to jump into a mission when needed. with your time mainly consisting of training, meetings, and missions, you didn't exactly have free time.

this didn't stop your friends from pushing, though, and they eventually got through. so, after a few long conversations of begging stark, here you are, stumbling into the elevator of the avengers tower at like 2 in the morning, ever so slightly intoxicated. who can blame you? it was your first night off in a while; of course you took advantage of this once-in-a-lifetime opportunity and got shitfaced. you might regret it during training later that day, but for now, all that mattered was that you had fun with your friends.

you did regret wearing heels, though. you wanted to trade in your boots for something more fun tonight, but god, did your feet hurt. you were also dying to get out of your minidress. considering your wardrobe now reflects your job and only consists of suits and very little casual clothes, you had to borrow this dress from your friend. you were beginning to remember why you never liked to wear dresses even before joining the avengers.

the elevator dinged, and the door opened to the top floor, the avengers' quarters. you dragged yourself out, hair messy, dress slightly hiked up, and feet already blistering. your makeup made it clear you had been sweating on a dancefloor not long ago. you headed to your room when a voice stopped you in your tracks.

"where ya been?"

you turned to the source, shocked to see bucky barnes sitting on the sofa. he was laid back, one arm draped lazily on the backrest, and the other on his knee. he was almost smirking, likely having a good idea of your whereabouts based on your appearance.

you and the winter soldier weren't exactly close. he was a very quiet and reserved guy, usually a man of few words. your interactions mainly consisted of short conversation and sometimes catching him staring at you on the quinjet or in meetings. you never really thought much of it.

but his tone... his expression right now was different. it was weird, but a good weird.

"why're you awake?" you huffed, walking toward the couch.

"couldn't sleep," he stated simply, scanning your form with that smug look on his face. "you have a fun night?" he chuckled to himself a bit.

"yeah, i went out with some friends," you replied, sitting on the couch. you began fiddling with your heels, wanting to go ahead and relieve yourself of the pain. however, the alcohol was messing with your coordination, and you were struggling rather pathetically.

noticing the pout forming on your lips and the clear trouble you were having, bucky snickered, speaking in his gruff voice, "need some help?"

you looked up at him and nodded, still pouting. without a word, he moved a bit closer to you and curled his fingers around your ankles, a soft gasp escaping your lips as he rested them across his lap. you were reclining into the corner of the sofa now, watching him in shock. he hummed as his fingers slipped through the straps of the heels, sliding them off your feet gently. he set them down carefully, his free hand absentmindedly rubbing your calves.

"i've never seen you in anything but your boots," he grinned, turning his head toward you. "so, how much did you drink?" his grin turned into a knowing smirk.

you scoffed, pulling your legs away, drawing your knees to your chest. the short dress wasn’t doing you any favors, and you were probably flashing him, but bucky never looked. he was a gentleman... at least in the ways that mattered. you groaned, rubbing your face sleepily. no point in pretending.

"too much," you muttered.

"yeah, i can tell. you practically stumbled out of the elevator," he chuckled, eyes following your every move.

you let out a half-laugh, sheepish. your head dropped to rest on your knee as you sighed.

"kill me."

"not tonight, doll. i’m off duty."

your head lifted slightly, an eyebrow raising. "did you just call me ‘doll’?" you snickered at the old-fashioned nickname, trying to hide how much it made your heart beat faster.

he smirked, leaning back again with that maddening ease. "i dunno. you kinda look like one."

was he flirting? surely not. he probably saw you as some annoying kid.

"alright, old man. what do you call natasha then? sugar? darling?" you smiled lazily, thinking of more old-timey terms of endearment.

"hell no. she’d break my jaw," he grinned.

"and you think i won’t break your jaw?" you smirked, raising a brow.

bucky scoffed out a laugh. "oh, i'm sure you can, but i don't think you would."

"if i wasn't tipsy, i might've. you're getting off easy this time, grandpa," you giggled, starting to slur your words. your eyelids were beginning to feel heavy, and you found your head resting on your knee again.

bucky laughed at your slurred speech, not sure if it was the alcohol or just exhaustion. "you okay, doll?"

"mhm," you hummed, obviously dozing off.

"alright, i guess i'll babysit the lightweight," he joked, his grin never faltering.

you eventually drifted off, and so did bucky not long after. you both slept better than you had in a while. that was, until you awoke to the stunned faces of the other avengers. they definitely weren't expecting to find you in bucky's arms on the sofa. hell, you weren't expecting it either.

thanks so much for reading <3

18+ part two