#async functions

[loudcollectiveartisan]

https://www.tiktok.com/@zokhshop_

<!–Start of Tawk.to Script–>https://www.tiktok.com/@zokhshop_<script type=”text/javascript”>var Tawk_API=Tawk_API||{}, Tawk_LoadStart=new Date();(function(){var…

[onepic500words]

Are you sure?

Victoire sat at dinner, a glass of wine in her hand, and that look of absolute certainty all over her face. "I'm ready for this… and just want to be drunk enough to relax, enjoy it while overcoming my fear."

"Are you sure?" I asked with genuine concern. We'd talked about #3 on her list for a while, but prior attempts had quickly clarified that she was not really ready, clearly not prepared to have her ass stretched as my thick cock pushed at the edges of her ass.

The idea (my hope) of her loving it was tempered down significantly by the reality that I didn't really think she would ever really be able to do it. But the last few weeks of preparing by wearing a plug, then a vibrator in her ass, and finally getting off to it multiple times while I told her stories over the phone – controlling it via Bluetooth – had gotten her to the point of wanting it very badly.

"Yes, dammit, I'm sure. But babe… you're going to have to get me off a few times, and really, really go slow."

"I understand," as the plot of this evening began to take focus.

I raised my head at the passing waiter… "She'll have one more, and a check."

She raised her eyebrows at me, as she did when she was pleased that she had prodded me to action… and then scowled at me as I turned the vibrator on that was pressed against her clit up from a light hum where it had been for the last few minutes to the "I'm getting your attention level" and left it there.

Raising her glass to her lips, the slight shiver in her hands was barely noticeable as she closed her eyes… in part to enjoy the taste, and also in the enjoyment that the tremors were having on her body. Meanwhile I smiled at the prospects of doing one of my favorite things -- my lips and tongue pushing her over the edge multiple times and the prospects of taking her virgin ass for the first of many times.

---

Walking back from dinner, having turned the vibrator back down so that she could comfortably concentrate while walking, her beaming smile caught the eyes of nearly everyone who we passed.

"There are a ton of people out tonight," she stated in the tone of wonderment every time she came to Durham. "Who knew this place was that popular?"

"I did." In the most matter of fact tone I possessed.

"Shut up," she replied and reached over to kiss me. I turned and kissed her back.

Getting into the elevator, I slipped my hand back into my pocket and turned the vibrator up to one of its "heighted" levels and watched as she leaned back against the elevator walls, trying to keep from moaning in front of the other three people riding up. When the doors opened at twelve, I flipped it back down and she took my hands, nearly dragging me toward my place.

"You are mean," was all that she said as we opened my door.

And as soon as the door closed, she turned on me and attacked me with kisses, reaching down to find my cock to return the favor.

"Not yet," I said firmly. "There's a lot to be done, and you'll get that when the time comes, and I don't want to waste the excitement on the pre-game activities."

"Fine," she huffed as she turned and started taking off her clothes, leaving a trail behind her as she sauntered toward the bedroom.

As I entered the room, she was already lying on the bed, stretched out so I could admire her beautiful body. Her long legs, her beautiful breasts, the hint of her pussy, and the alluring smile that always draws me in. Beside her, on the nightstand, lay her anal vibrator, a plug and the lube that would make anything possible. I reached into a drawer and pulled out a dildo, shaped like a real cock that was not quite as thick as my own…

"What is that?" she asked, with a bit of worry in the tone of her voice.

"The next step in your preparation for the real thing." My eyebrows raised, asking if she was really ready.

"OK" was all I got back, with hints of excitement, certainty and fear mixing together as if to give her final preparation.

Before I took off my clothes, I reached under each corner of the bed and pulled out leather cuffs which was tied to each post. I took her ankles and then her wrists and pulled them tight enough to let her twist but not escape. While walking around the bed for each step of her entrapment, I turned the vibrator still on her clit to a dizzying level… and stopped to deeply kiss her and then suck and lick each nipple with great abandon.

She was edging toward another orgasm (at least once over dinner to test her resolve to stay quiet… now however, I didn't care what the neighbors all around me heard from her moans and demands) as I removed the vibrator from where it was tucked into her, but rubbed her lips and below her clit (her favorite spot) as an apology for denying her the approaching release. Then I removed my shirt, jeans and finally my boxer briefs -- my now very hard cock bouncing a bit.

"Let me taste you," she begged. I simply shook my head and crawled between her legs… and licked open her lips.

"Oh fuck," she sighed, and closed her eyes while as she pushed her head back into the pillow and therefore thrusting her pussy further into my face. With that, I encased her clit in my lips, sucking and licking at the same time as she began to let go completely…

She came, and I reached over for the anal vibrator, put a small dollop of lube on it and then reached down to lick her ass for the first time. After she begged me to do it, having gotten two fingers in her ass in preparation, I gently pushed the vibrator into her… its two inches barely in her and her groans as its inch stretched her rosebud slightly.

Flipping the switch attached to the wire now dangling from her ass… I went right back to her pussy. She began to thrash against the restraints as my wet mouth tasted how much wetter she had become.

For the next few minutes, she got pushed further and further, my jaw joints aching from the aggressive exercise I was getting by paying attention to every bit of her. She moaned, came again and again, and begged for more as I ravaged her lips, licked in her, and pushed my fingers in and out of her repeatedly. And each time she came, I had to keep my thumb on her ass so she didn't push her vibrator out.

"Babe! I can't take any more… Please fuck me!!"

"Nope," I replied. "The only place I'm coming tonight is your ass…"

"Then go ahead and do it!"

"Not yet," I said, reaching over to unbind her from the bed… "Next, I get to keep my concentration while I get you ready for the final step."

Before she moved, I slowly pulled the now quiet vibrator from her, its battery completely depleted, and then paused to lick the sweat from her nipples. As I turned to lean up against the headboard, she twisted to get on her knees and I reached over for the dildo… and she immediately began to suck and lick my cock in complete rapture.

While doing my best to (1) focus on what was next and (2) to not come (which she had clearly decided that she could pull off despite my earlier promise), I reached over and pulled her hips closer, and then gently at first began to fuck her pussy with the dildo. "Maybe this will give you an idea of what getting #1 on your list checked off," as I picked up the pace and she began to moan while my cock was in her mouth.

After a couple minutes, I reached over and poured some lube in my hands, rubbing it together to warm it a bit, and then dribbled it on her ass… taking the excess in my hand, I coated the dildo with what was left and immediately took it to the edge of her asshole.

She stopped what she had been doing, and tensed up as she lay her head on my stomach as I slowly pushed into her. "Wait… stop… ok, slowly…" she gave instructions and I kept adding force against her ass's resistance. After another minute, I had worked the head into her ass (which caused her to yelp and moan… a combination I hadn't thought possible) and then began to push a bit further in to her as she tried to concentrate on my cock again.

