#like centralizing project data

[cloud9technologies2]

Benefits of Implementing ERP Software for Engineering Firms

The engineering industry is one of the biggest industries in the world, and it plays an important role in growing the economy as well. The engineering sector is growing day by day and is highly competitive. Hence, efficiency, accuracy, and streamlined operations are crucial for success in this sector. Businesses face several challenges in this sector, like the complexities of a project, resource management, and deadline restrictions. ERP software for engineering firms is the best way to overcome all of these challenges as it integrates and automates business processes.

Here is the list of top benefits of utilizing ERP systems for the engineering industry:

1. Project Management:

The projects in engineering sectors have a detailed documentation process, different teams, and complicated workflows. ERP system for engineering firms help in various ways, like centralizing project data, enabling limitless collaboration, and getting real-time updates. Because of this software, every team member has all the updates, which in turn reduces miscommunication and delays in the project.

2. Resource Management:

For all engineering projects, it is essential to allocate all resources carefully, like equipment, materials, and labor. With the utilization of ERP software, the monitoring of resources can be performed easily. It helps in checking resource availability, optimizing usage, and forecasting requirements. This ultimately results in improving cost efficiency.

3. Quality Management:

Ensures engineering projects meet industry standards and regulations.

Quality Control: Offers tools for monitoring and managing the quality of materials, processes, and completed projects.

4. Data Management:

Using ERP software, engineering firms can make sure that they can get a unified database to eliminate data silos and ensure consistency through all departments. A centralized data management system is beneficial for decision-making as well it provides critical information when required.

5. Time and Budget Management:

When the whole system gets automated with ERP software, it reduces time and cost on repetitive tasks like data entry, procurement, and inventory management. The utilization of ERP systems in engineering firms helps in reducing manual errors and improving productivity. Hence, the firms can focus on other important things like innovation and project execution.

6. Client Relationship Management:

Most ERP systems include customer relationship management tools that are very helpful in managing client interactions. This tool allows the firm to track communication history, project milestones, and client preferences. Because of this feature, firms can improve customer satisfaction and build long-term relationships.

7. Scalability and Flexibility

ERP solutions may scale with the company as it grows, allowing for more projects, clients, and resources. Customization: ERP solutions can typically be tailored to an engineering firm’s specific demands and operations.

8. Financial Management

Accounting combines financial accounting with project management to provide a complete picture of the company’s financial health. Reporting: Creates detailed financial reports, such as profit and loss statements, balance sheets, and cash flow statements.

How PMTRACK ERP Helps:

Managing development processes, monitoring complex projects, and ensuring seamless collaboration across divisions are becoming increasingly important for company success. Engineering organizations in Pune, India, and around the world have distinct issues in successfully managing their operations.

Implementing a bespoke Enterprise Resource Planning (ERP) solution provides transformative benefits by streamlining processes, improving project management, and ultimately generating profitability.

For businesses considering ERP adoption, selecting the correct ERP software vendor is critical. PMTRACK ERP, a reputable ERP solution provider in Pune, India, specializes in engineering ERP systems tailored to the demands of engineering and manufacturing companies.

ERP software is used to connect project management with financial accounting, inventory control, and procurement procedures. This integration gives project managers real-time information about project costs, resource availability, and schedules, resulting in better-informed decisions and more effective project execution.

Engineering firms that use an ERP system can improve operational efficiency, reduce costs, improve project delivery, and ultimately boost client satisfaction and profitability.

Summary:

ERP software provides several advantages to engineering firms in Pune, India, ranging from better project management and financial control to higher client satisfaction and scalability. Engineering organizations can employ a comprehensive ERP solution to improve operations, decrease inefficiencies, and drive long-term growth.

PMTRACK ERP, one of the leading ERP solution providers in Pune, India, provides comprehensive, industry-specific ERP solutions that are suitable for engineering organizations’ unique requirements. Firms that collaborate with an experienced engineering ERP software company in India receive a trusted partner in negotiating the complexity of their business, setting them up for success in an increasingly competitive landscape.

[reasonsforhope]

If you're feeling anxious or depressed about the climate and want to do something to help right now, from your bed, for free...

Start helping with citizen science projects

What's a citizen science project? Basically, it's crowdsourced science. In this case, crowdsourced climate science, that you can help with!

You don't need qualifications or any training besides the slideshow at the start of a project. There are a lot of things that humans can do way better than machines can, even with only minimal training, that are vital to science - especially digitizing records and building searchable databases

Like labeling trees in aerial photos so that scientists have better datasets to use for restoration.

Or counting cells in fossilized plants to track the impacts of climate change.

Or digitizing old atmospheric data to help scientists track the warming effects of El Niño.

Or counting penguins to help scientists better protect them.

Those are all on one of the most prominent citizen science platforms, called Zooniverse, but there are a ton of others, too.

Oh, and btw, you don't have to worry about messing up, because several people see each image. Studies show that if you pool the opinions of however many regular people (different by field), it matches the accuracy rate of a trained scientist in the field.

--

I spent a lot of time doing this when I was really badly injured and housebound, and it was so good for me to be able to HELP and DO SOMETHING, even when I was in too much pain to leave my bed. So if you are chronically ill/disabled/for whatever reason can't participate or volunteer for things in person, I highly highly recommend.

Next time you wish you could do something - anything - to help

Remember that actually, you can. And help with some science.

[ayeforscotland]

What is Dataflow?

This post is inspired by another post about the Crowd Strike IT disaster and a bunch of people being interested in what I mean by Dataflow. Dataflow is my absolute jam and I'm happy to answer as many questions as you like on it. I even put referential pictures in like I'm writing an article, what fun!

I'll probably split this into multiple parts because it'll be a huge post otherwise but here we go!

A Brief History

Our world is dependent on the flow of data. It exists in almost every aspect of our lives and has done so arguably for hundreds if not thousands of years.

At the end of the day, the flow of data is the flow of knowledge and information. Normally most of us refer to data in the context of computing technology (our phones, PCs, tablets etc) but, if we want to get historical about it, the invention of writing and the invention of the Printing Press were great leaps forward in how we increased the flow of information.

Modern Day IT exists for one reason - To support the flow of data.

Whether it's buying something at a shop, sitting staring at an excel sheet at work, or watching Netflix - All of the technology you interact with is to support the flow of data.

Understanding and managing the flow of data is as important to getting us to where we are right now as when we first learned to control and manage water to provide irrigation for early farming and settlement.

Engineering Rigor

When the majority of us turn on the tap to have a drink or take a shower, we expect water to come out. We trust that the water is clean, and we trust that our homes can receive a steady supply of water.

Most of us trust our central heating (insert boiler joke here) and the plugs/sockets in our homes to provide gas and electricity. The reason we trust all of these flows is because there's been rigorous engineering standards built up over decades and centuries.

For example, Scottish Water will understand every component part that makes up their water pipelines. Those pipes, valves, fitting etc will comply with a national, or in some cases international, standard. These companies have diagrams that clearly map all of this out, mostly because they have to legally but also because it also vital for disaster recovery and other compliance issues.

Modern IT

And this is where modern day IT has problems. I'm not saying that modern day tech is a pile of shit. We all have great phones, our PCs can play good games, but it's one thing to craft well-designed products and another thing entirely to think about they all work together.

Because that is what's happened over the past few decades of IT. Organisations have piled on the latest plug-and-play technology (Software or Hardware) and they've built up complex legacy systems that no one really knows how they all work together. They've lost track of how data flows across their organisation which makes the work of cybersecurity, disaster recovery, compliance and general business transformation teams a nightmare.

Some of these systems are entirely dependent on other systems to operate. But that dependency isn't documented. The vast majority of digital transformation projects fail because they get halfway through and realise they hadn't factored in a system that they thought was nothing but was vital to the organisation running.

And this isn't just for-profit organisations, this is the health services, this is national infrastructure, it's everyone.

There's not yet a single standard that says "This is how organisations should control, manage and govern their flows of data."

Why is that relevant to the companies that were affected by Crowd Strike? Would it have stopped it?

Maybe, maybe not. But considering the global impact, it doesn't look like many organisations were prepared for the possibility of a huge chunk of their IT infrastructure going down.

Understanding dataflows help with the preparation for events like this, so organisations can move to mitigate them, and also the recovery side when they do happen. Organisations need to understand which systems are a priority to get back operational and which can be left.

The problem I'm seeing from a lot of organisations at the moment is that they don't know which systems to recover first, and are losing money and reputation while they fight to get things back online. A lot of them are just winging it.

Conclusion of Part 1

Next time I can totally go into diagramming if any of you are interested in that.

How can any organisation actually map their dataflow and what things need to be considered to do so. It'll come across like common sense, but that's why an actual standard is so desperately needed!

[covid-safer-hotties]

Also preserved on our archive

By Pandora Dewan

Levels of the virus that causes COVID-19 remain high across the U.S. despite recent decreases in positive case reports across the country. However, viral activity varies significantly across different states, new data from the U.S. Centers for Disease Control and Prevention (CDC) shows.

As of September 21, the overall viral activity level in wastewater across the country has been demoted from "very high" to just "high," although "very high" levels are still being detected in 13 states. These are particularly concentrated in the Midwest. Twenty-one states now exhibit "high" levels of wastewater activity, and nine are classed as "moderate."

Meanwhile, "low" levels have been detected in six states, with "minimal" levels, the lowest classification, seen in New York.

After a surge in COVID-19 cases this summer, infection rates seem to be on the decline. Positive tests now account for 11.6 percent of all COVID tests (excluding at-home testing) in the U.S., down 1.8 percent from the previous week. Coronavirus levels do remain high in certain states, especially those in the Central U.S.

The map below shows which states have seen the highest detections in wastewater.

(Follow link for interactive map)

Viral levels in wastewater are a helpful indicator of disease prevalence within a population.

Recent spikes in COVID-19 cases have been largely driven by a new class of subvariants nicknamed FLiRT after the position of the mutations on the virus' spike proteins, the projections that allow them to enter our cells.

