TypicalHog

joined 2 years ago
[–] TypicalHog@lemm.ee 0 points 1 year ago

Not as disgusting as this community tho, lol. Keep downvoting, yall know I'm spitting truth.

[–] TypicalHog@lemm.ee 1 points 1 year ago (3 children)

OMG yes. I wanna ban words like Trump, Elon, Musk, Nazi, Fascism, Fascist, Biggot etc.

[–] TypicalHog@lemm.ee -2 points 1 year ago (2 children)

Fair. You just don't like it huh? I actually hate the fact I can't add a custom thumbnail to my video without verifying my phone number first. Like wtf, man can't have more than 2 channels these days...

[–] TypicalHog@lemm.ee 1 points 1 year ago

I use VSCodium atm.

[–] TypicalHog@lemm.ee 16 points 1 year ago (1 children)

Lemmy is WAY more left-leaning and instance/community mods are often more trigger-happy when removing comments/banning people.

[–] TypicalHog@lemm.ee 7 points 1 year ago (4 children)

Love it or hate it - YouTube is still the largest and best video platform out there. It doesn't matter how "good" any other platforms are if they don't have the content and creators. I'm all for posting on other platforms in addition to YouTube, but you can't just ignore something like YT.

[–] TypicalHog@lemm.ee -1 points 1 year ago

How am I pathetic? And if I'm ignorant - ignore me back.

[–] TypicalHog@lemm.ee -1 points 1 year ago

If you think Trump/Elon/republicans will cause television to not function - you must be batshit psychotic. Also, who tf said I'm a fascist? You are assuming shit without substance. I dislike fascism very much. Also, I don't give a flying fuck about any instance that bans people for calling out people who litter r/pics with mostly political pics.

[–] TypicalHog@lemm.ee -1 points 1 year ago

To the 9 people who disliked my comment (and many more who will in the future) - just think about how fucking weird it is to not want to higher certain races in favor of other races just cause you want to create artificial equity. There are literally instances where white person who is more qualified for a position will get denied in favor of let's say black person who might be less qualified just because companies wanna fill some DEI quotas. That's super racist. Companies should hire he best candidates (be it black, asian, white or whatever) and not some (often) mediocre candidates just cause they a certain race.

DEI is RACIST!

 

What are some of your favorite YouTube video(s) that always pull you back?
Be it weeks, months, or years since you've last seen them, but you know you'll want to come back and watch them again.

I'm looking for specific videos you find great value in re-experiencing.

It absolutely doesn't matter what the video is, how many views it has, how long it is, or what it's topic and genre are - it just has to be something you'll always want to re-watch and experience from time to time.
It could be for nostalgia, sentimental value, memories, meaning, usefulness, something that cheers up when you're feeling down, something that inspires you, cracks you up, tickles your emotions, some vibe you really like, something immersive or anything meaningful enough that keeps you coming back.

My motivation behind this post is to potentially find some gems I still haven't discovered to add to my collection (and perhaps help others do the same).

EDIT:
I guess it would be fair I also share some of mine, both as examples and to share these finds with others who may also like them (some of my favorites, random order):
https://pastebin.com/iYu2SsXn (external link because it's a pretty big list)

Alternative description of what I'm looking for:
Which video(s) do you love so much (and keep watching repeatedly) that you would want them backed up and saved offline in a hypothetical scenario of a global permanent internet outage?

 

