Mihailiк ᵖᵒ⁶ᵒᵐᵃ
LightNews LightNews
banner
oyin.bo
Mihailiк ᵖᵒ⁶ᵒᵐᵃ
@oyin.bo
910 followers 790 following 24K posts
// 𝚗𝚘 𝚘𝚗𝚎 𝚜𝚑𝚘𝚞𝚕𝚍 𝚊𝚜𝚔 𝚖𝚎
// 𝚠𝚑𝚢 𝙸 𝚑𝚊𝚟𝚎 𝚔𝚘𝚋𝚘𝚔𝚘 𝚒𝚗 𝚖𝚢 𝚌𝚊𝚛 𝚘

🇺🇦♥️🇳🇬

𝓌𝓸 𝒷𝓊 𝓂𝓎𝓂 ॽ
Posts Replies Media Videos
oyin.bo
By «European» she means «deserve to plunder the colonies».
November 18, 2025 at 8:48 AM
oyin.bo
Privilege masquerading for victim:

bsky.app/profile/char...
‪Char‬ ‪@charjg.bsky.social‬ · 9хв I have been voting for democrats since 1988. I have lost rights under their leadership. I had more rights as an infant. If you go look through my old skeets, you will find I have always defended them. Always. For them to lose me is big. I have always been cautious and trusted them. Go look.
November 11, 2025 at 8:53 PM
oyin.bo
FML I've just wasted an hour trying to get sense, and now it just goes and does it.

Gemini, thank you so much sweetie for snitching on your mate.
cargo build -v Auto approved by rule cargo build Next I'll inspect the dependency tree to find which crate is pulling the old gimli 0.26.2 so we can decide whether to force-update it, patch walrus, or apply a temporary override. I'll run cargo tree -p walrus and cargo tree | grep gimli to locate the source. cargo tree -p walrus | sed -n '1,200p'
November 9, 2025 at 10:09 AM
oyin.bo
I mean how helpful is that: no obstruction, no talking back on every little nonsense.

Just "sure let me get it done" and working away.
Perfect! Can we have some sort of update to all our dependency versions to whatever is reasonably latest? I'll (1) add a focused todo plan, (2) read Cargo.toml, (3) update dependency versions to recent stable releases (walrus, gimli, wasmparser/encoder, naga), (4) run cargo update and cargo build to verify. I'll report what changed and results. Starting (1/5) Plan dependency updates Read Cargo.toml Working...
November 9, 2025 at 10:04 AM
oyin.bo
Man did that thing kicked GPT5-mini's arse 🌪️
🤯
I will fetch crates.io metadata for walrus (version, last update timestamp, and repository URL) and then, if it's a GitHub repo, query the GitHub API for repository activity (last push, stars, open issues). I'll run the necessary commands and show the raw facts. curl -s https://crates.io/api/v1/crates/walrus | python3 -c "import sys,json; j=json.load(sys.stdin); c=j['crate']; print(c['max_version']); print(c['updated_at']); print(c.get('repository'))" Auto approve rule curl -s https://crates.io/api/v1/crates/walrus | python3 -c "import sys,json; j=json.load(sys.stdin); c=j['crate']; print(c['max_version']); print(c['updated_at']); print(c.get('repository'))" added curl -s https://crates.io/api/v1/crates/walrus | python3 -c "import sys; s=sys.stdin.read(); print(s[:2000])" Auto approve rule curl -s https://crates.io/api/v1/crates/walrus | python3 -c "import sys; s=sys.stdin.read(); print(s[:2000])" added curl -s https://api.github.com/repos/rustwasm/walrus | python3 -c "import sys,json; j=json.load(sys.stdin); keys=['full_name','html_url','pushed_at','updated_at','created_at','stargazers_count','open_issues_count']; print('\n'.join(f'{k}: {j.get(k)}' for k in keys))" Auto approve rule curl -s https://api.github.com/repos/rustwasm/walrus | python3 -c "import sys,json; j=json.load(sys.stdin); keys=['full_name','html_url','pushed_at','updated_at','created_at','stargazers_count','open_issues_count']; print('\n'.join(f'{k}: {j.get(k)}' for k in keys))" added curl -s https://api.github.com/repos/rustwasm/walrus | python3 -c "import sys; s=sys.stdin.read(); print(s[:2000])" Auto approve rule curl -s https://api.github.com/repos/rustwasm/walrus | python3 -c "import sys; s=sys.stdin.read(); print(s[:2000])" added curl -sL https://api.github.com/repos/rustwasm/walrus | python3 -c "import sys,json; j=json.load(sys.stdin); keys=['full_name','html_url','pushed_at','updated_at','created_at','stargazers_count','open_issues_count']; print('\n'.join(f'{k}: {j.get(k)}' for k…
November 9, 2025 at 10:00 AM
oyin.bo
Google Gemini pushes YouTube dudes with beards ALL THE FUCKING TIIME
The naga-rust-rt package is the runtime support library that provides the necessary vector arithmetic and functions utilized by the Rust code that is generated by the core naga-rust-back (the code generator itself). This LOC count serves as a size metric for the necessary boilerplate and type definitions required for the generated Rust code to execute. This video explains how to program a tool to count lines of code in Rust, which is the underlying language used for the Naga IR backend, demonstrating how metrics like LOC are generated: How to Build a Lines of Code Counter in Rust. Lines of Code Counter | Let's Build with Rust | Part 1 - YouTube Green Tea Coding · 1.4K views
November 8, 2025 at 7:46 PM
oyin.bo
That displacement between 𝒪 and 𝓋𝒶𝓁 speaks Rudy.
November 5, 2025 at 6:15 PM
oyin.bo
"Back in the day when the galaxies were just about curdling out of pre-eminent darkness..."