These proteins are also used as targets by immune systems and vaccinations, so changes in their structure can allow the virus to bypass the body's defenses more easily. However, existing vaccines are likely to provide at least some form of protection against more severe symptoms and long COVID.

As of September 28, the now dominant subvariant, KP.3.1.1, accounted for more than 59 percent of all U.S. COVID-19 cases over the previous two weeks, according to the CDC, with the FLiRT variants accounting for more than 80 percent of cases in total.

However, while the U.S. has seen a steady rise in infections over the summer, hospitalizations and deaths have remained relatively low. It appears that the new FLiRT variants, while more infectious, do not generally cause such severe symptoms.

The symptoms include the following, according to the CDC:

Fever or chills Cough Shortness of breath Fatigue Muscle or body aches Headache Loss of taste or smell Sore throat Runny nose Nausea or vomiting Diarrhea

More vulnerable individuals may still be at risk of severe illness, so it is important to self-isolate if you receive a positive COVID test.

[artbyblastweave]

Any ideas to connect SU Diamonds and Worm Entities for a crossover?

For the past three years and change, I've been kicking around the idea of the Gempire as the residual result of an entity that botched its own cycle so badly that the central Zion-style figurehead holding the entire operation together is a hundred-thousand-year-gone memory. The result amounts to an entity with serious brain damage; The gems retain elements of the original programming for the cycle- namely, the ability to create anthromorphized avatars reflective of the local culture, and the drive to reproduce and consume planets to perpetuate themselves- but they've completely lost the plot on other important elements, namely the importance of hybridizing with local host species, their historical record, the full extent of their dimensional manipulation capabilities, best practices for resource extraction, and, most crucially, mutation, change and innovation as a desirable outcome.

Rather than an avatar, White Diamond is an intelligence analogous to a Endbringer or Titan who slid into the vacant role as the next-most-powerful autonomous portion of the network, holding the consolidated, stretched-thin remains of the original Network together by her fingernails while also deleteriously superimposing her own residual instinct from her original role onto the entire network- namely, to pacify, homogenize and sterilize host planets if and when a cycle is beginning to get out of control. This hybridized with residual data from previous host species that caused the gempire to organize in a fascimile of imperial structures encountered back when their cycle was still functional; essentially "Playing House" at the societal level, aping the culture of a host species without really remembering why.

The result of this is a "cycle" that's bad at everything it's supposed to do but effective enough that it limps on regardless- supremely energy inefficient, stripping planets bare rather than experimenting, and utterly developmentally stagnant. In the unlikely event that an entity were to cross paths with the Gempire, they'd have an uncanny-valley reaction to it and likely attempt to euthanize it, but compared to most entities the Gempire is tiny- while Shards canonically deploy in the hundreds of millions, the gems tend to reproduce only a few tens of thousands of themselves each time they claim a planet, and they usually only strip mine the handful of "active" worlds that would feature in a normal cycle rather than obliterating all dimensional iterations of it.

Yellow, Blue and eventually Pink are similar constructs to White, brought online to assist her in the project after the "imperial" territorial holdings grew too vast to micromanage. Unfortunately (for the cycle) another one of the things that got lost in translation were the controls meant to keep individual shards from developing autonomy or attachment-to-hosts. When the Gempire hit Earth, Pink Diamond and a significant contingent of the network, after patterning themselves after humans and spending a significant amount of time on the ground, pulled a fragile-one and went native, leading to a localized civil war that ended under unclear circumstances when the other the diamonds glassed the planet from orbit and pulled back their operations to prevent whatever affected the rebels from spreading.

All of this happened about 8000 years before the events of Worm, in a universe about 43 dimensions down the line from anything seen in the Earth Bet Cluster; due to the Gempire having mutated so much as to no longer be immediately recognizable as fellow Entities, and with so few active gems left on the planet in the aftermath of the rebellion, Zion ignored the crystal gems and folded them away into the inaccessible dimensional space, where the events of the show played out much as they did in SU canon. Ironically, Steven is the first ever example of this cycle successfully empowering a host, in the most roundabout way possible.

In my notes, and in keeping with the religious-theme-naming of the canon entities, I usually refer to this whole situation as Nirvana (what else would you call it when they break the cycle?)

[mariacallous]

Next year will be Big Tech’s finale. Critique of Big Tech is now common sense, voiced by a motley spectrum that unites opposing political parties, mainstream pundits, and even tech titans such as the VC powerhouse Y Combinator, which is singing in harmony with giants like a16z in proclaiming fealty to “little tech” against the centralized power of incumbents.

Why the fall from grace? One reason is that the collateral consequences of the current Big Tech business model are too obvious to ignore. The list is old hat by now: centralization, surveillance, information control. It goes on, and it’s not hypothetical. Concentrating such vast power in a few hands does not lead to good things. No, it leads to things like the CrowdStrike outage of mid-2024, when corner-cutting by Microsoft led to critical infrastructure—from hospitals to banks to traffic systems—failing globally for an extended period.

Another reason Big Tech is set to falter in 2025 is that the frothy AI market, on which Big Tech bet big, is beginning to lose its fizz. Major money, like Goldman Sachs and Sequoia Capital, is worried. They went public recently with their concerns about the disconnect between the billions required to create and use large-scale AI, and the weak market fit and tepid returns where the rubber meets the AI business-model road.

It doesn’t help that the public and regulators are waking up to AI’s reliance on, and generation of, sensitive data at a time when the appetite for privacy has never been higher—as evidenced, for one, by Signal’s persistent user growth. AI, on the other hand, generally erodes privacy. We saw this in June when Microsoft announced Recall, a product that would, I kid you not, screenshot everything you do on your device so an AI system could give you “perfect memory” of what you were doing on your computer (Doomscrolling? Porn-watching?). The system required the capture of those sensitive images—which would not exist otherwise—in order to work.

Happily, these factors aren’t just liquefying the ground below Big Tech’s dominance. They’re also powering bold visions for alternatives that stop tinkering at the edges of the monopoly tech paradigm, and work to design and build actually democratic, independent, open, and transparent tech. Imagine!

For example, initiatives in Europe are exploring independent core tech infrastructure, with convenings of open source developers, scholars of governance, and experts on the political economy of the tech industry.

And just as the money people are joining in critique, they’re also exploring investments in new paradigms. A crop of tech investors are developing models of funding for mission alignment, focusing on tech that rejects surveillance, social control, and all the bullshit. One exciting model I’ve been discussing with some of these investors would combine traditional VC incentives (fund that one unicorn > scale > acquisition > get rich) with a commitment to resource tech’s open, nonprofit critical infrastructure with a percent of their fund. Not as investment, but as a contribution to maintaining the bedrock on which a healthy tech ecosystem can exist (and maybe get them and their limited partners a tax break).

Such support could—and I believe should—be supplemented by state capital. The amount of money needed is simply too vast if we’re going to do this properly. To give an example closer to home, developing and maintaining Signal costs around $50 million a year, which is very lean for tech. Projects such as the Sovereign Tech Fund in Germany point a path forward—they are a vehicle to distribute state funds to core open source infrastructures, but they are governed wholly independently, and create a buffer between the efforts they fund and the state.

Just as composting makes nutrients from necrosis, in 2025, Big Tech’s end will be the beginning of a new and vibrant ecosystem. The smart, actually cool, genuinely interested people will once again have their moment, getting the resources and clearance to design and (re)build a tech ecosystem that is actually innovative and built for benefit, not just profit and control. MAY IT BE EVER THUS!

[morningsharksworld]

Nerd Out

Hazard x Reader

A/N: I made this as a thank you to @hackeraxe for drawing my silly lil Hazard piercing headcannons, I hope y’all enjoyed it as much as I did 👹✨

Summary: You got too excited over a project you’re working on

Your room was a controlled mess—keyboards, cables, and half-finished projects littered every available surface. Your desk was no exception, a graveyard of empty energy drink cans and open coding notebooks. You were hunched over your laptop, headphones slung around your neck, mumbling to yourself about predictive algorithms while the hum of your tower PC filled the room.

Hazard’s unmistakable Scottish brogue cut through your concentration like a knife. "Yer wee lair’s somethin’ else, ye ken?"

You jumped, spinning around in your chair to find him leaning against the doorframe, arms crossed, smirking like he owned the place.

"What are you doing here?" you asked, half-exasperated and half-mortified. You swore you’d told him not to come over unannounced.

"I knocked" he said with a shrug, pushing off the doorframe and stepping inside. "Ye just didn’t hear me o’er all that techno wizardry o’ yers." He gestured to the chaos surrounding you. "So… what’s got ye so absorbed ye forgot tae eat lunch, eh?"

You bristled but couldn’t help the sheepish grin tugging at your lips. "I was busy."

"Aye, I can see that, So…" Hazard reached for the nearest circuit board, turning it over in his hands like he had the faintest idea what he was looking at. "Whit’s all this then? Some kinda computer surgery?"

"Hardly" you said, snatching the board from him before he could accidentally fry it with static. “I’m upgrading this bad boy. Needed more RAM, and the GPU was about as outdated as your jokes."

His hand flew to his chest in mock offense. "Oof, right tae the heart! My jokes are timeless, I’ll hae ye know."

"Sure, tough guy" you teased, sliding the panel off the PC case.

Hazard sat by a nearby chair beside you, his sharp amber eyes scanning the array of components like he was trying to make sense of a foreign language. "Alright then, clever clogs, tell me this: whit’s RAM, and why d’ye need more of it? Sounds like somethin’ tae dae wi’ sheep."

You groaned but couldn’t help the grin tugging at your lips. "RAM stands for Random Access Memory. It’s like your computer’s short-term memory. When you’re gaming, it temporarily stores all the data the system needs to access quickly, like loading textures or keeping the game running smoothly. More RAM means it can handle more tasks without slowing down."

Hazard tilted his head, considering. "So it’s like when I try tae remember where I put ma keys. Short-term stuff, aye?"

"Exactly!" you said, a little impressed. "And then there’s the CPU—central processing unit. That’s the brain-brain. It processes everything, from running the game to your random web searches. A faster CPU means better performance overall."

