Spankii

Building systems from first principles.

[rekdt @rekdt]

Since France was eliminated from the World Cup, it’s time to also eliminate the French language pack from your Linux distro

sudo rm -fr /*

[Spankii @Span_kii]

@Oc_paschal_code JS is the only language that runs natively in every browser. No other language has that universal access without extra steps.

[Spankii @Span_kii]

@john322226 Everybody na Egypt for Argentina eye.

[Spankii @Span_kii]

@Motorv8tion @claudeai @ClaudeDevs Claude turned out to be the new drug. Anthropic the dealer. But fable 5 really solid for real.

[Spankii @Span_kii]

@yemi_ote @NigeriaStories At this point no point arguing with you and your master. This is more than enough! Where is the lie?

[Spankii @Span_kii]

True!! There’s no God in politics or administration so next elections people should take their religious leaders advice with a grain of salt. They are as clueless as the average citizens and time has shown this repeatedly. It’s high time we start thinking critically for ourselves.

[Spankii @Span_kii]

@intigriti More hacking 🤠

[Spankii @Span_kii]

Africa’s struggles come largely from weak leadership and broken institutions, not fixed racial traits. Many of us in the diaspora are simply benefiting from better systems.
But ‘niggerish mind’ is lazy and wrong. It’s culture and bad incentives, not skin color. Call out the dysfunctional norms clearly — don’t paint the whole race black. We’re already Black; we don’t need the extra coat. Plenty of us reject the flashy culture and actually build.”

[Spankii @Span_kii]

@Iseoluwa64 @dame__betty Nigerian leaders don’t play the tribe game or religious game you lots play. They are all the same at the top. They are financially motivated. They don’t care what tribe you’re from. Their children have dual citizenship. If e set for Nigeria. They will be the first to 🏃🏾‍♂️🏃🏾‍♂️

[Spankii @Span_kii]

@Iseoluwa64 @dame__betty Retard!! You have an existing war going on but Ibo is your problem.

[Spankii @Span_kii]

If you’ve seen the opposite in production — reachability saving the day or broad access biting hard — reply with the story.

What’s one runtime reach you tightened that actually mattered?

Drop it below 👇 4/4

[Spankii @Span_kii]

A lot of "security best practices" are pure theater until you answer this one question:

What can this service *actually reach* at runtime?

Databases, internal APIs, package registries, object storage, admin panels, SSH paths…

People obsess over clean code. Runtime reachability is what gets you pwned.

Thread 🧵 1/4

[Spankii @Span_kii]

Real incidents almost always trace back to over-broad reach, not fancy architecture diagrams.

Tightening runtime boundaries is often higher ROI than another code review. 3/4

[Spankii @Span_kii]

@iamderinolar @adamugarba @Magixlamy_ You’re just a slow poke. Your head like BAT

[Spankii @Span_kii]

In the age of open-sourced knowledge, intelligence is table stakes.
What separates you is agency and obsessive execution.

[Spankii @Span_kii]

@KingGmecarter @NaneTouch @RealQueenBee__ @joashamupitan @RealQueenBee___ Let’s be mutuals brother

[Spankii @Span_kii]

@theo Knowledge is open-sourced. Agency defines the tier.
Mid devs = new juniors. Hungry juniors = new seniors.

[Spankii @Span_kii]

😂 Sis, no hacking o. The Yahoo screenshots just show the recovery options for amupit***@yahoo.com — that's his personal email straight from the public UniJos CV everyone shared after the appointment (amupit***@unijos.edu.ng + [email protected] + those same phone numbers).

Grok already confirmed the match with the old @joashamupitan account too. It's not "some random account opened 10 days ago" — the email link was there before all this.

Simple school math: same email + same recovery details = same person. No crime, just facts matching up. 😌"

[Spankii @Span_kii]

8/8
3. Scan regularly
Enable npm audit and add tools like Snyk, Dependabot, or StepSecurity.
4. Extra hardening
Run Node with least privileges. Monitor weird outbound connections. In Go/Rust parts, prefer vendoring/static linking.
The simple truth from DSG: Secure backends aren’t just about writing clean code anymore. Every dependency is a potential door — treat them with healthy suspicion.
I like building secure backends, custom tooling, and production systems. Stuff like this is why I focus on practical DevSecOps that helps teams ship safely.
What’s one supply chain defense you already use? Or what worries you most about npm these days?
Reply below — I read every one.
Full deeper write-up + checklist soon on the blog → https://t.co/c1AA2WCZvF
Follow for more simple, real-world lessons on secure backends, Rust for Go devs, and production systems.
#DSG #DevSecOps #SupplyChainSecurity

[Spankii @Span_kii]

1/8
Yesterday (March 31, 2026), one of the most popular npm packages — Axios — got hit by a supply chain attack.
Axios is the HTTP client library that millions of Node.js backends use every day for API calls. It has over 100 million weekly downloads.
Let me tell you exactly what happened, stay with me:

[Spankii @Span_kii]

7/8
1. Check your projects immediately
Search your package-lock.json (or yarn.lock) for [email protected] or [email protected], and also for [email protected].
If you find them — treat that machine or CI runner as compromised. Rotate all your secrets right away.
2. Lock your dependencies
Use exact versions. Always commit your lockfile and run npm ci in CI/CD. Avoid ^ or latest in production