#Interface Configuration

[ss-1990]

Connecting the Dots: The Importance of Lab Analyzers Interfacing

In the intricate tapestry of laboratory operations, the seamless integration of lab analyzers is paramount. From chemistry analyzers to hematology instruments, each component plays a vital role in the diagnostic process. However, the true magic happens when these disparate pieces come together through lab analyzers interfacing. This synergy not only streamlines workflow but also enhances the efficiency and accuracy of diagnostic testing.

At the heart of lab analyzers interfacing lies instrument integration. Gone are the days of siloed instruments operating in isolation. Modern laboratories demand interconnectedness, where analyzers communicate harmoniously to deliver cohesive results. Through advanced integration protocols, laboratories can orchestrate a symphony of analyses, maximizing throughput and minimizing turnaround times.

Yet, integration is merely the first step. The crux of lab analyzers interfacing lies in data transfer. Patient samples traverse a labyrinth of analyzers, each generating a plethora of data points. Efficient data transfer mechanisms ensure that these valuable insights flow seamlessly from one instrument to another, without loss or distortion. Whether it's transmitting test results or patient demographics, the integrity of data transfer is sacrosanct.

However, the path to seamless interfacing is fraught with challenges, chief among them being compatibility testing. Not all analyzers speak the same language or adhere to uniform data standards. Compatibility testing is akin to deciphering a complex code, ensuring that disparate instruments can understand and interpret each other's signals. Through meticulous testing protocols, laboratories can preempt compatibility issues and preemptively resolve them.

Moreover, effective interface configuration is essential for optimizing analyzers' interoperability. Customized configurations tailor interfaces to the unique needs of each laboratory, ensuring smooth data exchange and minimizing errors. Whether it's defining data formats or establishing communication protocols, meticulous interface configuration is the linchpin of successful lab analyzers interfacing.

In the realm of lab analyzers interfacing, middleware solutions serve as the bridge between disparate instruments. These software platforms harmonize data exchange, transcending the barriers of instrument heterogeneity. Middleware solutions not only facilitate seamless interfacing but also offer advanced functionalities such as result validation and autoverification, further enhancing laboratory efficiency and quality.

In conclusion, lab analyzers interfacing is the linchpin of modern laboratory operations, fostering synergy among disparate instruments and maximizing the efficiency and accuracy of diagnostic testing. Through the seamless integration of instruments, efficient data transfer mechanisms, meticulous compatibility testing, customized interface configurations, and middleware solutions, laboratories can unlock new frontiers of efficiency and excellence. As laboratories continue to evolve in tandem with technological advancements, the importance of lab analyzers interfacing will only grow, cementing its status as a cornerstone of diagnostic excellence.

[catastrophic-crow]

gods i love wired headphones. love having headphones with a headphone jack (and thus a replaceable cable) and no other way of playing music. love 10 foot long audio cables. love dedicated usb DACs. love headphones that are designed primarily for long-term listening comfort and don't need to have extra bulk in hinges or padding to make them more sturdy or flexible to accommodate being shoved in a bag when you're done with your commute. love high-quality audio with no perceptible delay and no fucking battery life and no extra mass from a bluetooth module and microprocessor and flashable ROM and a battery and charging circuit and onboard DAC and amp driving the speaker(s) weighing my head down.

[doolallymagpie]

befitting the work of a mad scientist being bankrolled by fascists, the Caliban III A would probably explode if it tried to alpha strike, seeing as how it mounts so few heat sinks compared to the horrifying number of laser weapons

plus it's got a direct neural interface, specifically to mount MORE shit on the thing by removing the need for a gyro (explanation for a 3048 chassis having that kind of tech is "Cortazar is your typical mad scientist miracle worker with an infinite budget"

basically, everything he hoped and dreamed for the original he made (and later retrofitted after Bobbie tore its arm off) for JPM, with all of the consequences

[deliandiver]

Новая идея - «Модуль Счетверённых Конфигурируемых Логических Вентилей»

[jumoyz]

Comment Utiliser ChatGPT? Guide pour 2024

En 2024, ChatGPT, le chatbot révolutionnaire développé par OpenAI, continue de transformer la manière dont nous interagissons avec l’intelligence artificielle. Que ce soit pour rédiger des dissertations, écrire des e-mails, générer du code, ou encore trouver des titres d’articles, ChatGPT s’est imposé comme un outil indispensable pour les professionnels et les étudiants. Ce guide vous montrera…

[hms-software-timecontrol]

A configurable search interface helps set TimeControl apart

A configurable search interface helps set TimeControl apart from other enterprise applications. The configuration of the Table Search function allows a TimeControl Administrator to determine what fields they want to be searchable and which should be ignored. That makes searching in a table as simple and easy for end users as the Administrator decides.

Many versions of TimeControl ago, we were confronted with a dilemma. How do we search the TimeControl tables? TimeControl is architected around many interrelated tables and each of these tables can hold dozens or hundreds of fields.  Some of these fields may be designed for internal system use. Some may contain data.  Some may only contain data if that TimeControl instance has been configured to…