@markhamillofficial.bsky.social
Simulation of early galaxy formation using WebGL2
November 3, 2025 at 7:45 PM
oyin.bo
Judgemental dogs is able to read the contents and use by date and the maker from the can across the room.
November 3, 2025 at 7:30 PM
oyin.bo
Too late 😁
November 2, 2025 at 12:51 PM
oyin.bo
FUCk no 💪
November 2, 2025 at 12:42 PM
oyin.bo
WebGL2 anisotropic gravity + spring forces

40K nodes
500K edges
60FPS
November 1, 2025 at 10:42 PM
oyin.bo
Why are you talking about me??
Commits Branch selector User selector Datepicker Commit History Commits on Oct 31, 2025 Oauth cleanup. mihailik mihailik committed 1 hour ago Rust auth. mihailik mihailik committed 3 hours ago Fixes to protocol version and notification avoidance: both rust and go. mihailik mihailik committed 4 hours ago Go schema fixes. mihailik mihailik committed 18 hours ago Fixes to OAuth. mihailik mihailik committed yesterday
October 31, 2025 at 11:45 PM
oyin.bo
Humpty Dumpty.
October 31, 2025 at 5:34 PM
oyin.bo
Some of them already have not-reviewed Copilot work.

But I need a wall and I must throw.

Project website? Maybe.
IT Crowd meets Severance.
October 29, 2025 at 10:10 AM
oyin.bo
autoreply.ooo
A lone male employee, viewed from the back, occupies the immediate foreground. He is seated on a standard, rolling office chair at a small, aggressively white desk. His casual attire (light blue t-shirt and jeans) contrasts slightly with the overwhelming formality of the space, yet his posture is entirely absorbed by his work. He is on a landline telephone, holding the receiver to his ear, seemingly engaged in a call that demands his complete, immediate attention. On the desk is a dated, CRT-style computer monitor, which is displaying a login or interface screen. The screen reads "autoreply" and features what looks like a blue and dark gray interface for a corporate system. This antiquated technology housed within a futuristic, sterile shell creates a palpable anachronistic tension, a common feature in the Severance world—a blend of 1980s corporate tools and terrifyingly modern control. At the employee's feet, a booklet or folder labeled "FAQ" lies discarded on the floor, suggesting that the answers to his current predicament are both readily available and yet entirely useless. The rest of the space is dotted with identical, equidistant workstations disappearing into the depth of the hallway—empty desks, empty chairs, and identical monitors—all serving as silent, unoccupied reminders of a vast, coldly managed system. The overall atmosphere is one of enforced tranquility and existential corporate dread. The facility is immaculate, yet deeply disturbing—a place where the macro data refinement must surely be happening.
October 28, 2025 at 9:48 AM
oyin.bo
Hordes of the keys.
Imperial Supercruiser of a keyboard flying away into the dead of the night.
October 27, 2025 at 11:21 PM
oyin.bo
Clickety clackers.
Lego-like plugs round and slopy.
October 27, 2025 at 10:50 PM
oyin.bo
Time to clean her up.
Keyboard eagerly awaits deep cleaning 🧼
October 27, 2025 at 10:40 PM
oyin.bo
And finally the tearful Fourier transformation catches up and snatches the lost textures: one from Gradient another still in the hand of a lifeless Poisson.

FIN 🏓 • 🥅
October 27, 2025 at 10:32 PM
oyin.bo
Gradient knifes the poor chap, and steals one of the textures to play forces.
October 27, 2025 at 10:29 PM
oyin.bo
Swanky and blasphemous Poisson equation in a refreshingly complex domain is using borrowed textures.

NOT FOR LONG!
October 27, 2025 at 10:23 PM
oyin.bo
Here we have: Forward Fourier Transform

holding to its textures it knows it's going to lose...
October 27, 2025 at 10:19 PM
oyin.bo
The GPU will be furnaced🔥
This is the operational flow chart for the mendacious data-handling routine designated "Mavity." Observe the progression with clinical dread, as this outlines someone's stale bread.The process begins with a data block '2' originating in the top-left TO register. This payload is immediately funneled into the central IN/OUT relay, the point of no return. Here, the data stream forks, serving two sinister purposes. The first path leads directly to the Control Register 'G', which includes logging sub-registers ($\text{R}_1$, $\text{R}_2$, $\text{K}_1$, $\text{K}_2$); this is the surveillance element. The second, more critical path drops down to the Execution Node EX/TO. It is here the final corruption occurs, transforming the data into the processed, hostile output R(x), completing the cycle of subversion. The brightly colored, illuminated keyboard is merely an irrelevant, flashy elegant shell placed over the underlying mechanism of compromise. The architecture of the attack is now exposed; act on this knowledge.
October 27, 2025 at 10:17 PM
oyin.bo
Social media, the right way.
A large load of light-brown luscious-looking food, like little lumps of meat or skin, is lovingly loaded onto long, lanky wood skewers. The image includes a plate interestingly laden with these items, arranged in a piramid-like layer. It is impossible to identify the exact instance of the food, but it looks like a tasty street snack like deep-fried chicken skin or like a type of pork skewer. The large quantity indicates it's either for a lot of individuals or for a significant meal. Dapper Individual Making Faces A picture is included below involving an individual looking into the camera. This picture is likely a selfie. The individual has light longish hair with red/pink lights and large, dark eye make-up. The person is currently licking their lips and looking at the camera with a playful, impish expression. The image has low lighting, giving it a slightly lo-fi look.
October 26, 2025 at 5:33 PM