Skip to content

Instantly share code, notes, and snippets.

@VINXIS
VINXIS / ffmpeg_updater.rs
Last active March 17, 2024 17:20
Automates updating ffmpeg
use std::error::Error;
use std::io::{copy, stdin, Read};
use std::path::{Path, PathBuf};
use std::fs::{create_dir, read_dir, remove_dir_all, remove_file, rename, File};
use std::process::Command;
const URL: &str = "https://www.gyan.dev/ffmpeg/builds/ffmpeg-git-full.7z";
const EXTRACTION_PATH: &str = "A:\\Programs\\ffmpeg";
// Improved error handling and path manipulation
[1:23 PM]Okoratu: also would u push terminal entrance
[1:23 PM]Okoratu: i have sotarks second cuz he owes me a m4m or something
[1:25 PM]VINXIS: Lol 01:01:570 - still threw me off
[1:25 PM]VINXIS: Yea sure tho
[1:26 PM]Okoratu: maybe i can introduce the idea before
[1:26 PM]Okoratu: if u have ideas im all ears cuz the entire thing is just whatever the fuck anyways
[1:26 PM]VINXIS: uhh thatll proly help
[1:26 PM]Okoratu: 00:32:020 - like i could do same rhythm here i think
[1:26 PM]VINXIS: Dunno the clashing of the 2 ideas of the epic jumpo for kicks and then that that takes over later for the most part conflicts a lot at that
[1:27 PM]VINXIS: tghat

https://osu.ppy.sh/beatmapsets/1346246/discussion/2787950/general its all an accident most proly since it is a collab and they were lowkey just doing their own shit probably but still very very good

00:06:229 - starts off with basic patterning choices but is very consistent at its implementation with consistency in when slider choices are made and the (very obvious) rhythmic contasts like 00:10:076 (4,1) - vs 00:16:229 (1,2) - for example

00:18:537 - first thing i noticed that was great when going thru this map was the evolution that occurs from the previous section in the choices made (some at least seemingly unintentional but may be intentional)

  • Previous had used the wave specifically only for emphasis on those 1/1 gaps but the subtle sv bumps are now also added (albeit could have been stronger than just a .1x raise honestly since the effect is almost barely felt rn)
  • Noticing 00:06:229 (1,1) - vs 00:18:537 (1,2) - where the stack usage that was established in places like 00:12:383 (3,1) - is now used

Really good read, I agree with almost everything being said here and the issues pointed out are to the point and exact, but I feel inclined that it is necessary to argue against the suggestions provided for splitting the BNG into 2 groups.


The suggestion provided to create a split between the BNG and the QAT for the reasons stated has already been done exactly the same way before and was considered a failed operation; around 2014-2015, BATs were enforced into a split into 2 groups that they could decide to join in: BAT and QAT. After decided, the BAT then became the BNG like current while the QAT became the QAT suggested in the document.

This operation was considered a failure. While this TO A DEGREE partly solved the issue with regards to having unrankables checked and "spread quality" TO A DEGREE was ensured, this did not exactly ensure the health of the system and of the beatmaps themselves

Many cases in this era showed the common event of QATs attempting to improve and discuss on a beatm

@VINXIS
VINXIS / shitbot.js
Created October 27, 2019 07:07
Actual Shit
const { exec } = require('child_process');
const http = require('http');
const https = require('https');
const fs = require('fs');
const axios = require('axios');
const stringTable = require('string-table')
const osuApiKey = 'APIKEY';
const pasteApiKey = 'APIKEY';
package main
import (
"encoding/json"
"fmt"
"io/ioutil"
"log"
"math"
"os"
"sort"