[forlinx]

Display and Modification of LVDS Display Interface on AM62x Development Board

1. LVDS Interface Specification

Forlinx Embedded OK6254-C development board provides 2 x 4-lane LVDS display serial interfaces supporting up to 1.19Gbps per lane; the maximum resolution supported by a single LVDS interface is WUXGA (1920 x 1200@60fps, 162MHz pixel clock).

In addition, the interface supports the following three output modes:

(1) Single-channel LVDS output mode: at this time, only 1 x LVDS interface displays output;

(2) 2x single-channel LVDS (copy) output mode: in this mode, 2 x LVDS display and output the same content;

(3) Dual LVDS output mode: 8-lane data and 2-lane clock form the same display output channel.Forlinx Embedded OK6254-C development board is equipped with dual asynchronous channels (8 data, 2 clocks), supporting 1920x1200@60fps. All signals are by default compatible with Forlinx Embedded's 10.1-inch LVDS screen, with a resolution of 1280x800@60fps.

2. Output Mode Setting

(1) Single LVDS output mode:

We need a single LVDS screen cable. The black port of the cable is connected to the embedded OK6254-C development board, and the white port is connected to the embedded 10.1-inch LVDS display screen. Connection method as shown in the figure below:

Note that the red line section corresponds to the triangle position, so don't plug it in wrong.

(2) 2x single LVDS (duplicate) output mode:

This mode uses the same connections as the Single LVDS Output Mode. Two white ports link to two 10.1-inch LVDS screens from Forlinx Embedded, and a black port on the right connects to the OK6254-C board's LVDS interface for dual-screen display.

(3) Dual LVDS output mode:

The maximum resolution supported by a single LVDS interface on the OK6254-C development board is WUXGA (1920 x 1200@60fps). To achieve this high-resolution display output, dual LVDS output mode is required.

It is worth noting that the connection between the development board and the screen in this mode is the same as in [Single LVDS Output Mode], but the LVDS cable's and the screen's specifications have been improved.

3. Screen Resolution Changing Method

OK6254-C development board device tree is easy to modify, we need to open the OK6254-C-lvds.dts (single 8-way configuration) and OK6254-C-lvds-dual.dts (dual 8-way configuration) files.

Open OK6254-C-lvds.dts

Open OK6254-C-lvds-dual.dts

The above figure is the single LVDS and dual LVDS screen resolution information, the default resolution of 1024 * 600, and the maximum resolution support of 1920x1200, you can modify the corresponding parameters according to the Screen User’s Manual.

4. Compilation Configuration

Because we only modified the device tree, we don't need a full compilation. After compiling the kernel, a new Image and multiple device tree files will be generated in the images directory. Here we only need to compile the kernel separately.

(1) Switch directory: cd OK6254-linux-sdk/

(2) Execution environment variables:.. build.sh

(3) Execute the instructions that compile the kernel separately: sudo./build. Sh kernel.

(4) Pack all the device tree files to the development board /boot/ directory and replace them, then sync save and reboot scp images/OK6254-C* root@172.16.0.225:/boot/

We have modified the corresponding file. How should we select the screen after replacing it? At present, there are three kinds of screen switching control methods: kernel device tree designation, Uboot menu dynamic control, Forlinx Desktop interface and Uboot menu application. Today, I will briefly introduce the dynamic control of Uboot menu.

During Uboot, pressing the space bar will take you to the Uboot menu. There are three options in the menu:

Enter 0 to enter the Uboot command line;

Enter 1 to restart Uboot;

Enter 2 to enter the Display Configuration menu.

There are three options in the menu:

Enter 0 to return to the previous menu;

Enter 1 will toggle what option 1 displays to configure Screen 1 LVDS; Note: Screen 1 supports single LVDS, dual LVDS, and off (i.e., LVDS off)

Enter 2 to toggle the display of option 2 to configure the Screen 2 LCD. Note: Screen 2 supports 1024 * 600 resolution LCD screen, 800 * 480 resolution LCD screen and off (i.e. RGB off)

When selecting the LVDS screen, we enter 1 to select single 8-channel LVDS or dual 8-channel LVDS.

After selecting the desired configuration, enter 0 to return to the previous menu level. Restart Uboot or enter the command line to start the system, which can make the screen settings take effect. For other resolution screens, please modify the kernel device tree screen parameters according to the screen parameter requirements.

Originally published at www.forlinx.net.

[sw5w]

Anakin Skids to a Stop

STAR WARS EPISODE I: The Phantom Menace 01:59:00

[virtualizationhowto]

TrueNAS SCALE Network Configuration Tips for Home Server

TrueNAS SCALE Network Configuration Deep Dive for Home Server #homeserver #TrueNASScaleNetworkConfiguration #FailoverSetupGuide #LoadbalancingOnTrueNAS #VLANConfigurationTrueNAS #BridgeInterfaceGuide #TrueNASStaticIPAddressSetup #TrueNASSystemSettings