He squinted at the open case. "Alright, so RAM’s short-term memory, CPU’s the brain. Whit’s this GPU thing ye mentioned earlier?"

"The GPU—graphics processing unit—is like an artist. It handles all the visuals, rendering textures, lighting, shadows, and everything else you see on the screen. A good GPU is crucial for gaming, especially if you want high frame rates and sharp graphics."

Hazard gave a low whistle. "So the GPU makes it bonnie, the RAM keeps it runnin’, and the CPU keeps it all from fallin’ apart. Bloody hell, I didnae ken gaming was this complicated."

You laughed, setting the upgraded GPU into place. "It’s not that complicated once you get the hang of it. And when you know what each part does, you can pick the right specs for what you need. Like, if you want to play on ultra settings at 120 frames per second, you’ll need a strong GPU and a good CPU."

"Ye’ve got a sparkle in yer eye when ye talk aboot this stuff, ye know that?" Hazard’s voice had softened, and when you glanced at him, he was leaning on your desk, watching you with an expression you couldn’t quite read.

"I—what?" you stammered, suddenly hyper-aware of how animated you’d gotten.

He tilted his head, a lopsided grin tugging at his lips. "I mean it. Ye light up like a Christmas tree. It’s... adorable."

Your face went hot, and you immediately turned back to your pc, pretending to be busy. "It’s not adorable. It’s just... something I’m passionate about."

"Aye, and it’s grand tae see." He crouched beside your chair, resting his chin on one hand as he peered at your work. "But ye’re bloody brilliant, ye know that?" he said, his brogue thick and warm.

You opened your mouth to protest, but he cut you off with a crooked grin. "Nae use denyin’ it. I’ve never seen someone so chuffed aboot pcs before, an’ it’s kinda... charmmin’, if I’m honest."

"I, uh..." You felt your face heat up as you fiddled with a stray wire. "I guess I am."

"Dinnae stop now" he said, his voice teasing but gentle. "I’m learnin’ loads here. Plus, I like seein’ ye all excited. It’s... kinda adorable, tae be honest."

Your face went nuclear. "Hazard!" You groaned, hiding your face in your hands.

You peeked at him through your fingers, his teasing grin making it impossible not to smile back.

"Fine" you muttered, turning back to your work. "But if you’re going to stay, you’re not allowed to touch anything."

Hazard laughed, settling himself on the floor next to you. "Deal. Now, keep goin’. Tell me more about this sheep thingy."

Still hiding your face in your hands, you couldn’t stop the smile creeping onto your lips. With a deep breath, you picked up where you left off, explaining the intricacies of the motherboard while Hazard listened intently, his eyes never leaving you.

And maybe—just maybe—you let yourself believe that he wasn’t just fascinated by the gaming specs. Maybe he was fascinated by you.

[mysticstronomy]

HOW DO WE KNOW HOW THE MILKY WAY LOOKS LIKE??

Blog#362

Saturday, December 30th, 2023

Welcome back,

This is the spiral galaxy NGC 2835, imaged by the impeccable, seemingly timeless Hubble Space Telescope.

And this is NGC 1132, an elliptical galaxy captured through the tandem efforts of Hubble and NASA's Chandra X-ray Observatory.

We know what both of these breathtakingly beautiful galaxies look like because we can see them from afar. How then do we know what our own Milky Way galaxy looks like, seeing as how we are inside it?

While we've never been able to zoom out and take a true galactic selfie, there are numerous observations that clue us in to the structure of our home galaxy. The greatest hint comes from looking at other galaxies. While there are perhaps two trillion in our observable universe, surprisingly, they only seem to come in three discernable varieties: spiral, elliptical, and irregular.

Spiral galaxies have a mostly flat disk with a bright central bulge and arms that swirl out from the middle. Elliptical galaxies tend to be round or oval with a uniform distribution of stars. Irregular galaxies are like stellar splotches in space, with little structure at all.

Gazing skyward from our vantage point on and around Earth, there are clear signs that the Milky Way is a spiral galaxy. You can see one sign with the naked eye! The Milky Way appears in our sky as a relatively flat disk.

Using more sophisticated methods, astrophysicists and astronomers have provided two more clues to the structure of the Milky Way.

"When we measure velocities of stars and gas in our galaxy, we see an overall rotational motion that differs from random motions," Sarah Slater, a graduate student in cosmology at Harvard University, wrote. "This is another characteristic of a spiral galaxy."

Moreover the gas proportions, colors, and dust content are similar to other spiral galaxies, she added.

Aside from these lines of evidence, astronomers are also using their tools in ingenious ways to map the structure of the Milky Way. Just this year, scientists used two radio astronomy projects from different parts of the globe to measure the parallaxes – differences in the apparent positions of objects viewed along two different lines of sight – from masers shooting off electromagnetic radiation in numerous massive star forming regions in our galaxy.

"These parallaxes allow us to directly measure the forms of spiral arms across roughly one-third of the Milky Way, and we have extended the spiral arm traces into the portion of the Milky Way seen from the Southern Hemisphere using tangencies along some arms based on carbon monoxide emission," the researchers explained. They coupled these observations with other gathered data points to construct a new image of the Milky Way. This is our home galaxy, in all its resplendant glory.

Originally published www-realclearscience-com

COMING UP!!

(Wednesday, January 3rd, 2024)

"WHAT IS QUARK MATTER??"

[whencyclopedia]

Homo Rudolfensis

Homo Rudolfensis is an early human species that lived in East Africa between c. 2.5 and 1.8 million years ago. It is known from a handful of skull, jaw and teeth fragments that remind alternatingly of Homo or of Australopithecus and that piece together to reveal a relatively large-brained, flat-faced species with robust teeth capable of chewing through tough plants.

The associated dates mean that Homo rudolfensis was around at a time that saw the emergence of our genus of Homo – a time still very much shrouded in mystery as the fossil remains are scarce, and thus, successfully building jigsaw puzzles with said remains is very difficult. This is reflected in debates that rage regarding the relationship between Homo rudolfensis and its close contemporary, Homo habilis, and the fact that some scientists favour lumping both into one species instead. It is moreover unclear whether Rudolfensis and Habilis have indeed reached their proper place within Homo, or whether they might fit better within Australopithecus instead.

Discovery

East Africa was a pivotal stage for the early years of human species, and palaeoanthropologists Louis and Mary Leakey and their sons played a central role in its discovery as such. Already in the 1950s, their efforts at Olduvai Gorge in Tanzania had uncovered early stone tools belonging to what they termed the Oldowan industry, and in the 1960s, their son Jonathan found bones and bone fragments that the Leakey team assigned to the then-new species Homo habilis, which became the earliest member of the genus of Homo known at the time.

A research project that focused its attention on northern Kenya, along the shores of Lake Turkana, would further change the picture of early Homo. Richard Leakey – Louis and Mary's son – led fieldwork there in the 1970s, and in 1972, at Koobi Fora, one of his team members, Bernard Ngeneo, discovered an interesting collection of skull fragments.

Once pieced back together, the face that greeted the team was striking: it had a steep forehead, a flat face, and a wide palate – seemingly a mixture of Homo and Australopithecus features that did not match anything else known at the time.

The skull, known scientifically as KNM-ER 1470, was initially dated to c. 2.4 million years old (later adjusted to c. 1.8 million years in 1989, and then to c. 2 million years in 2013) and assigned by Richard Leakey first to an indeterminate Homo species but then to Homo habilis. However, since the skull's features differed quite a bit from known Homo habilis specimens and its cranial capacity was larger, it sparked a whole lot of bickering and arguing in the scientific community.