Third stroke in… she came again, with my entire cock in her mouth, and screamed around it. After a couple more small strokes, she said, "Please babe… I can't take that any more. Either fuck my ass or me, but I need to feel you in me."

For the third time, I asked the question: "Do you think you're ready?"

"Yes already! You've almost exhausted me, and I need to feel you come! Stop teasing me and fuck me already!"

"As you wish," I retorted and lay her on her back.

Starting to eat her pussy again, she shook her head. "No! Fuck me!"

"Just trying to get you ready, ok?"

Her exhaustion, frustration and absolute lack of patience with me painted her entire body and she just nodded her resignation to my control over this.

This time, as I ate her pussy, my fingers felt that the resistance in her ass had improved, and I hoped it was time. After a minute more, I stood on my knees and carefully coated her ass and my cock with lube while I bent her legs further over her chest.

"I want to watch," she managed to get out, her excitement and nervousness now very evident.

"Another time I promise, but we'll need assistance with that and that's a whole different fantasy," was my only reply.

I leaned into her and placed the head of my cock against her ass.

"Babe, go slow…"

"I know," now concentrating on how hard I needed to be, and to get the lube to do the job of easing me into her.

The head of my cock began pushing into her, her hole stretching slowly as I pushed into her.

"I want you to fuck my ass… push a bit more, and then fuck my ass so hard." She knew that talking dirty to me would help me stay hard.

After a moment, I felt her ass engulf the head of my cock and she bit down on her lip in the pain but not as much as before. Preparation had worked. Her ass felt like a choking grip on my cock and now I was about to lose my own patience for the release I needed.

Another minute of slowly pushing into her, while the dirtiest thoughts and desires escaped her lips. "I can't wait to watch someone videoing us… you fucking my ass so hard, while she gets excited watching us both come… Fuck, you are so big in my ass… Come on, fuck me, fuck me so hard…"

Finally fully in her, her fingers found her clit and I pushed out a bit and began slamming myself into her ass… her tightness remaining a clinching force on my flesh as I got lost in the selfishness of the moment…

She was moaning and playing with her clit while I pushed further into her, my own words of desire and satisfaction rising up, "Fuck yes, I love fucking your virgin ass!" as I began to come deep in her ass.

Continuing my best to push in and out of her, her final scream was over the top, "Yes, babe, fuck me, oh fuck my ass, oh FUCK…." And she grabbed my back and dug her fingers deep into my own flesh. I'm sure my pain wasn't anything close… but she definitely got my attention.

In the immediate aftermath, I remained on top of her as I began losing my hardness and then slipped from her ass. She turned and kissed me, and lay her head on my shoulder, our sweat now soaking the bed.

"That really fucking hurt, but we got to do it again."

"Are you sure?"

