ChristleVania

お呼びでない？こりゃまた失礼しました！

Algunos soundtracks que llegaron esta semana… #streetfighter #capcom #magicaldrop

Just spent an entire day wading through Newlib, GCC, and libstdc++ code, trying to patch our GCC15/16 SH toolchains for KallistiOS in an attempt fix a long-standing issue with using a modern C++ API on the Sega Dreamcast. We support every freaking common time API under the sun with KallistiOS: 1) Direct kernel timer routines. 2) C89's time() and clock(). 3) C11's timespec_get() with C23 extensions. 4) POSIX's gettimeofday() and clock_gettime(). 5) C++11's std::chrono. 6) SDL1/2/3 timer APIs. Every one of these routines reports the highest resolution ticks supported by their respective APIs... up to 80ns increments, which is the finest granularity the SH4's TMU peripheral can even tick at... Every API that is... EXCEPT FOR C++'s GODDAMN STD::CHRONO. For quite awhile now, EVERY clock source queried with std::chrono returns a maximum resolution of... A WHOLE FREAKING SECOND??? WTF? As it turns out, deep within GCC's libstdc++ configuration scripts, std::chrono attempts to detect the presence of certain low-level timing APIs to call into for the implementation of its clock sources... The problem? It looks for the presence of _POSIX_TIMERS, which is an entire asynchronous timing API which we hadn't implemented within KOS yet, just to determine that it should back std::chrono with POSIX's clock_gettime()--which we do support! So without _POSIX_TIMERS defined in KOS, what does GCC back std::chrono's clocks with? Freaking C89's time() function--returning a unix timestamp with a whopping 1 second resolution!!!! So basically I had to go patch Newlib to define _POSIX_TIMERS for GCC when targeting SH, then I had to go stub out all of the other POSIX asynchronous timer routines that we have yet to fully implement within KOS, and finally, I had to go patch libstdc++'s configuration scripts to try to use clock_gettime() for our GCC target tuple... Was a long, hard road through hell and back, but... C++ users rejoice, as you're no longer cucked out of high-resolution timing with std::chrono! PR incoming!

4-1) Fuck it! Decidí que sí quería terminarlo jaja

4) Antoino Aguilar 1+2 Terminé completo el 1 y solo la mitad del 2, porque si bien el update gráfico se aprecia, lo único refrescante para mi fue tener mecánicas de Vert y Manuals del 2 integradas al 1. Jugar el 2 es lo mismo que jugar la versión de PS1 con gráficos modernos.

Este año empezamos tarde, pero aquí va la lista de juego que voy terminando en 2026. ->

6) Balatro ¿A qué hora dieron las 3AM?

5) O2JAM: The Beginning La más reciente encarnación de O2JAM por fin en manos más copetentes. Recientemente agregaron un modo 2D y 7-key para tratar de emular el estilo original. Tiene sus detalles, pero esto y el collab con EZ2ON es lo más cercano que tenemos al O2JAM original.

Amo a Prince pero Snoop tiene razón.

Bloomberg: Bungie planning significant layoffs following end of Destiny 2 development. Destiny 3 is not in active production. Bungie staff are pitching and prototyping new projects, including in the Destiny franchise, but none have been greenlit bloomberg.com/news/articles/…

@Xocoroll Me da miedo jajaja

@ChristleVania De un vicio solo se sale con otro: baja el demo de Gambonanza

He vuelto a caer en el vicio

@ChicleroGamer Los hunters son mi coco.

@ChristleVania Si jajajaja lo tenía medido, aunque en alguna que otra ocasión me madreaban y me frustraba demasiado jajaja fuera de esos enemigos es muy viable hasta para alguien sin manos como yo xd

Resident Evil 1 Remakes cuando me aferre a hacerle speedrun xD podía acabarlo unas 3-4 veces por día

Habrá que regresar a Destiny una vez más

@ChicleroGamer Son zurdos. Corre hacia su brazo derecho ;)

@ChristleVania Nah, ese es sencillo excepto por los crimson...

@ChicleroGamer Simon, pero me sigue impresionando

@ChristleVania Creo que ya te había contado esa anécdota jajaja intenté hacerle speedrun en ps3 muchísimas veces, hasta me sabía las rutas óptimas de memoria