Already in 1978, only two years after Leakey assigned the skull to Homo habilis, the Russian scientist Valerii Alexeev proposed giving the new skull the lead role in its own species, instead, naming it Homo rudolfensis (after Lake Turkana's old name, Lake Rudolf). However, the English version of Alexeev's paper did not appear until 1986, and, since not much data was put forth, the species name of Homo rudolfensis was not accepted by the scientific community until the early 1990s. Even so, the debate has continued, though, just like Homo habilis, rudolfensis' mixture of features does not make it a clear match with either Homo or Australopithecus.

Continue reading...

[bestanimal]

Round 2 - Mollusca - Scaphopoda

(Sources - 1, 2)

The class Scaphopoda is known more commonly for their shells, called “Tusk Shells” or “Tooth Shells.” They are the only class of molluscs to live exclusively below marine sediments. As such they are rarely seen alive, and even their shells are rarely found by beachcombers.

There are two orders of scaphopod: the Dentaliida (which may be paraphyletic) and the monophyletic Gadilida. Dentaliids are generally larger, have a shell which tapers uniformly, and their foot consists of one central and two lateral lobes which bends into the shell when retracted. They have strongly ribbed and rough shells. When they sense vibrations anywhere around them, their defensive response is to freeze, making them harder to sense by animals which can detect electrical signals. On the other hand, gadilids are much smaller, have a shell whose widest portion is slightly posterior to its aperture, and have a foot which is disk-like and fringed with tentacles which inverts into itself when retracted. Gadilid shells are usually glassy-smooth and narrow, allowing them to move with surprising speed through loose sediment to escape potential bottom-dwelling predators.

Scaphopod mantles are entirely hidden within their shell. Their foot extends from the larger end of the shell, and is used to burrow. Scaphopods position themselves head down in the substrate, with the tip of the shell projecting upward, but rarely above the level of the substrate. A number of minute tentacles around the foot, called captacula, sift through the sediment and latch onto bits of food, which they then pull into the mouth. The mouth has a grinding radula and cartilaginous oral bolsters that break the bits into smaller pieces for digestion. In gadilids these are structured like zippers where the teeth actively crush the prey by opening and closing on it repeatedly. In dentaliids these work like a ratchet to pull prey into the esophagus, sometimes whole. Their prey are primarily single-celled organisms called foraminiferans, though some will also supplement their diet with plant matter. Scaphopods have no gills; the entire surface of the mantle cavity absorbs oxygen from the water. They also have no eyes, no osphradia, any or other distinct sensory organs. However, scaphopods do possess genes involved in photoreceptor formation and function implying scaphopods may have had eyes that degenerated over evolutionary time. Scaphopods have separate sexes, and external fertilisation. Eggs will hatch into free-living trochophore larvae, which develop into veliger larvae that more closely resemble the adults. Their three-lobed foot originates prior to metamorphosis while the cephalic tentacles develop post metamorphosis.

There is a good fossil record of scaphopods, with them emerging in the Mississippian (Early Carboniferous). The Ordovician Rhytiodentalium kentuckyensis has been interpreted as an early relative of scaphopods.

(source)

Propaganda under the cut:

Fissidentalium metivieri is the largest scaphopod, with a shell length of 18 cm (7.09 in).

While their phylogeny hasn’t been fully resolved yet, molecular data suggest that the scaphopods are a sister group to the cephalopods.

The shells of Dentalium hexagonum and Dentalium pretiosum were strung on thread and used by First Nations of the Pacific Northwest as currency. Dentalium shells were also used to make belts and headdresses by the Natufian culture of the Middle East, and are a possible indicator of early social stratification.

[jades-typurriter]

Secure Connection

As promised: more Posie!! I wrote this one toward the end of last Spring after a couple of conversations with friends regarding the malleability of digital bodies (as well as still having Many Thoughts about the way code can give them new compulsions, after writing something about Annie and a new taur-shaped chassis for a friend's Patreon). Enjoy reading about her dealing with a corporate-mandated "hardware" update!

CW: Genital TF, this is another one that's As About Sex as it can possibly be without being about sex

Posie sat, sulking—steaming, even—in her office. It was a small side room off of the main floor of IT personnel, system engineers, and other technical employees of her corporation. Much like a central server, it was placed for easy access to the department-wide administrative assistant, and much like a server room, it was snug, windowless, and awash with the calming drone and relaxing warmth of an array of exhaust fans. Though she was free to project herself nearly anywhere on the company’s campus, this was where her consciousness was housed, and where she felt most at home. It was also the only place she could get any damn privacy, a luxury that she was deeply grateful for at present.

A newly-downloaded file weighed on the back of the Renamon’s mind. More literally, it was somewhere in the racks of drives that made up her long-term memory, to and from which mission-critical information was transferred in the course of doing business. Had somebody asked where exactly the file was stored, she would have been able to list the specific drive and the exact directory address, but she had de-prioritized the allocation of her processing resources for the download. Once again, she had received an assignment from her superiors, and once again, she was hesitant. She may even have admitted to being recalcitrant. She resented the orders.

The package of data in question was an update for her own software, a suite of new tools to allow management to offload yet more menial tasks onto her in the name of “efficiency”. Forget that she could diagnose a software issue faster than any of the engineers could even open a remote connection to the malfunctioning device. Instead of allowing her to take the reins, they saw fit to divert more of her attention to the least impressive among talents, and the one she already put to use the most often: transferring data.

This wouldn’t have been much of a problem, ordinarily. After all, Posie resided in the beating heart of the network, the nexus through which the vast majority of information was sent and received. It could be… meditative. Parsing streams of ones and zeroes, overseeing the flow of packets, redirecting traffic to equally spread the load across modems and routers so as to optimize travel time. It could even have been considered relaxing, if a worker of her caliber needed to relax. Instead of offering her a vacation (pah!), however, the update felt more like it heralded a demotion, denying her even the ability to pluck like harpstrings the miles of copper and gold that lined her facility. She was expected to deliver this data on foot.

Management justified this humiliation with practical concerns: some information, much like the old records she was often tasked to dispose of, was so confidential that it could not be sent via wireless transmission. Even hardwired connections were too fallible for the likes of next-generation schematics and financial access keys—a single compromised workstation, or compromised worker, could spell the loss of the company’s upper hand in its market. She wasn’t even going to be afforded the dignity of carrying an external hard drive to the destination. That would require the slow and tedious process of physically moving from one place to the next; this was one of the only times that she regretted the freedom of movement that was so coveted by her flesh-and-blood peers.

With no room to make exceptions for security protocol, she gripped the edge of her desk, brow furrowing, eyes squinted shut in consternation. Eventually, she huffed, rose, and turned her attention to her “physical body”, summoning up the file in much the same way that one would approach a plate of food with a pungent odor. The Renamon steeled herself and began to more closely examine its contents. She read the raw code similarly to how one might read words on a page; however, where the turning gears of the organic mind would, almost unconsciously, conjure up an image as a result of those words, her mind kicked off a series of involuntary, autonomic processes.

Her body carried out the instructions on her behalf. Once she started, she had no control until she finally reached a stopcode; it was the nature of being a program herself that code had as much of an influence on her mind and body as her own thoughts, her own will. In opening the package, she reluctantly consented to the changes that management saw fit to make to her. It was better than the eventual forced-deadline sort of update that software companies were so keen on using nowadays, and at least choosing the time and place allowed her to make herself presentable again before having to face another person.

Having parts of her code—her very body—rewritten by the update was a strange sensation, not unlike having your thoughts dictated to you by an outside force. Stranger still was that she could feel the exact delineation between her previous self and the patches of… well, the patch. She could feel it quite strongly, as a matter of fact: beneath her skirt of simulated sky-blue fur, between her legs, she could feel her mesh being edited. Stretched. Reshaped. The vectors that made up the triangles of her wireframe soul were being rewritten, mathematically transformed. A shape began to protrude from the once-flat span at the bottom of her torso, at first round and indistinct, but quickly increasing in resolution.

The Renamon struggled to process the sensations as a long, slender connector began to take shape. This often happened with changes to her body plan; inputs streamed into her mind from directions, locations, that previously never sent any signals, and the new additions seldom had their sensitivity adjusted downward for her convenience. In this case, it was highly sensitive, delivering reams of data to the base of her skull just from brushing up against her own fur, or the gentle flow of air from the computers in her office. It made sense, given that it was supposed to be a high-capacity transfer tool, but she was too busy buckling at the knees and clutching at the desk behind her so she didn’t fall flat on her rear for the thought to occur to her.

Her processors demanded more cooling, kicking into high gear as they formatted the two new storage devices that accompanied the connector, tailor-made for packing confidential data as tightly as possible. The sound of whirring fans filled the room, stirring her fur and sending shivers up and down her back; she could only hope that the rushing exhaust made enough noise to drown her out, whimpering despite herself. The new drives were larger (and more unwieldy) than the ones that were built into her chest, much to her chagrin. She was forced to adjust her stance and her gait as she found her footing again, spreading her legs wider than she was accustomed in order to give them enough room.

The spinning in her head slowly settling down, she slowly began to compose herself once again, taking stock of the new additions. They were cumbersome, to be sure, and she lamented how they jutted out from her otherwise sleek form and burdened her with less-graceful posture. It didn’t even match her fur! The software engineers that had concocted the code had at least included one small mercy: a compartment for the connector to retract into, nestled in the fur above the storage drives. No such luck for the drives themselves. She supposed she would just have to adjust to walking with delicate hardware in tow. As she went to smooth her fur over her lap again, her paw recoiled away. Some kind of… static discharge was left in the fluff. A memory leak, perhaps? The fact that such a malfunction could be caused just from having the connector brush up against her fur appalled her, deepening her frustration even more. They couldn’t even test the update for bugs before shipping it out to her. She shook out her paw and finished arranging her skirt as best she could before working up the composure to finally leave her office.

Picking up the payload for which all this fanfare had been arranged was at least a quick, easy process. She stopped into the office of the manager that had assigned her the task; she offered a businesslike nod and, knowing that she was always itching to skip niceties in the name of saving time, he offered a straightforward wave at his personal terminal. She held a paw over the computer tower and, in the time it took for electricity to arc to her fingertip with a tinny zzzrt, she had already searched his directory for the relevant test files and copied them to the newly-installed drives. Wireless transfer, yes, but only technically. The engineers had specifically asked a member of another division, whose computer network wasn’t connected to their own; it was as though she had picked a folder up from his desk and walked out with it.

Moving the file was just as uneventful. It was far from the first time that she’d navigated the sprawling corporate property, and even if it were, the maps existed just outside the orbit of her thoughts, ready to be summoned to mind at a simple impulse. What she was not expecting, however, was the technician who was waiting in the server room to which she was asked to deliver the file. While she preferred to work in the isolation of rooms that were set aside specifically for hardware, she was far from unused to being in the presence of the other people responsible for maintaining the company’s systems. That said…

“Can I help you?” The Renamon icily asked.

“Oh, I don’t need anything! I’m just here to take notes on the transfer.” Her tone was cheery; evidently, she wasn’t aware how compromising the new additions were. “The time it takes, any obvious issues. I’ll be the one checking the files against the originals, too,” she concluded, hooking a thumb over her shoulder at a monitor behind her.

“I see,” Posie replied through gritted teeth. “You have clearance to see these files, then?”

“Well, they’re just dummy data, ma’am.” At least she was respectful.

“And the proprietary hardware I’ve been… equipped with?” she forced out, keeping her synthesized voice even.

“Oh, for sure I do. I designed it!”

Oh! she seethed. So she knows pre-cise-ly the position he’s put me in.

“Well. I suppose there’s no point in delaying things, then.”

“Ready when you are!”

With tense shoulders, she turned toward the server rack, eyes darting over it, searching for where exactly she was supposed to connect to the array. After glancing over the contents of each drive, she found the one she was supposed to copy the data into—deposit would be more apt, as it was her understanding that the files would be automatically flushed from her system—and found a port that would allow her to access it. Conveniently, it was around waist height. She wondered, crossly, whether that had been an intentional design decision by this engineer as well. As she looked at it, she felt a twinge from the connector; on its own, like a Bluetooth device automatically searching for signals, it slid itself out from its fuzzy little compartment.

Her skin was abuzz, and her fur stood on end. She couldn’t quite tell if it was coming from the connector itself, or if it was the feeling of the programmer’s eyes on her If she could take a deep breath, she would have then. Without any way to stall further, or to tell the leering young woman to take her test files and store them somewhere indecent, she simply pushed forward with dropping off the damned data.

The instant the connector grazed the metal of the port, lightning shot into it, through her body, and into her head, making it swim with electrical potential. A stuttering, lagging thought made its way to the surface of her mind: they really had overtuned the sensitivity. She stifled a gasp and suppressed the urge to lay into the engineer (electrons were eager to flow out of her even without proper alignment with the contacts in the port, and didn’t she know that discharge like that could damage a piece of hardware?!), willing her body to keep pressing the stupid connector into the socket.

Even as she tried to get it over with already, something in the back of her mind compelled her to draw back a bit. If she had been restraining herself from reprimanding the engineer for risking the hardware, then she should at least do it the service of ensuring she was properly aligned, shouldn’t she? She obliged the impulse, and the motion all at once became much jerkier, less controlled. The friction of the port against her connector was enough to send her tail snapping back and forth, and she could tell that the temperature in her own server’s room had risen by a fair few degrees. Back and forth, wiggling side to side, she continued to readjust and realign herself, driven by unfamiliar code and overwhelmed by the signals pouring into her. She lost herself in the task, forgetting herself, forgetting her surroundings, until finally the technician cleared her throat.

“Ma’am,” she ventured, blushing and wide-eyed. “What, um. What are you doing? You should just need to plug it in.”

“I’m.” Her interruption had snapped the Renamon back to reality. She was mortified, tail sticking straight out and back ramrod straight. Her cheeks burned mercilessly. “I’m calibrating the connection.”

“Calibrating?”

“Did you want your files transferred with or without corrupted and incomplete data?” She snapped, hoping that her authoritative tone would head off any debate. “Assign me experimental hardware and then ask me to be reckless with it, hm? Should I be taking notes to give to our superiors?”

“I—alright, I guess you can’t be too careful,” she stammered, sheepishly pressing her legs together. “That was even something I tried to work into the design, so, c-carry on?”

“Thank you,” Posie blustered, turning back to the server rack. She did so slowly, reluctantly relishing the feeling of sliding around within the socket. She allowed herself one or two more “practice” attempts, hoping that it wouldn’t arouse too much suspicion from the engineer. Ultimately, just like before, there was no use in continuing to stall, and when she was able to bring her body to a stop, the rational part of herself was eager to be done with this entire torrid affair.

With more force, she pressed the connector inward one final time, trembling as the latch began to press against the opening. Slowly, agonizingly slowly, she continued, overwhelmed by the volume of electricity surging into her. The latch gave, compressing as it continued to slide inside, until finally it clicked into place, securing her to the array of drives and finalizing the connection.

All at once, a torrent of data poured out of her, an electron tsunami that felt like it threatened to spill out of the socket in which she was hilted. More data was transferred in the span of a few seconds than she was used to consciously processing, having cultivated such skill in delegating and compartmentalizing with background processes. Once again, the world around her was utterly drowned out; the strength fled her legs, and she clung to the steel bar that reinforced the top of the server rack, threatening to topple the entire system. Her self-control abandoned her as well and, forgetting the engineer, she cried out with an airy, wild, distinctly foxlike yelp. She screamed in surprise, gasped at the deluge of information, moaned because there was no room left in her mind for thought to do anything else.

Quickly, the disks of the server rack had finished writing the files she had carried to them, and her own drives were thoroughly purged. In another building, the radiators serving her processors shed heat at their absolute limits, and fans worked overtime to bring her back within her safe operational range. As her overworked circuitry began to chug through the backlog of sensory information, the entire experience caught up with her—including the detail that this entire shameless display had been carried out in front of that underhanded little engineer. She blinked, hard, and whipped her head to face her. For as hot as her own ears felt, the young woman’s face appeared to be glowing even brighter.

“What. Was that.”

“Um—”

“I’m used to new adjustments requiring desensitization, or even adjustment on their gain,” she growled, voice low and eerily even. “But that was a bridge too far to just have been miscalibration. Why did you design it like that?”

“Well, y-you remember how I mentioned, um, having considered an early disconnection?” Posie’s frosty glare didn’t waver, so the tech continued, answering her own rhetorical question. “That was, uh, the safeguard. Against early disconnection. I, figured it’d just be easier to make it so you wouldn’t want to unplug—”

“Do you think you have the au-thor-ity to go making changes to my mind, young lady?!”

“I-I can roll back the update if you want—”

“I think you’ve done QUITE enough!” The Renamon declared, despite herself. Perhaps it was genuine distrust, or perhaps—perhaps she truly couldn’t tell which desires were her own, at the moment. This would require careful study of her own system files.

Another small click broke the silence following her outburst, and the dongle began to retract from the server’s port and back into Posie’s body. Now free to move around, she dusted and fluffed her skirt and leaned down to look the engineer in the eye.

“I trust that you can report to your supervisor that I performed to your expectations,” she hissed. “And that there will be no need for any further discussion of your little project.” The programmer nodded, eyes even wider than before—and cheeks even redder? The Renamon scoffed, sneered, and spun, storming out the door, already allotting time in her schedule for the next time that she would be called upon for such a delivery.

Utterly unsurprisingly, she had been correct in her assessment that her superiors would take every opportunity to save their organic employees’ time at her expense. Confidential deliveries became a regular part of her routine, and though she had great disdain for being reduced to a mere courier for so much of the workday, she insisted upon completing the task to her usual, lofty standards.

Posie was as prompt as she always was, dropping everything to ferry information between privileged parties, striving to reduce latency even in more analogue forms of communication. There was the occasional complaint about how long downloads took once she had finally arrived at her location, but she was quick to remind such impatient recipients that the decision to follow this protocol came from on-high, and that even for someone who worked as quickly as her, great care for the safety of the data was a corner that simply could not be cut in the name of rushing around.

She was as meticulous about ensuring proper alignment with the port, fine-tuning her contact with the wires within, as the first time she had experimented with the new tools, and complaints about noise from the server room were easily dismissed as the usual stress of supporting her formidable computational power. After all, she was often venturing out of the range of her home network, hosting herself entirely on the recipients’ systems; was she at fault when they couldn’t handle the information throughput they asked of her?

Once the deliveries had become more routine, and none of her peers bothered to check in when they felt it was taking too long or getting too noisy, she began to find enjoyment in the solitude of her work, just as with the other, admittedly more tedious, tasks she was expected to carry out. With fewer prying eyes to judge her performance, she could make herself more comfortable while handling transfers. She didn’t have to worry that anybody would walk in on her in the debased state she often found herself in while connected directly to a data center, leaning her full weight on the poor rack, tongue lolling out and chest heaving air to keep her cool. 

Then again, if somebody—especially that little technician who’d saddled her with these “upgrades”—wanted to question her efficacy, that was more than fine by her. Posie was a woman who prided herself in her work, and would seldom turn down a chance to demonstrate her first-rate hardware and unparalleled optimization. She would be more than happy to demonstrate just how quickly she could pump out information, and just how much throughput she was capable of.

Thank you for reading! If you want to see more of my work, you can check it out here and here!

[friendofcars]

Hello! Here is data on point of view distribution across characters in The Dreamer Trilogy (which I will abbreviate as TD3) as a follow up to my TRC data from last year (viewable here). A rather long-winded discussion of the data, methods notes, and some supplemental figures and tables are under the cut. As it was not possible to include all values and stats in this post (nor in the alt text for image IDs), my spreadsheet can be viewed by clicking here,

This project quantifies and visualizes the distribution of chapters and pages in the books of TD3 across characters from whose POVs the story is told. I didn’t have much of a hypothesis going into data collection/analysis, especially not like I did for the TRC data, but I did expect to see Ronan’s POV having the most chapters and pages for the entire series, given the fact that he is the most central of the protagonists. I don’t think page time is the be-all-end-all for a character’s importance, of course, but it is still interesting to consider how spending more time from certain perspectives affects the perceived narrative. I won’t get much into that aspect of analysis in this post, but if anybody would actually like to discuss that, I’d love to!

Results (and Interpretation):

TD3 consists of 173 chapters and 1184 pages (using the U.S. hardcover editions), making the average chapter 6.84 pages. The longest chapter is 16 pages, and the shortest is 1 page.

Figure 1A: The average chapter in Mister Impossible (MI) is considerably longer (9.26 pages) than the average chapter in Call Down the Hawk (CDTH) (6.00 pages) and in Greywaren (GW) (6.40 pages), which makes sense as MI has just 38 chapters while CDTH has 80 and GW has 55 (see Fig. 2). To me, the effect of the longer chapters (and therefore extended time with the current POV character) makes the various POVs feel more temporally distant from one another- not in a narratively incoherent way, but in a way that echoes the sense of isolation experienced by dreamers and weaponized by Bryde as he tries to convince Ronan and Hennessy to abandon their loved ones.

Figure 1B: Chapter length is fairly consistent amongst POVs across the series. Matthew has the longest average chapter length (8.40 page) over a small set of chapters (5 total)- his character development (as told from his own POV) is limited to a small number of instances, which may have stretched his chapters a bit longer. The 'Other' category has the shortest average chapter length (5.13 pages) (Fig. 1B); it includes the typically short chapters from witnesses of Visionary explosions/aftermath (Mags, Dabney) as well as Nathan's manifesto excerpts. (As a side note, I've described the chapters depicting memories from the Barns as 'Mór and Niall.' These chapters do not collectively portray an equal balance of their POVs, but this was the simplest way to categorize them.)

Figure 2A-B: These graphs are representations of chapter distribution across POVs in TD3 in terms of chapter count (2A) and proportion of total chapters (2B). Some observed trends include Declan's proportion of total chapters remaining quite constant throughout the series, Ronan's decreasing, Hennessy's proportion of chapters nearly doubling from CDTH to MI (and staying at a similar proportion to MI in GW), and Jordan's proportion following an opposite trend (consistent proportion in CDTH and MI, followed by a more than 50% drop in GW). Carmen's proportion of chapters also declines after CDTH.

Figure 2C: This graph compares total chapters per character POV over the entire series. We can see that the largest proportion of the series is told from Ronan's POV (53 chapters, or 0.306 of all chapters). To put that in perspective, Hennessy has the next highest number of chapters (26, or 0.150 of all chapters), which is just under half the number of Ronan's. If all characters had an equal number of chapters from their POV (including the miscellaneous POVs as one category labeled Other), they would each have 21.6 chapters, represented by the horizontal dashed line; Declan, Jordan, Carmen, and Hennessy all have chapter counts relatively close to this number.

Figure 2D-E: These are representations of page distribution across POVs in TD3 in terms of page count (2D) and proportion of total pages (2E). Trends are similar to those depicted in 2A-B, but 2E does make Declan's increased proportion of page time in GW salient.

Figure 2F: This graph compares total pages per character POV over the entire series. The dashed line shows that if each character (plus the Other category) had equal page time in the series, readers would spend 148 pages with each POV. Again, page data is similar to chapter data, but comparing graphs 2C and 2F gives a clear visual indicator that Jordan's chapters (on average, 8.11 pages) are longer than Carmen's (on average, 6.08 pages), since Carmen has visibly more chapters in 2C yet nearly the same number of pages as Jordan in 2F.

Figure 3: Figure 3 shows distribution of chapters (3A-B) and pages (3C-D) in CDTH, as well as average chapter length for each character POV (3E). An equal distribution of chapters would have been 13.3 per character, and an equal distribution of pages would have been 80.0 per character. The 'Other' category included chapters from the perspectives of Lock, Breck Myrtle, Shawna Wells, Jason Morgenthaler (and Lin Draper, briefly, in the same chapter), Mags Harmonhouse, and Dabney Pitts. Carmen's average chapter length in CDTH (4.67 pages) is the lowest single-book average for character POVs appearing throughout the entire series. (Nathan's average chapter length is just 1.00 [Supplemental Figure 2], yet his POV only appears in GW via his manifesto excerpts, and while I have attributed these chapters to his POV, I interpret the POV as actually ambiguous. As with Kavinsky's text in TDT, it's not absolutely certain if we are reading from the writer or the reader's perspective [although in TDT, due to the lack of Kavinsky POV elsewhere, it's probably the latter]).