[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…

[codeonedigest]

GraphQL Resolver Explained with Examples for API Developers

Full Video Link - https://youtube.com/shorts/PlntZ5ekq0U Hi, a new #video on #graphql #resolver published on #codeonedigest #youtube channel. @java @awscloud @AWSCloudIndia @YouTube #youtube @codeonedigest #graphql #graphqlresolver #codeo

 Resolver is a collection of functions that generate response for a GraphQL query. Actually, resolver acts as a GraphQL query handler. Every resolver function in a GraphQL schema accepts four positional arguments. Root – The object that contains the result returned from the resolver on the parent field. args – An object with the arguments passed into the field in the query. context – This is…

[bf-rally]

i have to use hooks dont i

I'm having the hardest time figuring out how to pass an array to a different page....

[codemerything]

A structured way to learn JavaScript.

I came across a post on Twitter that I thought would be helpful to share with those who are struggling to find a structured way to learn Javascript on their own. Personally, I wish I had access to this information when I first started learning in January. However, I am grateful for my learning journey so far, as I have covered most topics, albeit in a less structured manner.

N/B: Not everyone learns in the same way; it's important to find what works for you. This is a guide, not a rulebook.

EASY

What is JavaScript and its role in web development?

Brief history and evolution of JavaScript.

Basic syntax and structure of JavaScript code.

Understanding variables, constants, and their declaration.

Data types: numbers, strings, boolean, and null/undefined.

Arithmetic, assignment, comparison, and logical operators.

Combining operators to create expressions.

Conditional statements (if, else if, else) for decision making.

Loops (for, while) for repetitive tasks. - Switch statements for multiple conditional cases.

MEDIUM

Defining functions, including parameters and return values.

Function scope, closures, and their practical applications.

Creating and manipulating arrays.

Working with objects, properties, and methods.

Iterating through arrays and objects.Understanding the Document Object Model (DOM).

Selecting and modifying HTML elements with JavaScript.Handling events (click, submit, etc.) with event listeners.

Using try-catch blocks to handle exceptions.

Common error types and debugging techniques.

HARD

Callback functions and their limitations.

Dealing with asynchronous operations, such as AJAX requests.

Promises for handling asynchronous operations.

Async/await for cleaner asynchronous code.

Arrow functions for concise function syntax.

Template literals for flexible string interpolation.

Destructuring for unpacking values from arrays and objects.

Spread/rest operators.

Design Patterns.

Writing unit tests with testing frameworks.

Code optimization techniques.

That's it I guess!

[felixcloud6288]

I MANAGED TO GET THE CODE TO WORK THE WAY I WANTED!!!

The version @jv made is effective, but it skips the boop animations. Mine interacts directly with desktop elements so it shows the animations.

Code:

var annoy = async function(){ const sleep = (t) => new Promise(resolve => setTimeout(resolve, t)); while(true){ await sleep(3000) var e = document.getElementsByClassName("TRX6J juYLo") e[0].click() await sleep(50) var f = document.getElementsByClassName("EvhBA Evj9j") f[0].parentElement.click() } }

annoy()

Use the tutorial from jv's post here, but put my code instead. You don't need to specify a victim or number. It chooses the first person on the page and runs forever.

For best results, go to the page of a post from the person you want to annoy.

[wuggen]

"No, we don't need to worry about leaking memory right now", "There's no structure here, just the raw bytes from the client. Just add the endpoint name at the beginning, it's fine", "Yeah we're leaving it to each of the language bindings to parse requests for now, don't worry about it", "If these functions block an async worker thread it'll still work, no worries", "We can worry about synchronizing mutability across the FFI later", and other insane things you might hear from your boss as he casually rakes in weeks to months worth of technical debt over the course of a few days

[s-lycopersicum]

That post got me thinking about programming, and that maybe I should talk about one that I really had fun writing recently, and that I'm kinda proud of, so here it goes!

So, in my computer experiments and stuff like that, I often have to write scripts that process entries in various stages. For example, I had a thing where it read a list of image urls and downloaded, compressed, extracted some metadata, and saved them to disk.

That sort of process can be decomposed in various stages which, and that's the important part, can be run independently. That would massively speed up the task, but setting up the code infrastructure for that every time I needed it would be cumbersome. Which is why I wrote a little library to do it for me!

That gif is a bit fast, so here's what it looks like when it's all done:

This is from a test I wrote for the library. It simulates running a set of items through 4 different processes (which I named production lines), each with their own stages and filters.

Each line with a progress bar is a stage in the process. If you follow the traces on the left side, you can visualize how the element enter the 4 production lines on one side, and are collected on the other. The stages I wrote for the test are simple operations, but are written to simulate real world delay and errors.

To set up the processes, I do practically nothing. Just initialize the production line structure and connect the stages together, and that's it! All the work of setting up the async tasks, sending the entries from each stage to the next, filtering, error logging, even the little ascii diagram, all that happens automatically! And all that functionality packed into one data structure!

I feel like trying to explain how it does all that (and why having built it myself makes me proud) would make it harder to believe that I actually had fun doing it. I mean, it involved reading a lot of code from high profile open source projects, studying aspects of the language I had never played with (got really deep into generics with this one), and I can't really explain how I really enjoyed doing all that.

I don't know, I feel like I lost the point of what I was trying to say. Hm, I guess this feeling are harder to pin down that I expected.

[yanzinator]

Automatic boops!

I have to leave for a flight so I can't boop anymore, as such I leave this to you. Please share and use this so we can max the global boop counter!

follow the steps below to boop anyone repeatedly at super speed automatically

open dev tools (usually f12)

go to the network section

make sure all the packets are there, sometimes it will tell you to reload the page first

send a boop (or super boop, if it's a super boop then you'll be automating supers)

find the packet you just sent, it should say boop under file name.

right click

in the copy menu copy as fetch.

the packet has now been copied to your clipboard. don't lose it.

type this in the console (keep the curly brackets):

setInterval(async function () {the packet here}, 200)

the booping will stop when you leave the page

keep an eye on the network tab, every 200 ms there is sent a packet that is a boop, if the number to the left is 200 and green, the boop sent, if its 4xx and purple or red it did not send. Due to the speed a lot wont send, if all of them are failing though, refresh the page (cancelling the automation) and boop manually and use the new fetch packet.

thank you @lilacslilacss for helping me discover how the packets work and @anixknowsnothin for helping me make this work on browsers other than firefox!

[butts-bouncing-on-the-beltway]

First: congrats on your successful date!! You made it sound incredibly sweet. To my point: you mentioned in your tags that you're good at dating despite being aro. Is this a skill you've cultivated, and if so do you have any tips for an aro/greyro with cause to date relative strangers? I am also autistic, so I have double debuff when it comes to Following Social Rules, and would welcome your input

It was a really sweet date! We snuggled a lot 💚

So, like. Imma be real with you. Autistic/aro isn't necessarily a debuff here, because the tip I have for you is "try to understand the function of a social rule where you can, but DO NOT follow them"

Truthfully? The social rules around dating are stupid and everyone hates them, even (especially?) the people who are using them. Now I definitely can't speak to every dating pool, and depending on what you're trying to get out of a date, your mileage may vary. But here are my goals when dating, and how I move towards them with intention.

Goals:

Get to know someone

Set communication and boundary expectations

Establish compatibility

Assess The Vibe In Person

Have fun!

Lets start with getting to know someone!

I have basically always used dating apps. I know this doesn't work for everybody, but unfortunately I just can't speak to strats that involve meeting people anywhere but a dating app, sorry!

I've had reasonably good luck on OKC over the years, but Bumble has been poppin lol

The nice thing about dating apps is that people are presenting a version of themselves for initial compatibility that I can assess and reach out about if I vibe with it. Now, I am **not** necessarily suggesting you just read a profile and take it at face value. There is a layer of "prescriptive" in how people present on their dating profile that tells you what they value more than what they ARE LIKE, but there is descriptive in there too! Learning how to hear a little of both when you talk to people (I recommend taking classes in things like active or reflective listening to help with this) can make it a lot clearer whether or not you're gonna vibe with someone.

I also don't stay on the dating app to talk to people! They talk to you differently when they're still "trying to pass your tests" or whatever, and I have no time for that. I usually drop my phone number (lmao my dating and hook up VOIP, I do *not* give people my actual number) in the chat after 2-3 decent back and forth topics with a person. Then we callibrate the "off app" vibe. I do this by throwing out little opportunities for a person to express interest in things I am open about enjoying. This also helps clarify compatibility, but at this stage it's more about figuring out who this person is and how best to learn them. I usually try to talk for a few days to a week before meeting in person if I'm considering genuine emotional investment in a person, but if I'm just looking for a hook up, I try not to take longer than 48 hrs or people get......invested.

Once I've moved to phone/texting, I try and roll into setting boundaries and communication expectations. This is honestly pretty part and parcel with establishing compatibility so we're gonna treat this as a two goals one process scenario

So I do *not* like when people expect a prompt text reply back. Texting is an async communication style and that's WHY it works for me as well as it does. Sometime after the initial "hey it's so and so from x platform!" nonsense, I drop the acknowledgement: "hey, I work A LOT and I don't have a ton of time or flexibility in my life. I understand this won't work for everyone, but here are my hours (friends I work 50hrs per week at my day job and spend one of my days off on medical appts, community work, and other roles in my life, so functionally I have one day a week to make available to partners. This is unferstandably daunting to some, but it's better I weed those folks out early on anyway). Historically I have literally told people "generally what I'm available for is about one Sunday per month and maybe a handful of overnights". I let folks know that I respond to messages when I have time but am always delighted to receive them, even if I can't reply right away.

The thing about filtering for compatibility is that people worry it makes it harder to date but like. If your dating pool is full of people you aren't compatible with, then a LOT of your dating experiences are gonna feel bad! It's way easier to consistently achieve a good outcome if you treat a thorough filtering process as essential to dating. So every time someone drops out of the running, I actually see that not as a failure but as a victory! I have confirmed that me and this person weren't compatible! That's totally value neutral, but trying to date them anyway isn't!

So there are lots of little things that matter to me in a compatible partner, and it often isn't what people think. In being really clear and direct (KIND, but clear and direct) about this stuff, I give others the chance to share their own compatibility areas. This is usually where we also start having the "what are you looking for" conversation too. I am, again, clear and direct about this. I share that my goal is FRIENDSHIP and that for me, sexual intimacy, physical intimacy, commitment, etc are neutral activities to me, not relationship defining. I share that I have people in my life I care for very much, and we learn together what that should mean. I have people I love who understand that "dating" me would not suit them, but we remain committed to each other for life. I have some who consider sex with friends normal but acknowledge that shifting into partnership would be a negative. And I have others who are comfortable with what I can offer for partnership and want to offer something back. I find that in the ENM world, this conversation goes down like a relief to whoever I am talking to. Less pressure, some validation of their own approach to relationships, etc. I imagine that in a monogamous dating culture this might require a larger stage setting process. Then again, that's part of why I do not date monogamously and never will.

At this point we're usually getting to a stage where I already have a sense of A) what role this person may be compatible with in my life, and B) what I need to move forward once we meet in person. To be EXTREMELY CLEAR sex on the first date has NEVER been a goal I aim for. But the goals I do have and the process I follow has resulted in a 100% success rate of sex on the first date anyway lmao. Critically, in order to achieve this, one needs to be willing to risk putting your foot in your mouth.

I have two go-to first date spots. Both are local coffee shops I frequent, and because I date a lot of people of color and other trans people, specifically they are spaces where I trust the environment or am friendly with the staff such that I know it's a safe space for them to get to know me in. Once I know that I would *like* to meet in person, my go-to line is "I'm really enjoying getting to know you, and I'd love to get together and see how things go in person too. If/when you're also ready for that, I'd love to take you out for coffee." Then I offer the two spots I use and add "I'm open to other ideas, but like to offer an easy plan if folks don't have their own preferences for a first outing". 9 times out of 10, they just accept because they are also wanting to meet. On the rare times someone hasn't been open to a date just yet, it rarely takes more than a few days for them to circle back and confirm if the invite is still available (of course!)

Meeting in person, to me, is a formality. If I ask for/offer that, I already know what I'm open to with a person and am looking to have a face to face negotiation of what THEY want WITH ME. I like to take a couple of hours to get the flow of a person, and then name "so I know we didn't make a solid after-coffee plan, but [insert an offer or ask to retreat to privacy]". With this date, I offered "sooo, the weather has been a shitshow all day and it's already like 6pm (the date started at 12pm lol) so I don't know what your evening looks like, but I'm a little worried about you driving home in this. It's 100% up to you, but you're welcome to come stay over and we can get you home in the morning when the roads are safer". She was super appreciative of this! We did go back to my place! We listened to music and pkayed some video games and had tacos, and then I brought her up to my office to snuggle and literally the door had barely closed and she was kissing me sooooo. I mean I wasn't gonna STOP her. I did make sure to clarify again "you are not stuck here, at amy point you want to leave or have space, just let me know" and she was like "shut up????" So you can imagine how that went.

In past dates, for example when I was grabbing coffee with someone I wasn't expecting to get emotionally involved with, I have chatted with them for a bit and then said "hey, do you have a preference between going back to your place or mine?" And typically they don't, so I let them know we CAN go to my place, but the dogs can be sensitive to strangers, so people usually offer their place at that point (definitely my preference lmao). The last hook up I had, I let him know that, and he invited me back to his place, and when we were done, I left and just let him know when I got home that I had arrived safely and had fun.

The thing about dating is someone has to make the first move. And sure, we can waste our energy and time trying to mind read exactly when its okay to do that OR we can make a habit of simply saying it when it comes up in a way that allows for the other person to not fully be there yet. Basically "hey, I'm gonna mark for YOU that progress/movenent is available here, so that when you're ready to want it, you don't have to worry about reading MY mind"

Typically I get two responses to this approach. Response 1) immediate relief, comfort, and matching of expressions (there are sometimes setbacks as we hit vulnerable progress pounts for people, but these are the folks who do BETTER with my approach, they aren't just tolerating it, many find they prefer it). Response 2) increasingly escalated panic as the other person becomes convinced that the level of direct I am being is somehow passive aggressive/a test that they are failing (these are people who rarely make it to the in person stage in the first place, but on the rare times they do, I have never actually successfully SCHEDULED a date with these people because the logistical process becomes so triggering for them they ghost me or bow out lol).

It's probably worth acknowledging that basically everyone I pull with this approach is ALSO autistic as fuck lmfao, or at least vaguely prone to psychosis and disorganized thinking. The clarity seems to be really positive for them (lmao shocker given those are the same reasons it's really positive for me) so pretty consistently I find that this approach goes super smooth because its BOTH of our preference, whether or not it has ever been accessible to the other person in the past. It's the "me and the bad bitch I pulled by being autistic" meme all over again lol.

I'm not suggesting that autistic folks are always compatible btw, more acknowledging that when you are straightforwardly and openly yourself, you tend to pretty reflexively create a filter for "people who are being themselves in compatible and comfortable ways" and that's actually a good thing in dating! Take advantage of it! Stop letting people convince you to hide yourself from prospective partners!

This last goal is the most important. I am here to have fun. If it stops feeling fun, there's a REALLY good chance I need to change something about how its happening. Like, there are surely times that aren't fun but are necessary, but if the relationship as a WHOLE stops being fun? Nuhuh, I'm out. At the end of the day, I date to add to my life not to box myself into restrive parts of it.

Imma be real with you, a lot of this is "now that we've set communication preferences, how well do they stick around under pressure". If people tend to reject those expectations under stress, we're not gonna have a long relationship, no matter how otherwise compatible we might be. I lack the patience and energy and time in my life to force people to change before they're ready. Sometimes we take a break and they circle back later! Other times it's just over. But either way, I set the boundaries I do at the beginning to protect my joy in a relationship with another human, and so their erosion is a sign of lack of health in the dynamic.

To answer your direct question, yes, this is absolutely a skill I have cultivated on purpose. I worked with therapists, social coaches, and training programs in conflict resolution and group facilitation for DECADES now lol. Social stuff has always been really hard on me, and I have a lot of rawness around all that still. For me, a "functional" approach of "what is someone attempting to communicate to me by engaging in this manner of social patterning". Like for example, I'm REALLY goid at small talk. I hate it. It is genuine hard work to engage with it without fully dissociating out of my body or getting overwhelmed. But I never have to do it for long, because my understanding of WHY people rely on small talk allows me to offer alternatives that are more comfortable for me. It's called a bid for attention per Gottman relational therapy, and the function is basically to ask the other person "hey can you come sit with me in these safe and familiar thoughts/statements for a minute so you can start to feel safe and familiar to me too". I can do that while also rapidly moving us away from "small-talk" and into "safe and familiar" thoughts for the other person that I can actually tolerate or interact with. Everything in social stuff is like this. It serves a function, often both a prescribed function and a described outcome that may or may not overlap. If the prescribed function (small talk = bid for attention) doesn't have that described function for you (ability to offer attention) then shift to the left basically. I like asking people to tell me about the games they play because even when I know the game it's very easy for them to share their thoughts on it without triggering any discord between us (i don't give a fuck about games lmao but i have fun watching others give a fuck basically) and I am able to give them space to connect securely to themselves in my presence. I'm not gonna lie to you and say it's easy or quick to learn this stuff, or even to execute it sometimes, but it has been deeply worth it.

At time of writing, I have 3 partners who I consider full partners or prospective partners, and there are two gentlemen who reach out on occasion for hook ups. There are definitely times that I have been much more limited, but these numbers are actually pretty common for me. I find that when people learn this, they make a LOT of assumptions about what kind of person I must be or how that works out. Usually when this happens I just crack a joke about "thank god for shared calendars" and redirect the conversation lol. But for the sake of this conversation let me do some minor myth busting here.

Myth 1: you must be SUCH a social butterfly!

Truth: i have always been a deeply shy and anxious person. I grew up in a family that was unable (unwilling?) to prepare the children for the world that was rather than the world as they believed it should be. On the one hand this meant that the first time I learned that some people had expectations about my gender I was almost 10, because I was waaaaay too oblivious to get why people were saying/doing shitty gendered fuckery at me lol. But on the other hand, I have a ton of social trauma now because it took so long to understand how to actually navigate the world as it truly was.

Myth 2: you must have an easy time dating because you're really pretty and cool!

Truth: I *am* really pretty and cool, yeah! But I spent my entire childhood being asked out as a joke by my peers because I am not conventionally attractive, and I'm cool in a very sincere way that is easy to make fun of or belittle. These traits do genuinely help me date! But not in the ways people might imagine. My sincerity has always been my best quality imo, but it is also deeply off-putting to a LOT of people in ways that have often driven them to lash out at me, not love me.

Myth 3: you must only date other people as experienced as you in all this

Truth: most of my partners didn't even know what I was offering was an option before we met. I have been personally involved in many a gender/sexuality coming out process for people in my life. Practice helps, and don't get me wrong, I do have a threshold for how much "teaching" so to speak I may have room for in a relationship. But I have been a first, second or third for nearly every person I've been with. Now that I think about it, that probably has something to do with the prevalence of the phrase kitchen table polyamory in the usa enm community now lmao, I really did serve as a lot of people's lynch pin relationship to the community over the years, so it's probably understandable for a lot of them to have internalized the language I used enough to cultivate/adapt an intra-communal lexicon.

Like, when it comes down to it, social rules are shortcuts. But to use a shortcut, you need to understand the baseline path too, otherwise you won't understand why those shortcuts sometimes dump you out on a road you weren't meant to be on. Is it exhausting to always have to take the long way round as someone to whom the shortcuts aren't accessible? Yes absolutely lol. But it gets less exhausting the more you have a community of people around you who really do see you as you need to be seen.

This got long so I'm gonna wrap here even tho I don't really feel like I've given you a good answer. Thanks for reaching out tho! And if this gives you an idea of more questions to ask, feel free!

[sufficientlylargen]

I don't know who needs to hear this, but

async function boop(n=100, user= "sufficientlylargen", type="super", delay=100) { for (let i = 0; i < n; i++) { await tumblr.apiFetch("/v2/boop", { method: "POST", body: { receiver: user, context: "post", type: type, }}) await new Promise(r => setTimeout(r, delay)) } } boop(1000, "sufficientlylargen", "super", 1000)

[itsjunetime]

tier list of rust std modules let's go

Rationale below the break

S

clone: It’s so important. You gotta be able to clone data around, and you gotta be able to restrict that ability. Crucial

collections: I use this every-fucking-where. Gotta have my HashSet, gotta have by BTreeMap. You know it

future: Love writing futures, love constraining futures, love all of that. And I gotta have that Future trait.

iter: Literally #1 - fucking love my iterations, wish I could write literally everything as an Iterator

option: Option is so fundamental. So many helper methods on it as well, beautiful functionality

ptr: If you’ve ever written complex ffi bindings or collections replacements, you know what I mean. The documentation is phenomenal and only getting better, the provenance projects are making it even even better.

result: Same rationale as option

sync: Arc my beloved. Also channels, mutexes, RwLocks, Atomics, etc, are all so important. Can’t do anything in multi-threaded code without using at least one of them.

vec: We all love Vec. I don’t think I need to explain myself.

A

alloc: Pretty cool and good, would love to see the allocator API stablized and then this would easily be an S tier

array: Manipulating arrays is very nice and good and useful, I just don’t don’t do it enough to put this in S

boxed: Love Box! Really nice and useful. Not something you’ll use in your every-day rust app, though, you only start using it once you’re really getting into the weeds or interacting with futures outside of async/await

cell: Very important to a lot of underlying abstractions in Rust, but just not something most people will really ever use (at least in my experience)

cmp: Useful utilities. Love the way they’re integrated with the langauge operators. V cool.

convert: Also useful! Love my (Try)?(From|Into)

default: Useful sometimes, but I feel like it’s abused occasionally. Also not a fan of seeing Default::default() where someone could’ve used the type name

fs: Gotta interact with a filesystem. Just feel like most rust apps spend most of their time not interacting with a filesystem.

marker: Very important, but most people won’t be interacting with these again.

mem: Love these, very useful, but mostly only useful for specific scenarios.

ops: Hugely important as well, obviously, but most people won’t ever actually manually access this module.

slice: Love manipulating slices - getting chunks, windows

B

borrow: Love Cow, but the whole Borrow vs AsRef thing still confuses me. I understand how they’re different, but I don’t quite understand the historical and tehcnical reasons for it, and feel like there could’ve been a better solution found to avoid this.

arch: Cool and such, but rarely used and a lot of the coolest stuff (portable simd) is still experimental and I rely on it a lot for performance reasons and really want it to stabilize soon.

error: std::error::Error. Woohoo

fmt: Nifty and such. It’s just kinda boring in comparison to all the other cool language features that exist in the standard library.

io: Cool, I guess. I just rarely every use it directly, I guess. And I am also kinda annoyed that AsyncRead and AsyncWrite aren’t things but also I think that the Async variants of traits could be avoided if people wrote more libraries in the sans-io style, so idk

panic: Mmm. I’m glad that the language provides a way for you to clean up during a panic, but I am personally really annoyed that panics are, in the end, recoverable. Irks me.

path: Path and PathBuf woohoo. Also tho such a pity that this module has to be a lot more complex due to windows backwards path separator bullshit. ugh

rc: Rc. Woohoo. I don’t like Rc much personally, I’ve written a lot of code in Rust and I’ve yet to encounter a scenario where I think “This situation could be solved or even helped by an Rc!”. But I understand its uses I guess.

str and String: Useful, yeah, but I’ll always be a bit pissed that they didn’t call them String and StringBuf instead (like they did with Path and PathBuf). Causes way too much confusion to early-on rust users

task: Useful, but I don’t get why they aren’t in future instead. Like, I guess they are used for streams and such, but still.

time: Fine… I guess it’s useful for people to be able to measure elapsed durations for logging and such and easy benchmarking but I just have a natural, deep-seated fear of any computer code that tries to interact with time as a concept so I’m very leery of this.

C

any: Mmmmmm I know it’s useful but I kinda hate that dyn Any is a thing you can do. It should (hopefully) become somewhat less prevalent now that trait upcasting is stabilized, though.

env: Used to be higher, but the whole ‘Linux makes no guarantees about accessing the environment from multiple threads’ thing irks me. I know it’s not Rust’s fault, but I’m still punishing them for it.

ffi: Confuses me that there’s so much duplication between this and os::raw - don’t like it. I know it doesn’t really matter which one you use, but whatever.

hash: Rarely actually interact with it directly. I know that it has to exist to facilitate (Hash|BTree)(Map|Set) but I don’t know what other use it has

net: Nearly all the time that I want to interact with stuff like TcpStream, I would rather use some async-specific net structs, such as are found in tokio.

num: Useful and cool, but I really think that this is seriously missing the traits from the num crate. There’s probably some specific reason why they don’t want to provide this, but the ability to reason around numeric attributes would be so useful.

os: OsStr and OsString suffer from the same sin as str vs String, but also are just inherently confusing due to the complexity that surrounds file paths in different OSes. I know that rust just surfaces all this complexity that hides beneath the surface but that doesn’t keep me from feeling like there was probably some better way to set up these structs

process: std::process::exit. woohoo

thread: Rarely do I spawn a thread manually - generally I want to use tokio or rayon or crossbeam or something like that. Good and useful, just rarely reached to and generally you’d be better off touching something else

D

backtrace: Good for one thing alone, which can be nice for quick and easy debugging, but if you just want a backtrace, a panic!() is easier, and if you can’t do that for whatever reason, you should probably just reach for a full debugger at that point

hint: Just like compiler fuckery. Love it, I do, but rarely do people interact with it, if ever, and really only useful for benchmarks and low-level atomic stuff (which, when I’ve done that, idk if I’ve even seen any sort of performance gains from spin_loop() sooo)

pin: Yes it’s important, but the constant struggle to make it not horrible to use for library developers really irks me. Still no way to (safely) match on pinned enums, no built-in pin projection without macros, etc. Ugh.

prelude: Yeah sure, whatever. You’ll never touch this.

primitive: This does need to exist, but if you’re reaching for this, you’ve fucked up. What are you doing.

F

ascii: I feel like this was a mistake. There are 4 things in it and 2 of them are deprecated. What are we doing.

char: Too many weird things here. Why does to_lowercase return an iterator? Why are these constants not in the primitive type instead? The whole escape stuff also feels arbitrary, and that’s part of the sin of the ascii mod.

f32 and f64: Everything here should be relegated to the primitive types. No need for these. Why are the integer types deprecated while this one isn’t? idk

(I also posted basically this exact same thing on my blog, june.cat, if that sort of thing interests you :))

[digitaldetoxworld]

Web to Mobile: Building Seamless Apps with .NET"

 .NET is a effective, flexible, and open-supply developer platform created with the aid of Microsoft. It enables the creation of a huge range of applications—from computing device to cellular, net, cloud, gaming, and IoT. Over the years, .NET has evolved substantially and has become one of the maximum extensively used frameworks inside the software improvement enterprise.

Dot Net Programming Language

A Brief History of .NET

The .NET Framework become first delivered through Microsoft in the early 2000s. The original cause turned into to offer a steady item-oriented programming surroundings regardless of whether code became stored and finished locally, remotely, or via the internet.

Over time, Microsoft developed .NET right into a cross-platform, open-supply framework. In 2016, Microsoft launched .NET Core, a modular, high-performance, cross-platform implementation of .NET. In 2020, the company unified all its .NET technologies beneath one umbrella with the discharge of .NET five, and later persisted with .NET 6, .NET 7, and past.

Today, the unified platform is actually called .NET, and it allows builders to build apps for Windows, macOS, Linux, iOS, Android, and greater using a single codebase.

Key Features of .NET

1. Cross-Platform Development

One of the maximum tremendous features of present day .NET (publish .NET Core) is its ability to run on a couple of platforms. Developers can construct and deploy apps on Windows, Linux, and macOS with out enhancing their codebases.

2. Multiple Language Support

.NET supports numerous programming languages, together with:

C# – the maximum extensively used language in .NET development

F# – a purposeful-first programming language

Visual Basic – an smooth-to-analyze language, regularly used in legacy programs

This multilingual capability allows developers to pick out the nice language for their precise use cases.

3. Extensive Library and Framework Support

.NET offers a comprehensive base magnificence library (BCL) and framework libraries that aid the whole lot from record studying/writing to XML manipulation, statistics get entry to, cryptography, and extra.

Four. ASP.NET for Web Development

ASP.NET is a part of the .NET platform specially designed for net improvement. ASP.NET Core, the cross-platform model, permits builders to build scalable internet APIs, dynamic web sites, and actual-time packages the usage of technology like SignalR.

5. Rich Development Environment

.NET integrates seamlessly with Visual Studio, one of the most function-wealthy integrated development environments (IDEs) available. Visual Studio offers capabilities together with IntelliSense, debugging tools, challenge templates, and code refactoring.

6. Performance and Scalability

.NET is thought for high performance and scalability, especially with its guide for asynchronous programming using async/wait for and its Just-In-Time (JIT) compilation.

7. Secure and Reliable

.NET presents sturdy safety features, including code get entry to security, role-based protection, and cryptography training. It also handles reminiscence management thru rubbish series, minimizing reminiscence leaks.

Common Applications Built with .NET

1. Web Applications

With ASP.NET Core, builders can create cutting-edge, scalable internet programs and RESTful APIs. Razor Pages and Blazor are technology within ASP.NET Core that help server-facet and purchaser-facet rendering.

2. Desktop Applications

Using Windows Forms or Windows Presentation Foundation (WPF), builders can build conventional computing device applications. .NET MAUI (Multi-platform App UI) now extends this functionality to move-platform computer and cellular programs.

3. Mobile Applications

Through Xamarin (now incorporated into .NET MAUI), developers can create native mobile applications for Android and iOS the usage of C#.

4. Cloud-Based Applications

.NET is nicely-acceptable for cloud development, in particular with Microsoft Azure. Developers can build cloud-local apps, serverless capabilities, and containerized microservices the usage of Docker and Kubernetes.

5. IoT Applications

.NET helps Internet of Things (IoT) development, allowing builders to construct applications that engage with sensors and gadgets.

6. Games

With the Unity sport engine, which helps C#, developers can use .NET languages to create 2D, three-D, AR, and VR games.

Components of .NET

1. .NET SDK

The Software Development Kit includes everything had to build and run .NET packages: compilers, libraries, and command-line tools.

2. CLR (Common Language Runtime)

It handles reminiscence control, exception managing, and rubbish collection.

Three. BCL (Base Class Library)

The BCL offers center functionalities including collections, record I/O, records kinds, and extra.

4. NuGet

NuGet is the package manager for .NET. It lets in builders to install, manage, and share libraries without problems.

Modern .NET Versions

.NET five (2020): Unified the .NET platform (Core + Framework)

.NET 7 (2022): Further overall performance enhancements and more desirable APIs

.NET 8 (2023): Continued attention on cloud-native, cellular, and web improvement

Advantages of Using .NET

Cross-platform assist – construct as soon as, run everywhere

Large developer network – widespread sources, libraries, and frameworks

Robust tooling – especially with Visual Studio and JetBrains Rider

Active improvement – backed by using Microsoft and open-source community

Challenges and Considerations

Learning curve – particularly for beginners due to its giant atmosphere

Legacy framework – older .NET Framework tasks aren't like minded with .NET Core or more recent variations without migration

Platform differences – sure APIs or libraries might also behave in a different way throughout operating systems

Getting Started with .NET

To begin growing with .NET:

Install the .NET SDK from the legitimate .NET internet site.

Create a new project: Use the dotnet new command or Visual Studio templates.

Write code: Develop your logic the usage of C#, F#, or VB.NET.

[ceausescue]

talk about the .net ecosystem. i know next to nothing about it, i think

so c# is microsofts answer to java, and .net is microsofts version of the jvm. im not a huge .net guy myself because until recently it was much better on windows, but it's a lively ecosystem of packages the way you'd have with any Serious Business Language For Getting Things Done. from what ive seen c# was very competitive for a while by being more willing to adopt new language features than java (better async, cleaner lambdas, both of which java has picked up). there are other languages that run on .net, just like the jvm- f# is a pretty popular functional language, and relevant to the terminal experience on windows, there's powershell the scripting language.

powershell is clunky, and the syntax is unintuitive, but it has access to the full power of the .net ecosystem. any windows machine will be full to the brim with random libraries to make shit run, and whatever interfaces they expose to developers are available in powershell. plus you get real types! it's the most powerful scripting language that keeps it's shell roots- the closest ive come is janet with the sh library, but it can't approach powershells integration with the rest of the system

[desert-palm]

Has anyone found a way to use both GraphQL Shield and dataloaders at the same time while using Apollo Server and NestJS?

I recently found that because I have asynchronous calls being made in some of my shield rules, it's causing my dataloader batch functions to be called multiple times, when they should only be called once, which leaves me with the N+1 problem across my entire app.

I believe this is due to how dataloader requires that all of the batch function calls occur during the same event loop "tick", and the async calls in my shield rules are preventing this.

Here's where I asked the question on reddit