When you set up a TrueNAS SCALE server, one of the first configuration items you will want to tackle is the network configuration. This helps make sure you achieve optimal performance and security. If you are struggling to configure your TrueNAS SCALE home server networking, this post will help you configure a static IP address, Link Aggregation (Failover, LoadBalance, LACP), VLAN, and Bridge…

[commodorez]

Cactus fascinates me, does it run on code similar to an existing instruction set or is it completely original on that front?

What can you do with it? What's it's storage?

Both the Cactus (the original wooden prototype from years ago) and the new PCB Cactus(es) are essentially derived from a minimal 6502 computer design by Grant Searle for their core logic. Here's what that would look like on a breadboard:

There isn't much to it, it's 32K of RAM, 16K of ROM containing Ohio Scientific's version of Microsoft BASIC, a 6850 ACIA for serial interaction, some logic gates, and of course a 6502 microprocessor (NMOS or CMOS, doesn't matter which). You hook it into a terminal and away you go.

Grant's design in turn can be best described as a distilled, modernized version of the OSI Challenger series of computers. Here's an OSI-400 and a Challenger 4P respectively:

The left one is a replica of the 400 circa 1976, also called the Superboard. It was affordable, endlessly reconfigurable and hackable, but ultimately very limited in capabilities. No BASIC, minimal monitor ROM you talk to over serial, but you could connect it to a bus to augment its features and turn it into a more powerful computer.

Whereas the OSI C4P on the right from about 1979 has more RAM, a video card, keyboard, BASIC built in, serial interface, cassette tape storage, and that's just the standard configuration. There was more room to expand and augment it to your needs inside the chassis (alot changed in 3 years for home computer users).

Grant's minimal 6502 design running OSI BASIC is a good starter project for hobbyists. I learned about the 6502's memory map decoding from his design. I modified and implemented his design on a separate cards that could connect to a larger backplane.

Here are the serial, ROM, RAM, and CPU cards respectively:

Each one is 100% custom, containing many modifications and fixes as I developed the design. However, that's only half of the computer.

I really wanted a 6502 machine with a front panel. People told me "nobody did that", or couldn't think of examples from the 1970s but that seemed really strange to me. Especially since I had evidence to the contrary in the form of the OSI-300:

This one I saw at VCF West back in 2018 illustrates just how limited of a design it is. 128 bytes of RAM, no ROM, no serial -- just you, the CPU, and toggle switches and LEDs to learn the CPU. I was inspired the first time I saw one in 2015 at VCF East, which is probably when this whole project got set in motion.

Later that year I bought a kit for a miniature replica OSI-300 made by Christopher Bachman, and learned really quickly how limited the design philosophy for this particular front panel was. It was a major pain in the ass to use (to be clear, that's by OSI's choice, not any fault of Christopher in his implementation)

So... I designed my own. Took awhile, but that's the core of what the Cactus is: my attempt at experiencing the 1970s homebrew scene by building the computer I would have wanted at the time. Over half of the logic in the Cactus is just to run the front panel's state machine, so you can examine and modify the contents of memory without bothering the 6502. I added in all of the things I liked from more advanced front panels I had encountered, and designed it to my liking.

Here's the original front panel, accompanying logic, and backplane connected to the modern single board computer (SBC) version of the machine:

And here's the new Cactus SBC working with the new front panel PCB, which combines the logic, physical switch mountings, and cabling harnesses into a single printed circuit board.

So, what can you do with it? Pretty much the same things I do already with other contemporary 1970s computers: play around in BASIC, fire up the occasional game, and tinker with it.

I've got no permanent storage designed for the Cactus as yet, it's been one of those "eventually" things. The good news is that a variety of software can be ported to the hardware without too much trouble for an experienced hobbyist. A friend of mine wrote a game called ZNEK in 6502 assembly which runs from a terminal:

Right now, you have to either toggle in machine programs from the front panel from scratch, burn a custom ROM, or connect it to a serial terminal to gain access to its more advanced features:

Here's it booted into OSI BASIC, but I have also added in a modern descendant of Steve Wozniak's WOZMON software for when I need to do lower level debugging.

I've also got a video card now, based on the OSI-440. I have yet to implement a keyboard, or modify BASIC to use the video board instead of the serial connection. Even if I did, screen resolution is pretty limited at 24x24 characters on screen at once. Still, I'm working on that...

Anyway, I hope that answers your question. Check the tags below to see the whole process stretching back to 2017 if you're curious to learn more of the project's history. I'm also happy to answer any more questions you might have about the project.

[leveragehunters]

Downloading fanfic from AO3

I've been downloading a lot of fanfic lately for personal archival purposes, and I figured I'd share how I do it in case it's useful to anyone else (and so I have it written down in case I forget!).

There are lots of different ways to save fic, including the file download built into AO3, but I find that this gives me the nicest ebooks in the most efficient way.

(Under a cut cause long.)

Download Calibre: https://calibre-ebook.com/ or (clickable link).