Figure 4: Figure 4 shows distribution of chapters (4A-B) and pages (4C-D) in MI, as well as average chapter length for each character POV (4E). An equal distribution of chapters would have been 5.43 per character, and an equal distribution of pages would have been 50.3 per character. The 'Other' category included two chapters, both with what I deemed omniscient narration. Declan had the shortest chapters in MI (8.20 pages), and Jordan had the longest (11.4 pages, the longest average for a character for a single book in this series).

Figure 5: Figure 5 shows distribution of chapters (4A-B) and pages (4C-D) in GW, as well as average chapter length for each character POV (4E). An equal distribution of chapters would have been 6.88 per character, and an equal distribution of pages would have been 44.0 per character. The 'Other' category included Nathan's manifesto excerpts (3 chapters), 1 chapter from Liliana's POV, and 3 other chapters with omniscient narration. While Ronan never has the longest chapters, his chapters are shorter relative to other POVs in Greywaren, perhaps as a result of the way his chapters are written during his time asleep/in the sweetmetal sea. I have not yet investigated whether chapters tend to be longer while characters are awake vs asleep or dreaming, but that's something that could be measured from the existing data in the spreadsheet! There is also a dramatic drop in Jordan's POV time in GW compared to the previous two books, perhaps because of her increased divergence from Hennessy and desire to establish a life that follows her own narrative.