요번에 숏컷/리믹스/풀송 전용 타이틀 작업 및 @Siesphere 님 와 함께 구 BGA 하나 복원했습니다. 피닉스2도 잘 부탁드립니다.

Acabo de subir un nuevo short de Resident Evil a mi tikis tokis vt.tiktok.com/ZSxABNVpm #REBHFun #RE30th #REvilaton

el crédito real es de Johan Renck, el director del clip (Chernobyl). los movimientos que inspiraron a Masahiro Ito para las enfermeras son de danza butoh, y los hacen bailarines suecos de ascendencia asiática. Madonna básicamente alquiló el set No nos flipemos.

Get ready to drive into uncharted territory unbound by time 🛞 ⏳ Paradox Pokémon make their entrance as Ancient and Future Pokémon and Trainer cards debut in the newest #ParadoxDrive expansion!

🇲🇽 A threat actor is advertising a massive alleged Mexican identity verification dataset containing more than 800,000 files, including government ID documents, selfies, bank statements, and payroll-related records. According to the underground listing, the dataset allegedly contains: • Front and back images of Mexican INE identity cards • Selfie/KYC verification images • Bank statement PDFs • Payroll documentation • More than 120 GB of total data The post claims the archive includes: • ~293,000 ID front images • ~261,000 ID back images • ~182,000 selfie verification images • ~67,000 bank statement PDFs • ~14,000 payroll-related files If authentic, this would represent one of the more dangerous categories of data exposure because it combines: • Government-issued identity documents • Facial verification/selfie images • Financial documentation • Employment/payroll information This combination creates what threat actors consider a “full-spectrum identity package,” which can significantly increase the success rate of: • Identity theft • Synthetic identity fraud • Loan fraud • Account takeover • SIM swapping • Crypto exchange verification abuse • KYC bypass attempts • Financial impersonation operations Selfie images paired with government IDs are particularly valuable in underground ecosystems because many modern financial institutions and fintech platforms rely on: • Facial verification • Liveness checks • Remote onboarding • Digital KYC workflows Compromise of these datasets can potentially enable attackers to: • Reconstruct digital identities • Defeat weak verification workflows • Conduct highly targeted social engineering • Open fraudulent financial accounts • Circumvent onboarding controls in poorly secured platforms The inclusion of bank statements and payroll documents also introduces additional risks: • Income verification abuse • Tax fraud • Employer impersonation • Financial profiling • Credit application fraud This type of dataset is often associated with: • Fintech platforms • Loan providers • KYC vendors • Identity verification providers • Banking onboarding systems • Document processing services One important trend visible across underground forums is the rising market demand for: • “Verified identities” • Full KYC packages • Selfie-ID combinations • Financial verification documents Unlike basic credential leaks, these datasets are far more difficult for victims to remediate because: • Faces cannot be changed • Government IDs have long validity periods • Historical financial documents remain useful • Identity attributes persist for years Organizations handling identity verification workflows should prioritize: • Secure storage segregation for KYC assets • Encryption of document repositories • Strict retention policies • Watermarking and access auditing • Monitoring for bulk exports • Third-party vendor risk assessments • Zero-trust access controls around onboarding systems At this stage, the claims remain publicly unverified. However, if confirmed, the exposure of combined identity documents, facial verification images, and banking records would represent a severe privacy and financial fraud risk affecting hundreds of thousands of individuals. 🇲🇽 #DDW #Intelligence #CyberSecurity #DarkWeb #DataBreach #IdentityTheft #Fraud #KYC #Fintech #Privacy #ThreatIntelligence

🇲🇽Hace 3 meses Bloomberg publicó una nota sobre un hackeo a diferentes instituciones del Gobierno de México, en esa nota mencionaban el robo de 195 milliones de registros al @SATMX. Tuve acceso al reporte técnico y el hackeo es más aún mayor. Este podría ser el ataque más grande que ha sufrido el gobierno de México, ¿Por qué? Por que no solo los ataques no solo se miden en la cantidad de información robada, sino también en la cantidad de instituciones y activos vulnerados. Algo similar a lo que le pasó al Gob. De Costa Rica, en el que vulneraron diferentes instituciones en 1 solo ataque por un grupo de ransomware.