Calibre is about the best ebook management and control program around and it's free. You can get it for windows, mac, and linux or download and run it from a portable storage device (I'm using a windows PC).

Install it and run it. It's gonna ask you where you want to put your library. Dealer's choice on this one. I recommend your internal drive (and then back up to external/cloud), but YMMV.

If you want to keep fanfic separate from the rest of your ebooks, you can create multiple libraries. I do, and my libraries are creatively named 'Books' and 'Fic'.

Customise Calibre

Now you're gonna install some plugins. Go to Preferences on the menu bar (far right), click its little side arrow, then choose 'Get plugins to enhance Calibre'.

At the top right of the box that pops up is 'Filter by name'. The plugins you want to get are:

EpubMerge

FanFicFare

Install them one at a time. It will ask you where you want them. I recommend 'the main bar' and 'the main bar when device is attached' (should be selected by default). When you're done, close and reopen Calibre.

The plugins you just installed should appear on the far right of the toolbar, but if you can't see one or both of them, fear not! Just click Preferences (the button, not the side arrow), then Toolbars and Menus (in the 'Interface' section) then choose the main toolbar from the drop down menu. That will let you add and remove things - I suggest getting rid of Donate, Connect Share, and News. That'll leave you room to add your new plugins to the menu bar.

(Do donate, though, if you can afford it. This is a hell of a program.)

Now you're ready to start saving your fave fanfic!

Saving fanfic

I'll go through both methods I use, but pick whatever makes you happy (and/or works best for what you're downloading).

ETA: if the fics are locked you can't easily use FanFicFare. Skip down to the next section. (It does ask for a username/password if you try and get a locked fic, but it's never worked for me - I had to edit the personal.ini in the configuration options, and even then it skips locked fics in a series.)

Calibre and FanFicFare

You can work from entirely within Calibre using the FanFicFare plugin. Just click its side arrow and pick from the menu. The three main options I use are download from URL, make anthology from a webpage, and update story/anthology.

Download from URL: pick Download from URL (or just click the FanFicFare button) and paste the fic's URL into the box (if you've copied it to your clipboard, it will be there automatically). You can do more than one fic at a time - just paste the URLs in one after the other (each on a new line). When you're done, make sure you have the output format you want and then go.