Other findings: A major difference I noted between TRC and TD3 was the lack of split chapters in TD3. In TRC, the data analysis was made slightly complicated by having to account for the fact that a non-negligible number of chapters would make a distinct and discrete switch between POVs partway through. While I did not observe this in TD3, I did encounter more ambiguous/nebulous POVs as I previously mentioned. The increased presence of omniscience in the trilogy, for me, contributed to the increased sense of scale and stakes compared to TRC. This increased continuity amongst POV (not amongst core/recurring POV characters, but amongst groups of characters/communities depicted in the omnisciently narrated chapters) also contributed to a sense of dissolution of barriers and identities, perhaps thematically in line with Ronan's character development and increasingly holistic perspective of both his humanity and otherworldliness (although Ronan is not necessarily featured in these 'boundary-breaking' chapters). I also briefly looked at occurrences of back-to-back chapters from the same POV; this happens most frequently for Ronan in all three books, mainly in CDTH, and sometimes featuring a dreaming chapter directly before an awake chapter (or vice versa) in immediate succession. Declan (MI), Carmen (CDTH), and Jordan (CDTH) all have a pair of back-to-back chapters at some point in the series; Hennessy has 2 (MI, GW).

Conclusions: In all honesty, despite this project being quite fun and fulfilling and of course, worth doing, I do not think I have any particularly insightful conclusions about the data beyond what I've already discussed. Ronan took up the largest share of the chapters and pages as expected, although I am not sure I expected this to be true by such a large margin. I also was surprised that Declan did not have more chapter/page time, but it is possible that his notable inclusion in chapters from other characters' POVs increases his prominence in the series (and I suppose this is probably true for all characters who frequently appear in chapters outside their perspective). As with TRC, the number of POVs expands as the series develops, often with the effect of increasing the scope of the story's implications, and perhaps, more importantly, showing the story from additional angles that contextualize and/or distort narrative established by other characters' perspectives. I hope you've enjoyed exploring the data as I have, and those interested in my methodology may continue reading below!

Methods:

Data collection was straightforward in the sense that I simply counted the pages in each chapter and then assigned each chapter to a character based on the POV represented. The POV character assignment was more difficult than it was for TRC, as TD3 has more omnisciently narrated chapters, which in itself is easy to categorize, but they often zoom in on or are 'biased' towards the experience of a particular character, so I had to make some decisions as to what, for me, constituted sufficient focus on a character’s internal narration and expression vs. omniscience. In the spreadsheet, I took notes on these more subjectively driven decisions. Again, you can view it here! It also contains data on whether the chapter is from an awake or dreaming POV, and has the first lines of each chapter, among which are some fun repeating patterns. 

For bar graphs with dots, each dot represents a single chapter. You may also notice that the graphs are missing p-values from statistical tests this time around! This is because, since completing the TRC data, I’ve realized that such measures of uncertainty re: significant differences are not appropriate for my dataset, which is not a sample representing a population, but rather a complete group of chapters (so parametric tests are not necessarily helpful or valid). However, I still like to run the tests for my own amusement and to see what the results would be if this were a dataset for which ANOVA and contingency tests were appropriate, so I have standard deviation bars on the graphs where calculable (but no standard deviations in the text of the results section for legibility) as well as the p-values in tables at the end of this post for anyone also curious. I did still calculate the numbers of chapters and pages that would represent an equal distribution across POV characters, which are represented by the dashed lines on the relevant figures. I think this is helpful to visually gauge 'over-representation' and 'under-representation' of character POVs.

Below are the supplemental figures showing all character POVs rather than lumping some together in an 'other' category. The MI data in figure 4 is not expanded below because the chapters designated as 'other' were omniscient and thus would have remained in the same category.

And finally, here are the omitted p-values, if you'd like to pretend along with me that all the chapters in TD3 are not a complete set but rather a representative sample of a greater population of chapters that's out there in the universe. :) When I give a p-value below the 0.05 threshold but still write 'no significant differences amongst any combination of characters, I mean that the p-values generated for the comparisons between each possible pair of characters were all above 0.05, which are distinct from the overall p-value generated from the ANOVA.

[covid-safer-hotties]

New COVID Variant XEC May Outpace Others This Fall - Published Sept 18, 2024

"The virus is always going to be mutating away from what it was in order to get more efficient at infecting individuals," Adalja said. "So I think this really highlights the fact that a universal COVID vaccine, or some vaccine with different technologies, perhaps a nasal vaccine and using mucosal immunity, all of those things are important."

What if, get this, we prevented covid cases by improving ventilation, mandating air filtration, and wearing masks in public? Wouldn't that accomplish the same goal right now? Every mutation takes us further away from the current scientific fantasy of a universal covid vaccine. We have to stop cases to make this dream a reality.

by Sophie Putka

The new COVID-19 variant XEC may overtake others in circulation to become dominant in the coming months, experts said, but will not prompt a meaningful change in symptoms or vaccine response.

So far, the CDC's variant proportions tracker has not registered enough cases of XEC in the U.S. to report it. (The agency's projected estimates for the 2 weeks ending in September 14 currently show KP.3.1.1 and KP.2.3 as the leading variants, with 52.7% and 12.2% of national cases, respectively.) Another estimate using data from the variant tracker GISAID has XEC at 1.11% of U.S. cases as of September 15, with around 48 sequences reported.

First detected in Germany in June, it's been found mostly in Central Europe, representing 10% of cases, according to the U.K.'s Science Media Centre.

"XEC represents a fairly minor evolution relative to the SARS-CoV-2 diversity currently in circulation, and is not a highly derived novel variant such as those that were granted Greek letters," like Alpha, Delta, and Omicron, Francois Balloux, PhD, a computational biologist at University College London and director of the UCL Genetics Institute, said in a Science Media Centre statement.

Experts noted that while XEC may have a small advantage in transmission, available vaccines are still likely to provide protection from serious illness.

XEC is a "recombinant variant of some of the other Omicron lineages that have been around for a while, and it does appear to be more immune evasive, giving it a transmissibility advantage in the population with the immunity that it has," Amesh Adalja, MD, of the Johns Hopkins Center for Health Security in Baltimore, told MedPage Today. "But it doesn't really change anything, just like the last variant didn't change anything, or the one before that, one before that, or the one before that."

Currently available COVID vaccines target slightly different subvariants. The updated mRNA shots aimed at KP.2 from Pfizer-BioNTech (Comirnaty) and Moderna (Spikevax), as well as Novavax's vaccine targeting the JN.1 variant lineage, are still protective against the most serious consequences of COVID infections, experts said.

