#Nest JS

[technical-origami]

Welcome to Technical Origami, your go-to destination for state-of-the-art Nest Js Development Services. As a premier Nest Js Development Company in UK, we pride ourselves on delivering high-performance, scalable, and customized solutions that cater to the unique needs of your business. Our experienced team leverages the power of Nest Js to build robust, maintainable, and enterprise-grade applications that propel your digital success.

[tapanacharjee]

SOLID Principles in NestJS

NestJS is a powerful framework for building efficient and scalable server-side applications. Leveraging TypeScript and strong design patterns, it encourages developers to write clean, maintainable, and testable code. One way to achieve this is by applying SOLID principles. What are the SOLID Principles in NestJS? SOLID is an acronym for five design principles intended to make software designs…

[codeonedigest]

Nestjs Middleware Tutorial with Coding Example for Beginners | Functiona... Full Video Link -      https://youtu.be/3-l7fk1CFQ8 Check out this new video on the CodeOneDigest YouTube channel! Learn nestjs middleware with example. Learn how to create middleware, what is functional & global middleware #nestjsmiddleware #nestjs #nestjstutorial #middleware #dependencyinjection #nodejs #javascript #codeonedigest@java @awscloud @AWSCloudIndia @YouTube @codeonedigest @nestframework @typescript @Shopify @springboot @nodejs @JavaScript

[kyoukamiiz]

rody i love you but your hair kills me..every time i draw this man he has a different hairstyle like??????

i mean I've definitely got better at drawing his hair so thats something

oldest to newest sketches I've done and i just realized i never finished any of these wips...

[opal-owl-flight]

*a pj striped inkling with cyan blue ink walks up to neo*

