#Delete a partition

[clouds-of-wings]

Fun fact: Divinity OS 2 Definitive Edition contains the entire original game too. As a separate game. That means when you install it you get 30GB of data that serves no purpose if you actually want to play the DE. You can basically delete the "Data" folder. Just keep the "DefEd/Data" folder.

(This is true for the GOG version, idk how it works on Steam.)

[ponyatowski]

so ive been to london for the (kindof) very first time as a conscious human being and man it is like. i can’t articulate all the feelings ive been having but its making me REALLY emo because Wow heres a city that seemingly works!

[turnedpalefromlackofsun]

Up next: windows 10

[daniel-nerd]

the sheer fear of using a dd command as a data hoarder is so immense that it dwarfs my anxiety

[effemimaniac]

I'm just strait up dd copying the whole still encrypted partition to the new drive I put in my laptop hope this works bc that would be soooo easy

[acotars]

my eras show is this week!!!! wooooo ?

[rajaniesh]

Supercharge Your Data: Advanced Optimization and Maintenance for Delta Tables in Fabric

Dive into the final part of our series on optimizing data ingestion with Spark in Microsoft Fabric! Discover advanced optimization techniques and essential maintenance strategies for Delta tables to ensure high performance and efficiency in your data Ops

Welcome to the third and final installment of our blog series on optimizing data ingestion with Spark in Microsoft Fabric. In our previous posts, we explored the foundational elements of Microsoft Fabric and Delta Lake, delving into the differences between managed and external tables, as well as their practical applications. Now, it’s time to take your data management skills to the next…

[budgiesizedchicken]

dd

tumblr tournament most fuckable gnu coreutils command

[monody-monody]

So I've recently been finally getting around to something I've wanted to do for a few years: switching to Linux.

To safely test out this process before applying it to my main tower machine, I decided to first do the switch over on an old Mac Mini which had a lot to gain from this as it was stuck on an outdated and unsupported version of MacOS.

But of course this all involved shuffling around a lot of old data and making sure everything was backed up. And here's where the story begins.

I backed up the Mini's MacOS install to its own partition on an external backup drive shared by my Windows tower machine. Once done, I shrank it to only the used size( which was complicated in its own right for reasons I'll explain shortly,) and then wanted to move it to the end of the drive so I could expand the Windows partition back out to fill the unused space.

Problem #1: MacOS's Disk Utility is so stripped down and lacking in functionality in the name of gloss, it literally cannot work with unallocated space on a drive in any way. You cannot see unallocated space, and you cannot create it. Want to shrink or delete a partition? It automatically creates a new one to fill the space whether you wanted it or not. Want to make a new partition in unallocated space without wiping the whole drive? Gotta use a different OS to make a dummy partition first and then replace it in Disk Utility. And the real problem… Want to move a partition? Can't.

Problem #2: Windows's Disk Management doesn't know what HFS+ is and refuses to work with it. Windows can't even read the Mac backup partition, let alone move it. But wait! I can use EaseUS Partition Manager! …Aaand most of its essential functionality is locked behind one of its multiple paywall tiers, including the ability to work with non-Windows filesystems at all.

But what about that new Linux install on the Mini?

I run 'sudo apt-get install gparted', a FOSS program, and in less than a minute I've already got it moving the partition. No hassle. No BS.

And if this whole thing doesn't just sum up the operating system trio, I don't know what does.

[xiao-come-home]