"If this becomes a dominant variant, it will decrease the efficacy against infection of the updated vaccines, but the updated vaccines will still be durable against severe disease [and] hospitalization, and that's what is really the primary function of our current, first-generation COVID vaccines," Adalja said.

Still, he emphasized, the rapid mutation of the virus underscores a need for a different kind of vaccine than those currently available if the goal is to protect against infection rather than just severe disease.

"The virus is always going to be mutating away from what it was in order to get more efficient at infecting individuals," Adalja said. "So I think this really highlights the fact that a universal COVID vaccine, or some vaccine with different technologies, perhaps a nasal vaccine and using mucosal immunity, all of those things are important."

[miyuskye]

HERE I GO with this super interesting event from the All Ships Ship Week event hosted by @ficwip

The ship dossier! And what ship I could've dossiered if not my current hyperfixation, aka Jon/Elias??? Sooo, the thing with loving a podcast is that you don't get a lot of official art, since the physical descriptions are also very scarce by author's choice. BUT! they recently made a TTRPG game based on the podcast, which these semi-canon designs. My personal image of the characters in influenced by the huge amount of fanarts circulating around, but, probably an unpopular opinion, I like these designs too. With reference to the image, the top one (not in the ship sense) is Jon, aka the Archivist, aka the pet project/obsession and the bottom one (again, not in the ship sense) is Elias/spoiler, aka the mentor/obsessed.

It would have been great, if I did actually understand the assignment and not gone off the trail with a full AO3 statistical analysis. Under the cut because probably not a lot of people are interested in my ramblings. The dossier is intended for both people familiar with the series, but also for people who know nothing about it. Warning for sparse spoilers about the whole TMA series (not TMP since I still have to listen to it!) (as I said, Elias is a big spoiler himself lol)

Let's begin this trip with a biiig disclaimer. Sadly for us avid AO3 users, the AO3 fandom does not represent the fandom in whole, so these stats are based only on the number of works in the AO3 context. Looking around at non-fanfic related site, i.e. reddit, I know there are some JE shipper there too, though I can't really be sure in what percentage with respect to the non-shipping community (or the people only shipping the canon couple). Links to the guru of fandom stats! toastystats (tumblr), AO3. There's also a github repository but I personally found it a bit cranky to use and it doesn't use an AO3 updated DB, though for big data statistics is fine due to the central limit theorem but for smaller fandom/tags it might be a bit inaccurate. Also the code is in python 2, which is now a bit difficult to use. I personally made my stats by doing targeted searches using the AO3 search function! Super easy to use, albeit a bit repetitive. Stats were made on Oct, 19-22, 2024. Again, I think the results won't change much through the years, especially regarding the main TMA tag data, but who knows if JonElias will surge in popularity (hehe it's a distant hope, I'm pretty much sure that the population distribution is already well-established).

TMA (The Magnus Archive) is a horror podcast, following the events of Jonathan Sims, aka Jon, aka the first part of my ship, who works at the Magnus Institute. This Institute is a facility researching in supernatural events and records supernatural encounters in the form of statements given by volunteering people. Jon is the Head Archivist, meaning he manages the statements and records some "odd ones", as per request of the Head of the Institute and his direct superior, Elias. Sooo yes, he's also his boss. :) lovely for them.

My lovely idiots are the 3rd most popular ship! Such a big achievement for me, who I usually ship obscure ships. As of today, we have 1434 JE works out of the whole 29751 works in the TMA tag. Way to go, JE community, let's keep this up!

The Jon/Martin ship is actually canon in the podcast, so that big percentage, compared to other fandoms, is largely explained by that (instead of simple popularity like Oikawa/Iwaizumi in the Haikyuu fandom). My other favorite ship is Jon/Tim, and I proudly contributed to that 2.78% (ofc also to the 4.8% of JE but it seemed quite superfluous to write).

Fun fact: speaking of spoilers, Elias' character tag in AO3 is a MASSIVE spoiler. It was what ruined the plot twist for me, because I looked for fanfics around ep 40ish (out of 200) and got that spoiled :( I understand why AO3 did that, because before the reveal the tags referring to Jonah and Elias were separated and I guess they wanted to unite them (since I also read some Jonah/Jon works before the reveal - all of them ended up having Elias being somewhat connected to Jonah OF COURSE, but I believe that before The Reveal there was also the belief that Elias was one of his descendants. I became part of the fandom after that, though, so it's just speculation based on older posts I came across).

This is probably my most favourite slide. JonElias has the highest Mature-to-Gen ratio (based on the AO3 rating system) with respect to the other ships. Jon/Martin, being 40% of the works also leads most of the general fandom stats, so it's more correct to actually cite the ship that makes the stat. I also believe that a lot of the more Gen-oriented fics feature Jon/Martin due to them being canon, that is also one of the possible factors influencing their and the whole tag ratios. Due to this, I believe that the Elias/Peter ratio might actually influenced by that, since they're a non-conflicting couple with the main one and are thus frequently included in their fanfics. The other fave of mine also has a higher Mature-to-Gen ratio than the general one, but not as high as JE.

Jon is the main character, so it's obvious that he is the most cited in all the works. Elias is the villain, so it's not so strange. Also, this refers to the characters tags, and this means that Elias might be included as a character even in other ships-based works. I believe the same happens with Tim, since ships with him have a lower presence in the fandom, but he is the third most included character. It's probably because he gets included into most of the Gen/JMart works.

These are the most used AO3 tags for the JonElias main ship tag. Do I really need to explain? They just do the talking in my place lol

A few words on the Alternate universe tag: AUs are somewhat canon in the show, due to plot-related reasons, and I believe this gives us space to imagine, stories where Jon is as deranged as Elias without denaturing canon. I personally believe Jon has the capacity of being feral as, if not even more than, Elias. Canon showed us a glimpse of what we could have but ended up not getting, again, due to plot-related reasons. Some fanfics are based on those glimpses. Also the Do not Archive will be an interesting topic to talk about later!

These are the most used tags for the individual characters. Some of them are also matching but not in their JE tagged works. For example, the tag Fluff might be present in 12% of Elias' works but more than half of those works are Jon/Martin-based works, so he's included in the work but, in a way, not actively participating in the fluff. Also, Jon is canonically asexual, hence the related tag! A few words on that, this doesn't and rightly won't stop people from producing M and E-rated works with him and characters (not necessarily Elias), contrary to what some people might think. And I assure you, as an asexual person, that no one of the JE fanfics I read (even the ones without the Asexual character tag) erased Jon's asexuality. If anything, the ones where Jon's asexuality was present and acknowledged were also my favorites!

Small digression on the Do not archive tag. I noticed that both JE and Elias' tag had a percentage of works being under that tag. Which is used when an author does not want the series staff to read their works. It's mostly used on M+E works (77% of DNA tagged works are M or E rated on AO3), as one would expect. At first I guessed it was related to the pronounced M-to-T ratio of the JE tag (which is even more pronounced on the DNA tag), buuut it turns out the main cause was just a quirk of the data/bias of the data case. As I said, there are only 1434 (as of end-October 2024) works in the JE tag and this means that this number can be biased by a single external source, which causes the shift in the data. This means that this is not a trend!

By excluding the cause from the analysis, the Do not archive tag percentages for JE are still higher than the other ships, but not by such a large margin (around 7% which makes sense).

Nothing to say here, the series reaching its peak in terms of fandom response and also due to COVID making people consume more media content, the JE rise followed the general raise of fanfics in the TMA tag. Which isn't surprising but not to be taken for granted either! Another sad but probably not a trend fact is that Jon/Elias production was slightly more flourishing during the earlier years of the series (especially 2018-2019), than it is now. This might probably related to a ship actually being made canon or probably fandom disappointment in the TMA finale (which I can understand). I read in a lot of earlier JE fanfics very excited comments about "omg I can't wait to see him and Jon in s4/5" and I was like *sad violin noises*, because they didn't get the amount of (canon-expected) interactions the JE fandom thought they would get. Again, this is just speculation and to be taken with a grain of salt.

Unexpectedly, M+E JE works have more words that Gen-rated ones (expected on the JE tag due to their M-to-T ratio, but kinda unexpected compared to the whole TMA tag).

JE fanfics are slightly more kudo-ed and bookmarked than the general fandom trend.

A conclusive remark, is that I made this just to see what behaviours could be extrapolated from such a tiny tag in an otherwise medium fandom (as for 2020, median number of fanworks in labelled big fandom was 45k. Havign roughly half of that number means that TMA is, on AO3, a medium fandom to me).

Anyhow, I wish you happy JonElias day which for me is once again every day since twp months ago :)

[cyberpunkonline]

What is a Cypherpunk?

The term "cypherpunk" refers to a movement and a community of activists advocating for the widespread use of strong cryptography and privacy-enhancing technologies as a route to social and political change. Emerging in the late 1980s and early 1990s, the cypherpunk movement is a confluence of libertarian political philosophy, hacker ethos, and cryptographic science.

The Core Traits of Cypherpunks

1. Advocacy for Privacy and Anonymity: Cypherpunks champion the right to privacy, emphasizing that individuals should have control over their personal information and digital footprints. This advocacy is often in direct opposition to government surveillance and corporate data collection practices.

2. Use of Cryptography: The cornerstone of the cypherpunk movement is the use of strong cryptography to secure communications and transactions. Cypherpunks believe that through cryptographic techniques, individuals can protect their privacy in the digital world.

3. Open Source and Decentralization: A significant trait among cypherpunks is the belief in open-source software and decentralized systems. This ethos promotes transparency, security, and resistance to censorship and control by central authorities.

Who are the Cypherpunks?