I got a question for you neo. Did you have any...I'll just be blunt. I hate beating around the bush. Contact with mamalian ink caused any mutations? And unless yer some sorta dodging god I highly doubt you ain't touched the stuff. Before ya ask how I know of th' stuff, I have a partially fuzzy friend who wasn't always that way. And im a friend of yer senior advisor. (How's he holdin' up btw?

*they have a heavy splatlandian accent*

Her own accent is thick, interlaced with growls and clicks reminiscent of salmonkind.

“An I see vis’ns of a wrld looong gune... Ancient mem’rries o crrreachers asleep ‘nda oor feet. Dead soongs. Dead mel’dis. Elegies.

heheheh…fun stuff, rrrlly.”

[isle-of-misfit-joys]

this is the nicest my bed has ever looked

[lyrebirb]

fjfddfs almost done hehehe

[liamastatine]

I. Need human interavtion

[kamiya-memo-nagoya]

post cssやってみたのでその時に見てた記事。 なんか色々調べたけどGulpで使うのが一番良さそうだったのでこちらを参考に対応してみた。

まずscssを使わずにネストcssでやりたいというのが今回の契機なのだが、ネストcssって古いIphone（～8ぐらいまで）が対応してないんよね。。。

さすがにまだ使ってる人結構いるので、これはそのままでは無理となったとき��、post cssの記事を目にした。

前からあったのだが、いわゆるcssでコンパイルしてる感じ。やってることは変わらないが、書き方が昔と同じ方法で行けるのでめんどくさくはなくていい。

あとこの記事だと自動的に監視してくれる記載がないので、注意。このままだと毎回実行する手間が出てくるのでそのあたりはまた違う記事調べて実装することはオヌヌメする。

使ってみた率直的な感想はpreprosを使ってたときのscssとあまり変わらない・・・ｗ

でも今後発展してきてネストcssがpost cssなしでも対応できそうになったらこの対応も吉かもしれない。何にせよ、まだ他のものには流用できそうにはないな・・・。

ということでまたやりたくなったときのためにここにメモしておく。

[tapanacharjee]

SOLID Principles in NestJS

NestJS is a powerful framework for building efficient and scalable server-side applications. Leveraging TypeScript and strong design patterns, it encourages developers to write clean, maintainable, and testable code. One way to achieve this is by applying SOLID principles. What are SOLID Principles? SOLID is an acronym for five design principles intended to make software designs more…

[peanutheaddd]

new peanuthead au 😭😭😭😭 cant stop putting these beasts into situations

extras + au deets below cut

essentially this au is where current petey and older petey switch bodies and they get up to various shenanigans . LOL . theres not That much of a plot and not much rlly changes perse . its just a silly situation .

current petey is after he starts living w dog man long enough such that they got a routine going . atp petey secretly likes how domestically hes been living and he has Not been handling that revelation well LMFAOOOO

older petey is married (probs about 10 years atp) + he basically just sent lil petey off to college before the switch and he was handling it poorly . LMFAO me when im in a struggling competition and my opponent is petey t cat

lil petey saved him and petey knows that Very Very well. caring for him became his new purpose and helped him turn his life sround so now that lil peteys off living his own life hes kinda lost and it freaks him out really badly . he misses his son so damn bad bru 😭😭😭😭 bro was not prepared for empty nester depsair

thats why he gets so emotional in the comic LOL . seeing lil petey as a little baby again is basically a dream come true for him . he misses baby lil petey so bad 😭😭😭😭

the switch happens bc (current) petey makes some new body switching invention boogaloo and he thinks that it didnt work and calls it a day but it Did work it just took effect overnight instead of immediately like he had expected . also the body switching invention was across universes instead of within a single world like he had intended. LMFAO His stupid baka life 😭😭😭

older dog man is retired at this point. hes also kinda mellowed out bc hes older . older dogs are chiller and that applies to dog man too LMFAO . he doesnt have the stamina to be that high energy anymore

older dog man can recognize the switch almost Instantly bc peteys demeanor is waaaaayyy too different and too similar to how he used to act 15 years ago .

older dog man tries 2 be understanding and give petey space bc he knows that hes not his petey anymore but he gets separation enxiety really bad and he misses his petey Really Really bad. especially bc atp lil peteys not living w them anymore so he js feels Really lonely. my goat 😭😭😭😭

older petey is having the time of his life. his baby is a baby again and his body is light and he doesnt have back pain anymore and he doesnt need glasses to see . however he Knows his dog man gets separation anxiety and needs his daily quota of physical touch (never underestimate a mf whose love language is ohysical touch) and he knows that the past him would Not give him that . so he Is having a good time but hes also constantly worrying about how his dog man is doing .

current petey meets older lil petey at some point and he feels a crushing sense of despair about it 😭😭😭 in my mind dog man comforts him and tells him his petey also didnt handle lil petey growing up very well .

eventually the two peteys sync up the body switching thingy and go back to their og worlds . i assume when they switch back older peteys reached peace abt his empty nest despair probs thanks to lil petey . and current petey has a bit of a different perspective on both dog man And lil petey . smth smth valuing the time he has w them Now. yah. #corny but thats how i like it YAYYYYYY

lil petey can immediately tell that older petey isnt His papa . he can do that in canon so he can do it here too lol . id assume it kinda confuses him tho bc he can tell its petey but hes too different to be PETEY ygwim

ok thats it i think

[codewithnazam]

Calling Js Promise Inside Another Promise: A Real-World Example

Dive into the world of JavaScript promises! Learn how to call a js promise inside another promise, with real-world examples.

Introduction In the world of asynchronous JavaScript, calling a Js promise inside another promise can enhance the efficiency and readability of your code. Let’s explore this concept through a real-world example. Consider a scenario where you need to fetch user data from an API and, based on that data, initiate a secondary operation like fetching additional details for each user. “If you’re new…

[sh4nksslvt]

CLINGY MUCH? | ONE SHOT

Shanks x GN!Reader

Zoro x GN!Reader

Mihawk x GN!Reader

a/n: this js me trying to write ffs, this is experimental and for fun only so expect this ff cringe and oc

tags: sfw, fluff, soft, ooc(?)

masterlist | ko-fi

: 𓏲🐋 ๋࣭  ࣪ ˖✩࿐࿔ 🌊

SHANKS

You were many things aboard the Red Force—calm, sharp-tongued, and painfully unbothered by Shanks’ endless antics.

You were also completely unaware of the fact that the most feared (and flirted-with) captain in the New World couldn’t seem to stop touching you.

Not in a creepy way. Not even in a romantic way… at least, not that you noticed.

He’d toss an arm around your shoulders like it was a habit. Rest his hand on your waist when laughing. Tug you into his side when something “dangerous” happened, like a slightly aggressive breeze or a seagull flying too low.

You just chalked it up to him being Shanks.

Until, one bright morning, the crew decided enough was enough.

It started with Benn Beckman sighing dramatically as he walked onto the deck.

“Do you two need a room or something?”

You blinked from where you stood, arms crossed. “We’re not even doing anything.”

Benn pointed. “His hand has been on your lower back for ten minutes.”

Shanks blinked down at his own hand like it betrayed him. “Huh. Didn’t even notice.”

You raised a brow. “Are you okay? Do you have tactile issues?”

Lucky Roux snorted as he passed by with a turkey leg. “Yeah, it’s called ‘falling for someone and not knowing what to do with your hands.’”

Shanks turned red. You remained… utterly unaffected.

“Touch-starved pirate disease,” Lime Juice muttered, jotting fake notes like a doctor. “Tragic. Symptoms include: prolonged physical contact, excessive grinning, and spontaneous cuddling in public.”

Hongo popped his head out of the crow’s nest. “I saw him brush your hair behind your ear during the storm last week.”

“That was because it got in their face,” Shanks defended.

You nodded. “He didn’t want me to get stabbed by my own bangs. Very heroic.”

“You’re wearing a braid,” Yasopp called from the helm.

A long pause.

“…Okay, I’m not good with excuses,” Shanks muttered, rubbing the back of his neck. His hand bumped yours in the process.

You tilted your head, eyes narrowing. “Captain.”

“Yes?”

“You’re touching me again.”

“...I genuinely didn’t notice DAHAHAHA.”

The crew erupted into laughter.

You blinked slowly and glanced down at your joined hands, then back up at him. “You’ve been holding my hand for a minute now. You good?”

“Maybe.”

You stared.

He stared.

“…You’re kinda warm,” he added, grinning.

“I’m wearing gloves.”

“Exactly. Impressive.”

You didn’t smile, but your voice was flat with dry humor. “You wanna marry me, too? Get it over with?”

Shanks choked. “Whoa—what?”

“You’re already touching me like I’m your lover. Might as well commit.”

The crew howled.

“I’m starting to like them more than you, Cap,” Benn said, lighting a cigar.

“They’ve got more bite,” Lime Juice grinned.

Lucky Roux offered you a celebratory turkey leg like a sword. “You just proposed better than he ever could.”

You calmly took it, giving a single nod. “Thanks. I accept my own proposal.”

Shanks was still frozen. “Wait, are we actually engaged now?”

You took a slow bite of the turkey leg, deadpan. “Keep touching me like that, and you’ll owe me alimony.”

ZORO

You were minding your own business—arms crossed, eyes half-lidded, back leaned slightly against the Sunny’s railing—when a familiar weight thunked into your side.

Again.

You didn’t flinch, didn’t glance, didn’t even blink. Just spoke.

“Zoro.”

“What.”

“You’re doing it again.”

“Doing what.”

“Treating me like a living chair.”

He grunted. “You’re stable. And not annoying.”

“That’s a compliment?” you asked, still deadpan.

“Take it or leave it.”

The crew had noticed. Of course they had. This was the sixth day in a row Zoro had casually latched onto you like a sleepy barnacle.

“Oi, mosshead!” Sanji snapped, appearing from the galley with smoke swirling and a righteous fury in his eyes. “Get off them, you clingy cucumber!”

Zoro cracked open an eye. “Make me.”

“Oh, I will!” Sanji stomped over dramatically. “Y/N-chwaann shouldn’t have to carry your freeloading swordsman body weight! If anyone deserves to be close to them, it’s me!”

You raised an eyebrow. “You literally tripped into my lap yesterday trying to ‘tie your shoe.’ You were barefoot.”

“It was a metaphor!” Sanji cried. “For falling head over heels!”

Zoro scoffed. “That was the dumbest thing I’ve ever heard.”

“Says the mossy limpet glued to their side like a touchy fungus!”

Zoro didn’t move. “Jealousy’s not a good look, curly.”

“You—!!”

“Guys,” Nami sighed, “can’t we go one day without turning affection into a shouting match?”

Brook leaned on his cane, chuckling. “Yohohoho! Young love… or something!”

Usopp squinted. “Wait. Has Zoro always been this clingy with Y/N?”

Robin smiled mysteriously. “Since thriller bark, at least.”

Franky nodded solemnly. “Saw him fall asleep on their shoulder mid-battle once. SUPER unconscious.”

“I thought he was dead,” Chopper added, horrified. “Turns out he was just really comfy.”

Zoro’s grip on your shoulder tightened very slightly, and you finally glanced sideways at him.

“Do you know you’re this touchy?” you asked.

He looked like he wanted to evaporate into the deck. “I… just don’t mind you being close.”

You blinked slowly. “Is that samurai code for ‘I like you’?”

Sanji audibly gagged. “Oi! Don’t flirt in front of me!”

“We’re not flirting,” you said.

Zoro mumbled, “Might be.”

Sanji died inside.

“Y/N-chwann” he said gravely, dropping to one knee. “I beg of you—pick me instead! I would never lean on you like a sweaty tree log!”

Zoro growled. “Because you’d faint from being close.”

“AT LEAST I’D DIE HANDSOME!”

You looked between the two of them and sighed.

“I just want to drink my tea without being fought over,” you muttered, walking off—Zoro immediately following, like a shadow with swords.

“You’re still touching me,” you noted.

“Didn’t say I’d stop,” he replied casually.

You stopped walking, turned, and looked him square in the eye.

“You’re aware this is very couple-coded, right?”

He blinked, then grunted. “Guess we should make it official then.”

You blinked right back. “That was fast.”

“Why waste time.”

You smirked just a little. “Romantic.”

He shrugged. “You’re warm. And you don’t talk too much.”

“That’s your idea of a proposal?”

“Worked, didn’t it?”

From behind you, Sanji dramatically screamed into the ocean.

MIHAWK

Kuraigana Island was a wasteland of stone, wind, and uncomfortable silences. You didn’t mind. You were the type to thrive in eerie places — quiet, observant, and allergic to nonsense.

Which is probably why Mihawk didn’t bother with small talk.

Or... so you thought.

Lately, the world’s greatest swordsman had developed a habit of materializing wherever you were. You’d be cleaning a blade — and there he was, pouring tea. You’d sit on the crumbling stone wall for some air — and there he’d be, suddenly trimming the overgrown vines right next to you.

At first, you thought it was coincidence.

Until today.

“...You know you don’t have to sharpen every one of my knives,” you said flatly, watching him work silently at the bench beside you.

“I didn’t,” Mihawk replied, still honing the blade. “Only the dull ones.”

You blinked. “That was my butter knife.”

“Then it was very dull.”

From the far side of the ruins, Zoro grunted as he finished a set of squats. “He refilled their canteen twice this morning.”

“Once,” Mihawk corrected, still not looking up.

“Twice,” Zoro insisted. “Once after breakfast. Then again after they just looked at the sink.”

Perona floated down with a snort. “He also folded their coat. While they were still wearing it.”

You narrowed your eyes. “Wait. Is that why my sleeves were shorter for a second?”

“You had a wrinkle.”

“I always have a wrinkle.”

Mihawk looked up with that unreadable expression. “And now you don’t.”

Zoro huffed. “What even is this? He acts like a butler. But like, a scary one.”

Mihawk narrowed his eyes at him. “I’m not a butler.”

“Could’ve fooled me,” Perona muttered, arms crossed. “You fixed the strap on their satchel too.”

Mihawk didn’t respond to that.

Perona raised a brow. “You gonna deny it?”

“No,” Mihawk said coolly, “because it was crooked.”

Zoro leaned against a stone pillar, towel around his neck. “He also moved your seat at the dining table.”

“That was my seat,” you said.

Mihawk finally gave you a long, side glance. “You’ve sat on the left for the past four mornings. I simply ensured it remained consistent.”

You deadpanned. “You rearranged the furniture.”

“Briefly.”

Zoro stared. “And when they tripped over that vine—”

“I cut the vine before they fell,” Mihawk snapped with a tone just shy of defensive.

“Bro. You lunged across the courtyard.”

Mihawk sipped his wine calmly. “It was in the way.”

You raised an eyebrow. “And when you pulled me by the hood into the shade the other day?”

“You were overheating.”

“I wasn’t sweating.”

“You were blinking slowly.”

You stared. “That’s just how I blink.”

There was a long pause.

Then Perona gasped. “Wait, wait — you also fixed the strap on their scabbard!”

“I adjusted it. The weight distribution was uneven.”

Zoro clapped once, grinning. “So you are clingy.”

Mihawk’s eyes narrowed, the glint in them sharp and dangerous. “I am not.”

You leaned your chin on your hand, amused. “Then what would you call this?”

He paused. “Awareness.”

Perona lost it. “You mean hyper-awareness. Of one (1) person.”

Mihawk ignored her. “It’s strategic. I simply ensure you're at your most efficient.”

“That’s not efficiency,” Zoro said, wiping his forehead. “That’s doting.”

Mihawk arched a brow. “You think a swordsman cannot be observant?”

“You folded their laundry in order of fabric weight.”

“They prefer it that way.”

You blinked. “I never said that.”

He side-eyed you, expression cool. “You didn’t need to.”

You blinked again.

Zoro grunted. “You see? He’s acting like we’re all weird for noticing.”

Perona jabbed a finger toward him. “He's totally doing the ‘if I act calm, no one will notice I'm obsessed’ thing.”

Mihawk finally gave a soft, tired sigh — the kind that said you people are exhausting.

Then, turning to you, he asked, “Would you like tea?”

“I haven’t said I was thirsty.”

He didn’t blink. “You will be.”

You stared. “Are you psychic?”

“No,” he said simply. “You’re predictable.”

You squinted. “...That sounds like flirting.”

Mihawk blinked slowly. “I don’t flirt.”

Perona groaned. “OH MY GOD—”

Mihawk stood up, cloak sweeping behind him, expression unreadable as always. He held out the canteen like he’d already won this conversation.

You took it with narrowed eyes, muttering, “Thanks... I guess.”

He nodded, calm as ever. “You’re welcome.”

Zoro crossed his arms. “Still denying it?”

Mihawk looked at all of them — then at you — and with perfect poise said,

“I’m just efficient.”

And with that, he turned and walked away.

You stared after him, took a sip from the canteen, and sighed.

“…Efficiently annoying.”

[brilworks]

Optimize Your Nest.js App Performance With These Practices

In the modern era of rapid technological advancement, users tend to lose interest in using an application if it doesn’t load quickly. Since there are multiple alternatives available for each app, users are more likely to switch to another app if you don’t optimize your app.

A survey shows that if an app takes longer than three seconds to load, the probability of losing users increases by 40%. The optimization of an app is an essential factor that plays a critical role in the app’s success.

Nest.JS applications come equipped with a wide range of tools that developers can leverage. In this article, we will be exploring ways in which you can enhance your Nest.JS app’s performance by optimizing it effectively.

What is Nest.JS?

Nest.JS ranks among the popular JavaScript frameworks in 2023 that offer a robust set of tools for creating server-side applications, and native support for TypeScript elevates the development process to a higher level.

You can use Nest JS to develop sophisticated, high-performing, and scalable server-side applications. It provides you with a modular structure which makes it easier to organize the code. Additionally, it comes equipped with a range of tools and plugins that you can use to optimize your app. However, the overall performance of the application ultimately depends on the level of effort put in by the developer.

Here are some practices that can help you optimize your NestJS application to improve its performance and efficiency.

1. Implement Caching

Caching refers to the process of temporarily storing frequently accessed data in high-speed storage — cache memory. By activating caching, you can reduce the data retrieval time. Here’s how you can implement caching in your application.

Install Cache-Manager: NestJS provides a solution for implementing caching using cache-manager. To install it, run the following command:

$ npm install @nestjs/cache-manager cache-manager

This cache manager offers a unified interface that supports various cache storage providers beyond just the default in-memory option.

To enable in-memory caching, run the following command:

import { Module } from '@nestjs/common';

import { CacheModule } from '@nestjs/cache-manager';

import { AppController } from './app.controller';

@Module({

imports: [CacheModule.register()],

controllers: [AppController],

})

export class AppModule {}

To learn more about caching, you can explore additional resources and consider switching to alternative service providers.

2. Choose Appropriate Dependency Injection Library

Nest.JS provides developers with the sweet nectar of dependency injection. This design pattern allows for a more maintainable codebase by injecting dependencies as needed. But this blessing can also turn sour if not used properly, leading to sluggish application performance.

NestJS provides built-in support for dependency injection (DI), but it also allows you to use other DI libraries if you prefer. There are several popular DI libraries that are compatible with NestJS, including:

InversifyJS: InversifyJS is a powerful and flexible DI library that supports advanced features such as constructor parameter injection and named dependencies. It has a large community and well-documented resources for developers. You can use it with NestJS by installing the `@nestjs/inject` package and importing the `InversifyAdapter` from it.

Awilix: Awilix is a lightweight DI library that emphasizes simplicity and ease of use. It has a simple API and supports many of the same features as other DI libraries, such as constructor injection and property injection. You can use Awilix with NestJS by installing the `awilix` package and using the `awilix-express` integration library.

TypeDI: TypeDI provides a simple and intuitive API for defining and injecting dependencies. You can use TypeDI with NestJS by installing the `typedi` package and importing the `TypeDIAdapter` from the `@nestjs-typeorm` package.

tsyringe: tsyringe is a lightweight and flexible DI library that supports many advanced features such as circular dependencies and conditional injection. It has a simple and intuitive API, and you can find comprehensive documentation to work with the tsyringe. To use tsyringe with NestJS, you can install the `tsyringe` package and importing the `TsyringeAdapter` from the `@nestjs-modules/injection` package.

If you’re just getting started with NestJS and don’t have any particular requirements, the built-in DI system is a good choice as it is lightweight and easy to use.

3. Use Compression

The more code you have, the slower application will become. Therefore to prevent your app performance from getting bogged down by heavy code, you can use various compression techniques available to reduce the size of HTTP responses, JavaScript, and CSS files.

This technique includes Gzip, deflate, and Brotli compression. These tools or techniques can help you reduce the weight of your code, which will result in improved performance.

To use compression in NestJS, you can take the following steps:

1. Install the compression package:

npm install --save compression

2. Import the CompressionMiddleware from compression:

import * as compression from 'compression';

import { NestFactory } from '@nestjs/core';

import { AppModule } from './app.module';

async function bootstrap() {

const app = await NestFactory.create(AppModule);

// Use the compression middleware

app.use(compression());

await app.listen(3000);

}

bootstrap();

This file imports the compression middleware and adds it to the application using the app.use() method.

By default, the compression() middleware will use the gzip compression algorithm. You can also pass in options to customize the behavior of the middleware, such as the threshold at which responses will be compressed, using the following syntax:

app.use(compression({

threshold: 512 // set the threshold to 512 bytes

}));

With compression enabled, responses from your Nest.JS application will be compressed before they are sent to the client, reducing the amount of data that needs to be transferred over the network and improving performance.

4. Optimize database queries

You can enhance your app’s performance by optimizing your database queries. One effective method is to minimize the number of queries by utilizing query batching and compatible ORM frameworks that enable streaming and enhance the overall database process. Rather than retrieving all available data, reducing the amount of data fetched can also minimize the workload on the database and optimize its operations.

5. Revamp your Algorithm

To optimize an app’s performance, it’s essential to fine-tune its algorithm, which entails creating a series of instructions that direct the code on how to operate.

The algorithm’s defined steps have a direct impact on the app’s performance, as they dictate the optimal times and conditions for the code to perform specific tasks.

Evaluating the algorithm’s optimization level is critical to enhancing the app’s overall performance, as it informs the code when to execute particular tasks and when not to, enabling it to work more efficiently. Essentially, the algorithm acts as a roadmap for the code, guiding it on how to function for optimal efficiency.

Continue to read more at https://www.brilworks.com/blog/optimize-your-nest-js-app-performance-with-these-practices/

[pearlescentparade]

Ur probably gonna ignore cuz it’s kinda boring but can i request two time x reader angst ?

Two and reader spending time together, reader trying to enjoy snuggling up to their partner yet two time isn’t returning any of the affection. Just sitting with their hands to themselves with no attempt to do anything besides watch whatever was in front of them.

Basically reader trying to cope with two time not actually returning their feelings despite dating and probably terrible communication.

up to you if two time loves them back.

light years 🔄 two time x reader angst drabble❤️‍🩹

it's cold tonight.

you shouldn't complain, considering it was your idea to go star-gazing. but in your defense, it sounded cute in the moment.

the blades of grass uncomfortably drag against and poke your skin, prickled with goosebumps, as you shift to turn on your side to face two time. they only blankly stare up at the eternal night sky.

"timey?"

they hum, but are complacent in making any other effort beyond that to acknowledge you.

"i'm a little cold.. can we cuddle? ...please?" your whispered pleas could've been mistaken for the ambient howling of the wind. perhaps that's why they don't answer you. but there is much shame to be had in asking again, you think.

hesitantly, and with much space, you reach your hand out to them.

nothing. no acceptance, no rejection.

then, you dare to slink your arms around their body, loosely embracing them as if unsure whether to commit fully to it. you think you feel colder touching them than not.

their body tenses under your touch. did they feel disgusted by you?

you shakily exhale, trying to ignore the deep pain rooting in your heart and constricting your throat. times like these, you wish that they'd start yelling how much they hate you. at least then, you'd know for sure, and you'd know how they feel or think for once. but instead, you are left in the dark, blind and guessing, and playing a game meant for two alone.

a familiar sting burns your eyes, and you take it as your cue to distract yourself.

"..that's orion's belt. it's thr-three stars." you point to the constellation, light years away. two time blinks, inches away. it's less about telling them, and more about telling yourself.

"over there is gemini. it--hic--has the twin stars, castor and- and pollux-" despite your futile attempts, the tears fall anyway. and when one slips out, the rest comes in a flood. it takes only seconds before you're uncontrollably sobbing, muffling your cries in two time's arm.

yet, even as you wet their arm with tears, snot, and saliva, they say nothing. no comfort, no disgust, simply silence.

they couldn't say anything.

not when fear paralyzes them.

they've messed this up before. it's not out of the question to say it could happen again. the same voices that lead them to atrocity chatter viciously in their mind, angry wasps rattling in the nest, urging for another sacrifice.

to once again spill blood, warm with infatuation. to take advantage of this golden opportunity to present their devotion to the spawn by stealing the love they hold with you and metamorphosizing it into the love for their god. one wrong move, and their ghostfire dagger will plunge right into your heart.

to two time, inaction is the greatest reciprocation of love they could offer you.

without turning their head, their eyes flick to glance at your blubbering form.

it's cold tonight.

(parade postscript: sorry this one is a lot shorter mostly bc reader is talking to a fkin brick wall and yk dialogue carries all my mfin writing and also i js thought itd be fitting that everything is all short and lacking bc of the whole two time not showing reciprocation thang [me pulling out a million bullshit excuses out of my ass for why ts is so short and pretending im being a literary genius]

also fun fact! castor and pollux look close together from earth but are farther from each other in reality! castor is actually 51 light-years away, while pollux is closer at 33.8 light-years)