A while ago I've noticed Discord using 8-10% of my CPU every time I open Task Manager. This doesn't really sound weird... Until you realize this is when my Discord client is NOT running (AKA after I fully exit out of it so it's not even present in the tray area on the right side of the taskbar). From what I can tell, it's using about 400MB of memory, no disk or network and about 8% of CPU (I have 6 cores/12 threads and that 8-10% seems to be distributed among all of them). It's possible it uses disk and network in short bursts after a long period of inactivity, but I havent spotted it doing that so far). If I were to kill Discord.exe in the task manager - it would go away and not come back until I restarted my computer. At first, I didn't think much of it - I thought maybe it's doing some background update or something, but it is constant, it doesn't go away unless I kill it. When I run Discord - another Discord entry appears in the task manager - the suspicious one seems unaffected. Both entries take me to the same file when I click "Open file location". The file seems normal and signed by Discord. What is going on here? Do you guys also have this going on or is it just me? I'm getting some really sus vibes ngl. I suspect a discord bug/unoptimized code, 3rd party malware or Discord itself secretly doing some malicious thing.

UPDATE: Multiple clean reinstalls haven't helped.

 

I came up with an algorithm and implemented it in Rust.
I want to ensure the code is of sufficient quality before releasing it on Crates.io and GitHub. You can also find more info about the algorithm and its purpose there.

I'm eager to hear your feedback and thoughts and am open to ANY suggestions that may help me improve the code further.
The code should be performant, clean, easy to use, idiomatic, etc.
I'm also looking for potentially better names for certain variables and stuff.

Note that some things have changed a bit since the last release (for example - the hash calculation has been changed from blake3(blake3(OBJECT) || blake3(DATE)) to blake3::keyed_hash(DATE, OBJECT) to improve performance by eliminating 2 out of 3 hash calculations), but the README is still valid (and hopefully at least somewhat decent source of info about the algorithm - I did my best trying to explain stuff, but I'm still looking to improve it further in the future).

The functions can panic if they are given a date where the year is outside of the 0000 to 9999 range.
I'm not sure if I should make the function return the result/option instead of panicking since I'd like to avoid having to unwrap() the output and would prefer if the function returned just a simple u32/chrono::NaiveTime (but I'm open to changing my mind on this one).

I'm also curious if there is a cleaner way to create a key from a date. Previously, I've been using format("%Y-%m-%d") to convert it into a string slice and copy it into the key array, but I've found that approach to be very slow (over 50% of the CPU time was being spent just for that alone), so I opted out for an approach you can see below.

The newest function rdvt() is not yet documented anywhere, but I'll do my best to explain it here:   In addition to an object and a date (same as rdv()), it also takes a rank (which is a positive integer - u32).
The function calculates the keyed blake3 hash of an object, using the date and a rank as key, and uses the resulting (pseudorandom) bits to generate and return a random uniform time (chrono::NaiveTime) between 0h and 24h (down to nanosecond precision).
Time is calculated by taking the first bit of the hash and in case it's a binary one - 12h is added to the time, then we add 6h if the 2nd bit of the hash is a one, 3h for the 3rd bit, 1.5h for 4th and so on until the increment reaches the small enough value where it doesn't contribute anything to the time (when it becomes less than 1ns, essentially).   This means if all of the bits in the hash were zeros - time would be zero, and if they were all ones - time would be 23:59:59:999:999:999h (the very last and highest possible value). The code short-circuits and stops earlier than going through all 256 bits since we usually only need around 46 bits before the increment becomes smaller than 1ns (the code stops only in case the sum of tiny sub 1ns increments can't contribute enough to change the last digit in the total time (even if all of the rest of the bits in the hash were to be ones))):  

Feel free to ask ANY questions regarding the code, the algorithm, its function, use cases, or anything else you'd like explained or clarified.  

Here's the code (I haven't written any tests yet, so they are not included for review):  

//! The official Rust implementation of the [RANDEVU](https://github.com/TypicalHog/randevu) algorithm
//!
//! # Example
//! ```rust
//! use chrono::Utc;
//! use randevu::{rdv, rdvt};
//!
//! fn main() {
//!     let object = "THE_SIMPSONS";
//!     let date = Utc::now();
//!     let rdv = rdv(object, &date);
//!     let rdvt = rdvt(0, object, &date);
//!
//!     println!("Object {} has RDV{} today with RDVT0 at {:?}", object, rdv, rdvt);
//! }
//! ```

use blake3;
use chrono::{DateTime, Datelike, NaiveTime, TimeDelta, Utc};
use itoa;

/// Returns the 32-byte KEY `[u8; 32]` created from a given DATE `&DateTime<Utc>` and an optional RANK `Option<u32>`
fn create_key(date: &DateTime<Utc>, rank: Option<u32>) -> [u8; 32] {
    let mut key = [0u8; 32];

    let mut year = Datelike::year(date);
    let mut month = Datelike::month(date);
    let mut day = Datelike::day(date);

    let mut year_len = 4;
    let mut prefix_len = 0;

    // Add a prefix (-/+) if the year is not between 0 and 9999 (-YYYY-MM-DD / +YYYY-MM-DD)
    if year < 0 {
        key[0] = b'-';
        prefix_len = 1;

        year = year.abs(); // Make year positive
    } else if year > 9999 {
        key[0] = b'+';
        prefix_len = 1;
    }

    // Adjust year_len for very large years (both positive and negative)
    if year > 9999 {
        year_len += 1;
        if year > 99999 {
            year_len += 1;
        }
    }

    let full_year_len = prefix_len + year_len;

    // If a rank is provided, write it into the key after the date, separated by an '_'
    if rank != None {
        let mut buffer = itoa::Buffer::new();
        let rank_str = buffer.format(rank.unwrap());
        key[7 + full_year_len..7 + full_year_len + rank_str.len()]
            .copy_from_slice(&rank_str.as_bytes()[..rank_str.len()]);

        key[6 + full_year_len] = b'_';
    }

    // Write the day into the key
    key[5 + full_year_len] = b'0' + (day % 10) as u8;
    day /= 10;
    key[4 + full_year_len] = b'0' + day as u8;

    key[3 + full_year_len] = b'-';

    // Write the month into the key
    key[2 + full_year_len] = b'0' + (month % 10) as u8;
    month /= 10;
    key[1 + full_year_len] = b'0' + month as u8;

    key[full_year_len] = b'-';

    // Write the year into the key
    for i in (prefix_len..full_year_len).rev() {
        key[i] = b'0' + (year % 10) as u8;
        year /= 10;
    }

    key
}

/// Returns the RDV value `u32` for an OBJECT `&str` on a specific DATE `&DateTime<Utc>`
///
/// **RDV = number of leading zero bits in blake3::keyed_hash(key: DATE, data: OBJECT)**
pub fn rdv(object: &str, date: &DateTime<Utc>) -> u32 {
    let hash = blake3::keyed_hash(&create_key(date, None), object.as_bytes());

    // Count the number of leading zero bits in the hash
    let mut rdv = 0;
    for &byte in hash.as_bytes() {
        rdv += byte.leading_zeros();

        if byte != 0 {
            break;
        }
    }

    rdv
}

/// Returns the RDVT time `DateTime<Utc>` of a given RANK `u32` for an OBJECT `&str` on a specific DATE `&DateTime<Utc>`
pub fn rdvt(rank: u32, object: &str, date: &DateTime<Utc>) -> DateTime<Utc> {
    let hash = blake3::keyed_hash(&create_key(date, Some(rank)), object.as_bytes());

    // Calculate the time using bits from the hash
    let mut total: f64 = 0.0;
    let mut increment = 12.0 * 60.0 * 60.0 * 1_000_000_000.0; // 12h in nanoseconds
    for (i, byte) in hash.as_bytes().iter().enumerate() {
        for j in (0..8).rev() {
            let bit = (byte >> j) & 1;
            if bit == 1 {
                total += increment;
            }
            increment /= 2.0;
        }
        // Stop once increments become too small to affect the total
        if i > 4 && (2.0 * increment) < (1.0 - total.fract()) {
            break;
        }
    }

    // Construct the RDVT time from total
    let rdvt = date.with_time(NaiveTime::MIN).unwrap() + TimeDelta::nanoseconds(total as i64);

    rdvt
}

view more: ‹ prev next ›