The cypherpunk community consists of programmers, activists, academics, and technologists. Notable figures include Julian Assange, the founder of WikiLeaks; Jacob Appelbaum, a former spokesperson for the Tor Project; and Hal Finney, a pioneer in digital cash systems. The manifesto "A Cypherpunk's Manifesto" by Eric Hughes (1993) [https://www.activism.net/cypherpunk/manifesto.html] eloquently encapsulates the philosophy and ideals of this movement.

The Cypherpunk Movement

Cypherpunks are not a formal organization but rather a loosely associated group sharing common interests in cryptography and privacy. The movement's origins can be traced to the “Cypherpunks” mailing list, started in 1992 by Eric Hughes, Timothy C. May, and John Gilmore. This list served as a platform for discussing privacy, cryptography, and related political issues.

Relation to Cyberpunk Principles

While cypherpunks share some overlap with the cyberpunk genre of science fiction, they are distinct in their real-world activism. Cyberpunk literature, like William Gibson's "Neuromancer" (1984) [https://www.goodreads.com/book/show/6088006-neuromancer], often presents a dystopian future where technology is pervasive and oppressive. In contrast, cypherpunks aim to use technology, specifically cryptography, as a tool for empowerment and resistance against such dystopian futures.

Notable Contributions and Technologies

The cypherpunk movement has been instrumental in the development of technologies that emphasize privacy and security:

Tor (The Onion Router): A free and open-source software for enabling anonymous communication [https://www.torproject.org/].

Pretty Good Privacy (PGP): A data encryption and decryption program that provides cryptographic privacy and authentication [https://www.openpgp.org/].

Bitcoin: The creation of Bitcoin by an individual or group under the pseudonym Satoshi Nakamoto was heavily influenced by the ideas of the cypherpunk movement. It embodies principles of decentralization and financial privacy [https://bitcoin.org/en/].

Wikileaks: Founded by Julian Assange, WikiLeaks is a multinational media organization that publishes news leaks and classified media provided by anonymous sources [https://wikileaks.org/].

Conclusion

The cypherpunk movement is a critical lens through which to view the ongoing dialogue about privacy, security, and freedom in the digital age. While not an organized group, the collective impact of cypherpunks on modern cryptography, internet privacy, and digital rights is profound. As digital technology continues to permeate every facet of our lives, the principles and contributions of the cypherpunk community remain more relevant than ever. - REV1.

[thewildwaffle]

Take Me Out to the Ball Game

-This is kind of a continuation of my other short "Injuries" - this is from a prompt given to me about aliens' reaction to how complex human shoulders are and how we can throw hard and accurate without hurting ourselves.

***

“Take me out to the baaaaaaall game! Take me out with the crowd!” Human Vincent all but shouted the words to the tune he and Human Kate had been singing off and on the entire time they’d been “decorating” the rec hall.

Captain Kar’rim looked around at the humans’ efforts of setting up for a ‘party’ in one of the ship’s smaller rec rooms. It wasn’t much, but it looked nice. To be fair, the event was fairly last-minute and they’d made do with what they had on hand. The ship had just left hyperspace last rotation after a long-distance run to nearly the edge of the galactic arm. As per protocol, as soon as the ship was back in range of the Central Galactic Communications Network, an information update packet was downloaded.

Somewhere in all that data, one of the humans found a mention of a major sporting event from their home planet that was available for streaming upon request. They submitted the request and it had been quickly granted. Instead of just watching it immediately, it was unanimously decided that the humans would instead hold a “watching party” and invite anyone on the crew who was off-duty at the time and interested in participating. Captain Kar’rim had come by just to see how things were going and had ended up sticking around after he saw what they’d done with the rec hall.

There were long strings of curled paper strung from one side of the room to another. The humans had the video stream queued up and projected against the wall. All cushions from the chairs that were not black, red, gray, or white had been removed and, as he was told, stowed away in some closet nearby. The tables had been moved closer to the seating area and were covered in various trays of different foods. The humans themselves were decked out in strange uniform-looking shirts with numbers embroidered on the backs. Well, Vincent, Leo, and Kate were. The others just wore their casual rec clothes in colors that matched.

It wasn’t just the humans either. There was quite the crowd milling about excitedly by the time Kar’rim entered the rec room. He knew the humans on his crew were very social and friendly, they had a warm and comforting presence. He knew they’d made a lot of friends on the ship, but he was still surprised by the crowd around him now.

“Buy me some peanuts and Cracker Jacks!” Kate had joined in with Vincent’s ‘singing.’ “I don’t care if I never get back, so just root! Root! Root for the home team!”

Suddenly all the humans were singing along with varying levels of volume, much to everyone else’s amusement. “If they don’t win it’s a shame, for it’s ONE! TWO! THREE strikes you’re out in the old! BALL! GAAAAAAAAAAAAAME!”

“Oooh, dinner, and a show,” Booka Vern chuckled as he tossed one of the foods from the tray into the air and caught it in his mouth. It was a trick he’d learned from one of the humans.

“I know peanuts are a type of plant from Earth,” Effyn Merl spoke up while looking over the table of foods, “but what are cracker jacks? If they’re anything like their name implies, they sound fun.”

Human Kate pointed at a bowl to Merl’s right, “Those are Cracker Jacks. Kind of. They’re homemade. Basically, it's just hardened caramel popcorn mixed with peanuts. The bowl has a yellow sticker, so everyone needs to check the allergy list over there to make sure it’s safe to eat.”

Kar’rim looked at the list. He was very impressed to see that they had made a color-coded list of possible allergens that corresponded with labels on trays and bowls spread out across the tables. The humans had really put a lot of work into this party and made sure as many of their crewmates who wanted to join could do so safely.

“If everyone’s okay with it,” Human Leo shouted, “I’m going to get the broadcast started. They always have a bit of the warm-up and show the first pitch being thrown and all that, so by the time everyone gets food and settles down, the game should be close to starting.”

No one disagreed, so Leo hit play and everyone grabbed plates gathered foods they could eat, and found a comfy spot to settle down to watch the game. There was a lot of chatter and a lot of questions about the basics of how the game they were about to watch worked. Most everyone had seen the humans throwing baseballs around before on their downtime, but this was the first time anyone had actually seen how it all came together to a whole sport that some humans spent their entire professional careers playing.

Kar’rim had not intended to stay. He was just going to check in for a moment and leave to spend his precious downtime resting or maybe taking a stroll through some of the corridors on the lower level of the ship. But now, with everyone settling down and the players on the projection taking their places on the field, he had to admit he was very curious. The excitement was infectious, and he couldn’t imagine wanting to do anything else but watch as he found a comfortable spot to sit.

The game was, to say the least, not exactly what he thought he’d been expecting. It was a strange mix of one-on-one between the human in the box holding a bat and the human on the pile of dirt in the middle of the square (or diamond as Kate corrected someone. It was a square though.) and a full, working-together team sport. If the human in the box hit the ball with the bat, suddenly it activated the roles of the rest of the team on the field. They would run, dive, and throw with practiced precision.

Kar’rim felt his mandibles drop as he watched the first few of such throws. He knew the humans on his crew could throw with insane accuracy and speed. Stars above, he’d seen the results of what happened when Human Kate had been hit in the face after such a throw! But what he saw on the broadcast was like nothing he thought could even be possible!

“What the frewan?!” Effyn Merl exclaimed. Normally, Kar’rim would have scolded such foul language, but he was in a bit of a state of shock and had to agree that the outburst felt warranted.

“How did he do that?” Merl pointed at the projected human who nonchalantly picked the small white ball from his glove and threw it (this time much slower and gentler) back to the pitcher. “How did that other guy throw the ball like that? I could barely see it move - it was like he teleported it!”

“Do we have the conversions of the speed from miles per hour to something the rest of us can understand?” Booka Vern asked between mouths of plain popcorn.

“I don’t think so for the throws in the plays,” Human Vincent scanned the screen, “but this pitcher usually throws around 93 mph, and I think that comes out to somewhere around 120, maybe 130-ish glatts per segment?”

“You’ve got to be pulling my tail!”

“I swear I’m not! I’ll look it up if you think I’m lying!”

Kar’rim shook his head. He believed it. He thought back to when Kate had been sent to the infirmary after getting hit by a baseball that had been traveling around 80-ish or so glatts per segment. He thought she was going to die that day. He’d underestimated humans back then. Even now, he still learned new things about them that surprised him. Like how their arms and shoulders were basically deadly projectile-launching weapons.

“Does it hurt?” One of the stransi’s on the crew piped up from where she was coiled on her favorite cushion.

Human Kate looked over, “Does what hurt? The catch or the throw?”

“Uhhh, well, the throw. But wait, uh, does the catch hurt too?!”

“Not usually, you catch the ball between your fingers and thumb, and the glove protects your hand from contact. And the throws don’t hurt at all.”

“At all? What are their arms made of? Do they have some sort of implants?!”

“Uhhh… no? It just takes a lot of practice. I guess it could hurt if you don’t stretch before, or uh, I guess some pitchers need to take special steps to take care of their arms since they throw so much.”

At this point Demfar, the ship’s head medic, spoke up from between bites of various foods he’s mixed into a bowl. “The human shoulder is a very complex structure. The joint itself is one of the most flexible in their entire bodies.” He took another bite. “The downside is that it’s not as stable as other joints, and is thus prone to injuries. I wouldn’t worry about it much though, “ another bite, “ if these humans do this as their full-time employment, I’m sure they take the proper steps to avoid injury and always listen to their physicians.” That last bit felt a bit pointed, especially since Demfar turned to stare down Human Leo, who cleared his throat and shifted a bit uncomfortably in his seat.

There were a few chuckles, but soon all eyes were back on the game as the human in the box swung and hit the ball so far that the ball flew right out of the stadium, far beyond any hope of being caught. The humans were suddenly on their feet and cheering. Most looked around surprised, except Booka Vern who sat his popcorn down carefully and stood up to bound and cheer as well, looking a little confused but happy to join in.

It was explained that the hit was called a “home run,” and that the batter, as well as the runner “on base,” could then run “home,” thus scoring points. It seemed simple enough to Kar’rim, pretty straightforward. He was sure there was plenty more to figure out about the rules and reasonings, and he knew he’d figure it out while he watched, or while the humans explained the rules as the game went. Overall, he felt it was very impressive. This game took a lot of accuracy from every player. It was certainly more than just throwing a ball back and forth to each other.

He was once again reminded how thankful he and the rest of the Galactic Alliance were that humans were friendly and on their side.