TwilightKiddy

Install Gentoo.

So, you are telling me I'm free to try and then just return to where I was if something goes wrong?

RWBY is the name of the show. Though, it's not an anime in the strict sense of the word, was made by RoosterTeeth and almost completely CGI, as far as I'm aware.

It's a decent show, mostly because they used their CGI stuff to incorporate pretty choreography into battles and their sound design is cool, but with RoosterTeeth now practically dead, I doubt we'll ever get to see the end of it, sadly.

Wouldn't say I use it often, but this thing resolves a domain name to an IP address:

function resolve() {
  case $1 in
    -4)
      getent ahostsv4 $2 | grep STREAM | head -n 1 | cut -d ' ' -f 1
      ;;
    -6)
      getent ahostsv6 $2 | grep STREAM | head -n 1 | cut -d ' ' -f 1
      ;;
    -p)
      getent hosts $2 | head -n 1 | cut -d ' ' -f 1
      ;;
    *)
      getent ahosts $1 | grep STREAM | cut -d ' ' -f 1 | sort -u      
      ;;
  esac
}

All my aliases are just default arguments for programs or shorthands for my other scripts, most of which are specific for my setup.

This is a very good argument for ffmpeg and ffprobe, by the way:

alias ffmpeg="ffmpeg -hide_banner"
alias ffprobe="ffprobe -hide_banner"

BitTorrent breaks your data in blocks, each block is hashed, their sizes are known. Assuming you got your .torrent file from a legitimate source, it's practically impossible to receive something else, as long as your client does all the checks properly.

In theory, it is possible to write malware that will collide hashes with some other content, but considering you are restricted to the size of the actual content, it's extremely unlikely that out of all the millions of .torrents we created so far we can find even one for which it is possible.

And even if you win this absolutely bizzare lottery, you'll be competing with legitimate peers for serving the blocks. If at least one block that you care about is not served by you, the recepient will just get corrupted content that won't be dangerous in any way. In other words, you need to have so much bandwidth, that you serve everything before anyone else can serve even one significant block. At which point you will probably have to spend a lot more money on that than you'll ever get from whatever malware you are trying to serve.

.for_each(|((_, _, t), (_, _, b))| { ... }

This is actually fairly similar to what C# has.

This is a closure syntax:

| arguments | { calls }

In C#, the closest is lambda expressions, declared like this:

( arguments ) => { calls }

Parentheses are tuple deconstructors. In C# you have exactly the same thing. Imagine you have a method that returns a two element tuple. If you do this:

var (one, two) = MethodThatReturnsATuple();

You'll get your tuple broken down automatically and variables one and two declared for you.

First of all, I'm using .zip() to pair the rows of the picture by two, that returns a tuple, so, I have to deconstruct that. That's what the outer parentheses are for. The pixel enumeration stuff I'm using returns a tuple (u32, u32, &Rgba<u8>) first two values are x and y of the pixel, the third one is a reference to a structure with color data. I deconstruct those and just discard the position of the pixel, you do that with an underscore, same as C#.

I'm not that far into learning myself, but I'm not a textbook learner at all. Poking around opensource projects and wrestling with the compiler proved to educate me a lot more.

As an extra optimization, if top and bottom colors of a pixel match, you can just output space and only set background color. Implemented correctly, this can save a lot of memory. Didn't want to make the code more complex in fear of people being scared of running it.

I gladly present you this jank.

You might need these to compile:

cargo add image
cargo add clap --features derive

And the jank itself:

use std::path::PathBuf;

use clap::Parser;
use image::{ imageops::{self, FilterType}, ImageReader };

#[derive(Parser)]
struct Cli {
    path: PathBuf,
    #[arg(short = 'H', long, default_value_t = 30)]
    height: u32,
    #[arg(short, long, default_value_t = 0.4)]
    ratio: f32,
    #[arg(short, long, default_value_t, value_enum)]
    filter: Filter,
}

#[derive(clap::ValueEnum, Clone, Default)]
enum Filter {
    Nearest,
    Triangle,
    Gaussian,
    CatmullRom,
    #[default]
    Lanczos3,
}

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let args = Cli::parse();
    let filter = match args.filter {
        Filter::Nearest    => { FilterType::Nearest },
        Filter::Triangle   => { FilterType::Triangle },
        Filter::CatmullRom => { FilterType::CatmullRom },
        Filter::Gaussian   => { FilterType::Gaussian },
        Filter::Lanczos3   => { FilterType::Lanczos3 },
    };
    let img = ImageReader::open(args.path)?.decode()?;
    let original_ratio = img.width() as f32 / img.height() as f32;
    let width = ( args.height as f32 / args.ratio ) * original_ratio;
    let out = imageops::resize(&img, width as u32, args.height * 2, filter);
    let mut iter = out.enumerate_rows();
    while let Some((_, top)) = iter.next() {
        let (_, bottom) = iter.next().unwrap();
        top.zip(bottom)
            .for_each(|((_, _, t), (_, _, b))| {
                print!("\x1B[38;2;{};{};{};48;2;{};{};{}m\u{2584}", b[0], b[1], b[2], t[0], t[1], t[2])
            });
        println!("\x1B[0m");
    }
    Ok(())
}

I use Gentoo. I install systemd willingly. We are not the same.

Assuming you made a bit of a typo with your regexp, any of these should work as you want:

grep -oE '/dev/loop[0-9]+'
awk 'match($0, /\/dev\/loop[0-9]+/) { print substr($0, RSTART, RLENGTH) }'
sed -r 's%.*(/dev/loop[0-9]+).*%\1%'

AWK one is a bit cursed as you can see. Such ways of manipulating text is not exactly it's strong suite.

How did we arrive at networking? I feel like we are on two completely different pages.

I was talking about your regular end user machines, what we usually call "desktop computers". They are connected to the internet, but I don't have any way to remotely login into those. And I have a single person per computer. There is no need to disable root passwords on these, seeing that Larry executed a command as root won't provide any insight, I know that Larry is the only person who uses the machine. And it can complicate things in a sense that if Larry fatfingers his password three times and gets locked out, I'll have to get into his filesystem somehow and remove tallies manually instead of just logging in as root and doing faillock --reset.

So, we are clearly talking about different environments here. Of course I would not have a password for root in an enterprize setting where you have a lot of different people managing one machine. But for your regular desktop computer with one user, it just complicates things needlessly without providing any benefits.