stone faced anon (💫 anon if it's free) here; as someone who has a hyperfixation in IT and coding I also think it would be very funny if Boothill had an s/o who wasn't necessarily a mechanic but like a software engineer or just a real big nerd about coding or something. He'll be experiencing a malfunction or a memory leak and go "oh yeah this happens sometimes don't worry about it" and then 10 minutes later he's sitting down plugged into a laptop listening to his s/o rant about how terrible his code is (crack hc: boothill's code was written in javascript) and how it's a wonder he hasn't bricked* yet

Would also be mad funny if Boothill ever got hacked and his s/o basically says "no you're not" and uses a previously made system restore point or something because of course they would both use and design every feature imaginable to keep Boothill in control of his own body, can you imagine the stress that losing control would cause him?? Even better if whoever designed him originally intentionally left a backdoor incase he ever went against their orders and when they try to use it his s/o just goes "oh yeah I quarantined and encrypted all the old files related to that backdoor and whatever else you were planning on a partition as bait and personally rewrote every file and function involved since your code is *an actual crime against technology*. by the way i'm going to go ahead and format that partition i mentioned, boothill- we won't be needing anything on it now that we can trace whoever made it. trust me, this won't be happening ever again."

*(bricking is a term mostly used to refer to hardware that's been rendered basically completely nonfunctional and beyond saving by using it wrong, mostly by messing with system files. Kinda like how windows can't even repair itself if you delete the system32 folder. Though i guess you could still install it with a usb stick if you formatted your pc- i digress you get what I mean. also since this almost happened to me recently: if you manage to fill up a hard drive to the brim, with literally 0 bytes of space left, that bricks it. reminder to check your storage thoroughly and often!)

Honestly wow I read it all and I'm a little bit speechless 🥹 thank you 💫 anon, it was great 🙏

Boothill would DEFINITELY appreciate a s/o who's a tech savvy in general! I think at some point, he'd be pretty shocked you're so knowledgeable and just sit there, listening to you rant.. and just letting you do your thing.

Don't get me wrong, he definitely knows a lot about his body, his system and the way he works, but once you start to get in the zone and explain stuff to him, berate his code even, he just sits next to you, plugged in to your laptop, leaning his cheek against his hand listening to you like he obviously understands everything you say.

His other hand begins to gently play with a stand of your hair, humming deeply when the soft clicking sounds of your keyboard reach his ears; he twirls your hair with his fingers and chuckles, "mmm, really now?" Boothill raises an eyebrow, "encryptin' this, encryptin' that... How about we do somethin' more fun instead?" And then you shut him down from your laptop (😭).

Jokes aside, he'd feel very secure with you especially when he first got his new body, just knowing you'll probably fix a lot of things that could possibly blow up his face in no time, maybe even improve his life even more.

[pleaseletmeinibeg453]

Paper cuts

|Jelsa, Modern AU, Enemies with Benefits, Fake dating, Forced Proximity|

Agent Elsa Stenford [NID-SO-ES-07] — Operation Report Upload Log

—Logged into secure terminal: Vienna Safehouse Terminal-2

—Date: 2022-07-08

—Time (UTC): 23:16

—Connected to secure node: NIDNet

—Report file: OP_SILENTRAVEN_AAR.enc

—Encryption status: Secured with NID Master Key — encryption signature verified (Checksum ID: F1A5-7C9B)

—Recipient(s): Jack Frost, Section Chief Special Operations (SO-92A), Acting Division Supervisor (DS-4), National Intelligence Directorate

—Transmission channel: Priority-One Secure Uplink (Classified Level: TOP SECRET)

—Transmission status: COMPLETE — audit log updated (Reference Log ID: ES07-0525-2214)

—Backup status: Encrypted local backup stored (Partition ES-07-SAFE); master copy uploaded to Central Ops Archive (Vault-4)

—Field confirmation: Agent ES-07 signed digital attestation; no tampering detected; self-authentication successful

Note: Automatic alert dispatched to Division Supervisor terminal. Clearance authentication required upon access.

---------------------------

Operation Silent Raven is an ongoing mission targeting a covert illicit arms trafficking network operating primarily in South Carolina. [Flag—Acting supervisor: Delete ‘ongoing mission’ — this is filler from someone unfamiliar with concise reporting. Vague and redundant.] This report details recent operational progress, intelligence collection, and actionable recommendations. [Flag—Acting supervisor: You clearly do not understand report structure. This useless sentence wastes time and space.] 

The primary objective is to identify, monitor, and dismantle the arms trafficking chain responsible for the flow of small arms and light weapons through various transit points in the region. [Flag—Acting supervisor: Restating obvious without any specifics or measurable targets reflects poor understanding of operational goals. Omit.] HUMINT sources have verified the existence of a new maritime transit corridor utilizing the seaport. [Flag—Acting supervisor: “HUMINT sources” is lazy projection. You apparently cannot be trusted to identify sources properly. Brackets demonstrate careless drafting.] SIGINT intercepted encrypted communications that suggest coordination between traffickers and local facilitators. [Flag—Acting supervisor: ‘Suggest’ is weak speculation, unbefitting a professional intelligence report. Either confirm or remove this guesswork.] 

Financial forensics have traced suspicious funds transfers totaling approximately $8 million USD linked to traffickers. [Flag—Acting supervisor: Provide specifics or this bland, meaningless statement reveals superficial analysis.] Technical surveillance detected multiple covert meetings in [Urban Centers], corroborated by photographic evidence. [Flag—Acting supervisor: Using placeholders signals either incompetence or utter disregard for accuracy.] On 2022-06-21, interdiction team, operating with local law enforcement, seized 250 illegal firearms at the port city warehouse. [Flag—Acting supervisor: Poorly structured sentence; the muddled passive voice further obscures the facts you apparently cannot clearly present.] Two principal suspects were detained, providing critical intelligence that identified higher-level facilitators. [Flag—Acting supervisor: Passive construction and vague attribution further demonstrate your failure to take ownership of this data.] 

Informant “Falcon” supplied actionable intelligence regarding a planned arms shipment scheduled for early June. [Flag—Acting supervisor: Finally, a clear statement, but unfortunately, it’s buried among verbosity and filler.] Operational security protocols were heightened after detecting possible surveillance by hostile intelligence actors. [Flag—Acting supervisor: ‘Possible’ surveillance indicates your uncertainty and it undermines the entire assessment and betrays inadequate situational awareness.] The network disruption has temporarily halted major arms transfers. [Flag—Acting supervisor: ‘Temporarily’ suggests you lack the insight or confidence to forecast outcomes. Such ambiguity is unacceptable.] 

Surveillance and intelligence collection continue focusing on secondary facilitators and financing channels. [Flag—Acting supervisor: Non-specific, passive phrasing again. You appear unable to report with decisiveness or clarity.] Coordination with allied intelligence agencies is ongoing to leverage broader interdiction efforts. [Flag—Acting supervisor: “Allied intelligence agencies” — weak and meaningless. Omit.] Risk assessment indicates elevated threat levels against NID assets involved in this operation. [Flag—Acting supervisor: Without elaboration, this statement is worthless. The absence of detail is either negligence or incompetence. I’m leaning towards the latter, although the first one also seems to be your defining trait.] Approve expansion of covert operations targeting secondary facilitators and financiers. [Flag—Acting supervisor: Recommendations lack essential resource planning and rationale, further exposing your inexperience.] Request additional SIGINT and counter-surveillance resources. [Flag—Acting supervisor: ‘Additional’ is meaningless without quantification. This sloppy request reflects poor operational understanding.] Initiate an inter-agency task force to address cross-border financing and logistics. [Flag—Acting supervisor: Unsubstantiated recommendation with no defined objectives — this is amateurish.] Continue monitoring and protection of key HUMINT sources and operatives. [Flag—Acting supervisor: Failing to specify protection protocols reflects a dangerous oversight on your part.] Attachments include interdiction team after-action report, financial transaction analyses, SIGINT intercept summaries, and photographic documentation of seized arms and facilities. [Flag—Acting supervisor: Referencing attachments without actual inclusion indicates either incompetence or disregard for proper reporting. Which one is it?]

Flag—Acting supervisor: This report is miserably inadequate and reflects a disturbing lack of professionalism and capability. The careless placeholders, vague assertions, passive voice, and speculative language betray your failure to grasp even the basic standards of intelligence reporting. Such work not only wastes time but actively hampers operational efficiency. REWRITE. 

---------------------------

Secure Directive

From: Jack Frost 

[Code: NID-SO-JF-01]

Section Chief, Special Operations / Acting Division Supervisor [Code SO-92A/DS-4]

To: Agent Elsa Stenford [Code:NID-SO-ES-07]

Subject: RE: Report Review – Operation Silent Raven

Classification: TOP SECRET // EYES ONLY

Agent Stenford,

Your submitted report for Operation Silent Raven is wholly inadequate and reflects a concerning lack of analytical rigor, operational discipline, and professional attention. The presence of unresolved placeholders, vague assertions, speculative conclusions, and critical data gaps is unacceptable at this operational level and wastes valuable time and resources.

This level of oversight is incompatible with the standards expected from an intelligence officer assigned to this unit. You are to:

1. Eliminate all placeholders and provide verified, cross-checked intelligence.

2. Remove speculative or assumptive language; include only confirmed, actionable data.

3. Rewrite sections for clarity, precision, and direct accountability — passive formulations are unacceptable.

4. Deliver detailed, concrete descriptions of sources, operational locations, timelines, and outcomes without ambiguity.

5. Ensure all referenced materials are attached, properly labeled, and internally consistent.

6. Strengthen recommendations by specifying exact resource needs, operational impacts, and executable directives.

7. Fully address risk assessments with defined threats, probability ratings, and specific mitigation strategies.

The supervisor-annotated version of your report (File ID: SR-Report-Rev1-JF) has been uploaded to the secure review system. You are to address all marked corrections and resubmit the fully corrected report no later than 1800 hours today. No further extensions will be granted.

Jack Frost 

[Code: NID-SO-JF-01]

Section Chief, Special Operations (SO-92A)

Acting Division Supervisor (DS-4)

National Intelligence Directorate

---------------------------

Agent Elsa Stenford [Code: NID-SO-ES-07] — Report Upload Log (Revised Submission)

—Logged into secure terminal: Vienna Safehouse Terminal-2

—Date: 2022-07-09

—Time (UTC): 17:38

—Connected to secure node: NIDNet 

—Report file: OP_SIENTRAVEN_AAR_v2.enc

—Encryption status: Secured with NID Master Key — encryption signature verified (Checksum ID: F1A9-7C3B-R2)

—Recipient(s): Jack FrostJack Frost (NID-SO-JF-01), Section Chief Special Operations (SO-92A), Acting Division Supervisor (DS-4), National Intelligence Directorate

—Transmission channel: Priority-One Secure Uplink (Classified Level: TOP SECRET)

—Transmission status: COMPLETE — audit log updated (Reference Log ID: ES07-0525-2316-R2)

—Backup status: Encrypted local backup stored (Partition ES-07-SAFE); master copy uploaded to Central Ops Archive (Vault-4, Revised Submission Folder)

—Field confirmation: Agent ES-07 signed digital attestation; no tampering detected; self-authentication successful

Note: Automatic alert dispatched to Division Supervisor terminal. Clearance authentication required upon access. Revision flag registered under Audit Protocol 4B.

---------------------------

Secure Directive

From: Jack Frost [Code: NID-SO-JF-01] 

Section Chief, Special Operations / Acting Division Supervisor [Code: SO-92A/DS-4]

To: Elsa Stenford [Code: NID-SO-ES-07]

Subject: RE: Secure Directive – Operation Silent Raven Report (Revised Submission)

Agent Stenford,

I have completed my review of your revised report on Operation Silent Raven. The annotated document is attached under:

Attachment: SilentRaven_Rev2_ES07_JFcomments.secure

To be precise: this submission remains below acceptable operational standards. Your continued use of speculative phrasing, unsupported assertions, and vague recommendations demonstrates a concerning lack of analytical discipline. This is not a matter of inexperience. You are not a trainee, Agent. At your level and position, you are expected to understand and apply the standards of rigor, precision, and clarity required in all agency reporting. That expectation is not optional.

Your report exhibits repeated failures:

1. Speculative language where concrete analysis is required;

2. Lack of referenced source attachments, despite multiple directives;

3. Unquantified risk assessments, absent methodological support;

4. Action recommendations devoid of operational specificity.

This is not a learning exercise nor is it a second chance, Agent Stenford. I should not be required to remind you of the foundational protocols governing intelligence reporting. You are expected to deliver work that reflects your clearance level, your operational rank, and your assigned responsibilities — without need for remedial oversight.

You are hereby directed to produce a final, fully compliant, actionable revision and submit it under secure protocol no later than 1300 hours tomorrow. Failure to meet this directive will result in formal escalation to the Division Office for immediate performance review. There will be no further instructions, no extended clarifications, and no tolerance for repeated submission failures.

Jack Frost [Code: NID-SO-JF-01]

Section Chief, Special Operations (SO-92A)

Acting Division Supervisor (DS-4)

National Intelligence Directorate

*

Operation Silent Raven: A report

1.⁠ ⁠Executive Summary:

—The target group’s network activity has intensified in the last 72 hours, with encrypted communications suggesting a planned operation within the capital region. [Flag—Acting supervisor: “Suggesting” is a charming euphemism for “guessing.” Precision is not your forte, is it?]

—HUMINT sources indicate the possible involvement of an external actor, potentially destabilizing regional security. [Flag—Acting supervisor:  “Possible” and “potentially” — a truly inspiring display of hedging. I applaud your commitment to ambiguity.] While these indicators warrant heightened surveillance, conclusive evidence regarding the exact nature and timing of the planned event remains unconfirmed. [COMMENT: I look forward to the day when ‘unconfirmed’ is replaced by ‘confirmed.’ Continue taking baby steps, we’re all here to babysit you and instruct on every level, not to do our job.]

2.⁠ ⁠Intelligence Sources:

SIGINT: Intercepted encrypted transmissions on frequencies 8.1 GHz to 8.3 GHz, believed to originate from multiple cell towers in the downtown sector. [Flag—Acting supervisor: “Believed.” A masterclass in non-committal language. Bold. Yet, it fails to meet the minimum standards of verification.] Metadata analysis aligns with previous hostile activity patterns.

[Flag—Acting supervisor: Please specify the parameters of your analysis. Otherwise, it reads as a hopeful suggestion rather than intelligence.]

HUMINT: Confidential informant reported unusual meetings near industrial sector 4. Reliability assessed as moderate; corroborating SIGINT incomplete. [Flag—Acting supervisor: ‘Moderate’ is an imaginative way of saying ‘I’m not sure.’ The agency appreciates your creativity but prefers facts.]

IMINT: Limited satellite imagery from 23-25 MAY shows increased vehicular movements near potential staging areas, but imagery quality insufficient for identification of personnel or equipment. [Flag—Acting supervisor: Including non-identifiable imagery is an excellent way to fill pages. Whether it aids operations is another matter. But who cares?]

3.⁠ ⁠Operational Assessment:

The convergence of SIGINT and HUMINT suggests preparatory steps for an operation targeting critical infrastructure. [Flag—Acting supervisor: ‘Suggests’ again. I see a pattern. Perhaps next time try ‘confirms’ or ‘demonstrates.’] Risk assessment places the likelihood of attack at moderate (probability 0.55), with potential impact categorized as high due to target significance. [Flag—Acting supervisor: : Quantify your methodology. Numbers plucked from thin air are less useful than no numbers at all.] Recommended actions include intensifying electronic surveillance, deploying field assets for direct observation, and liaising with allied cyber-intelligence units to monitor digital footprints. [Flag—Acting supervisor: Vague directives are the hallmark of an inexperienced analyst. Details and accountability please.]

4.⁠ ⁠Recommendations:

Immediate deployment of SIGINT intercept teams in the identified frequency bands. Enhanced HUMINT debriefings with source ES-27 to confirm meeting details. [Flag—Acting supervisor: The lack of specificity here suggests an admirable level of trust in the reader’s imagination.] Coordination with Cyber Ops for real-time network traffic analysis. [Flag—Acting supervisor:  Nomenclature alone does not constitute a plan. Flesh this out.]

Notes [Acting Supervisor] : 

—Formatting inconsistent with NID operational report guidelines. You’ve transformed a simple formatting standard into an elusive art form. Bravo.

—Failure to attach referenced supporting materials AGAIN. This recurring omission hinders operational efficacy. Consider attaching documents next time.

—In conclusion, REWRITE.

---------------------------

Agent [Code: NID-SO-ES-07] — Field Report Upload Log (Revised Submission)

—Logged into secure terminal: Vienna Safehouse Terminal-2

—Date: 2022-07-10

—Time (UTC): 13:00

—Connected to secure node: NIDNet

—Report file: OP_SILENTRAVEN_AAR_v3.enc

—Encryption status: Secured with NID Master Key — encryption signature verified (Checksum ID: F1A9-7C3B-R2)

—Recipient(s): Jack Frost, Section Chief Special Operations (SO-92A), Acting Division Supervisor (DS-4), NID

—Transmission channel: Priority-One Secure Uplink (Classified Level: TOP SECRET)

—Transmission status: COMPLETE — audit log updated (Reference Log ID: ES07-0710-1300-R2)

—Backup status: Encrypted local backup stored (Partition ES-07-SAFE); master copy uploaded to Central Ops Archive (Vault-4, Revised Submission Folder)

—Field confirmation: Agent ES-07 signed digital attestation; no tampering detected; self-authentication successful

Note: Automatic alert dispatched to Division Supervisor terminal. Clearance authentication required upon access. Revision flag registered under Audit Protocol 4B.

---------------------------

Secure Directive

From: Jack Frost [NID-SO-JF-01]

Section Chief, Special Operations / Acting Division Supervisor [Code: NID-SO-92A/DS-4]

To: Elsa Stenford [Code: NID-SO-ES-07]

Subject: RE: Secure Directive – Operation Silent Raven Report , Revocation of Field Authority and Immediate Reassignment

Agent Stenford,

I was informed last afternoon that due to shifting operational priorities, the report in question [Ops Silent Raven] is no longer required. 

After review of your latest submission — the revised report you provided earlier today — I must formally acknowledge that the material remains below acceptable operational standards. While I did not realistically anticipate any significant improvement, it is nonetheless disappointing that even after detailed corrective input, your output failed to meet the basic analytical and procedural thresholds expected of an intelligence officer at your level.

However, the time I was forced to expend personally correcting and annotating your repeated errors constitutes an unacceptable diversion of supervisory resources. You have now occupied more of this division’s time and attention than your current role warrants.

Accordingly, effective immediately, your independent field authority is revoked. You are reassigned to trailing support under Intelligence Officer Logan Parrish [CODE: NID-SO-LP-33], Team Blue. While Officer Parrish holds the same formal rank as you, his superior reliability and competence justify his lead role in this arrangement.

You are to operate strictly under Officer Parrish’s direction, with no independent decision-making or external communications without prior clearance. This corrective assignment will remain in place until further notice and serves as a necessary intervention to address the persistent deficits in your performance.

You are to report to Team Blue at 07:00 hours tomorrow, prepared and fully compliant. Written acknowledgment of this directive is required by 16:00 hours today. Noncompliance will result in immediate formal disciplinary action.

Jack Frost [Code: NID-SO-JF-01]

Section Chief, Special Operations (SO-92A)

Acting Division Supervisor (DS-4)

National Intelligence Directorate

---------------------------

Elsa Stenford read the message over and over again, because she knew it wasn’t serious. It must be a mistake. A joke. That’s what it was. Maybe if she read it again, it would change, it would shift and it would fix itself. So she read it, the words physically burning her, over and over again, but it stayed the same. She just stared at it, mouth hanging open, eyes wide with shock, unblinking. 

“Elsa?” Merida’s voice shattered the silence in her head. “Are you—”

“THAT MISERABLE FUCKING BASTARD! THAT FUCKING—” She stopped herself, but there was just too much rage and hate in her, enough for her to combust and paint the walls red. "FUCKING PIECE OF SCUM! I FUCKING HATE HIM, THAT USELESS, ARROGANT, SLIMY RAT!"

---------------------------

[maythedreadwolftakeyou]

MY BEAUTIFUL FILES AND 32 BIT PROGRAMS ARE ALL BACK IN PLACE AND FUNCTIONAL AGAIN HALLELUJAAAAAAAH 😭 the process was as MISERABLE as i expected since there's so so many conflicting tutorials out there. but after 2 days and many hours/frustrations (between the many hours of Waiting as things transfer and install) i found a nice old man on youtube who explained every step and what to change for diff models/machines that WORKED FOR REAL. and he didnt even have comments turned on so i cant post a heartfelt thank you. oh well.

anyway! the state of things:

last backup was from March 21st, my computer went out April 10th, so I lost about 3 weeks in there

luckily i was busy both of the weekends in there so not much was actually lost

what i lost, writing wise: recent progress on the lavellan-gets-gifted-a-dog fic (which isn't posted anywhere at all, so that's whatever i guess. it was just a thousand words or so i think + some brainstorming/notes section. gonna pretend no more than that if not), edits and miscellaneous added paragraphs for But One Truth which is already SO overdue so that's annoying, some lines/notes for the Spite POV fic and the Lucanis Ossuary fic but those are both still so chaotic i cannot fully remember which sections it may have been in.

what i lost, photoshop wise: some progress on the Davrin embroidery pattern, but a section i was already messing with, so... that's annoying but fine. Also some edits I made to art of Juniper. annoying but i can redo in an hour probably. also files for a meme or two but I don't really need those psd's anyway if i have the images themselves sent via internet to recover.

my beautiful chrome tabs: i did lose the new tabs i opened in those 3 weeks but lucky me the backup did in fact save all 836 tabs i had open from March so yippee. stop gasping in horror. its fine. the computer fans are just purring. she likes it.

whatever else: uploaded photos from my phone which don't count bc i still have my phone and can just reupload them, screenshots consigned to eventually be deleted anyway, had to reinstall 2 programs i did manually update in those 3 weeks but they didnt give me issues with the liscence keys so that was painless enough

don't you have a real job: luckily i do have emailed copies of my grad school manuscript drafts and r code so those were surviving anyway. but it Would be a big pain to have to set everything up on my windows computer instead for version reasons and also just my sanity. so i'm glad i can keep working on this system instead

so anyway. I'M BACK IN BUSINESS. also general reminder to back up your data. this would have been so so so much worse if i did not do that fairly regularly. also dont trust the apple store to honor their word that they won't try to sneakily update your computer to "help".

no WIPs or tag game snippets or etc from me for a bit because my main computers ssd crashed/failed this week so 🙃 rip

[turnedpalefromlackofsun]

i accidentally deleted the entire mac os

oopsies i wasnt trying to do that

[chosaraki]

You're still my home, even behind bars

—————————————————————————

Gun Park x R.femele. (Sensitive, stubborn, brave )

—————————————————————————

Y/N inspired by Takemichi Hanagaki.

—————————————————————————

The cell was small, cold, smelling of wet concrete and old food.

Gun was sitting in the corner, his hands handcuffed in front of his body. The orange uniform made him look even more out of place than ever. He didn't talk to anyone. Not with the guards. Not with the other inmates.

But that day, he was called to the living room.

The guard opened the metal door with a dry snat.

- You have a visitor. -

Gun got up without haste, as if he didn't care. But inside, something was turning around. He already knew who it was.

⸻

Guest Room.

The glass partition separated the two worlds. That of violence and that of hope.

And there she was.

Y/N. Sitting with her hands on the metal table. Loose hair, eyes too big for that dirty place, heart exposed just for existing there. She wore a wide and simple sweatshirt, but for Gun... she looked dressed like a miracle.

He sat on the other side. He picked up the phone with laziness. But his eyes were glued to her.

- That's stupid - he said right away. - You shouldn't have come.

She held the phone too. Her voice trembled a little, but it was firm.

- So why did you come here?

Silence. He looked at the floor. Then for her.

That small and fragile face. The eyes that always seemed about to cry - but never gave up.

She reminded him that he was human. And he hated it. I loved that.

- Why do you visit me, Y/N?

- Because you're still mine. Even so. Even here.

She leaned her forehead against the glass, her eyes watery.

- I know you, Gun. I know who you are when no one is looking.

- I'm trash.

- No. You treat yourself like trash. But you're not.

She took a deep breath. The eyes shone with anger and love mixed.

- You protected me so many times, kept me alive, faced monsters for me... and now you want to throw yourself into the bottom of this hole alone?

- I deserve this hole.

- And do I deserve to live without you? - she replied. The voice came out broken. - Do you think only you bleed? That only you feel pain?

Gun squeezed the phone hard. His eyes turned red.

But he hasn't cried yet. Not yet.

She put her hand on the glass.

- Play here, please. That's all.

Gun hesitated.

But then, he raised his handcuffed hand and touched the glass as well.

The hands didn't really touch each other. But the gesture... hurt as if they were touching.

- When you leave here, I'll still be here - she whispered. - Waiting for you. Even if you hate me for that.

He finally looked into her eyes with truth.

- I don't hate you.

Pause.

- I just don't know how to be worthy of you.

She smiled. Crying.

- So start being worthy of yourself.

—————————After the visit—————————

Back in the cell, Gun was sitting in the dark corner, with his eyes fixed on any point.

But he was shaking.

One of the inmates mocked:

- Was she your wife? Too cute for you, huh.

Gun got up slowly. Very slowly.

- Repeat that.

- What, that she's hot?

The sound that came later was dry. Violent.

Gun broke the man's nose with a single headbutt, then pressed him against the wall with the handcuff still on his wrists.

- Talk about her again and I'll make you unrecognizable, understand?

The inmate was bleeding, but laughing nervously.

- Are you in love?

- Fuck you.

Gun walked away, throwing himself back on the hard bed.

But that night...

He dreamed about her.

Not with her body. But with laughter.

With the way she looked at him as if there was still salvation.

With the way her hand trembled when she touched the glass.

———————Another day——————————

The next day, the guard brought a letter.

Gun opened in a hurry. Y/N era.

Inside, just a handwritten phrase:

"Even in the dark, you are still my most dangerous light. Don't delete it."

He smiled. For the first time in weeks.

—————————————————————————

She disarms him with words, tears and a silent promise: she will wait for him - even if he thinks he doesn't deserve it.

—————————————————————————

[shadowbannedhero]

Today I learned that for the Anti-Israel / Pro-Hamas crowd, it is perfectly acceptable to kink shame and encourage others to do the same.

@papasmoke didn't care to respond to my points or questions about his rhetoric (which is fine, no one said he has to), but instead chose to attack me because of my fetish, and sent others to do the same.

No matter what @angelsarecomputers thinks, this is kink shaming. This is a personal blog. I have political opinions and I like women's feet. I find neither embarrassing. All his demand that I partition the two does is showcase his judgement and disdain of other people's desires.

Then there is @putriddevine jumping on the pile, contributing nothing of value.

Finally, we have @zandraxofnebulon. Tell me zandrax, why would I delete it? Because you think I might possibly care about what those who make fun of someone's sexual desires think? That I am ashamed of what I am attracted to?

Fuck off, zandrax. Attack my views on the rhetoric I questioned if you must. But to assume I am ashamed of being attracted to a body part? Seriously. Fuck yourself. That goes for the others as well.

Learn some toleration. Be better.

[lu-sn]

Arm has a top-secret file that he keeps on a separate partition of his hard drive, locked behind three different password walls. It’s a list of all of the main family’s bodyguards, ranked by how likely they are to be the mole.

(It’s top-secret because he’s not supposed to be looking into this. Chan explicitly ordered him not to.)

There’s a handful of people Arm doesn’t even bother putting on the list. Pol, for one. Pete. Erika. Chan.

By contrast, every single one of Kinn’s personal bodyguards, past and present, is a prime suspect. Kinn’s had a notorious streak of bad luck lately. Four murder attempts in four months cannot be a coincidence.

Ken is just aloof enough that nobody seems to know what he’s up to on his off-days. This rockets him straight to the top of Arm’s list, tied with Big, who has fallen so far out of favor with Kinn that Arm can’t help but wonder if Kinn is doing it on purpose.

And then there’s the name directly under those two.

“Be honest,” he says to Pete one day. They’re sequestered in his armory, but he keeps his voice low: there’s no harm in being careful with matters like this. “Do you think there’s any chance Porsche is the mole?”

Pete is silent for a good, long moment.

“You live with him,” Arm says. “You’ve been on more missions with him than me. If anyone here knows him best, it’s you.”

“There are reasons to suspect him,” Pete says slowly. “A lot of his missions have gone wrong. He didn’t stop that girl from attacking Kinn in the bathroom. The casino stakeout was a mess. The diamond auction was worse.”

“But…?”

Pete sighs. “I don’t know. He’s young. He’s made a lot of mistakes, but he’s improving.”

Arm stares forlornly at his list, cursor blinking innocently next to Porsche’s name. “Pete, I can’t clear his name just because he’s young.”

“No,” Pete concedes. He leans back in his chair, arms crossed behind his head. “But he’s kind, too. He’s principled. He won’t betray people he cares about.”

“And that’s enough? You trust him?”

“I do.”

The knot in Arm’s chest jerks tighter. “But… he’s so likable.”

“Ohhh, right, he’s nice. Never mind. Death by firing squad.”

Arm smiles, sheepish.

“Okay,” Pete says. “So you think he’s tricking us?”

“Shit, Pete, I don’t know,” Arm splutters. “Isn't it possible?”

“I don't think so. Porsche isn't like that.”

Arm considers this, then plops his face into his hand.

“Did you want me to say something else?” Pete says, faintly amused.

“Yes,” Arm groans.

“Why?”

“Because…” Arm trails off.

Because the security of the main family rests on his shoulders. Arm cannot afford to be anything other than objective; he needs to leave Porsche on his list.

But the problem is that Porsche barreled into their lives and immediately made Khun Noo happier than Arm had ever seen before. The problem is that Pol hasn’t been this comfortable around someone since Arm himself. The problem is that Arm vaguely remembers being carried home from Hum Bar by an equally drunk Porsche, who took off his shoes for him and tucked him into bed and grinned brightly over his shoulder before staggering out the door.

The problem is that Arm is biased.

Pete, on the other hand, is the most level-headed person Arm knows. Leaving Porsche’s name on his list wouldn’t feel so terrible if Pete agreed with it.

“I wanted you to give me a reason to keep him on here,” Arm mumbles. “I feel bad. He’s our friend.”

“You’re doing your job,” Pete says sincerely. “There’s no shame in that. But…” He reaches over to pat Arm on the shoulder. “There’s nothing wrong with trusting your gut. If you think he’s innocent, leave him off.”

Arm mulls over this. Then he pokes Pete in the side. “I think I trust your gut more than mine.”

Pete lets out a laugh, incredulous, and pokes Arm back.

-

Later, Arm highlights Porsche’s entry with his cursor and drags it to the bottom of the file. Then he pauses. His hand hovers over the delete button.

He thinks about Pete saying, I trust him. He thinks about what Pete didn’t quite say: you should trust yourself, too.

He hits delete.

-

#kpanniversary2024 episode 9 + prompt 9: trust