Make Anthology Epub From Web Page: if you want a whole series as a single ebook, pick Anthology Options, then Make Anthology Epub From Webpage. Paste the series URL into the box (if you've copied it to your clipboard, it will be there automatically), click okay when it displays the story URLs, check your output format and go.

Update series/anthology: if you downloaded an unfinished fic or series and the author updates, you can automatically add the update to your ebook. Just click on the ebook in Calibre, open the FanFicFare menu using its side arrow, and select either Update Existing FanFic Books or Anthology Options, Update Anthology epub. Okay the URLs and/or the output format, then go.

Any fic downloaded using FanFicFare will be given an automatically generated Calibre cover. You can change the cover and the metadata by right clicking on the title and picking edit metadata. You can do it individually, to change the cover or anything else specific to that ebook, or in bulk, which is great for adding a tag or series name to multiple fics. Make sure you generate a new cover if you change the metadata.

Browser plugins, Calibre, and EpubMerge

You can also use a browser addon/plugin to download from AO3. I use FicLab (Firefox/Chrome), but I believe there's others. FicLab: https://www.ficlab.com/ (clickable link).

FicLab puts a 'Save' button next to fic when you're looking at a list of fics, eg search results, series page, author's work list etc. Just click the 'Save' button, adjust the settings, and download the fic. You can also use it from within the fic by clicking the toolbar icon and running it.

FicLab is great if you're reading and come across a fic you want to save. It also generates a much nicer (IMO) cover than Calibre.

You can add the downloaded fic to Calibre (just drag and drop) or save it wherever. The advantage to dropping it into Calibre is that all your fic stays nicely organised, you can adjust the metadata, and you can easily combine fics.

Combining fics

You can combine multiple fics into an anthology using EpubMerge. This is great if you want a single ebook of an author's short fics, or their AUs, or their fics in a specific ship that aren't part of a series. (It only works on epubs, so if you've saved as some other format, you'll need to convert using Calibre's Convert books button.)

Select the ones you want to combine, click EpubMerge, adjust the order if necessary, and go.

The cover of the merged epubs will be the cover of the first fic in the merge list. You can add a new cover by editing the metadata and generating a new cover.

Combing with FanFicFare

You can also combine nonseries fics using FanFicFare's Make Anthology ePub from URLs option by pasting the individual fic URLs into the box.

Where there's more than a few fics, I find it easier to download them with FicLab and combine them with EpubMerge, and I prefer keeping both the combined and the individual versions of fic, but again YMMV.

Reconverting and Converting

Once I'm done fussing, I reconvert the ebook to the same format, to ensure everything is embedded in the file. Is this necessary? YMMV, but it's a quick and easy step that does zero harm.

If you don't want your final ebook to be an epub, just convert it to whatever format you like.

Disclaimers

Save fanfic for your own personal enjoyment/offline reading/safeguarding against the future. If it's not your fic, don't distribute it, or upload it to other sites, or otherwise be a dick. Especially if the author deletes it. Respect their wishes and their rights.

This may work on other fanfic sites, eg FFN, but I've never tried so I don't know.

If you download a fic, do leave the author a kudo or a comment; you'll make them so happy.

This is how I save fic. I'm not pretending it's the only way, or even the best way! This is just the way that works for me.

[codingquill]

Welcome back, coding enthusiasts! Today we'll talk about Git & Github , the must-know duo for any modern developer. Whether you're just starting out or need a refresher, this guide will walk you through everything from setup to intermediate-level use. Let’s jump in!

What is Git?

Git is a version control system. It helps you as a developer:

Track changes in your codebase, so if anything breaks, you can go back to a previous version. (Trust me, this happens more often than you’d think!)

Collaborate with others : whether you're working on a team project or contributing to an open-source repo, Git helps manage multiple versions of a project.

In short, Git allows you to work smarter, not harder. Developers who aren't familiar with the basics of Git? Let’s just say they’re missing a key tool in their toolkit.

What is Github ?

GitHub is a web-based platform that uses Git for version control and collaboration. It provides an interface to manage your repositories, track bugs, request new features, and much more. Think of it as a place where your Git repositories live, and where real teamwork happens. You can collaborate, share your code, and contribute to other projects, all while keeping everything well-organized.

Git & Github : not the same thing !

Git is the tool you use to create repositories and manage code on your local machine while GitHub is the platform where you host those repositories and collaborate with others. You can also host Git repositories on other platforms like GitLab and BitBucket, but GitHub is the most popular.

Installing Git (Windows, Linux, and macOS Users)

You can go ahead and download Git for your platform from (git-scm.com)

Using Git

You can use Git either through the command line (Terminal) or through a GUI. However, as a developer, it’s highly recommended to learn the terminal approach. Why? Because it’s more efficient, and understanding the commands will give you a better grasp of how Git works under the hood.

GitWorkflow

Git operates in several key areas:

Working directory (on your local machine)

Staging area (where changes are prepared to be committed)

Local repository (stored in the hidden .git directory in your project)

Remote repository (the version of the project stored on GitHub or other hosting platforms)

Let’s look at the basic commands that move code between these areas:

git init: Initializes a Git repository in your project directory, creating the .git folder.

git add: Adds your files to the staging area, where they’re prepared for committing.

git commit: Commits your staged files to your local repository.

git log: Shows the history of commits.

git push: Pushes your changes to the remote repository (like GitHub).

git pull: Pulls changes from the remote repository into your working directory.

git clone: Clones a remote repository to your local machine, maintaining the connection to the remote repo.

Branching and merging

When working in a team, it’s important to never mess up the main branch (often called master or main). This is the core of your project, and it's essential to keep it stable.

To do this, we branch out for new features or bug fixes. This way, you can make changes without affecting the main project until you’re ready to merge. Only merge your work back into the main branch once you're confident that it’s ready to go.

Getting Started: From Installation to Intermediate

Now, let’s go step-by-step through the process of using Git and GitHub from installation to pushing your first project.

Configuring Git

After installing Git, you’ll need to tell Git your name and email. This helps Git keep track of who made each change. To do this, run:

Master vs. Main Branch

By default, Git used to name the default branch master, but GitHub switched it to main for inclusivity reasons. To avoid confusion, check your default branch:

Pushing Changes to GitHub

Let’s go through an example of pushing your changes to GitHub.

First, initialize Git in your project directory:

Then to get the ‘untracked files’ , the files that we haven’t added yet to our staging area , we run the command

Now that you’ve guessed it we’re gonna run the git add command , you can add your files individually by running git add name or all at once like I did here

And finally it's time to commit our file to the local repository

Now, create a new repository on GitHub (it’s easy , just follow these instructions along with me)

Assuming you already created your github account you’ll go to this link and change username by your actual username : https://github.com/username?tab=repositories , then follow these instructions :

You can add a name and choose wether you repo can be public or private for now and forget about everything else for now.

Once your repository created on github , you’ll get this :

As you might’ve noticed, we’ve already run all these commands , all what’s left for us to do is to push our files from our local repository to our remote repository , so let’s go ahead and do that

And just like this we have successfully pushed our files to the remote repository

Here, you can see the default branch main, the total number of branches, your latest commit message along with how long ago it was made, and the number of commits you've made on that branch.

Now what is a Readme file ?

A README file is a markdown file where you can add any relevant information about your code or the specific functionality in a particular branch—since each branch can have its own README.

It also serves as a guide for anyone who clones your repository, showing them exactly how to use it.

You can add a README from this button:

Or, you can create it using a command and push it manually:

But for the sake of demonstrating how to pull content from a remote repository, we’re going with the first option:

Once that’s done, it gets added to the repository just like any other file—with a commit message and timestamp.

However, the README file isn’t on my local machine yet, so I’ll run the git pull command:

Now everything is up to date. And this is just the tiniest example of how you can pull content from your remote repository.

What is .gitignore file ?

Sometimes, you don’t want to push everything to GitHub—especially sensitive files like environment variables or API keys. These shouldn’t be shared publicly. In fact, GitHub might even send you a warning email if you do:

To avoid this, you should create a .gitignore file, like this:

Any file listed in .gitignore will not be pushed to GitHub. So you’re all set!

Cloning

When you want to copy a GitHub repository to your local machine (aka "clone" it), you have two main options:

Clone using HTTPS: This is the most straightforward method. You just copy the HTTPS link from GitHub and run:

It's simple, doesn’t require extra setup, and works well for most users. But each time you push or pull, GitHub may ask for your username and password (or personal access token if you've enabled 2FA).

But if you wanna clone using ssh , you’ll need to know a bit more about ssh keys , so let’s talk about that.

Clone using SSH (Secure Shell): This method uses SSH keys for authentication. Once set up, it’s more secure and doesn't prompt you for credentials every time. Here's how it works:

So what is an SSH key, actually?

Think of SSH keys as a digital handshake between your computer and GitHub.

Your computer generates a key pair:

A private key (stored safely on your machine)

A public key (shared with GitHub)

When you try to access GitHub via SSH, GitHub checks if the public key you've registered matches the private key on your machine.

If they match, you're in — no password prompts needed.

Steps to set up SSH with GitHub:

Generate your SSH key:

2. Start the SSH agent and add your key:

3. Copy your public key:

Then copy the output to your clipboard.

Add it to your GitHub account:

Go to GitHub → Settings → SSH and GPG keys

Click New SSH key

Paste your public key and save.

5. Now you'll be able to clone using SSH like this:

From now on, any interaction with GitHub over SSH will just work — no password typing, just smooth encrypted magic.

And there you have it ! Until next time — happy coding, and may your merges always be conflict-free! ✨👩‍💻👨‍💻

[gamebird]

The Murderbot Diaries Writing Micro-Fest

Two years ago we had All Systems Love, last year it was Heartificial Condition, and this year it is Rogue Emotions! What is it, you ask? It's an annual short-fic celebration of the idea of love in The Murderbot Diaries fandom. It covers fic or art, dedicated to some form of love, either for self, for humanity/all sentient life, one special someone, or several special someones! For all ship configurations, any TMBD characters or TMBD OCs, as long as love/devotion/importance is involved in some way. Does not have to be romantic or sexual, but also can be.

Drabbles, drabble series, or micro-fics encouraged! There is no word limit, but we're aiming at short and quick here, 100 to 5000 words. Collection open until end of February, 2025.

Anytime in February, you can post your short fic or art to the AO3 Collection RogueEmotions (https://archiveofourown.org/collections/RogueEmotions)

If you need inspiration, click on over to https://app.pipefy.com/organizations/300623467/interfaces/14d61385-a87b-4340-96cd-786ac73430eb/pages/46813c5b-583e-4000-bcd2-cb22300a7389 to find a list of prompts and tropes!

[timdrakequotes]

Metallo: What’s going ON here?

Robin: I’m going on here.

Metallo: Little brat!

Robin: I’ve got you by the configurations, Metallo.

[…]

Metallo: You little brat! What’ve ya done?!? I can’t morph! I got no control over anything!

Robin: That’s right, Metallo. See--a smart cyborg would’ve protected his interface a lot better. Now I’m in the driver’s seat! But don’t worry--our little ride will be over soon enough!

--Tim Drake with Metallo (WF3: World’s Finest Three - Superboy/Robin #2)

[mollysunder]

Shimmer & The Glorious Evolution: A Love Story

We can see how a specialized high quality strain of Rio's shimmer can alter the biology of living organisms to make users produce their own shimmer, as is the case with Jinx. So what will happen now that Rio's specialized shimmer has been exposed to an artificial life form, i.e. the hexcore?

What Has the Hexcore Done Without Shimmer?

Prior to the hexcore's exposure to shimmer infused blood we've only seen it capable of releasing short bursts of massive energy when Viktor experiments with it.

When exposed to human blood the hexcore reacted by "consuming" a drop of it. The blood effected the entire magical dimension the hexcore connects to by turning it to a shade of purple similar to the plants found in Singed's cave.

Later we see that this newly blood infused hexcore's magic turned purple and is able to not only react to organic matter such as plants, but stimulate their growth in turn (not for long of course). The affected plants also take on the purple tinge similar to the hexcore's magic.

What Have We Seen the Shimmered Hexcore Do So Far?

Once Viktor exposed the hexcore to his shimmer infused blood it was capable of producing a longer lasting stable state with its test subject twice. Initially, what exactly happened to Viktor's leg was up to interpretation, but later on animators in Bridging the Rift confirmed that Viktor's new leg and hand are made of metal.

This means that the hexcore took Viktor's flesh and shimmer infused blood (more than the first time) and exchanged it for an arcane/shimmer configured metalic replacement. His skin is gone and we're looking at what his muscle has been converted to.

The transmutation of Viktor's hand and leg into metal could have only been facilitated through the use of shimmer. It was likely the remaining shimmer in Viktor's system that prevented him from being absorbed into the hexcore. Without a sufficient amount of shimmer, a regular human hand does not equal a shimmerized arcane metalic hand. The flesh, bone, and blood of an entire adult woman and a pitance of shimmer is worth the hand it provides.

What Will Happen Next Season?

The further the hexcore directly interfaces with organic matter the more similar it becomes in appearance and ability to shimmer. Where it improves health and strength at increasing biological costs. Once Viktor realizes that he's missing the "Inspiration" rune, the rune matrix will finally be complete and reach a "stable" state.

A "stable" state could mean the hexcore could reliably interact with and alter organic matter like Rio's shimmer is capable of. Based on the notes Sky left behind, her research focused on plant biology. In theory, a "perfect" hexcore could not only stimulate plant life to grow impressively, they could be durable enough to survive in extreme environments like Zaun.

While there is evidence that shimmer and its byproducts can enhance plant growth, especially in Zaun, there is a catch. Any plant affected by a hexcore corrupted by Rio's specialized shimmer would be altered in a way that makes them capable of being producing shimmer independently.

Just from Viktor's experiment with a hexcore exposed to a single drop of blood, the plants began to glow purple like the plants Rio would eat and break down into shimmer. Except, like Jinx the hexcore would pass down its own strain to the plant subjects that's compatible with the hexcore's "exchange" requirements.

But why would Viktor want to create plants capable of producing MORE shimmer for Zaun. Simple! Without shimmer you can't get... The Glorious Evolution. It's already been mentioned that Viktor's limbs have become metal, and to make his transformation complete he'll need more shimmer. For others to become like him, he needs more shimmer.

but...

Who Would Be Willing to Follow the Herald's Path?

Shimmer addicts like Huck and those who live in the sump with dying flesh and residual concentrations of shimmer in their bodies could be "healed" from their state of deterioration through the hexcore.

In Bridging the Rift we actually saw an unfinished clip of Viktor reaching his metalic hand to reach out and grab the face of a shimmer addict. Upon further inspection of the unidentified character's scars, we can guess this is Huck.

There's also the underlying culture of flesh sacrifice in Zaun, which is actually in the same vein as the Church of the Gloriously Evolved. In League, specifically through Camille's lore, the Church of the Gloriously Evolved actually exists outside of and likely before the Machine Herald came to the scene. The Church's roots even stretch into both Zaun & Piltover.

They believe that you must sacrifice something close and dear (like diseased flesh) with the faith that something better will take its place. Splinters of this organization likely made Silco an object of worship admiring his power and assuming the shimmer he brought was the miracle they sacrificed so much for already. Without Silco and his shimmer, Viktor and his hexcore would become the Church's new object of adoration as they bring shimmer AND immediate transmutation.

Finally, there's Sevika. In the tarot seen, Sevika drew a winning hand with a pair of card, Death and The Magician, that resemble Jinx and Viktor respectively. The scene may foreshadow that Jinx and Viktor will be the trump cards to win her Zaun's independence. But How will that work with Viktor?

You could argue that Sevika could bring Viktor in to repair her arm, but there's an entire industry backed up by a chembaron, Smeech, to fulfill that need. Viktor's going to need to bring something new to the table to be brought into the fold, and that could be shimmer infused plants and the "healing" properties of the hexcore. And I'm sure Sevika's pragmatic enough to know that for Zaun to survive Piltover's retaliation she'll need to bolster her resources in manpower and shimmer... lots of it.

Whether Sevika will be able to handle the cult of personality around the Machine Herald, especially if Jinx ends up siding him is a whole other discussion.

[zeroseuniverse]

Wires Crossed

Word Count: 1.0K Summary: “So,” She said, pushing off the table, “what’s next? Do you let me help, or do I just stand here and look pretty?” Yeosang’s gaze lingered on her for a beat longer before he turned back to the display. “If you’re going to stay, make yourself useful. The disruptor isn’t finished, and I don’t have time for dead weight.” Pairing: Yeosang X Fem Reader

Disclaimer: Please be aware that this is apart of the from the ashes series. This series will have aspects of violence, weapons, angst, blood, injuries, killing, and will heavily focus on oppression and segregation of mutants, Look after your mental state if any of these make you uncomfortable please.

Series Masterlist

Navigation

The workshop was hidden deep within the ruins of an old industrial district, concealed by layers of security both physical and digital. She adjusted her headset, glancing at the directions on her tablet. Each step closer to her destination felt like walking into a legend. No one met Yeosang unless they had to, and even then, the encounters were rare and shrouded in secrecy.

A rusted door came into view, flanked by flickering motion sensors. She reached for the access card she’d been given, but before she could insert it, a mechanized voice crackled through a hidden speaker.

“Step back.” The voice was calm but unyielding, as if the speaker already doubted her competence.

She sighed, holding their hands up. “I’m here for the resistance. Mission code Theta-9. You can verify it.” A pause. Then the door creaked open just enough for her to slip inside.

 The workshop was a labyrinth of technology: glowing blueprints floated mid-air, devices hummed softly on cluttered tables, and wires coiled like metal vines. The air smelled of solder and ozone.

In the center of it all stood Yeosang.

He didn’t look up immediately, his attention fixed on a holographic display filled with scrolling data. His expression was serene, almost detached, as his fingers moved through the interface like a conductor commanding an orchestra.

“You’re late,” he finally said without turning around.

She raised an eyebrow, unimpressed by the lack of acknowledgment. “Or maybe you’re just early.” She let the door shut behind her, leaning casually against a table. “You’re Yeosang, I presume?”

The faintest twitch of a smirk appeared on his lips before he turned, his gaze sharp and assessing. “And you’re the operative who’s supposed to keep the resistance from falling apart in the field. Let’s hope you live up to the hype.”

“Bold words from someone hiding in a workshop,” She shot back, though there was no malice in her tone. Her eyes wandered to a nearby table where a small device emitted a soft glow. “Is that the drone disruptor?”

Yeosang stepped forward, blocking her view. “It’s a prototype. Not a toy. You don’t touch anything unless I say so.”

She crossed her arms, smirking. “Touchy. You know, I could help. Tech isn’t exactly foreign to me.”

Yeosang narrowed his eyes. “You think you can keep up with this?” He gestured to the sea of machines and data displays around them.

“Only one way to find out,” She replied, already reaching for a diagnostic tablet on the table.

For the first time, Yeosang hesitated. Instead of brushing her off, he tilted his head, watching as she deftly navigated the device’s interface. she made a quick adjustment to the output configuration and held it up for him to see.

“Looks like your disruptor’s feedback loop is unstable. I tightened the parameters. Should work better now,” she said casually.

Yeosang stared, the faintest trace of surprise flickering in his eyes. “Not bad,” he murmured. “But let’s see if you’re as useful under pressure.”

Yeosang didn’t waste time with further pleasantries—he turned back to the holographic display, his fingers moving with precision as new schematics unfolded in midair. She watched him work for a moment, her curiosity piqued despite herself.

“You know,”cshe said, breaking the silence, “for someone who supposedly doesn’t trust anyone, you’re taking a big risk letting me in here.”

Without looking up, Yeosang replied, “Trust has nothing to do with it. I needed someone who could make the delivery without breaking it. That doesn’t mean I trust you to do more than that.”

She bristled at the slight but hid it behind a smirk. “And yet, here I am, already fixing your prototype.”

Yeosang’s hands paused over the hologram, and he glanced at her, his expression unreadable. “It wasn’t a complete fix,” he said flatly. “But it was... sufficient.”

She snorted. “Wow. High praise.”

Yeosang ignored her sarcasm and returned to his work, but she wasn’t about to let him off the hook so easily. She stepped closer, scanning the holographic schematics. The disruptor device he’d built was leagues ahead of anything she’d seen before, its complexity matched only by its elegance.

“This is brilliant,” She admitted, genuine admiration creeping into her tone. “The way you’ve routed the power flow to minimize energy loss—most engineers wouldn’t even think of that.”

Yeosang’s head tilted slightly, as if intrigued by her observation, but he still didn’t respond.

“And these dampening fields,” She continued, gesturing to a section of the blueprint. “They’re calibrated to avoid detection while still neutralizing the drones. That’s... risky. But clever.”

This time, Yeosang turned to face her fully, his expression finally betraying a hint of interest. “You know what you’re looking at,” he said, more a statement than a question.

“Enough to appreciate good work when I see it,” she replied with a shrug. “Guess you’ll just have to decide if you’re impressed or annoyed by that.”

Yeosang studied them in silence for a moment, his gaze sharp and calculating. Then, to her surprise, the corner of his mouth lifted in the faintest trace of a smile.

“I’ll let you know,” he said, his tone lighter than before.

She chuckled, leaning against the table. “You know, for someone who doesn’t like people, you’re not as insufferable as I expected.”

“And for someone who barged into my workshop, you’re less incompetent than I expected,” Yeosang shot back, his voice dry but not unkind.

Their eyes met, and for a brief moment, the tension between them shifted, replaced by a mutual spark of respect.

“So,” She said, pushing off the table, “what’s next? Do you let me help, or do I just stand here and look pretty?”

Yeosang’s gaze lingered on her for a beat longer before he turned back to the display. “If you’re going to stay, make yourself useful. The disruptor isn’t finished, and I don’t have time for dead weight.”

“Careful,” She teased as she moved to the workbench. “Keep talking like that, and I might start thinking you enjoy my company.”

Yeosang didn’t respond, but the faint smirk tugging at his lips as he handed her a toolkit said enough.